VirtualBox 6.0.4_SUSE r128164 - Win 7 "the BIOS in this system is not fully ACPI compliant"

English Virtualization
21

On 4/27/19 3:46 PM, iDominic42 wrote:
>
> and if I did do something wrong, I was doing that in about the 20mins
> whilst drinking a cup of tea in the morning before heading off to work
>
> So I got SSL errors trying to download a repo file, curled it, and still
> got a javascript filled page telling me unauthorised, replaced the https
> with http and curled it,
>
> copied it to a .repo file in /etc/zypp/repos.d
>
> tried a sudo zypper ref
>
> and then modded the repo file so it gave a me an answer.
>
> A quick hack or two, but one that added a working repo
>
>

What I do for a trouble free installation of TW from Oracle. I created a
local dir repo on my system where I download the new versions of TW. Not
only are the rpm files placed there but also the needed extension files
for ease of access. (I actually have versions of TW going back to the
3.x versions.) I currently use the rpm provided for openSUSE 15.0. After
installing the latest version of TW I start the TW management program
and install the extension pac. The only recent problem was with having
to also install the libvpx library which I found using osc.
Using this procedure I rarely have problems installing and using TW.
I hope this helps anyone having issues with the openSUSE provided
version of TW.

–
Ken
unix since 1986
S.u.S.E.-openSUSE since 1998

22

On 4/28/19 10:14 AM, Ken Schneider wrote:
> On 4/27/19 3:46 PM, iDominic42 wrote:
>>
>> and if I did do something wrong, I was doing that in about the 20mins
>> whilst drinking a cup of tea in the morning before heading off to work
>>
>> So I got SSL errors trying to download a repo file, curled it, and still
>> got a javascript filled page telling me unauthorised, replaced the https
>> with http and curled it,
>>
>> copied it to a .repo file in /etc/zypp/repos.d
>>
>> tried a sudo zypper ref
>>
>> and then modded the repo file so it gave a me an answer.
>>
>> A quick hack or two, but one that added a working repo
>>
>>

Please replace TW with VB, I use the Oracle version of VB on TW.

>
> What I do for a trouble free installation of TW from Oracle. I created a
> local dir repo on my system where I download the new versions of TW. Not
> only are the rpm files placed there but also the needed extension files
> for ease of access. (I actually have versions of TW going back to the
> 3.x versions.) I currently use the rpm provided for openSUSE 15.0. After
> installing the latest version of TW I start the TW management program
> and install the extension pac. The only recent problem was with having
> to also install the libvpx library which I found using osc.
> Using this procedure I rarely have problems installing and using TW.
> I hope this helps anyone having issues with the openSUSE provided
> version of TW.
>

–
Ken
unix since 1986
S.u.S.E.-openSUSE since 1998

23

I probably took the long way around, but I dealt with this issue by:

  • Restoring a partition saved before the 20190412 snapshot that introduced the villainous 20190405 acpica.
  • Locking **acpica, virtualbox, virtualbox-host-kmp-default, virtualbox-host-source, virtualbox-qt
    *** Zypper dup to the current 20190428 snapshot
  • as root, /sbin/vboxconfig to help Virtualbox deal with the kernel update

I hope someone posts a heads’ up when the acpica problem is fixed, so I can remove the locks. In the meantime, my Win7 VM works again.

24

Just like to confirm that the 6.0.6 TW release of VirtualBox still has this ACPI bug that affects Window 7 VMs


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

I removed my official “Oracle” repo , rebooted, disabled that repo, and installed VirtualBox from the TW repo.

And my Win7 VM will not boot as described because the “BIOS in the system is not fully ACPI compliant”

I know Larry Finger has tried to get the OpenSuse factory people to realise that there is a bug in the toolchain when building VirtualBox

It appears that they have chosen to release an update whilst still using that broken toolchain.

I will revert to the official Oracle repo, repo file as below (Now using Leap 15.0 not 42.3 a I posted earlier up this thread)

/etc/zypp/repos.d/Oracle_virtualbox.repo

[oracle_virtualbox]
name=VirtualBox for openSUSE 15.0 x86_64
enabled=1
autorefresh=1
baseurl=http://download.virtualbox.org/virtualbox/rpm/opensuse/15.0/x86_64
type=rpm-md
priority=120
gpgcheck=1
gpgkey=https://www.virtualbox.org/download/oracle_vbox.asc
keeppackages=0

and remove the TW packages

I’d rather not do this

(and to be honest, I’d rather not have to use any software that uses Windows, but if anyone can get Line6/ Yamaha / Arturia to release software for linux then fine)

(Line6 HX Stomp is my latest irritation there) (sigh)

:wink:

25

Thanks for the update on ACPI, iDominic42.

If I correctly interpret the change log at:

https://www.virtualbox.org/wiki/Changelog-6.0#v6

I shouldn’t expect the 5.1 kernel to work with my locked VB 6.0.4. When 5.1. reaches Tumbleweed, I’ll probably lock the kernel in Yast until a Win 7 compatible ACPI reaches the repositories. Sooner rather than later, I hope.

26

A heads up, to save trouble for others: I spotted a new acpica (20190509) in the announcement for snapshot 20190525 – https://lists.opensuse.org/opensuse-factory/2019-05/msg00308.html – and assumed that it would include a fix for the non-starting Windows 7 VMs problem.

Not for me. I removed all locks, zypper dup’d to virtualbox 6.0.6 and the 20190509 acpica, and pulled a blue screening Windows 7 VM on the first test. Back to VB 6.0.4. and a locked acpica go I. :\

27

hello, I am also affected by this problem… for many weeks now. I do not really understand who messed this up (the version from the oracle repo seems to work) but is there any solution in sight?