From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id B4A421FF13F for ; Wed, 14 Jan 2026 13:53:42 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0213B12194; Wed, 14 Jan 2026 13:53:44 +0100 (CET) Message-ID: Date: Wed, 14 Jan 2026 13:53:04 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Proxmox VE development discussion References: Content-Language: en-US From: Fiona Ebner In-Reply-To: X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1768395144622 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.016 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] Subject: Re: [pve-devel] [PATCH qemu-server 1/1] QemuServer.pm: add support for storing VM memory in /dev/shm X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Cc: Drew Green Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Hi, Am 19.11.25 um 10:50 PM schrieb Drew Green via pve-devel: > PVE supports the VM option "ivshmem" which creates a memory-backed file on > the host operating system in /dev/shm to allow sharing resources between > the guest and host and other guests. There is currently no support for > utilizing the Qemu feature to make the guest's system memory available via > the filesystem, which can be useful for experimentation and testing > purposes. This patch adds an additional boolean option to the existing > "ivshmem" configuration called "ram", which when set to 1 will store the > guest's memory in the same location in /dev/shm that "ivshmem" normally > would. Additional logic is added to support that option, such as adding an > additional "-machine" argument required for this and excluding the > "-device" argument normally required for traditional "ivshmem". yes, it is a rather niche use case. You can also add the machine flag and object via custom '-args' in the VM configuration. Would using that instead work for you? If yes, I'd rather postpone this, but feel free to open a feature request on the bugzilla (referring back to your patch), so we can better track interest from other users. For completeness, regarding the patch submission: please use 'git format-patch' to generate the email. And we'd also need a signed CLA and a Signed-off-by trailer to be able to accept your patch. For details, see: https://pve.proxmox.com/wiki/Developer_Documentation Best Regards, Fiona _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel