From: Daniel Kral <d.kral@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Markus Frank <m.frank@proxmox.com>
Subject: Re: [pve-devel] [PATCH cluster/guest-common/docs/qemu-server/manager v15 0/12] virtiofs
Date: Fri, 4 Apr 2025 14:22:02 +0200 [thread overview]
Message-ID: <516fc86b-5cd2-46f4-90a5-8f6e981f8063@proxmox.com> (raw)
In-Reply-To: <20250403103442.136958-1-m.frank@proxmox.com>
On 4/3/25 12:34, Markus Frank wrote:
> Virtio-fs is a shared file system that enables sharing a directory
> between host and guest VMs. It takes advantage of the locality of
> virtual machines and the hypervisor to get a higher throughput than
> the 9p remote file system protocol.
>
> build-order:
> 1. cluster
> 2. guest-common
> 3. docs
> 4. qemu-server
> 5. manager
>
> I did not get virtiofsd to run with run_command without creating
> zombie processes after stutdown. So I replaced run_command with exec
> for now. Maybe someone can find out why this happens.
>
> changes in v15:
> * removed announce-submounts option altogether and always set it for
> virtiofsd.
> * added die if both memory hotplug and virtiofs are enabled
> * added fstab entry example in the docs
> * assert_valid_map_list: only run assert_valid for the mappings on the
> current node
> * see individual patches
Gave this another look and spin with the same setup as yesterday (single
node and the three mentioned Debian/Fedora/Win11 VMs) and a 3 node test
cluster to also test the remaining parts in a cluster setting with
migration.
=== Migration tests ===
Tested that offline migration and live migration is blocked correctly,
if the resource is not available on another node, i.e. whether there is
a dir mapping on another node.
If I try to live migrate a VM from one node to another, where the target
does not have a dir mapping defined, I get the following precondition
errors in the WebGUI:
- Can't migrate VM with local resources: virtiofs
- Can't migrate running VM with mapped resources: virtiofs0, virtiofs1
- Mapped Resources (virtiofs1) not available on selected target
And on the CLI:
- can't migrate VM which uses local devices: virtiofs
If I try to migrate a VM from one node to another, where the target does
not have a dir mapping defined, I get the following precondition errors
in the WebGUI:
- Mapped Resources (virtiofs1) not available on selected target
And on the CLI:
- can't migrate to 'node2': missing mapped devices virtiofs1
=== Config tests ===
Otherwise, I did the same tests with xattr / POSIX ACLs as before and
this worked just as before. Also the existence of the dir mapping path
on the current node is asserted correctly, but in a multi-node setting
this could still be improved, see my comments inline.
Otherwise, there were some undefined variables warnings and some
warnings that could be improved, I also noted them in my comments inline.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-04-04 12:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 10:34 Markus Frank
2025-04-03 10:34 ` [pve-devel] [PATCH cluster v15 1/12] add mapping/dir.cfg for resource mapping Markus Frank
2025-04-04 13:46 ` Fiona Ebner
2025-04-03 10:34 ` [pve-devel] [PATCH guest-common v15 2/12] add dir mapping section config Markus Frank
2025-04-04 12:17 ` Daniel Kral
2025-04-03 10:34 ` [pve-devel] [PATCH docs v15 3/12] add doc section for the shared filesystem virtio-fs Markus Frank
2025-04-04 12:20 ` Daniel Kral
2025-04-03 10:34 ` [pve-devel] [PATCH qemu-server v15 4/12] control: add virtiofsd as runtime dependency for qemu-server Markus Frank
2025-04-03 10:34 ` [pve-devel] [PATCH qemu-server v15 5/7] fix #1027: virtio-fs support Markus Frank
2025-04-04 12:19 ` Daniel Kral
2025-04-03 10:34 ` [pve-devel] [PATCH qemu-server v15 6/12] migration: check_local_resources for virtiofs Markus Frank
2025-04-04 12:18 ` Daniel Kral
2025-04-03 10:34 ` [pve-devel] [PATCH qemu-server v15 7/12] disable snapshot (with RAM) and hibernate with virtio-fs devices Markus Frank
2025-04-03 10:34 ` [pve-devel] [PATCH manager v15 08/12] api: add resource map api endpoints for directories Markus Frank
2025-04-03 10:34 ` [pve-devel] [PATCH manager v15 09/12] ui: add edit window for dir mappings Markus Frank
2025-04-04 12:21 ` Daniel Kral
2025-04-03 10:34 ` [pve-devel] [PATCH manager v15 10/12] ui: add resource mapping view for directories Markus Frank
2025-04-04 12:21 ` Daniel Kral
2025-04-03 10:34 ` [pve-devel] [PATCH manager v15 11/12] ui: form: add selector for directory mappings Markus Frank
2025-04-03 10:34 ` [pve-devel] [PATCH manager v15 12/12] ui: add options to add virtio-fs to qemu config Markus Frank
2025-04-04 12:21 ` Daniel Kral
2025-04-03 11:18 ` [pve-devel] [PATCH cluster/guest-common/docs/qemu-server/manager v15 0/12] virtiofs Markus Frank
2025-04-03 14:11 ` Lukas Wagner
2025-04-04 8:27 ` Lukas Wagner
2025-04-04 15:08 ` Markus Frank
2025-04-04 12:22 ` Daniel Kral [this message]
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=516fc86b-5cd2-46f4-90a5-8f6e981f8063@proxmox.com \
--to=d.kral@proxmox.com \
--cc=m.frank@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal