Date: Thu, 19 Dec 2019 01:04:44 +0000 From: bugzilla-noreply@freebsd.org To: vbox@FreeBSD.org Subject: [Bug 234878] emulators/virtualbox-ose: Update to 6.1 Message-ID: <bug-234878-26505-0Js12KHQ2u@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234878-26505@https.bugs.freebsd.org/bugzilla/> References: <bug-234878-26505@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234878 Naram Qashat <cyberbotx@cyberbotx.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cyberbotx@cyberbotx.com --- Comment #51 from Naram Qashat <cyberbotx@cyberbotx.com> --- So, I had been trying these patches as they came about. The 6.0.x line seemed to work perfectly fine (albeit that I've never been a= ble to get audio to work in the guest, despite the host driver working on the h= ost, but this was a problem for me in the 5.x line too and I don't know when that started happening). But 6.1.0 seems to be trouble galore. I've had the following issues at one point or another: * VMs won't start (I would get a pretty generic NS_ERROR_FAILURE 0x80004005= in component SessionMachine, and while others online say it was from starting = from a snapshot, I was starting from an offline VM) * With a dual-monitor Windows 10 VM and using mouse integration, I was gett= ing an issue with the mouse cursor treating the first monitor as if it was both monitors combined (so as I moved right, the cursor position inside the VM itself was going farther right than it should've) * When I tried to change the display type (which was originally VBoxVGA) to another option, I'd either start getting those generic errors from the first point or it would start fine, but the mouse issue would persist. At one poi= nt I switched back to VBoxVGA and ran into an issue where the guest display was = some small 640x480 I think with an almost grayscale like 16-color-ish looking display. * Every time a VM shuts down, it says it aborted instead of being powered o= ff. I see the following in one of the logs: 00:00:05.595427 !!Assertion Failed!! 00:00:05.595427 Expression: <NULL> 00:00:05.595428 Location : /wrkdirs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-6.1.0/src/VBox/= VMM/VMMR3/MMHeap.cpp(667) void MMR3HeapFree(void *) 00:00:05.595433 Stack : 00:00:05.595434 00000008014439a7 00:00:05.595434=20 00:00:05.595453 Invalid heap header! pv=3D0000000818c3be20, size=3D0x2d6e49= 2d * Some of the above issues ended up with the processes of VBoxNetDHCP, VBox= SVC and VBoxXPCOMIPCD still persisting even though no VMs were running (and not even the manager GUI was running). I didn't attempt to stop them because I didn't want to possibly cause a kernel panic. * After a forced reboot caused by a kernel panic (that wasn't caused by VirtualBox), my Windows 10 VM no longer seems to want to do mouse integrati= on (regardless of if the Guest Additions were installed or not) and wouldn't s= tart if I had my guest audio driver set to Intel HD, getting the following in the log: 00:00:28.109998 !!Assertion Failed!! 00:00:28.109998 Expression: RT_SUCCESS_NP(rc2) 00:00:28.109999 Location : /wrkdirs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-6.1.0/src/VBox/= Devices/Audio/DevHDA.cpp(1348) VBOXSTRICTRC hdaRegWriteSDCTL(PPDMDEVINS, PHDASTATE, uint32_t, uint32_t) 00:00:28.110020 Stack : 00:00:28.110021 00000008014439a7 00:00:28.110022=20 00:00:28.110052 VERR_NOT_SUPPORTED (-37) - Not supported. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234878-26505-0Js12KHQ2u>