[Call for Testers] VirtualBox 4.3.0

[Mario Lobo]

On Sat, 02 Nov 2013 18:38:05 +0600
Гуляев Гоша <gosha-necr at yandex.ru> wrote:

>    01.11.2013, 14:45, "Volodymyr Kostyrko" <c.kworr at gmail.com>:
> 
>      31.10.2013 21:06, Гуляев Гоша wrote:
> 
>      Thanks! Adding #include <stdlib.h> solve problem with building.
>      But VBoxManage "any action" gets error (Exact same error with
>      VirtualBox
>      from ports on 10-STABLE, PR: 183085 ):
>      VBoxManage: error: Failed to create the VirtualBox object!
>      VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation
>      aborted
>      (extended info not available)
>      VBoxManage: error: Most likely, the VirtualBox COM server is not
>      running
>      or failed to start.
>      uname -a: FreeBSD BSD-VBOX 10.0-BETA2 FreeBSD 10.0-BETA2 #0: Thu
> Oct 31
>      23:11:53 MSK 2013 mike at BSD-VBOX:/usr/obj/usr/src/sys/BSDSERV
> amd64 I have a headless machine. My user is in vboxusers group, and
>      vboxdrv,
>      vboxnetadp and vboxflt loaded and dbus started.
>      Volodymyr, can you tell please, are your VirtualBox instance
> works on
>      10-STABLE? And how it working (For example is VBoxManage list
>      ostypes -
>      working?). Maybe you say that it works only with existed machines
>      and
>      not works on any other actions?
> 
>      Weird. VirtualBox is working for me on 10-STABLE (BETA2 right
> now I suppose). `VBoxManage list ostypes` yields a lengthy list of
>      systems.
>      Maybe this is something about build options? I'm building it only
>      with
>      DBUS GUESTADDITIONS NLS QT4 X11. Can you share your list of build
>      options?
>      --
>      Sphinx of black quartz, judge my vow.
> 
>    I have only 3 enabled options: DBUS, UDPTUNNEL, VNC
> 
>    And server has no X installed (Identical configuration perfectly
> works on other servers with 8 and 9-STABLE). On 10-STABLE VirtualBox
> from ports and that test 4.3.0 port gets that error.
> 
>    --------------------------------------------
>    С уважением, Гуляев Гоша.
> _______________________________________________
> freebsd-emulation at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> To unsubscribe, send any mail to
> "freebsd-emulation-unsubscribe at freebsd.org"

Hi guys;

I keep getting these errors when trying to compile. The error shows up
just the same in a 4.3.0 compile attempt. I patched the port to 4.3.2
in the hopes that this would go away but it didn't. Both compile fine
up to this point.


kBuild: Compiling VBoxVMM - /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.2/src/VBox/VMM/VMMR3/PATMA.asm 

/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.2/include/iprt/x86extra.mac:143:
error: (AssertCompileSizeML:2) cannot reference symbol `X86TSS16_size'
in preprocessor 

/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.2/include/iprt/x86extra.mac:143:
warning: (AssertCompileSizeML:5) X86TSS16 is 1 bytes instead of
44 

/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.2/include/iprt/x86extra.mac:206:
error: (AssertCompileSizeML:2) cannot reference symbol `X86TSS64_size'
in preprocessor 

/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.2/include/iprt/x86extra.mac:206:
warning: (AssertCompileSizeML:5) X86TSS64 is 1 bytes instead of 136

kmk: ***
[/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.2/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.o]
Error 1


System: FreeBSD Papi 8.3-STABLE FreeBSD 8.3-STABLE #0 r243751M: Fri Jan
11 19:30:42 BRT 2013     root at Papi:/usr/obj/usr/src/sys/LOBO  amd64


VBox 4.2.18 compiles and runs fine!


Any hints on how to get past this?

Thanks,

-- 
Mario Lobo
http://www.mallavoodoo.com.br
FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] (99% winblows FREE)