virtualbox.org

I'm looking for clues why this is happening. Same thing happens on Windows 7 64-bit guest. Host system (Mint Linux 17.2) will randomly lock up and must be power-cycled. 32-bit guest (Win-XP) will run all day, every day. Here's the "showvminfo" from the Win10 guest:

Code: Select all

$ VBoxManage showvminfo win10-user --details
Name:            win10-user
Groups:          /
Guest OS:        Windows 10 (64-bit)
UUID:            b291abaf-db90-4ef5-b1b9-5c4147be1698
Config file:     /home/user/VirtualBox VMs/win10-user/win10-user.vbox
Snapshot folder: /home/user/VirtualBox VMs/win10-user/Snapshots
Log folder:      /home/user/VirtualBox VMs/win10-user/Logs
Hardware UUID:   b291abaf-db90-4ef5-b1b9-5c4147be1698
Memory size:     3096MB
Page Fusion:     off
VRAM size:       32MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             off
Long Mode:       on
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): Not Assigned
ACPI:            on
IOAPIC:          on
Time offset:     0ms
RTC:             local time
Hardw. virt.ext: on
Nested Paging:   off
Large Pages:     off
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Legacy
State:           powered off (since 2015-12-28T19:42:39.000000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Default Frontend: 
Storage Controller Name (0):            IDE
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):            SATA
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      2
Storage Controller Bootable (1):        on
IDE (1, 0): Empty
SATA (0, 0): /home/user/VirtualBox VMs/win10-user/win10-user.vdi (UUID: 75d2a502-326d-4ad6-94a8-a9d761e399e7)
NIC 1:           MAC: 08002739AD2D, Attachment: Bridged Interface 'eth0', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
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
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: PulseAudio, Controller: HDA, Codec: STAC9221)
Clipboard Mode:  disabled
Drag and drop Mode: disabled
VRDE:            disabled
USB:             enabled
EHCI:            enabled
XHCI:            disabled

USB Device Filters:

<none>

Bandwidth groups:  <none>

Shared folders:  

Name: 'user', Host path: '/home/user' (machine mapping), writable

Video capturing:    not active
Capture screens:    0
Capture file:       /home/user/VirtualBox VMs/win10-user/win10-user.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25

Guest:

Configured memory balloon size:      0 MB


$

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

log attached...

Code: Select all

00:00:15.542108 VMMDev: Guest Log: VBoxMP::DriverEntry: 3D is NOT supported by the host, falling back to display-only mode..

The only host issue I see is above, but I don't believe this is causing your issue. Since it might you should see if you can fix it and try again. Other than that it probably is a guest issue and to make this more visible to Windows experts I am going to move this to Windows guests.

Hmm. I'm not sure how a guest issue could make the host lock up. Hog network or I/O bandwidth yes, lock up no.

The only thing I can think of is a host hardware issue, such as bad disk sectors or RAM.

Sorry I didn't make it clear. The guest side of the server code is what I meant, especially considering the difficulties of Windows-10 in VirtualBox.

I did think of one more thing though and that is a bios update of the host might be in order. Before you say "what?" it really does make a difference in today’s PCs when you run into strange issues.

FWIW, I don't have any suggestions, I just wanted to say I've had a Windows 10 guest running for months and months on Linux Mint 17.2 (now 17.3) without a problem and it's certainly not locked up the host.

It's not just Win-10 guest that causes the lockup. Win7-x64 guest does it as well. I have attached Win7 log as well.

Host is an HP P7-1414 desktop running an A8 processor. I'll check for a BIOS update...

Created a CentOS 7 x64 guest and it locked up as well. log file attached.

virtualbox.org

Windows 10 64-bit guest causes host to lock up

Windows 10 64-bit guest causes host to lock up

Re: Windows 10 64-bit guest causes host to lock up

Re: Windows 10 64-bit guest causes host to lock up

Re: Windows 10 64-bit guest causes host to lock up

Re: Windows 10 64-bit guest causes host to lock up

Re: Windows 10 64-bit guest causes host to lock up

Re: Windows 10 64-bit guest causes host to lock up

Re: Windows 10 64-bit guest causes host to lock up

Re: Windows 10 64-bit guest causes host to lock up

Re: Windows 10 64-bit guest causes host to lock up