TLDR; Thanks that fixed it!
I made the changes you suggested (in this case disabling QEMU) because you are correct QEMU-guest-agent has STILL not been implemented for OPNSense / FreeBSD - I believe due to the consideration that a reboot / shutdown command can be sent to the server without...
Thanks to frenchfries, I was able to resolve my quest via passthrough by adding something like this to the config for the VM:
virtio1: /dev/disk/by-id/ata-ST3400832NS_<uuid>-part1,backup=0,size=381552M
That said, looking at it 2 years later there doesn't seem to be a way to mark this as resolved?
I am running Proxmox 6.3-3 and have a OPNSense (FreeBSD) firewall running. I noticed several versions ago that ACPI commands were being ignored by several of my VMs.
Recently, I found some spare time and discovered that while I had enabled QEMU Guest Agent in Proxmox at VM creation acpi wasn't...
I have 5 Hard Drives in my "server." There is no other storage anywhere on my network, especially not a CIFS/NFS/SAN box, all the other computers on the network are Windows 10 workstations.
In the Server there are:
1 drive (240GB SSD) = Proxmox Boot (LVM & lvm-thin) volume
4 drives are "data"...
I have been googling and have yet to find a solution to this issue.
History: I am running Proxmox 5.2-1 and am migrating from XenServer Community due to the removal of dynamic memory allocation. In XenServer my NextCloud VM booted from one drive and then saved all the data on a 4 drive raid...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.