VirtualBox 3.1.8 on current (after ACPICA 20100428 merged)

Beat Gaetzi beat at FreeBSD.org
Mon May 17 18:59:00 UTC 2010


Hi,

Daichi GOTO wrote:
> Hi VirtualBox guys, thanks for your great work of VirtualBox!
> 
> I am trying VirtualBox 3.1.8 port on current, and found
> that one needs follow patch to build:
> 
> -------------------------------------------------------------------------
> --- src/VBox/Devices/PC/vbox.dsl.orig    2010-03-25 15:56:03.000000000
> -0400
> +++ src/VBox/Devices/PC/vbox.dsl    2010-04-29 19:14:38.000000000 -0400
> @@ -1064,7 +1064,7 @@
>                               // (all of low memory space)
>                       ResourceProducer,        // bit 0 of general flags
> is 0
>                       PosDecode,               // positive Decode
> -                     MinFixed,                // Range is fixed
> +                     MinNotFixed,             // Range is not fixed
>                       MaxFixed,                // Range is fixed
>                       Cacheable,
>                       ReadWrite,
> @@ -1073,7 +1073,7 @@
> 
>                       0xffdfffff,              // Max = 4GB - 2MB
>                       0x00000000,              // Translation
> -                     0xdfdfffff,              // Range Length (calculated
> +                     0x00000000,              // Range Length (calculated
>                                                // dynamically)
>                       ,                        // Optional field left blank
>                       ,                        // Optional field left blank
> -------------------------------------------------------------------------
> 
> It is the same situation as VirtualBox 3.2.0-dev on current after
> ACPICA 20100428 merged.  How about to add above patch to
> VirtualBox 3.1.8 port?

Thanks for your reminder. I have added the patch to the 3.2.0 port in
our development repository and forgot to add it to the 3.1.8 port.
Unfortunately Virtualbox panics on system after r207577 (3rd May) at the
moment. Once we have a fix for this problem we will commit the given
patch to the port too.

Thanks,
Beat


More information about the freebsd-emulation mailing list