Bug 1132941

Confirmed 

See https://bugzilla.opensuse.org/show_bug.cgi?id=113295 which I probably wrote whilst this report was being posted

The arch tracker bug report says it is a problem because of this:

" iasl from acpica 20190329-1 miscompiles ACPI tables of VirtualBox. Building with older acpica fixes the issue"

"https://bugs.archlinux.org/task/62381#comment178770"

*** Bug 1132951 has been marked as a duplicate of this bug. ***

(In reply to Dominic Mason from comment #1)

> See https://bugzilla.opensuse.org/show_bug.cgi?id=113295 which I probably
> wrote whilst this report was being posted


sorry, that should have been 1132951

 https://bugzilla.opensuse.org/show_bug.cgi?id=1132951

The upstream acpica project is aware of the problem (https://github.com/acpica/acpica/issues/462) and is working on the issue as of 3 days ago.

A patch to the iASL component of acpica has been published. I used it to generate a new RPM for VirtualBox. Only one of the packages is affected. To use this updated code before the revised acpica package reaches TW, stop the VB GUI and run the following commands:

wget http://lwfinger.com/download/virtualbox-6.0.6-0.x86_64.rpm
sudo zypper in --force virtualbox-6.0.6-0.x86_64.rpm

The new new package is not signed, thus ignore the warning that pops up.

Hi Larry

Thanks for sorting out a virtualbox rpm for 6.0.6

(which is what all the arch users were having this problem with)

The problem with OpenSUSE Tumbleweed is appears to have started with version 6.0.4-3.3

(I'm pretty sure 6.0.4-3.1 did not have this problem)

Will your 6.0.6 rpm work with the other TW packages which are all for 6.0.4? 

sudo zypper info virtualbox
Information for package virtualbox:
-----------------------------------
Repository     : openSUSE-Tumbleweed-Oss  
Name           : virtualbox               
Version        : 6.0.4-3.3                
Arch           : x86_64                   
Vendor         : openSUSE                 
Installed Size : 38.6 MiB                 
Installed      : Yes                      
Status         : up-to-date               
Source package : virtualbox-6.0.4-3.3.src 
Summary        : VirtualBox is an Emulator



Sorry to be a pain, I know the reference bug on Arch Linux are for 6.0.6 

So it looks like Arch is ahead on TW on VirtualBox versions, but Tumbleweed is building earlier releases with later tools.


I note that the latest version in Oracle's own VirtualBox repo is 6.0.6, too


Regards

You have s slight misunderstanding. The bug is NOT in VirtualBox, but in iASL - a BIOS compiler used to build VirtualBox.

Unfortunately, I cannot back out of v6.0.6 in order to generate a fixed version of 6.9.4; however if you add https://build.opensuse.org/package/binaries/home:lwfinger:branches:openSUSE:Factory/virtualbox/openSUSE_Factory as a new repository and update the VB packages from it, and then use the commands in Comment #5, you will get a working version. Yes, it is a bit of a pain.

I have no idea what version of iASL is being used by Oracle. Their version might work, and if might not.

I have an update. As discussed in https://build.opensuse.org/request/show/697900, the openSUSE maintainer of acpica is unwilling to accept the patch that I tested. He will be waiting for the upstream maintainer to complete all of his tests to verify the patch. Of course, that ignores the fact the the test suite completely missed the introduction of the bug! :)

Until those tests are completed, and any fixes are done upstream, booting of Windows 7 VMs will continue to fail UNLESS you follow the prescription of comment 5. If you have Win 7 VMs and the above fails, then please notify me through this bug report.

Larry: I can confirm that your solution of comments 7 & 5 works flawlessly.
As far as the maintainer aptitude, I am going to keep my opinion private. 
Thank you so much for your great help with this issue, truly appreciated.

Thanks Larry, your build of VirtualBox 6.0.6 works perfectly for me too. Since you haven't built the virtualbox-host-kmp and virtualbox-qt packages, I used the official 6.0.4 versions from Tumbleweed, and interestingly it still works with it. I also updated the extansion pack and guest additions to 6.0.6. Thank you very much again.

Thanks Larry, 
Patch is working well after fresh Tumbleweed install make today with 6.0.6.
Great work.

*** Bug 1135290 has been marked as a duplicate of this bug. ***

The GitHub repo for acpica has been updated, but I have not yet seen any action for the openSUSE maintainer of the package.

*** Bug 1135452 has been marked as a duplicate of this bug. ***

Larry,

  I see you added a new version of VB (6.0.8.477) to your OBS repository.  What I haven't been able to successfully figure out is how to add your OBS repo to zypper in such a way as to let me upgrade.  I did a 'dup' without thinking and ended up with a broken version of VB again.

To get a correct version of 6.0.8 to handle Windows 7,

wget http://lwfinger.com/download/virtualbox-6.0.8-0.x86_64.rpm
sudo zypper in --force virtualbox-6.0.8-0.x86_64.rpm

The update for acpica is now in hardware/acpica, but not yet in openSUSE:Factory/acpica. If all goes well, it should be in Tumbleweed fairly soon. Leap 15.1 has an older version that does not contain the bug.

FWIW:  After seeing a new package date for acpica in today's 20190525 snapshot, I removed locks for acpica and virtualbox and zypper dup'd to the new (20190509) acpica and Virtualbox 6.0.6.

Same Windows 7 blue screen, unfortunately.

(In reply to T Adams from comment #18)
> FWIW:  After seeing a new package date for acpica in today's 20190525
> snapshot, I removed locks for acpica and virtualbox and zypper dup'd to the
> new (20190509) acpica and Virtualbox 6.0.6.
> 
> Same Windows 7 blue screen, unfortunately.

The new version of acpica fixes the problem; however, virtualbox was not rebuilt. Thus you will need to continue to apply the RPM from lwfinger.com. Once VB 6.0.8 reaches TW, this sorry mess should be fixed.

> The new version of acpica fixes the problem; however, virtualbox was not
> rebuilt. Thus you will need to continue to apply the RPM from lwfinger.com.
> Once VB 6.0.8 reaches TW, this sorry mess should be fixed.

Ah ha!  That explains it.  Thanks, Larry.

This one is fixed. However, virtualbox-host-kmp-default is built for an incorrect kernel version now, but it can be fixed by compiling the kernel modules from the package virtualbox-host-source. Thank you Larry for the interim solution.

(In reply to Tamás Németh from comment #21)
> This one is fixed. However, virtualbox-host-kmp-default is built for an
> incorrect kernel version now, but it can be fixed by compiling the kernel
> modules from the package virtualbox-host-source. Thank you Larry for the
> interim solution.

I just did a zypper dup to Tumbleweed snapshot 20190604. The correct kernel modules were included. I'm not sure what happened to you, but it should be a one-off problem.

(In reply to Larry Finger from comment #22)
> (In reply to Tamás Németh from comment #21)
> > This one is fixed. However, virtualbox-host-kmp-default is built for an
> > incorrect kernel version now, but it can be fixed by compiling the kernel
> > modules from the package virtualbox-host-source. Thank you Larry for the
> > interim solution.
> 
> I just did a zypper dup to Tumbleweed snapshot 20190604. The correct kernel
> modules were included. I'm not sure what happened to you, but it should be a
> one-off problem.

OK, a further update solved the problem. Before this very last update virtualbox-host-kmp-default was built for kernel 5.1.4, but the latest on is for the current 5.1.5.