VirtualBox

Opened 8 years ago

Closed 4 years ago

#15911 closed defect (fixed)

Windows 7 Guest freezes on Windows 10 Host

Reported by: mtcrc Owned by:
Component: virtual disk Version: VirtualBox 5.1.4
Keywords: ahci error Cc:
Guest type: Windows Host type: Windows

Description

After a short time after the guest is started some errors appear inside the Windows System log of the host (see attached event log picture). This error repeats every second and disappears after virtualbox is closed. A little bit later (about 10 Minutes) the guest crashes and freezes (the messagebox I also added to the picture).

vbox.log is also added

It seems it the same error, which prevents me from upgrading another system from 5.0.26 to 5.1.x with Windows Server 2008r2 OS as an host system. After upgrading virtualbox the guest complete freezes on start up after some seconds.

Both systems uses a similar hardware configuration (AMD Phenom X4 with AM790GX chipset).

Attachments (2)

vbox-Error.png (35.7 KB ) - added by mtcrc 8 years ago.
Messagebox and Eventlog entry
PLV001-2016-09-08-18-05-12.log (321.3 KB ) - added by mtcrc 8 years ago.
vbox.log

Download all attachments as: .zip

Change History (6)

by mtcrc, 8 years ago

Attachment: vbox-Error.png added

Messagebox and Eventlog entry

by mtcrc, 8 years ago

vbox.log

comment:1 by mtcrc, 8 years ago

With Version 5.1.6 a little bit changed. The entries inside the eventlog of the host still persist. But the client don't freeze. There also still a lot of log entries inside the vbox.log:

08:08:52.353871 AHCI#0P0: Write at offset 204660736 (131072 bytes left) returned rc=VERR_UNRESOLVED_ERROR
08:08:52.355854 AHCI#0P0: Write at offset 205447168 (131072 bytes left) returned rc=VERR_UNRESOLVED_ERROR
08:08:52.356549 AHCI#0: Port 0 reset
08:08:52.357832 AHCI#0P0: Canceled write at offset 205578240 (131072 bytes left) returned rc=VERR_UNRESOLVED_ERROR
08:08:52.362915 AHCI#0P0: Write at offset 205053952 (131072 bytes left) returned rc=VERR_UNRESOLVED_ERROR
08:08:52.370738 AHCI#0P0: Write at offset 204791808 (131072 bytes left) returned rc=VERR_UNRESOLVED_ERROR
08:08:52.370985 AHCI#0: Port 0 reset
08:08:52.371625 AHCI#0P0: Canceled write at offset 76643618816 (4096 bytes left) returned rc=VINF_SUCCESS
08:08:52.376853 AHCI#0P0: Write at offset 204791808 (131072 bytes left) returned rc=VERR_UNRESOLVED_ERROR
08:08:52.499554 AHCI#0P0: Write at offset 204791808 (131072 bytes left) returned rc=VERR_UNRESOLVED_ERROR
08:08:52.500041 AHCI#0: Port 0 reset
08:08:52.500074 AHCI#0P0: Canceled write at offset 18191314944 (131072 bytes left) returned rc=VINF_SUCCESS
08:08:52.504337 AHCI#0P0: Write at offset 205709312 (131072 bytes left) returned rc=VERR_UNRESOLVED_ERROR
08:08:52.506648 AHCI#0P0: Write at offset 205840384 (131072 bytes left) returned rc=VERR_UNRESOLVED_ERROR

Sometimes the Guest reboots showing a BSOD with an errorcode 0x0000007a KERNEL_DATA_INPAGE_ERROR.

The guest logs also inside its system eventlog atapi errors. (EventID 11) source atapi

Last edited 8 years ago by Frank Mehnert (previous) (diff)

comment:2 by mtcrc, 8 years ago

Additional info: If the guest uses the LSI-SCSI Controller all errors disappear. The error is caused by the ahci implementation.

comment:3 by mtcrc, 7 years ago

could be closed - error is fixed

comment:4 by aeichner, 4 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use