| Description |
The sound driver in Win2K Virtual Machines stop randomly at certain points. (I'm running a Win2K Pro RTM Virtual Machine.)
Example: I open up Control Panel and the Speech window, click the Microsoft Speech Synthesis Engine, press the Pronunciation button and enter anything in the "Please type in the word you want to modify" text box to edit the pronunciation. The sound then stops itself.
Another example: I shut down the computer by opening the Start Menu and then selecting Shut Down to bring up the Shut Down Windows dialog. I then selected "Shut down", clicked OK and nothing happens. I have to shut down the virtual machine with safe mode.
I attached the VBox.log file for this virtual machine.
|
| Description |
After an upgrade to 5.0.20, my Win 10 VM running on a Linux Mint host does not start anymore.
Please see the attached logs that finishes with:
00:00:03.402036 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
00:00:03.760651 Display::handleDisplayResize: uScreenId=0 pvVRAM=00007f4b50000000 w=1024 h=768 bpp=24 cbLine=0xC00 flags=0x1
00:00:03.760732 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1024x768, Sending to async-handler
00:00:03.760830 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1024x768
00:00:03.760845 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1024x768
00:00:03.760857 GUI: UIFrameBufferPrivate::performResize: Size=1024x768, Directly using source bitmap content
00:00:04.780429 RTC: period=0x200 (512) 64 Hz
00:00:05.962578 AHCI#0: Reset the HBA
00:00:06.042372 VMMDev: Guest Log: VBoxGuest: Windows version 10.0, build 14328
00:00:06.048451 VMMDev: Guest Additions information report: Version 5.0.18 r106667 '5.0.18'
00:00:06.048500 VMMDev: Guest Additions information report: Interface = 0x00010004 osType = 0x0003B100 (Windows 10, 64-bit)
00:00:06.048583 VMMDev: Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:06.048690 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:06.048707 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:06.048780 VMMDev: Guest reported fixed hypervisor window at 000d6800000 LB 0x2400000 (rc=VINF_SUCCESS)
00:00:06.048796 VMMDev: vmmDevReqHandler_HeartbeatConfigure: No change (fHeartbeatActive=false).
00:00:06.048839 VMMDev: Heartbeat flatline timer set to trigger after 4 000 000 000 ns
00:00:06.048948 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:00:06.048969 GUI: UIMachineLogicFullscreen: Additions-state actual-change event, rebuild multi-screen layout
00:00:06.050540 GUI: UIMultiScreenLayout::update: GUI/AutomountGuestScreens is disabled
00:00:06.050622 GUI: UIMachineViewFullscreen::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:00:06.050631 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:00:06.194383 AIOMgr: Flush failed with VERR_INVALID_PARAMETER, disabling async flushes
00:00:10.296452 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:00:27.336362 VMMDev: GuestHeartBeat: Guest is alive (gone 21 144 441 512 ns)
00:00:31.875673 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:01:09.613749 TM: Giving up catch-up attempt at a 60 680 384 414 ns lag; new total: 60 680 384 414 ns
00:01:12.085788 AsyncCompletion: Task 0x007f4b9400df40 completed after 12 seconds
Note that the guest additions is 5.0.18 in the log but I have upgraded to 5.0.20 on the host (it is not installed on the guest as I cannot start it)
|
| Description |
Since Friday morning, my VirtualBox VMs start up and fail immediately with a "Kernel driver not installed (rc=-1908)" error.
I note that the error message stated to run "/sbin/rcvboxdrv setup", but "/sbin/rcvboxdrv" does not exist.
Note that I filed most of the details of this problem at https://forums.virtualbox.org/viewtopic.php?f=7&t=77506 .
I think this problem was caused when I attempted a "yum update" on Friday. I noticed a VirtualBox update come through, but around the same time I also had a crash of my laptop (which seemed to also coincide with a hardware failure on my WIfi adapter).
|