From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Friedrich Weber <f.weber@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs 1/2] pci passthrough: mention incompatibility with ballooning
Date: Tue, 14 Nov 2023 09:30:14 +0100 [thread overview]
Message-ID: <39993056-a0d8-418b-8abd-71df1b86be99@proxmox.com> (raw)
In-Reply-To: <20231113170916.184994-2-f.weber@proxmox.com>
Am 13.11.23 um 18:09 schrieb Friedrich Weber:
>
> +xref:qm_ballooning[Automatic memory allocation (ballooning)] is not possible
> +when using PCI(e) passthrough. As the PCI device may use DMA (Direct Memory
> +Access), QEMU needs to map the complete guest memory on VM startup. Hence, the
> +QEMU process will use at least the (maximum) configured amount of VM memory and
> +setting a minimum amount does not have any effect. When using PCI(e)
> +passthrough, it is recommended to set memory and minimum memory to the same
> +amount and keep the balloning device enabled. However, keep in mind that the
typo: s/balloning/ballooning/
Is there any advantage to keeping the ballooning device enabled?
> +memory consumption reported in the GUI for the VM may be much lower than the
> +memory consumption of the QEMU process.
Maybe mention what the reported value is?
next prev parent reply other threads:[~2023-11-14 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 17:09 [pve-devel] [PATCH docs/qemu-server 0/2] Ballooning/PCI passthrough incompatibility: add warning and docs Friedrich Weber
2023-11-13 17:09 ` [pve-devel] [PATCH docs 1/2] pci passthrough: mention incompatibility with ballooning Friedrich Weber
2023-11-14 8:30 ` Fiona Ebner [this message]
2023-11-14 10:20 ` Friedrich Weber
2023-11-17 12:37 ` Friedrich Weber
2023-11-13 17:09 ` [pve-devel] [PATCH qemu-server 2/2] vm start: warn if using ballooning and PCI(e) passthrough Friedrich Weber
2023-11-14 9:13 ` Fiona Ebner
2023-11-14 10:20 ` Friedrich Weber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39993056-a0d8-418b-8abd-71df1b86be99@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=f.weber@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.