Yeah, the Guide is not so helpful in making the VirtIO choice or not, I filed this a while back: https://jira.ixsystems.com/browse/DOCS-67
Can you see if this works for you. https://www.ixsystems.com/community...orking-in-vm-ubuntu-18-04-4.83705/post-579350Will this also fix my issue of having no control over noVNC?
[...] VirtIO [...]
I have changed my VM to Virtio drivers as I too was using the default AHCI. The VM now fully boots and allows login to the terminal, but networking is broken so Plex can't connect to my network shares. How should I go about fixing the network? (For linux VMs I always select Virtio adapters)OK ...
With AHCI the hypervisor painstakingly emulates a hardware device that is not there while the guest OS drives a HW interface that is not there.
So instead of saying "please give me block N from disk X" the guest OS has to fill in HW registers (that are not there) with e.g. a block address, triggers an interrupt, all this stuff that OSes do. The hypervisor then takes this data, reconstructs what the guest OS really wanted (read block N) and carries out the request. The hypervisor then triggers a request completion interrupt to wake up the part in the guest OS kernel that is waiting on the I/O ...
It's like you and me talking but instead of a direct connection in English you give your speech to an interpreter who translates it into Mandarin, gives it to another interpreter who translates it back and finally tells me.
VirtIO is an API specifically created for hypervisor environments where the guest OS can simply say "please give me block N". Similar for networking and a couple of other devices.
Long story short: if you run VMs you almost always want "paravirtualization" if available. All current open source guest OS's support it so there is really no reason not to use it. Try changing the setting and tell me how that goes ...
HTH,
Patrick
ifconfig -a
if your interface actually is that one. ;) Adjust /etc/netplan/*
accordingly.Yinz are fabuous <3
Formerly!Pittsburgh?!?
@kaamady Check your Ubuntu VMs netplan config is referencing the correct interface "enp0s5" ....
Wonderful! Thank you. Plex is back online and everyone is happy now haha.Check withifconfig -a
if your interface actually is that one. ;) Adjust/etc/netplan/*
accordingly.
Formerly!
~ ~ ~ ~ ~ ~ ~
...just an update, again, this time with not-so-great news. All the cursor-freeze symptoms are back. This is with trying an odd core count, and VirtIO. Persists across reboots. Affects all of my Ubuntu VMs.
The only thing I did was update my Ubuntu (18.04 and 19.10) test VMs through software manager. (Didn't think this would be an issue, as I selected to install updates while running the installer).
Everything looked good, then I went to bed. Did updating the VMs somehow cause this, or merely a coincidence?
I can at least vouch that switching to VirtIO has fixed all of the constant Disk-I/O failure messages and read-only errors on every Ubuntu VM.
Just to check -- VNC proper through a client, or noVNC through the browser?Same issue here - all VMs died - changing disk to VirtIO worked to allow me back in via VNC
Via noVNC through the browserJust to check -- VNC proper through a client, or noVNC through the browser?
Code:root@truecommand:~# uname -a Linux truecommand 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Absolutely no problem here - all disks VirtIO.
If I am not mistaken you can change the setting without a reinstall. Ubuntu uses UUIDs in/etc/fstab
, so the disks should be found regardless of device naming. Why would you use AHCI, anyway?
Kind regards,
Patrick