Window 10 guest on OpenSuse host: what am I missing

Discussions related to using VirtualBox on Linux hosts.
Post Reply
teo8976
Posts: 5
Joined: 7. Nov 2020, 12:11

Window 10 guest on OpenSuse host: what am I missing

Post by teo8976 »

Hi

My host machine is a 4-core intel i7 with 8GB RAM, with an almost-freshly installed OpenSUSE Tumbleweed.

I installed Virtual box with zypper (sudo zypper install virtualbox). Then I created a window10-type VM with 2 cores and 2GB of RAM.
I installed Windows 10 Home on it with a legitimate Windows installation USB stick built with the tool downloaded from Microsoft on a machine with a Windows license.

Then I installed the Guest Additions on the guest system.

What I get is a painfully slow guest system, with crackling audio, that randomly crashes all the time to a blue screen with the message: "kmode exception not handled".

There's doesn't seem to be much I can have done wrong, I mean I installed Virtual Box, created the VM, installed the guest OS and installed the guest additions.

Am I missing something, or is this just the state of the art of virtualization of Window guests on Linux hosts?
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Window 10 guest on OpenSuse host: what am I missing

Post by scottgus1 »

Start the guest from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

Is 'zypper' the normal way OpenSUSE installs things?
teo8976
Posts: 5
Joined: 7. Nov 2020, 12:11

Re: Window 10 guest on OpenSuse host: what am I missing

Post by teo8976 »

Ok so I did as you said:

- started the guest
- waited for the issue to happen (took me less than one minute browsing random websites in Edge)
- then the guest suddenly rebooted, with no blue screen, no error message, as if the virtual machine was reset by hitting a virtual hardware reset button
- then I shut down the guest from the guest OS, i.e. Windows' shut down button.

Since the very issue in this case was a sudden reset, and hence the whole test spanned two boots, I attach both the VBox.log and the VBox.log.1 files just in case (renamed 0.log and 1.log respectively, sorry about that)
Attachments
logs.zip
(64.95 KiB) Downloaded 22 times
teo8976
Posts: 5
Joined: 7. Nov 2020, 12:11

Re: Window 10 guest on OpenSuse host: what am I missing

Post by teo8976 »

> Is 'zypper' the normal way OpenSUSE installs things?

Yes.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Window 10 guest on OpenSuse host: what am I missing

Post by scottgus1 »

The log shows that the guest BSODed with auto reboot. The stop code was 1E:
00:02:08.319093 GIMHv: BugCheck 1e {ffffffff80000002, fffff803694d8343, ffff98057d70213c, 7010008004002001}
00:02:08.319094 KMODE_EXCEPTION_NOT_HANDLED
00:02:08.319094 P1: ffffffff80000002 - exception code - STATUS_DATATYPE_MISALIGNMENT
00:02:08.319094 P2: fffff803694d8343 - EIP/RIP
00:02:08.319094 P3: ffff98057d70213c - Xcpt param #0
00:02:08.319095 P4: 7010008004002001 - Xcpt param #1
You're using OpenSUSE's fork of Virtualbox:
00:00:01.068331 VirtualBox VM 6.1.14_SUSE r140239 linux.amd64 (no date no time) release log
I don't see anything egregiously wrong in the log. Try the official version from https://www.virtualbox.org/wiki/Linux_Downloads
teo8976
Posts: 5
Joined: 7. Nov 2020, 12:11

Re: Window 10 guest on OpenSuse host: what am I missing

Post by teo8976 »

Issue still exists on 6.1.18.
klaus
Oracle Corporation
Posts: 1115
Joined: 10. May 2007, 14:57

Re: Window 10 guest on OpenSuse host: what am I missing

Post by klaus »

Workaround (and later hopefully information about the fix) in https://www.virtualbox.org/ticket/20180
Post Reply