My usually stable Windows 10 (1607 build 14393.2189) hosted under Mojave 10.14.4 has been weirdly refusing to shut down without aborting. I believe this might be related to 6.0.8 causing the guest to not recognize a device connected to my MacBook Pro (see attached screenshot). The card reader referred to in the error message is built in to a USB port extender. Yes, I resolved the issue by removing the offending device, restarting the VM and then shutting it down - it did just fine without the device. But this is probably something that should be addressed properly in a future release.
Log also attached.
Cindy Harris
Pittsburgh, PA
Win 10 guest aborting on shutdown under VirtualBox 6.0.8
-
- Posts: 16
- Joined: 23. Aug 2010, 21:32
- Primary OS: Mac OS X other
- VBox Version: OSE Debian
- Guest OSses: Win 10
Win 10 guest aborting on shutdown under VirtualBox 6.0.8
- Attachments
-
- Screenshot of error message on startup of VM
- VirtualBox VMScreenSnapz00.jpg (23.42 KiB) Viewed 2095 times
-
- Windows 10-2019-06-07-13-22-24.log.zip
- VirtualBox log after aborted VM shutdown
- (28.86 KiB) Downloaded 20 times
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Win 10 guest aborting on shutdown under VirtualBox 6.0.8
cah329a wrote:My usually stable Windows 10 (1607 build 14393.2189)
Can you explain the "WinXP-2 Backup-disk1.vmdk" part? Both the XP and the VMDK parts...00:00:01.622098 Guest OS type: 'Windows10' ... 00:00:01.635224 File system of '/Users/cah/VirtualBox VMs/Windows 10/WinXP-2 Backup-disk1.vmdk' is apfs
Failed to attach the USB device Generic USB3.0 Card Reader [1538]...
You have a USB3 device on a guess that has a USB2 controller. Since Win10 has native support for USB3, I suggest that you switch the USB controller to the 3.0 version (xHCI).00:00:01.676320 [/Devices/usb-ehci/] (level 2)
That's interesting... According to my troubleshooting guide you're getting this because:00:00:02.029129 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to create a proxy device for the USB device. (Error: VERR_PDM_NO_USB_PORTS)}, preserve=false aResultDetail=-2861
... which I believe will be solved once you change the USB controller to xHCI.VERR_PDM_NO_USB_PORTS
- You are trying to use a USB3 device with a guest that does not support USB3 (see the "Guest support" section), or you haven't enabled the USB3 option in the VM settings.
Can you post the output of the command:
VBoxManage showvminfo "Windows 10"
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
- Posts: 16
- Joined: 23. Aug 2010, 21:32
- Primary OS: Mac OS X other
- VBox Version: OSE Debian
- Guest OSses: Win 10
Re: Win 10 guest aborting on shutdown under VirtualBox 6.0.8
That's easy. It's just a name that I never got around to updating as I migrated from WinXP to Win7 to Win10. Nothing more to it than that.socratis wrote: 00:00:01.622098 Guest OS type: 'Windows10'
...
00:00:01.635224 File system of '/Users/cah/VirtualBox VMs/Windows 10/WinXP-2 Backup-disk1.vmdk' is apfs
Can you explain the "WinXP-2 Backup-disk1.vmdk" part? Both the XP and the VMDK parts...
Yep, that was it. Hadn't thought about the fact that I recently migrated my physical hardware also. The old system had USB 2.0, this one has 3.0. Once I fixed the USB setting the message went away. And so did the shutdown problem.socratis wrote:VERR_PDM_NO_USB_PORTS
You are trying to use a USB3 device with a guest that does not support USB3 (see the "Guest support" section), or you haven't enabled the USB3 option in the VM settings.
... which I believe will be solved once you change the USB controller to xHCI.
I can, but now that I've changed the USB setting not sure it will be very interesting. Here it is:socratis wrote:Can you post the output of the command:
VBoxManage showvminfo "Windows 10"
Thanks for the help.Code: Select all
Name: Windows 10 Groups: / Guest OS: Windows 10 (32-bit) UUID: 73c329c5-b3b7-485c-949e-3430d9fbfc5a Config file: /Users/cah/VirtualBox VMs/Windows 10/Windows 10.vbox Snapshot folder: /Users/cah/VirtualBox VMs/Windows 10/{2281d1b3-9275-4c5d-ba0d-aeda697e704a} Log folder: /Users/cah/VirtualBox VMs/Windows 10/Logs Hardware UUID: 73c329c5-b3b7-485c-949e-3430d9fbfc5a Memory size 6834MB Page Fusion: disabled VRAM size: 80MB CPU exec cap: 100% HPET: disabled CPUProfile: host Chipset: piix3 Firmware: BIOS Number of CPUs: 1 PAE: enabled Long Mode: disabled Triple Fault Reset: disabled APIC: enabled X2APIC: disabled Nested VT-x/AMD-V: disabled CPUID Portability Level: 0 CPUID overrides: None Boot menu mode: message and menu Boot Device 1: Floppy Boot Device 2: DVD Boot Device 3: HardDisk Boot Device 4: Network ACPI: enabled IOAPIC: enabled BIOS APIC mode: APIC Time offset: 0ms RTC: local time Hardw. virt.ext: enabled Nested Paging: enabled Large Pages: disabled VT-x VPID: disabled VT-x unr. exec.: enabled Paravirt. Provider: Legacy Effective Paravirt. Prov.: None State: running (since 2019-06-08T00:05:26.007000000) Monitor count: 1 3D Acceleration: disabled 2D Video Acceleration: enabled Teleporter Enabled: disabled Teleporter Port: 0 Teleporter Address: Teleporter Password: Tracing Enabled: disabled Allow Tracing to Access VM: disabled Tracing Configuration: Autostart Enabled: disabled Autostart Delay: 0 Default Frontend: Storage Controller Name (0): IDE Controller Storage Controller Type (0): PIIX4 Storage Controller Instance Number (0): 0 Storage Controller Max Port Count (0): 2 Storage Controller Port Count (0): 2 Storage Controller Bootable (0): on Storage Controller Name (1): Floppy Controller Storage Controller Type (1): I82078 Storage Controller Instance Number (1): 0 Storage Controller Max Port Count (1): 1 Storage Controller Port Count (1): 1 Storage Controller Bootable (1): on IDE Controller (0, 0): /Users/cah/VirtualBox VMs/Windows 10/WinXP-2 Backup-disk1.vmdk (UUID: 80a825f7-a8e5-462f-a1e1-182b97b457db) IDE Controller (1, 0): /Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso (UUID: 842214ee-251f-4257-b918-98725055419d) Floppy Controller (0, 0): Empty NIC 1: MAC: 080027B2F3E7, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64) NIC 2: disabled NIC 3: disabled NIC 4: disabled NIC 5: disabled NIC 6: disabled NIC 7: disabled NIC 8: disabled Pointing Device: PS/2 Mouse Keyboard Device: PS/2 Keyboard UART 1: disabled UART 2: disabled UART 3: disabled UART 4: disabled LPT 1: disabled LPT 2: disabled Audio: disabled Audio playback: enabled Audio capture: enabled Clipboard Mode: Bidirectional Drag and drop Mode: Bidirectional Session name: GUI/Qt Video mode: 1264x824x32 at 0,0 enabled VRDE: disabled OHCI USB: disabled EHCI USB: disabled xHCI USB: enabled USB Device Filters: Index: 0 Active: yes Name: New Filter 1 VendorId: ProductId: Revision: Manufacturer: Product: Remote: Serial Number: Available remote USB devices: <none> Currently Attached USB Devices: UUID: 61d5d148-ae36-4748-b6be-06c9bf60491d VendorId: 0x05e3 (05E3) ProductId: 0x0749 (0749) Revision: 21.56 (2156) Manufacturer: Generic Product: USB3.0 Card Reader SerialNumber: 000000001538 Address: p=0x0749;v=0x05e3;s=0x0000017088673fb5;l=0x00140000 Bandwidth groups: <none> Shared folders: Name: 'Win7_Shared', Host path: '/Users/cah/Documents/Win7 Shared' (machine mapping), writable, auto-mount VRDE Connection: not active Clients so far: 0 Capturing: active Capture audio: not active Capture screens: 0 Capture file: /Users/cah/VirtualBox VMs/Windows 10/Windows 10.webm Capture dimensions: 1024x768 Capture rate: 512kbps Capture FPS: 25kbps Capture options: ac_enabled=false,vc_enabled=true,ac_profile=med Guest: Configured memory balloon size: 0MB OS type: Windows10 Additions run level: 3 Additions version 6.0.8 r130520 Guest Facilities: Facility "VirtualBox Base Driver": active/running (last update: 2019/06/08 00:05:31 UTC) Facility "VirtualBox System Service": active/running (last update: 2019/06/08 00:05:40 UTC) Facility "VirtualBox Desktop Integration": active/running (last update: 2019/06/08 00:06:11 UTC) Facility "Seamless Mode": active/running (last update: 2019/06/08 00:05:31 UTC) Facility "Graphics Mode": active/running (last update: 2019/06/08 00:05:31 UTC)
Cindy Harris
Pittsburgh, PA
Last edited by socratis on 8. Jun 2019, 06:34, edited 1 time in total.
Reason: Enclosed the information in [quote][code] tags for better readability
Reason: Enclosed the information in [quote][code] tags for better readability
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Win 10 guest aborting on shutdown under VirtualBox 6.0.8
Glad you got it going, marking as [Solved].
However...
Your VM has some serious issues (CPUs, RAM, USB, LargePages), but in order to have the complete picture, I need to see a complete VBox.log, from a complete VM run:
However...
Oh, you wouldn't believe!cah329a wrote:now that I've changed the USB setting not sure it will be very interesting
Your VM has some serious issues (CPUs, RAM, USB, LargePages), but in order to have the complete picture, I need to see a complete VBox.log, from a complete VM run:
- Start the VM from cold-boot (not from a paused or saved state) / login / Shutdown the VM.
- With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
- Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.