Is it expected Ubuntu 18.10 kernel panics using Hyper-V Paravirtualizatrion Interface? Ubuntu 21.10 runs slower than "Default" interface? Should I just be leaving it on "Default" even when Hyper-V is enabled? When should I change the selection here, if ever?.What is going on here and is there a fix/workaround? Some Linux VMs I've tried occasionally "hang" until I focus the VBox VM Manager window (?!?) or sometimes until I reboot the VM.Is it expected "Enable nested paging" gives me slowdown with Hyper-V enabled? Is there some other setting I should adjust to fix this setting slowing things down?.Tl dr Would appreciate if anyone can help me with the following questions: HW Virt is enabled in BIOS (like I said things were great before Hyper-V and allowing Windows to reenable it is the only change I allowed).Host Extensions and Guest Additions installed.I updated the VM to Ubuntu 21.10 and tried again and it just seems to boot really slowly now, or it hangs. Not sure if that is expected or not, I know Hyper-V traditionally didn't handle Debian very well but I don't know if it's try now or how VBox uses it. While experimenting I also noticed that if I change "Paravirtualization Interface" from "Default" to "Hyper-V", Ubuntu 18.10 will kernel panic on boot. Other times I see "soft lockup" errors which I think are for the same thing. Several times now I observed Ubuntu hanging and I focus that window, and the boot screen prints out a warning for each CPU core telling me it's "stuck". Most of the time I can bring it out of it by focusing the VirtualBox VM Manager window, which makes no sense. In a few Linux VMs (one Ubuntu, two are Linux-based I installed from an OVA, not sure which distro they're based on) I noticed the VM will hang occasionally. Things are still sluggish but at least they're usable. This option did not cause problems like this with Hyper-V disabled. The first big thing I figured out is disabling "Enable nested paging" on a VM massively speeds the VM up to almost as fast as it was with Hyper-V off. I started messing around with the guest settings. Oracle should make improving VirtualBox running with Hyper-V a focus if it is not already. As an aside, I think with all the cool features MS are throwing into Windows which need Hyper-V, it is less and less of a favorable trade off to disable all those features for VirtualBox. Unfortunately Googling didn't find me much, mostly recommendations to disable Hyper-V. But since I want to keep Hyper-V I did some digging to try and actually resolve it. So now I am back to seeing massive slowdown (and as I saw similar slowdown on Windows 10, I think it's not a Win11 issue). Previously in Win10 I had kept it disabled since it caused massive, unusable slowdpwn in VBox, even versions which claimed to run with Hyper-V enabled. I have had no issues with Windows 11 yet though.Īnyway with the release of Windows Subsystem for Android I was convinced to reenable Hyper-V, after keeping it off for VBox and having no issues on both Win10 and previous versions of Win11. I intend to keep this PC past the Windows 10 end of life in 2025 though so I figured I'd have to ditch Windows 10 eventually, and who knows if Win11 upgrades will be free forever. My PC does not meet the Win11 requirements (just CPU). Yes, I know VBox does not formally support it Win11 yet.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |