Same as problem here. Can't run eve-ng CE (Ubuntu 16.04 image) unless I downgrade pve kernel to 5.11.22-7. problem still not fixed in 5.15! I'm on an Intel i5, not an AMD
That's correct. May seem overly convoluted in concept, but in theory, assuming nesting worked correctly, the performance impact in practice *should* be minimal I'd imagine, particularly with AMD-V/RVI passthrough coupled with using "host" CPU type for guests? What I'm seeing is another story...
Same issue here. Ryzen CPU running Windows 10. Proxmox virtualized with VMWare Player with AMD-V/RVI checked on the guest. Nested VM's extremely slow with host setting (especially at boot stage) while putting excessive load on the actual host's CPU
I'm facing the exact same issue, except I don't have a backup of corosync.conf ...
How can I clear any records of existing certs ?
I've tried "rm /etc/pve/qdevice-net-node.p12" and "rm -r /etc/corosync/qnetd/nssdb" on all nodes including the pi, to no avail...
I am trying to dial PPPoE from a guest VM, but I don't see the concentrator when using the bridged setup?? The only thing that works for me is to passthrough a real NIC to the VM. Doesn't matter which VM OS I use (tried linux, windows, and mikrotik), or virtual NIC type (tried E1000 and Realtek)...
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.