Welcome on my profile page!

📊 Coding Stats

From: 18 June 2024 - To: 25 June 2024

No activity tracked

virtio-fs-hookscript's People

Contributors

Stargazers

Watchers

virtio-fs-hookscript's Issues

qemu is not correctly configured for first VM boot

Hi, thanks for this script, I tested it on Proxmox 8 and it works mostly fine.

However, I encountered the first issue you mentioned on https://gist.github.com/Drallas/7e4a6f6f36610eeb0bbb5d011c8ca0be :

I had an existing VM
I installed your hook, added it to the VM, then restarted it with qm stop and qm start
the VM couldn't mount the filesystem, its dmesg said virtio-fs: tag <100-foo> not found
after rebooting the VM once more, it works fine

Apparently, qemu is not passed the args: arguments on the first boot after adding the hook. After the second VM reboot, qemu has the correct arguments.

I don't know much about Proxmox hooks, but maybe Proxmox does not support modifying VM parameters in pre-start?

start failed: org.freedesktop.systemd1.NoSuchUnit: Unit [email protected] not found.

Use of uninitialized value in split at /usr/share/perl5/PVE/QemuServer/Cloudinit.pm line 104.
generating cloud-init ISO
GUEST HOOK: 100 pre-start
100 is starting, doing preparations.
Creating directory: /run/virtiofsd/
attempting to install unit virtiofsd-100-gordo...
DIRECTORY DOES EXIST!
-object memory-backend-memfd,id=mem,size=24576M,share=on -numa node,memdev=mem -chardev socket,id=char0,path=/run/virtiofsd/100-gordo.sock -device vhost-user-fs-pci,chardev=char0,tag=100-gordo
Setting VM args to generated virtiofs arguments.
vfs_args: -object memory-backend-memfd,id=mem,size=24576M,share=on -numa node,memdev=mem -chardev socket,id=char0,path=/run/virtiofsd/100-gordo.sock -device vhost-user-fs-pci,chardev=char0,tag=100-gordo
start failed: org.freedesktop.systemd1.NoSuchUnit: Unit [email protected] not found.

Recommend Projects