Re: FreeBSD Port: phpvirtualbox-4.3.2 & virtualbox-ose-4.3.36

[Bernhard Fröhlich]

Am 06.03.2016 6:56 nachm. schrieb "Mario Lobo" <l...@bsd.com.br>:
>
> On Sat, 5 Mar 2016 20:47:00 +0100
> Bernhard Fröhlich <de...@bluelife.at> wrote:
>
> > Am 05.03.2016 3:56 nachm. schrieb "Mario Lobo" <l...@bsd.com.br>:
> > >
> > > On Sat, 5 Mar 2016 12:26:42 +0100
> > > Bernhard Fröhlich <de...@bluelife.at> wrote:
> > >
> > > > Am 05.03.2016 1:01 vorm. schrieb "Michael" <ma.z...@quicknet.nl>:
> > > > >
> > > > > Hi all,
> > > > >
> > > > >
> > > > >
> > > > > I write this as I like to request a major upgrade for virtualbox
> > > > > related ports on freebsd.
> > > > >
> > > > >
> > > > >
> > > > > Currently I face problems using the current ports with php70
> > > > > port
> > > > compiled.
> > > > >
> > > > > I don't want to go back to port php56.
> > > > >
> > > > >
> > > > >
> > > > > Those problems can easy be fixed when phpvirtualbox-4.3.2 gets
> > > > > an upgrade
> > > > to
> > > > > phpvirtualbox-5.0-5
> > > > >
> > > > > as it now support php7 out of the box.
> > > > >
> > > > > Please have a look:
> > > > >
https://github.com/imoore76/phpvirtualbox/blob/develop/CHANGELOG.txt
> > > > > Changelog.
> > > > >
> > > > > But before upgrading, the new Virtualbox version must be
> > > > > upgraded also see https://www.virtualbox.org/wiki/Downloads
> > > > >
> > > > >
> > > > >
> > > > > Please can those ports be upgraded by someone for support of
> > > > > systems
> > > > running
> > > > > PHP 7?
> > > > >
> > > > >
> > > > >
> > > > > Category www
> > > > >
> > > > > 
> > > > >
> > > > >
> > > > >
> > > > > phpvirtualbox-4.3.2 needs an upgrade for support of php 7 and
> > > > > phpvirtualbox-5.0-5
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Category emulators
> > > > >
> > > > > --
> > > > >
> > > > >
> > > > >
> > > > > virtualbox-ose-4.3.36 needs an upgrade for support of php 7 and
> > > > > phpvirtualbox-5.0-5
> > > > >
> > > > >
> > > > >
> > > > > virtualbox-ose-additions-4.3.36  needs an upgrade for support of
> > > > > php 7 and phpvirtualbox-5.0-5
> > > > >
> > > > >
> > > > >
> > > > > virtualbox-ose-kmod-4.3.36  needs an upgrade for support of php
> > > > > 7 and phpvirtualbox-5.0-5
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Thank you for all the work!
> > > > >
> > > > >
> > > > >
> > > > > With best regards,
> > > > >
> > > > > Michael
> > > >
> > > > Hi Michael,
> > > >
> > > > we know that we need to update vbox to 5.x but the sad truth is
> > > > that we do not have a reasonable stable version of it. The port
> > > > builds but the kernel module doesn't work properly so instead of
> > > > breaking vbox for all people we will just stay at the last stable
> > > > version that we have. phpvirtualbox is not backwards compatible
> > > > so you have two options:
> > > >
> > > > 1) help on vbox 5.x port
> > > > 2) create a phpvirtualbox patch for php7
> > > > ___
> > > > freebsd-emulation@freebsd.org mailing list
> > > > https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> > > > To unsubscribe, send any mail to
> > > > "freebsd-emulation-unsubscr...@freebsd.org"
> > >
> > > Pardon for barging in the thread but I've been running VBox 5.0.8
> > > with 4 VMs at my work since January without any problems (so far,
> > >

Re: FreeBSD Port: phpvirtualbox-4.3.2 & virtualbox-ose-4.3.36

[Bernhard Fröhlich]

Am 06.03.2016 9:04 nachm. schrieb "Naram Qashat" <cyberb...@cyberbotx.com>:
>
> > On Sat, 5 Mar 2016 20:47:00 +0100
> > Bernhard Fröhlich <de...@bluelife.at> wrote:
> >
> >> Am 05.03.2016 3:56 nachm. schrieb "Mario Lobo" <l...@bsd.com.br>:
> >> >
> >> > On Sat, 5 Mar 2016 12:26:42 +0100
> >> > Bernhard Fröhlich <de...@bluelife.at> wrote:
> >> >
> >> > > Am 05.03.2016 1:01 vorm. schrieb "Michael" <ma.z...@quicknet.nl>:
> >> > > >
> >> > > > Hi all,
> >> > > >
> >> > > >
> >> > > >
> >> > > > I write this as I like to request a major upgrade for virtualbox
> >> > > > related ports on freebsd.
> >> > > >
> >> > > >
> >> > > >
> >> > > > Currently I face problems using the current ports with php70
> >> > > > port
> >> > > compiled.
> >> > > >
> >> > > > I don't want to go back to port php56.
> >> > > >
> >> > > >
> >> > > >
> >> > > > Those problems can easy be fixed when phpvirtualbox-4.3.2 gets
> >> > > > an upgrade
> >> > > to
> >> > > > phpvirtualbox-5.0-5
> >> > > >
> >> > > > as it now support php7 out of the box.
> >> > > >
> >> > > > Please have a look:
> >> > > >
https://github.com/imoore76/phpvirtualbox/blob/develop/CHANGELOG.txt
> >> > > > Changelog.
> >> > > >
> >> > > > But before upgrading, the new Virtualbox version must be
> >> > > > upgraded also see https://www.virtualbox.org/wiki/Downloads
> >> > > >
> >> > > >
> >> > > >
> >> > > > Please can those ports be upgraded by someone for support of
> >> > > > systems
> >> > > running
> >> > > > PHP 7?
> >> > > >
> >> > > >
> >> > > >
> >> > > > Category www
> >> > > >
> >> > > > 
> >> > > >
> >> > > >
> >> > > >
> >> > > > phpvirtualbox-4.3.2 needs an upgrade for support of php 7 and
> >> > > > phpvirtualbox-5.0-5
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > Category emulators
> >> > > >
> >> > > > --
> >> > > >
> >> > > >
> >> > > >
> >> > > > virtualbox-ose-4.3.36 needs an upgrade for support of php 7 and
> >> > > > phpvirtualbox-5.0-5
> >> > > >
> >> > > >
> >> > > >
> >> > > > virtualbox-ose-additions-4.3.36  needs an upgrade for support of
> >> > > > php 7 and phpvirtualbox-5.0-5
> >> > > >
> >> > > >
> >> > > >
> >> > > > virtualbox-ose-kmod-4.3.36  needs an upgrade for support of php
> >> > > > 7 and phpvirtualbox-5.0-5
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > Thank you for all the work!
> >> > > >
> >> > > >
> >> > > >
> >> > > > With best regards,
> >> > > >
> >> > > > Michael
> >> > >
> >> > > Hi Michael,
> >> > >
> >> > > we know that we need to update vbox to 5.x but the sad truth is
> >> > > that we do not have a reasonable stable version of it. The port
> >> > > builds but the kernel module doesn't work properly so instead of
> >> > > breaking vbox for all people we will just stay at the last stable
> >> > > version that we have. phpvirtualbox is not backwards compatible
> >> > > so you have two options:
> >> > >
> >> > > 1) help on vbox 5.x port
> >> > > 2) create a phpvirtualbox patch for php7
> >> > > ___
> >> >

Re: FreeBSD Port: phpvirtualbox-4.3.2 & virtualbox-ose-4.3.36

[Bernhard Fröhlich]

Am 05.03.2016 3:56 nachm. schrieb "Mario Lobo" <l...@bsd.com.br>:
>
> On Sat, 5 Mar 2016 12:26:42 +0100
> Bernhard Fröhlich <de...@bluelife.at> wrote:
>
> > Am 05.03.2016 1:01 vorm. schrieb "Michael" <ma.z...@quicknet.nl>:
> > >
> > > Hi all,
> > >
> > >
> > >
> > > I write this as I like to request a major upgrade for virtualbox
> > > related ports on freebsd.
> > >
> > >
> > >
> > > Currently I face problems using the current ports with php70 port
> > compiled.
> > >
> > > I don't want to go back to port php56.
> > >
> > >
> > >
> > > Those problems can easy be fixed when phpvirtualbox-4.3.2 gets an
> > > upgrade
> > to
> > > phpvirtualbox-5.0-5
> > >
> > > as it now support php7 out of the box.
> > >
> > > Please have a look:
> > > https://github.com/imoore76/phpvirtualbox/blob/develop/CHANGELOG.txt
> > > Changelog.
> > >
> > > But before upgrading, the new Virtualbox version must be upgraded
> > > also see https://www.virtualbox.org/wiki/Downloads
> > >
> > >
> > >
> > > Please can those ports be upgraded by someone for support of systems
> > running
> > > PHP 7?
> > >
> > >
> > >
> > > Category www
> > >
> > > 
> > >
> > >
> > >
> > > phpvirtualbox-4.3.2 needs an upgrade for support of php 7 and
> > > phpvirtualbox-5.0-5
> > >
> > >
> > >
> > >
> > >
> > > Category emulators
> > >
> > > --
> > >
> > >
> > >
> > > virtualbox-ose-4.3.36 needs an upgrade for support of php 7 and
> > > phpvirtualbox-5.0-5
> > >
> > >
> > >
> > > virtualbox-ose-additions-4.3.36  needs an upgrade for support of
> > > php 7 and phpvirtualbox-5.0-5
> > >
> > >
> > >
> > > virtualbox-ose-kmod-4.3.36  needs an upgrade for support of php 7
> > > and phpvirtualbox-5.0-5
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Thank you for all the work!
> > >
> > >
> > >
> > > With best regards,
> > >
> > > Michael
> >
> > Hi Michael,
> >
> > we know that we need to update vbox to 5.x but the sad truth is that
> > we do not have a reasonable stable version of it. The port builds but
> > the kernel module doesn't work properly so instead of breaking vbox
> > for all people we will just stay at the last stable version that we
> > have. phpvirtualbox is not backwards compatible so you have two
> > options:
> >
> > 1) help on vbox 5.x port
> > 2) create a phpvirtualbox patch for php7
> > ___
> > freebsd-emulation@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> > To unsubscribe, send any mail to
> > "freebsd-emulation-unsubscr...@freebsd.org"
>
> Pardon for barging in the thread but I've been running VBox 5.0.8 with
> 4 VMs at my work since January without any problems (so far, at least)
>
> [~]>pkg info | grep virtual
> vde2-2.3.2_2   User-mode virtual ethernet infrastructure
> virtualbox-ose-5.0.8   General-purpose full virtualizer
>
> [~]>ps ax
>   PID TT  STAT TIME COMMAND
>   944  -  S22:49.70 /usr/local/lib/virtualbox/VBoxXPCOMIPCD
>   952  -  S66:11.24 /usr/local/lib/virtualbox/VBoxSVC
>   934 v0- I  3065:24.90 /usr/local/lib/virtualbox/VBoxHeadless
> -startvm DBServer --vrde off 935 v0- I
> 13068:32.29 /usr/local/lib/virtualbox/VBoxHeadless -startvm WEBServer
> --vrde off 936 v0- I
> 8552:00.08 /usr/local/lib/virtualbox/VBoxHeadless -startvm EXTServer
> --vrde off
> 15004  0- S   451:17.91 /usr/local/lib/virtualbox/VBoxHeadless
> -startvm xDBServer --vrde off
>
>
> On my desktop, I'm on V 5.0.14, also without any problems.
>
> It's a fact that the VMs at work are for development but they are
> heavily used by the team.
>
> All FreeBSDs mentioned above are 10.2 STABLE.
>
> Of course, in all these cases, I adapted the port to compile and test.
>
> When you say "the kernel module doesn't work properly", what exactly do
> you mean?

Then why don't you submit them as a PR? The version that I have tested and
seen last time was an early 5.0 and that easily paniced kernels. Might be
that this has been fixed in the meantime but let's find out.

At least we could do a broader call for testers to get a better overview of
where we are.
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

Re: FreeBSD Port: phpvirtualbox-4.3.2 & virtualbox-ose-4.3.36

[Bernhard Fröhlich]

Am 05.03.2016 1:01 vorm. schrieb "Michael" :
>
> Hi all,
>
>
>
> I write this as I like to request a major upgrade for virtualbox related
> ports on freebsd.
>
>
>
> Currently I face problems using the current ports with php70 port
compiled.
>
> I don't want to go back to port php56.
>
>
>
> Those problems can easy be fixed when phpvirtualbox-4.3.2 gets an upgrade
to
> phpvirtualbox-5.0-5
>
> as it now support php7 out of the box.
>
> Please have a look:
> https://github.com/imoore76/phpvirtualbox/blob/develop/CHANGELOG.txt
> Changelog.
>
> But before upgrading, the new Virtualbox version must be upgraded also see
> https://www.virtualbox.org/wiki/Downloads
>
>
>
> Please can those ports be upgraded by someone for support of systems
running
> PHP 7?
>
>
>
> Category www
>
> 
>
>
>
> phpvirtualbox-4.3.2 needs an upgrade for support of php 7 and
> phpvirtualbox-5.0-5
>
>
>
>
>
> Category emulators
>
> --
>
>
>
> virtualbox-ose-4.3.36 needs an upgrade for support of php 7 and
> phpvirtualbox-5.0-5
>
>
>
> virtualbox-ose-additions-4.3.36  needs an upgrade for support of php 7 and
> phpvirtualbox-5.0-5
>
>
>
> virtualbox-ose-kmod-4.3.36  needs an upgrade for support of php 7 and
> phpvirtualbox-5.0-5
>
>
>
>
>
>
>
> Thank you for all the work!
>
>
>
> With best regards,
>
> Michael

Hi Michael,

we know that we need to update vbox to 5.x but the sad truth is that we do
not have a reasonable stable version of it. The port builds but the kernel
module doesn't work properly so instead of breaking vbox for all people we
will just stay at the last stable version that we have. phpvirtualbox is
not backwards compatible so you have two options:

1) help on vbox 5.x port
2) create a phpvirtualbox patch for php7
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

Re: bug fixed/workaround

[Bernhard Fröhlich]

On Sat, Dec 26, 2015 at 7:12 PM, Mike Selner <m...@tela.com> wrote:
> On Sat, Dec 26, 2015 at 11:56:38AM -0600, Mike Selner wrote:
>> Hello,
>>
>> I've experienced the same problem with networking when running a vbox guest 
>> as described here:
>>
>> https://lists.freebsd.org/pipermail/freebsd-net/2014-July/039347.html
>>
>> On both 9.3-RELEASE and 10.2-RELEASE.
>>
>> The solution given in the post above (increase net.graph.maxdata in 
>> /boot/loader.conf) did work for me.
>>
>> Can you please add this info to the vbox wiki page and the post-install 
>> pkg-message?
>
>
> Hi,
>
> I think the above will fix or at least work around the open bug report:
>
> "Network: write Failed: Cannot allocate memory"
>
> listed on the wiki page: https://wiki.freebsd.org/VirtualBox/ToDo

I've added it to the pkg-message and added a hint on the wiki page as
well. Thanks!

-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

Re: ping ?

[Bernhard Fröhlich]

Am 10.10.2015 2:13 nachm. schrieb "Kurt Jaeger" :
>
> Hi!
>
> Who is reading this ? I'm asking because of
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181324
>
> Thanks!

The patch in the PR looks reasonable to me if that is the question. I just
cannot commit it myself in the near future so it would be faster if you do
it yourself.
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

Re: VirtualBox mangles memory

[Bernhard Fröhlich]

Am 23.09.2015 4:10 vorm. schrieb "Mark Felder" :
>
>
>
> On Tue, Sep 22, 2015, at 15:57, Michael Butler wrote:
> > On 09/22/15 16:20, Adam Vande More wrote:
> > > On Tue, Sep 22, 2015 at 2:26 PM, Martin Birgmeier 
wrote:
> >
> > >> I am quite sure that the
> > >> cause is to be found there
> > >>
> > >
> > > I don't see any cause for surety in the info you have given us.  Have
you
> > > tried any basic steps like monitoring usage during these events or
running
> > > it under truss/valgrind etc to find out what is going on?
> > >
> >
> > Another data point ..
> >
> > I run it on -CURRENT and there have been a number of VM-related changes
> > of late but I don't have any problems with it.
> >
> > However, you *must* recompile (at least) the modules whenever the kernel
> > is rebuilt as they depend heavily on the underlying kernel structures,
> >
> >   imb
> >
>
> I agree. Just to be safe we really shouldn't provide packages for the
> virtualbox kmods. It's just asking for trouble.

No it's absolutely the right thing to provide them or as a package only
user on a release you would be screwed. As a STABLE or CURRENT user you
should never use any of them.
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

Re: VirtualBox mangles memory

[Bernhard Fröhlich]

To me this sounds a lot like vbox and zfs arc are fighting for resources.
What does the memory line in top look like when this problem happens?

A simple workaround would be to limit zfs arc in loader.conf if that is the
problem.

Am 22.09.2015 5:13 nachm. schrieb "Martin Birgmeier" :
>
> This did not happen when the machine was running FreeBSD 9.2 with
virtualbox-ose-4.3.20 installed. So I would not qualify this as "known
behavior".
>
> One server has 16G main memory, a VM gets 3G. The other has 8G main mem
and again 3G allocated to the VM.
>
> This is definitely a bug in how VirtualBox handles memory on FreeBSD 10.
I am pretty sure that something changed in FBSD 10 which was not properly
taken care of in VB.
>
> -- Martin
>
>
>
> On 09/21/15 22:10, Mark Felder wrote:
> >
> > On Sun, Sep 20, 2015, at 06:20, Martin Birgmeier wrote:
> >> On machines where VirtualBox is running, I get memory allocation
errors.
> >>
> >> 'dd' aborts with 'dd: stdout: Cannot allocate memory'
> >>
> >> 'zfs send' aborts with 'internal error: Cannot allocate memory'
> >>
> >> I have created https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195970
> >> to track this.
> >>
> >> Could a knowledgeable person please have a look into this?
> >>
> >> FreeBSD 10.2, VirtualBox 4.3.30
> >>
> >> -- Martin
> >>
> > I'm not an expert, but I think this is known behavior. Virtualbox
> > requires a huge contiguous chunk of memory for the VM and that's
> > probably what you're running into.
> >
> > Can you give more information about the specs of the server itself and
> > the amount of resources allocated to VMs?
> >
>
> ___
> freebsd-emulation@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
> To unsubscribe, send any mail to "
freebsd-emulation-unsubscr...@freebsd.org"
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"

Re: Query about Virtualbox version.

[Bernhard Fröhlich]

On Wed, Jul 15, 2015 at 12:33 PM, muhammedzubair sharief
mzs...@yahoo.co.in wrote:

 Dear Maintainer,


 I am using Virtualbox 4.3.28 on FreeBSD 10.1, during recent pkg upgrade it 
 showed version 4.3.30.

 [..]
 pkg upgrade
 Installed packages to be UPGRADED:
 virtualbox-ose-kmod: 4.3.28 - 4.3.30
 virtualbox-ose: 4.3.28_1 - 4.3.30

 The process will require 14 KiB more space.
 32 MiB to be downloaded.

 Proceed with this action? [y/N]:
 [..]


 However there was no stable release of 4.3.30. Is this version 5 which was 
 recently released?

 Thanks for maintaining Virtualbox on FreeBSD!

 Regards,
 Zubair

It is 4.3.30 - https://www.virtualbox.org/wiki/Changelog-4.3

-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: Query about Virtualbox version.

[Bernhard Fröhlich]

On Wed, Jul 15, 2015 at 3:20 PM, Mario Lobo l...@bsd.com.br wrote:
 2015-07-15 9:07 GMT-03:00 Bernhard Fröhlich de...@bluelife.at:

 On Wed, Jul 15, 2015 at 12:33 PM, muhammedzubair sharief
 mzs...@yahoo.co.in wrote:
 
  Dear Maintainer,
 
 
  I am using Virtualbox 4.3.28 on FreeBSD 10.1, during recent pkg upgrade
  it showed version 4.3.30.
 
  [..]
  pkg upgrade
  Installed packages to be UPGRADED:
  virtualbox-ose-kmod: 4.3.28 - 4.3.30
  virtualbox-ose: 4.3.28_1 - 4.3.30
 
  The process will require 14 KiB more space.
  32 MiB to be downloaded.
 
  Proceed with this action? [y/N]:
  [..]
 
 
  However there was no stable release of 4.3.30. Is this version 5 which
  was recently released?
 
  Thanks for maintaining Virtualbox on FreeBSD!
 
  Regards,
  Zubair

 It is 4.3.30 - https://www.virtualbox.org/wiki/Changelog-4.3

 --
 Bernhard Fröhlich


 How about VBox 5.0? Is there a time frame of when will it reach the
 ports/pkg?

I'm actually not involved in vbox work for some time now but I've seen that
jkim has some patch around for 5.0 but it required some more work I think.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: VirtualBox development repository

[Bernhard Fröhlich]

On Mon, Apr 27, 2015 at 5:05 PM, fbalku fba...@gmail.com wrote:
 Hi All,

 After redports disapperared is there any public development repository for
 emulators/virtualbox-ose*

 Thanks for the answer.

No not right now. All work happens directly in the FreeBSD portstree now.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: virtualbox additions issue

[Bernhard Fröhlich]

Am 25.09.2014 08:15 schrieb Beeblebrox zap...@berentweb.com:

 I got GuestAdditions to work with WinXP VMGuest (except some USB
problems, to
 which I had been alerted previously):

 * Make sure you have an empty virtual CD-ROM in Storage for the VMGuest,
 then start the VMGuest session.
 * Devices (menu)  Insert GuestAdditions CD Image  select path and then
the
 VBoxGuestAdditions_4.3.16.iso file.
 * GuestAdditions gets installed and now starts to work.

 Does this have to be repeated for each VM separately? If so, having a port
 for Additins does not make sense IMHO?

I'm not sure what you are trying to say but the vbox additions port is for
FreeBSD guests only. That is required because the ISO is a big blob which
does not support FreeBSD and probably never will. For Windows guests the
ISO is your only choice and for Linux you sometimes have both choices
depending on the distro.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: virtualbox-ose-additions-4.3.16 - module doesn't load, service doesn't start

[Bernhard Fröhlich]

I have just committed a fix for that. Would be great if someone can confirm
that it works or not.

Am 22.09.2014 15:18 schrieb Theodor-Iulian Ciobanu thciob...@nth.ro:

 On Thu, 18 Sep 2014 18:36:41 -0700
 mvharding at gmail.com (Mike Harding) wrote:

  A follow-up:
 
  This seems to install fine on 9.3, actually, but the 10.0 client is as
  above.
 
  The 10.0 client was created by installing a release disk, including
  /usr/src, then doing a 'freebsd-update fetch/install', reboot.
  I don't know how the source could be out of sync.
 
  Give it a try on a 64 bit client, they are cheap... the last version
  did work fine.

 I've recently encountered this same issue after upgrading vbox (both
 host app and guest tools) to 4.3.16. Guest OS is 10.0-RELEASE-p9,
 GENERIC kernel. It has been installed as 10.0R and kept up-to-date
 using freebsd-update. Host is Win7 Ent.

 RTTermRegisterCallback is defined in:
 \VirtualBox-4.3.16\src\VBox\Runtime\common\misc\term.cpp

 So rather than out-of-sync kernel  /usr/src, this seems more like a
 linker/makefile bug for this port, 'optimizing' out this function from
 the binaries. My make.conf is almost identical with the default options:

 CFLAGS=-pipe -O2 -fno-strict-aliasing -funroll-loops
 COPTFLAGS=-pipe -O2 -fno-strict-aliasing -funroll-loops

 But even with everything off I still get this error when trying to load
 vboxguest.ko:
 kernel: link_elf_obj: symbol RTTermRegisterCallback undefined
 kernel: linker_load_file: Unsupported file type

 Searching the list a bit I came upon a similar error reported in the
 past, recommending a `make clean` and recompiling the port (can't find
 it again now to link), but that didn't help. And then I came upon this,
 considering this sort of issue as a bug:

http://lists.freebsd.org/pipermail/freebsd-emulation/2013-December/011159.html

 Any help on this is greatly appreciated.


  On Thu, Sep 18, 2014 at 7:10 AM, Mike Harding mvharding at
  gmail.com wrote:
 
   I tried this on a 9.3 and 10.0 client, with all options unchecked
   (no X on these virt. servers).
  
   kmod doesn't load - it spits out
   link_elf_obj: symbol RTTermRegisterCallback undefined
   linker_load_file: Unsupported file type
  
   Attempting to start the service:
   VBoxService: error: VbgIR3Init failed with rc=VER_FILE_NOT_FOUND
  
   Let me know if I can provide details, but I got this to happen on a
   generic 9.3 and 10.0 client, with only the -additions package
   installed from source.
  
   Mike H.


 Regards,

 --
 Theo
 ___
 freebsd-emulation@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
 To unsubscribe, send any mail to 
freebsd-emulation-unsubscr...@freebsd.org
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: Virtualbox-ose 4.3.12 guru meditation while booting any VM

[Bernhard Fröhlich]

On Sun, Sep 14, 2014 at 9:10 PM, Eric Masson e...@free.fr wrote:
 Bernhard Fröhlich de...@bluelife.at writes:

 Hi Bernhard,

 You could try to disable the ports debug option to rule out that it is a
 false assert. Building the vbox kmod port again with the matching kernel
 sources to ensure it's no stupid incompatibility would also be good.

 I've rebuilt virtualbox-ose  virtualbox-ose-kmod disabling DEBUG in
 both cases.

 The VM enters guru meditation state as soon as started like before.

 Thanks for your help.

Might make sense to update your ports to 4.3.16 which was just committed
a few minutes ago. This includes a lot of fixes from upstream.

-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: Cannot set VBOX_USE_IPV6 for VNC Server (VBoxVNC.cpp)

[Bernhard Fröhlich]

On Tue, Sep 16, 2014 at 3:16 AM, Gresnald Orlas gresn...@gmail.com wrote:
 Hi,

 I recently had a problem where the VNC server in VirtualBox would not bind
 to any IPV6 port except for the default.  I did some research and found
 this 
 http://lists.freebsd.org/pipermail/freebsd-emulation/2014-January/011194.html
 and this 
 http://newsarc.net/showthread.php/muc.lists.freebsd.emulation/Ports174976%3A%20Fix%20For%20IPv6%20Port%20Setting/4e0b86ff-9c4d-4cda-87fc-d6f759266...@lassitu.de
 After finding the last part I verified that the newer code is unpacked in
 the ports directory.  After trying several things I could not get the
 VBOX_USE_IPV6 bit to be set and the program always compiled with the
 default (broken) code.  Anyway after playing around some more it looks to
 me like kmk ignores /etc/make.conf and any CFLAGS passed in via the port
 'make CFLAGS=' command.  I could be doing something obviously wrong, but I
 think I am testing this right.  Perhaps kmk is supposed to work this way?
  In any case I thought you might want to know.  I checked the IRC channel,
 but no maintainers were around so I am sending this to v...@freebsd.org
 (maintainer) instead.  Hope this helps someone.  In the meantime for myself
 I have a patch which takes away the code for the default behavior from
 VBoxVNC.cpp directly.  If am doing something obviously wrong please let me
 know so I can do upgrades correctly and drop my ugly patch.

No kBuild (kmk) is not supposed to work that way. You need to patch the cpp
file as you did if you want/need that.

We did include that change in the port some time ago but it caused some
serious regression for other users so we had to revert it. That code
is definitely
a mess in vbox and just enabling that define is only the simple part
of the work.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: Virtualbox-ose 4.3.12 guru meditation while booting any VM

[Bernhard Fröhlich]

Am 13.09.2014 00:06 schrieb Eric Masson e...@free.fr:

 Eric Masson e...@free.fr writes:

 Hi,

  I'm facing serious issues with virtualbox-ose since 4.3.x
 
  Current test has been done on r367755 :
  virtualbox-ose-4.3.12_1General-purpose full virtualizer for x86
hardware
  virtualbox-ose-kmod-4.3.12 VirtualBox kernel module for FreeBSD
 
  Whenever I try to boot a VM (32/64 bits, any type), it enters Guru
  Meditation state with the following message on host console :
 
  HMR0InitVM: ff808b9d9000
  nfe0: promiscuous mode enabled
 
  !!Assertion Failed!!
  Expression: pVCpu-hm.s.idLastCpu == pCpu-idCpu
  Location  :
/vol0/ports/build/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.12/src/VBox/VMM/VMMR0/HMSVMR0.cpp(967)
void hmR0SvmFlushTaggedTlb(PVMCPU)
  vcpu idLastCpu= pcpu idCpu=1
  nfe0: promiscuous mode disabled
 
  Until now, I could revert to r340725, and then build 4.2.22, the last
  revision working flawlessly here, but 9.3-P1 ports infrastructure now
  refuses to build unstaged ports.
 
  Kernel, world  VBox ports have been built with gcc then clang, giving
  the same error.
 
  uname -a
  FreeBSD srvbsdfenssv.interne.associated-bears.org 9.3-RELEASE-p1 FreeBSD
  9.3-RELEASE-p1 #0 r271308: Wed Sep 10 00:21:18 CEST 2014
  e...@srvbsdfenssv.interne.associated-bears.org:
/usr/obj/usr/src/sys/M3N78-VM
  amd64
 
  dmesg
  http://emss.free.fr/contents/Divers/dmesg.txt
 
  VBox.log
  http://emss.free.fr/contents/Divers/VBox.log
 
  Any idea on something I could have overlooked ?
 
  What information could help solve the issue, please ?

 Using GENERIC kernel doesn't change anything to VirtualBox behaviour.
 Same error pops up, any idea please ?

 Regards

 Éric Masson

You could try to disable the ports debug option to rule out that it is a
false assert. Building the vbox kmod port again with the matching kernel
sources to ensure it's no stupid incompatibility would also be good.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: VirtualBox and GCC 4.8

[Bernhard Fröhlich]

Am 11.09.2014 16:54 schrieb Warren Block wbl...@wonkity.com:

 After the update yesterday to gcc 4.8, VirtualBox failed while
rebuilding.  Part of the kBuild stuff was still looking for gcc 4.7.  A
rebuild of devel/kBuild cured it.

Thanks for the info. Then we should bump portrevision on kbuild.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.0

[Bernhard Fröhlich]

On Mon, Aug 4, 2014 at 10:51 AM, Matthias Apitz g...@unixarea.de wrote:
 El día Friday, January 03, 2014 a las 04:15:30PM +0100, Bernhard Fröhlich 
 escribió:

 VirtualBox 4.3.6 Ports:
 http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.3.6-20140103.tar.gz

 ...


 Hello,

 Based on the call for testers file virtualbox-cft-4.3.0-20131020.tar.gz
 I compiled ports/emulators/virtualbox-ose-additions;

 the background of using this version from end of October is, that
 it is the last one which fits in my ports tree and the 10-CURRENT
 (r255948, ports: r328930, October 1st 2013) I have to run
 in this VM which runs fine in vbox of Ubuntu 14.04;

 after this 4.3.0 there was a fundamental change in the ports tree and it
 would mean that I have to compile all my ports from scratch;

 I had a few errors and removed

 -fformat-extensions
 -fno-format-extensions
 -mno-align-long-strings

 from work/VirtualBox-4.3.0/Config.kmk and after this it
 compiled and installed fine with:

 # make install USE_GCC=any

 but the system can not load the module:

 # /usr/local/etc/rc.d/vboxguest start
 /usr/local/etc/rc.d/vboxguest: WARNING: Can't load vboxguest module.
 # ls -ltr /boot/modules/vb*
 -r-xr-xr-x  1 root  wheel5433 Aug  4 10:24 /boot/modules/vboxvideo.ko
 -r-xr-xr-x  1 root  wheel  184387 Aug  4 10:24 /boot/modules/vboxguest.ko
 # kldload /boot/modules/vboxguest.ko
 kldload: can't load /boot/modules/vboxguest.ko: No such file or directory

 Why is this?

Please have a look at /var/log/messages when loading the kernel module
because the real cause is posted there when loading fails.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.0

[Bernhard Fröhlich]

Am 04.08.2014 14:40 schrieb Matthias Apitz g...@unixarea.de:

 El día Monday, August 04, 2014 a las 02:15:19PM +0200, Matthias Apitz
escribió:

   Please have a look at /var/log/messages when loading the kernel module
   because the real cause is posted there when loading fails.
 
  Thanks for your feedback; the message is:
 
  Aug  4 10:34:10 aurora guru: /usr/local/etc/rc.d/vboxguest: WARNING:
Can't load vboxguest module.
  Aug  4 10:34:10 aurora kernel: link_elf: symbol RTMpGetCoreCount
undefined


 more Infos:


 root@aurora:/usr/ports/emulators/virtualbox-ose-additions # ls -l `find
work | fgrep RTMpGetCoreCount`
   -rw-r--r--  1 root  wheel  2448 Aug  4 12:55
work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/RuntimeGuestR3/generic/RTMpGetCoreCount-generic.o
 -rw-r--r--  1 root  wheel  5274 Aug  4 12:55
work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/RuntimeGuestR3/generic/RTMpGetCoreCount-generic.o.dep
 -rw-r--r--  1 root  wheel  2504 Aug  4 12:55
work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/RuntimeGuestR3Shared/generic/RTMpGetCoreCount-generic.o
 -rw-r--r--  1 root  wheel  5350 Aug  4 12:55
work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/RuntimeGuestR3Shared/generic/RTMpGetCoreCount-generic.o.dep
 -rw-r--r--  1 root  wheel  1502 Oct 15  2013
work/VirtualBox-4.3.0/src/VBox/Runtime/generic/RTMpGetCoreCount-generic.cpp
 root@aurora:/usr/ports/emulators/virtualbox-ose-additions # nm
work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/RuntimeGuestR3/generic/RTMpGetCoreCount-generic.o
| fgrep RTMpGetCoreCount
  T RTMpGetCoreCount
 root@aurora:/usr/ports/emulators/virtualbox-ose-additions # nm
work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/RuntimeGuestR3Shared/generic/RTMpGetCoreCount-generic.o
| fgrep RTMpGetCoreCount
  T RTMpGetCoreCount
 root@aurora:/usr/ports/emulators/virtualbox-ose-additions # nm
/boot/modules/vboxguest.ko | fgrep RTMpGetCoreCount
U RTMpGetCoreCount


 i.e. RTMpGetCoreCount-generic.cpp was compiled but somehow not included
 in the kernel module?

 matthias

Have a look at the patches in virtualbox-ose for that function. There
should be a patch to add it to the kmod. You are just replicating issues
that were fixed already.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.0

[Bernhard Fröhlich]

Am 04.08.2014 21:03 schrieb Matthias Apitz g...@unixarea.de:

 El día Monday, August 04, 2014 a las 07:23:31PM +0200, Bernhard Fröhlich
escribió:

  i.e. RTMpGetCoreCount-generic.cpp was compiled but somehow not
 included
  in the kernel module?
 
  Â  Â  Â  Â  matthias
 
 Have a look at the patches in virtualbox-ose for that function. There
 should be a patch to add it to the kmod. You are just replicating
 issues that were fixed already.

 Thanks in any case for reading this and answering. I know that 4.3.0 is
 outdated. But even if outdated, I do not fully understand this: it means
 that the virtualbox-ose-application was never loaded into the kernel, or
 am I wrong?

 I will see how to fix this is the Makefile of its kmod.

No, this kind of issue exists because there is some kind of include list
for functions used by the kernel modules. The list is per OS and updated
manually and vbox developers tend to miss entries for FreeBSD. Adding the
filename to the list is simple and we usually create a simple patch for it
which we sure did in the following cft and it might still be in the
virtualbox-ose port if it wasn't yet included upstream.

After all this is wasting your time and now even mine so please try to use
packages or a newer portstree. This is a dead end.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: VirtualBox USB Shared Folders

[Bernhard Fröhlich]

On Tue, Jun 24, 2014 at 9:28 AM, Beeblebrox zap...@berentweb.com wrote:
 I have {virtualbox-ose-4.3.12_1, virtualbox-ose-additions-4.3.12,
 virtualbox-ose-kmod-4.3.12} installed on system  kldload vboxdrv
 vboxnetflt vboxnetadp

 Certain Guest Addition (GA) features are working (like smooth mouse
 transition) but I cannot get USB devices detected and selecting shared
 folders setting gives message that GA is not installed and to obtain the GA
 iso etc.

 * I have defined shared folder for the VGuest in question
 * User is member of operator  vboxusers groups

 What must I adjust in order to get USB devices detected and shared folders
 working on the VM?

1) USB passthru does not work reliable on FreeBSD hosts yet (FreeBSD guests
on Linux/Windows should be fine)

2) Shared Folders for FreeBSD guests are not supported yet. There was a Google
Summer of Code project that did not finish last year. There is some
draft code and
a kernel module for it but it's not working yet. Shared Folders
support for Linux/
Windows Guests on FreeBSD hosts are working fine.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: virtualbox-ose-kmod rc scripts

[Bernhard Fröhlich]

On Mon, May 26, 2014 at 4:25 PM, Warren Block wbl...@wonkity.com wrote:
 On Mon, 26 May 2014, Bernhard Fröhlich wrote:

 Am 26.05.2014 01:49 schrieb Dag-Erling Smørgrav d...@des.no:


 First of all, why is there a vboxnet rc script but not a vboxdrv rc
 script?

 Second, there is already support in /etc/rc.subr for checking whether a
 module is loaded, and loading it if it isn't.  Search for load_kld.
 There is no unload_kld, but IMHO you can just kldunload blindly.


 The vboxdrv module needs to be loaded via loader.conf or it can cause
 kernel panics. There are also some features that don't work properly if I
 remember correctly because of the startup order of startscripts so we
 can't
 use a rc script.


 Does it still do that?  Or maybe only on i386?  I've been reloading it after
 a rebuild for a long time now without problems, but maybe that was because
 it was on amd64 or just luck.

It's not quite as easy as that. We tried it two times already (back in
the old vbox
3.x days and last time around 4.0 I guess) and with both tests we ran into panic
reports from various people that we could not reproduce on any of our machines.

I don't remember the exact details about it anymore but there was another issue
with network interfaces coming up before vboxdrv and it was unable to see/use
the interface or so.

So it might be time to give it another try and see if we still run
into that issues.

-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: FreeBSD Port: emulators/virtualbox-ose

[Bernhard Fröhlich]

Unfortunately you did cut off the interesting part which should be a
few lines before that error.

On Sun, Apr 27, 2014 at 6:28 PM, Jason Selwitz jselw...@verizon.net wrote:
 Understood..

 - In general I always fetch/update the latest ports before updating
 anything,
 - No CFLAGS or CXXFLAGS statements in make.conf
 - Running FreeBSD 10.0-RELEASE-p1 AMD64

 And here is what seems to be erroring..


 The failing command:
 @gcc -c -O2 -g -pipe -Wall -Wextra -Wno-missing-field-initializers
 -Wno-unused -Wno-trigraphs -fdiagnostics-show-option
 -Wno-unused-parameter -Wno-long-long -Wno-long-long
 -Werror-implicit-function-declaration -Wno-variadic-macros -O2
 -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing
 -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN
 -DRT_USE_VISIBILITY_DEFAULT -fPIC -Wno-sign-compare
 -Werror-implicit-function-declaration -m64
 -I/home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/src/recompiler/Sun/crt
 -I/home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/src/recompiler/Sun
 -I/home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/src/recompiler/target-i386
 -I/home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/src/recompiler/tcg
 -I/home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/src/recompiler/fpu
 -I/home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/out/freebsd.amd64/release/obj/VBoxRemPrimary
 -I/home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/src/VBox/VMM/include
 -I/home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/src/recompiler/tcg/i386
 -I/home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/src/recompiler
 -I/usr/include -I/usr/X11R6/include -I/usr/local/include
 -I/home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/out/freebsd.amd64/release/obj/VBoxRemPrimary/dtrace
 -I/home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/include
 -I/home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/out/freebsd.amd64/release
 -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_DEBUGGER
 -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_AMD64 -D__AMD64__
 -DVBOX_WITH_HARDENING
 -DRTPATH_APP_PRIVATE=\/usr/local/share/virtualbox-ose\
 -DRTPATH_APP_PRIVATE_ARCH=\/usr/local/lib/virtualbox\
 -DRTPATH_SHARED_LIBS=\/usr/local/lib/virtualbox\
 -DRTPATH_APP_DOCS=\/usr/local/share/doc/virtualbox-ose\ -DIN_RING3
 -DHC_ARCH_BITS=64 -DGC_ARCH_BITS=64 -DPIC -DIN_REM_R3
 -DREM_INCLUDE_CPU_H -DNEED_CPU_H -DVBOX_WITH_RAW_MODE
 -DVBOX_WITH_RAW_RING1 -DLOG_USE_C99 -D_BSD -D__x86_64__
 -Wp,-MD,/home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/out/freebsd.amd64/release/obj/VBoxRemPrimary/VBoxRecompiler.o.dep
 -Wp,-MT,/home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/out/freebsd.amd64/release/obj/VBoxRemPrimary/VBoxRecompiler.o
 -Wp,-MP -o
 /home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/out/freebsd.amd64/release/obj/VBoxRemPrimary/VBoxRecompiler.o
 /home/jselwitz/work/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.10/src/recompiler/VBoxRecompiler.c
 kmk: *** Waiting for unfinished jobs
 kmk: *** Exiting with status 2
 *** Error code 2

 Stop.
 make[1]: stopped in /usr/ports/emulators/virtualbox-ose
 *** Error code 1

 Stop.
 make: stopped in /usr/ports/emulators/virtualbox-ose
 ** Command failed [exit code 1]: /usr/bin/script -qa
 /tmp/portupgrade20140427-11281-146uwyv env UPGRADE_TOOL=portupgrade
 UPGRADE_PORT=virtualbox-ose-4.2.18_1 UPGRADE_PORT_VER=4.2.18_1 make
 ** Fix the problem and try again.
 ** Listing the failed packages (-:ignored / *:skipped / !:failed)
 ! emulators/virtualbox-ose (virtualbox-ose-4.2.18_1)(unknown
 build error)


 Thanks for the assistance if I can provide any further output just let
 me know!



 On 04/26/2014 12:15, Thomas Hoffmann wrote:
 On Sat, Apr 26, 2014 at 1:49 AM, Jason Selwitz jselw...@verizon.net
 mailto:jselw...@verizon.net wrote:

 Hello,

   I recently tried upgrading to the latest release of virtualbox and ran
 into some errors, I was wondering if someone would be willing to have a
 look and lend a hand, I can forward on an output of the build and any
 other pertinent information. Thanks!


 1) update your local ports tree using 'portsnap fetch update' to make
 sure you are working with the latest version of  virtualbox-ose
 2) remove any CFLAGS and CXXFLAGS statements from /etc/make.conf.
 3) Re-try the installation

 If you still have a problem, provide the FreeBSD version and hardware
 platform, and the pertinent lines from the install log showing the
 error. Be generous.

 ___
 freebsd-emulation@freebsd.org mailing list
 

Re: VBoxManage errors at boot

[Bernhard Fröhlich]

On Thu, Mar 20, 2014 at 8:53 AM, Thomas Hoffmann trh...@gmail.com wrote:
 On Wed, Mar 19, 2014 at 11:25 PM, Thomas Hoffmann trh...@gmail.com wrote:

 On Wed, Mar 19, 2014 at 10:31 PM, Thomas Hoffmann trh...@gmail.comwrote:

 I'm running emulators/virtualbox-ose-4.3.8 on -CURRENT r263411 amd64. The
 last several boot sequences I have noticed the following errors in the
 console log:

 Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Failed to create the
 VirtualBox object!
 Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Code NS_ERROR_ABORT
 (0x80004004) - Operation aborted (extended info not available)
 Mar 19 22:11:01 tortoise kernel: VBoxManage: error: Most likely, the
 VirtualBox COM server is not running or failed to start.

 I'm perplexed by these messages because I do not have any cron jobs that
 invoke VBoxManage @reboot for any purpose whatsoever be it managing or
 starting a virtual machine.

 I'm thinking these messages appeared after the upgrade to 4.3.8, but I
 cannot be certain.

 Can anyone provide a context for these errors?

 -Tom


 I've done a bit of digging and can offer a bit more info. I upgraded
 virtualbox-ose to 4.3.8 on 3/3 and did not see the errors until 3/11, so
 the upgrade itself did not introduce the errors. The 3/3 upgrade was my
 last upgrade of virtualbox-ose and I did not re-install it after that.

 However, on 3/11 I built a new -CURRENT (r263062). Something in that build
 seems to have introduced the errors. My previous -CURRENT (r262295) built
 on 3/8 did not have the errors.

 I'm still looking into this.

 -Tom


 Okay, so I found the source of this error. In /usr/local/etc/rc.d/vboxnet
 (I have vboxnet_enable in /etc/rc.conf) it attempts to execute the
 following command for vboxnet_start:
 # initialize configured host-only interfaces
 /usr/local/bin/VBoxManage list hostonlyifs /dev/null

 I can run VBoxManage as a normal user without any problems, but when I run
 VBoxManage as root it results in the same three errors from my original
 post. That is why it errors out during the boot process. I don't know if
 that behavior is normal or not.

 In any event,  don't understand the purpose of the VBoxManage command in
 /usr/local/etc/rc.d/vboxnet since, contrary to the immediately preceding
 comment, it is only listing (not initializing) hostonly interfaces and
 sending the output to dev/null. It seems pointless.

 Anyway my conclusion is that the boot time error messages while annoying,
 are harmless. I'm still not certain why the error messages just started
 showing up in the console log on 3/11.

It does exactly what the comment says. host-only interfaces need to be
initialized (pretty early for some configurations) and the hostonlyifs listing
is the least intrusive one which ensures that they are.

It might be that the error output of vboxmanage has been switched to stderr
now and we need to add an 2/dev/null too. Have you recompiled all vbox
kernel modules after your update to a new current?

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: about gsoc 2014

[Bernhard Fröhlich]

On Tue, Mar 18, 2014 at 5:50 AM, Junyuan Zeng jz...@utdallas.edu wrote:
 Hi Bernhard

 I am Junyuan Zeng, a fourth year PhD student at The University of Texas at 
 Dallas. I am pretty interested on the project that you lead.
 I am very good at C programming and have advanced knowledge about 
 visualization and vfs in Linux Kernel.
 I have some experience about Virtulbox. I am implementing a mechanism on 
 Virtualbox for fast transferring files between guest OS and host OS now.
 We have implemented this mechanism in KVM and it's at least 5X-10X faster 
 than drag 'n' drop in Virtualbox. Basically, we redirect the system call from
 host OS to guest OS. We can talk more about it if you have interests.

 If let me implement the VirtualBox shared folder support for FreeBSD 
 guests, I will take a look at the source code in folder 
 VirtualBox-4.3.8/src/VBox/Additions/linux/sharedfolders, which
 implement the guest driver for shared folder. Based on that, I will implement 
 a freebsd version of guest driver. Do you think it's a good way to go?

 Thanks!


Hi Junyuan,

Thanks for your interest in the VirtualBox Shared Folders GSoC
project! This project
was already part of GSoC last year but it's still unfinished. In the
meantime lwhsu@
has continued on the result of that and he is the better technical
contact right now.

The current work can be seen on github:

https://github.com/lwhsu/freebsd-vboxfs

and I forward you the most recent mail from him which should give an
idea of what
work remaining to do. We would be very glad if someone takes that GSoC task
but it requires more bugfixing and adding read/write support than implementing
new code.

I have also CC'd a bunch of people that are currently involved in that
task to keep
them informed.

Looking forward to a great GSoC 2014 :o)


-- Forwarded message --
From: Li-Wen Hsu lw...@freebsd.org
Date: Fri, Mar 14, 2014 at 6:47 PM
Subject: Re: [GSoc] interested in VirtualBox shared folder support
for FreeBSD guests
To: waleed ziad wela64wal...@gmail.com
Cc: Bernhard Fröhlich de...@freebsd.org,
freebsd-emulation@freebsd.org freebsd-emulation@freebsd.org,
Oleksandr Dudinskyi dudins...@gmail.com, Daniel Lorch
dlo...@gmail.com


On Mon, Mar 10, 2014 at 19:47:53 +0200, waleed ziad wrote:
 Thanks a lot Mr.Bernhard Fröhlich for your care and reply i contacted him .

 On Mon, Mar 10, 2014 at 2:44 PM, Bernhard Fröhlich de...@freebsd.org wrote:
  On Mon, Mar 10, 2014 at 4:31 AM, waleed ziad wela64wal...@gmail.com wrote:
  Hello all, i am a student from Cairo , Egypt and i was hoping to
  participate at Google summer of code this year in FreeBSD organization
  i am interested in  VirtualBox shared folder support for FreeBSD
  guests and i was hoping someone Could someone suggest the first steps
  I should take to understand the project better or any issues(or bugs)
  that I can look into ? and any skills i should acquire ? , thank all
  in advance .
 
  Thanks for your interest! The project was part of GSoC last year already and
  Oleksandr did make good progress with it but hasn't got it fully
  working. Li-Wen Hsu
  took over his work and fixed a few things and also put it on github:
 
  https://github.com/lwhsu/freebsd-vboxfs
 
  So right now the best technical contact is Li-Wen Hsu and I guess he
  can also tell
  you what is blocking progress right now and if it's still a viable GSoC 
  project.

Sorry for the late reply, as Bernhard said, the current status is blocked
because it seems that I need to get familiar with our virtual memory
subsystem and how it interacts with VirtualBox's HGCM to make progress.
I'm trying to squeeze more time on this.

The README on https://github.com/lwhsu/freebsd-vboxfs is still valid for 4.3.8,
you can follow the instruction to setup the environment, kldload
vboxguest.ko and vboxvfs.ko .  However, mount_vboxfs still cannot work
because vboxCallMapFolder() returns error.

If digging this deeper, we can find that the call ends up in

rtR0MemObjNativeLockInMap()
(in VirtualBox-4.3.8/src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c)

while doing:

rc = vm_map_wire(pVmMap,  /* the map */
 AddrStart,   /* start */
 AddrStart + cb,  /* end */
 fFlags); /* flags */

the vm_map_wire(9) (in /sys/vm/vm_map.c) always returns KERN_INVALID_ADDRESS
when getting false with vm_map_lookup_entry(9) at the beginning.

That's my current status.  Any help on this is welcomed.

Add Daniel Lorch into CC list since he's also working on this.

Li-Wen

--
Li-Wen Hsu lw...@freebsd.org
http://lwhsu.org


-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: ports/187444: emulators/virtualbox-ose-kmod does not build (multiple definition of some macros)

[Bernhard Fröhlich]

The following reply was made to PR ports/187444; it has been noted by GNATS.

From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= de...@bluelife.at
To: bug-follo...@freebsd.org, ard...@yahoo.it
Cc:  
Subject: Re: ports/187444: emulators/virtualbox-ose-kmod does not build
 (multiple definition of some macros)
Date: Tue, 11 Mar 2014 20:13:02 +0100

 --e89a8ff1c01c4e102c04f4598254
 Content-Type: text/plain; charset=ISO-8859-1
 
 I remember a similar bugreport for 10.0-BETA1 on i386 but apparently the
 bug in the kernel headers that caused that pollution got fixed before
 10.0-RELEASE. But since you are running a recent 9.2-stable it seems
 someone has merged that stuff to 9 now and reintroduced the bug again.
 
 I still think this is a FreeBSD bug in the kernel headers that pollute the
 modules with MSR defines because it only happens on i386. Yes, a proper fix
 would also be to add #ifndefs to the vbox defines.
 
 --e89a8ff1c01c4e102c04f4598254
 Content-Type: text/html; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 p dir=3DltrI remember a similar bugreport for 10.0-BETA1 on i386 but ap=
 parently the bug in the kernel headers that caused that pollution got fixed=
  before 10.0-RELEASE. But since you are running a recent 9.2-stable it seem=
 s someone has merged that stuff to 9 now and reintroduced the bug again./p=
 
 
 p dir=3DltrI still think this is a FreeBSD bug in the kernel headers th=
 at pollute the modules with MSR defines because it only happens on i386. Ye=
 s, a proper fix would also be to add #ifndefs to the vbox defines./p
 
 --e89a8ff1c01c4e102c04f4598254--
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [GSoc] interested in VirtualBox shared folder support for FreeBSD guests

[Bernhard Fröhlich]

On Mon, Mar 10, 2014 at 4:31 AM, waleed ziad wela64wal...@gmail.com wrote:
 Hello all, i am a student from Cairo , Egypt and i was hoping to
 participate at Google summer of code this year in FreeBSD organization
 i am interested in  VirtualBox shared folder support for FreeBSD
 guests and i was hoping someone Could someone suggest the first steps
 I should take to understand the project better or any issues(or bugs)
 that I can look into ? and any skills i should acquire ? , thank all
 in advance .

Thanks for your interest! The project was part of GSoC last year already and
Oleksandr did make good progress with it but hasn't got it fully
working. Li-Wen Hsu
took over his work and fixed a few things and also put it on github:

https://github.com/lwhsu/freebsd-vboxfs

So right now the best technical contact is Li-Wen Hsu and I guess he
can also tell
you what is blocking progress right now and if it's still a viable GSoC project.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: Build Headless on 10-RELEASE?

[Bernhard Fröhlich]

The build problems of virtualbox-ose are independent from the other
stuff. It seems
that for this option combination misses a few dependencies. I will
have a look at that
and it should be trivial to fix.

The kernel panic is a different story and has nothing to do with
virtualbox-ose and
it's options. Could you please check the options of
virtualbox-ose-kmod and rebuild
the kernel modules with DEBUG enabled and manually load them on the console
so that you are able to see the kernel debugger? Then please send me the output
of bt (backtrace).


On Mon, Mar 10, 2014 at 3:40 PM, Evan Rowley rowley.e...@gmail.com wrote:
 Running kldload vboxdrv causes a panic.

 This is the main branch of virtualbox-ose 4.3.8 for amd64 available in
 ports, SVN commit 347141. It was compiled on FreeBSD 10-RELEASE.
 Options for X11, NLS, and QT were disabled. I also think an OpenGL
 option was disabled in either virtualbox-ose or one of it's
 dependencies, but I cant remember for certain.

 The original system install had the kernel, doc, and base sets. No lib32.

 Earlier compiles were failing because (I think) lib32 was missing.
 This was fixed by running cd /usr/src; make toolchain

 During the compilation of virtualbox-ose I recieved another compile
 error about missing libffi. I thought it was odd that the ports / make
 process did not take care of this dependency automatically. I
 mitigated that compile-time error by issuing a pkg install libffi -
 there was another dependency like this but I cannot recall what it
 was.

 After adding the two dependencies I was finally able to get a full
 compile. The end-product unforunatley doesn't work.

 Can I give any more details?

 On Sat, Mar 8, 2014 at 3:43 PM, Bernhard Fröhlich de...@bluelife.at wrote:

 Am 08.03.2014 20:45 schrieb Evan Rowley rowley.e...@gmail.com:



 Has this been successfully done with working kernel module on 10-RELEASE?
 I
 can't seem to get this working for myself. Is it only me? Has anyone else?
 By headless I mean without X11, without NLS, and without QT.

 Thanks,

 What problem are you seeing and which vbox version did you try?



 --
  - EJR



-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: Build Headless on 10-RELEASE?

[Bernhard Fröhlich]

Am 08.03.2014 20:45 schrieb Evan Rowley rowley.e...@gmail.com:

 Has this been successfully done with working kernel module on 10-RELEASE?
I
 can't seem to get this working for myself. Is it only me? Has anyone else?
 By headless I mean without X11, without NLS, and without QT.

 Thanks,

What problem are you seeing and which vbox version did you try?
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: FreeBSD Port: www/phpvirtualbox

[Bernhard Fröhlich]

Am 12.02.2014 23:06 schrieb Cleber Medina clebermed...@gmail.com:

 HI i just installed and set all things rigth... but just show a grey
screen at the browser?

 There are something new?

Please check that you have an up to date portstree because I added a
missing php xml dependency some days ago.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: virtualbox tips for performance specific to FreeBSD-10 hosts

[Bernhard Fröhlich]

On Sat, Feb 8, 2014 at 10:51 AM, John freebsd-li...@potato.growveg.org wrote:
 Hello list,

 As subject, can anyone recommend any tips for getting optimum
 performance from various guests on a freebsd-10-R host? I've looked at
 the page about changing polling interval but that only applies to
 freebsd guests. I'm looking advice specifically for linux guests on this
 host. Guests are ubuntu and opensuse.

 Machine is a Xeon E5-2650L @ 1.80GHz with 32 cores, 192GB RAM and 10TB
 available storage on zfs.

I would not recommend using VirtualBox on such a box. VirtualBox is a Desktop
Virtualisation product and that specs are too high to make good use of them.

One issue you will run into is ZFS ARC - with that amount of memory it will take
quite some time to fill up but ZFS ARC and VirtualBox wired memory will start
fighting each other. So I recommend limiting ZFS ARC to some sane amount.
(32GB?)

VirtualBox has quite a bit more overhead than all the other server
grade virtualisation
products out there and that is especially true for I/O. With FreeBSD
10 you should
already use AHCI on the host and the linux guests will likely use an
SATA controller
and AHCI too. That should be the minimum and is also what we have already
written down in the vbox tuning notes:

https://wiki.freebsd.org/VirtualBox/Tuning

 No issues sofar freebsd on freebsd. Just looking for advice linux guest
 on freebsd with virtualbox. Or perhaps there's something better than
 virtualbox? Basically all guests need to be isolated from one another.
 It makes backing up and restoring systems pain-free.

So far this are the mainstream candidates:

BSD:
- BHyVe

Linux:
- KVM
- Xen

Proprietary:
- VMware ESXi
- XenServer

I have had a look at a server virtualisation product myself some months ago
and came to the conclusion that there is no painfree server virtualisation
product that is focused on ONE machine with a proper webinterface with a
reasonable easy installation and for free.

VMware ESXi came close but it fails badly with the webinterface (no I don't
consider the required 8-16GB RAM for the webinterface appropriate).

RedHats oVirt also made a good impression but I broke it within half an hour
and the webinterface never detected the nodes properly. Also oVirt really wants
you to have a dedicated storage box which I wanted to avoid. Running it all on
one machine is on their todo for years. No I don't want to run 3 boxes for two
VMs.

OpenStack was just a mess and I gave up because all the different components
didn't fit into my small head. This really looks like you want to build your own
cloud with 1000+ nodes.

There are quite a few more KVM based products out there which I didn't try
just because I gave up at that point and went with the free ESXi and a windows
VM with vSphere Client. The ones that I remember were also appropriate candiates
for my search were Ubuntu 12.04 LTS with KVM + convirt2, Proxmox or a simple
Linux distribution and shell.

So VirtualBox + phpvirtualbox does a few things very very good and I love it
for that on small boxes with light load but it's not a proper server
virtualisation
product.

What I would really like to see is a FreeNAS like appliance for virtualisation
with a webinterface and based on BHyVe. The Linux KVM stuff is not quite
there yet when it comes to painless.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: VirtualBox 4.3.6 keyboard repeats keystrokes

[Bernhard Fröhlich]

On Tue, Feb 4, 2014 at 4:03 AM, Aryeh Friedman aryeh.fried...@gmail.com wrote:
 On Mon, Feb 3, 2014 at 8:44 PM, Kevin Oberman rkober...@gmail.com wrote:

 On Mon, Feb 3, 2014 at 12:38 PM, CeDeROM cede...@tlen.pl wrote:

  Hello :-)
 
  I have noticed that quite often keystrokes are repeated in VBox 4.3.6
  OSE on FreeBSD-10.0 AMD64. For example when I press cursor left it
  repeats many times, letters also. The fast way to stop this is to
  switch to another application on my BSD box then switch back to VBox..
 
  Did anyone notice this behavior? What is the problem?
 
  Best regards :-)
  Tomek
 
  --
  CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
 

 I have this issue, but only when logged into the VM remotely via RDP. From
 the local console this never happens. It is intermittent and never happens
 when the session is first opened.


 Do you notice this only in VBox or other hypervisiors like bhyve or qemu?
 (Some motherboards do not like virtualization even when the CPU allows it
 one easy way to test this is with petitecloud [you might even find it a
 good replacement for vbox])

Aryeh with all respect but could you please stop spamming all vbox related
threads with your commercials for petitecloud? It's seriously too much to tell
all people that have a problem with vbox to switch to a different product.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: patch to stage emulators/virtualbox-ose-additions

[Bernhard Fröhlich]

Am 26.01.2014 17:12 schrieb René Ladan r...@freebsd.org:

 Hi,

 in an effort to stage all USES=kmod ports, here is a patch to stage
 emulators/virtualbox-ose-additions.  Note that it also fixes installing
 with DEBUG on, vboxvideo.ko.symbols is no longer built.

 Is it OK to commit this?

 http://people.freebsd.org/~rene/patches/virtualbox-ose-additions.diff

 Regards,
 René

Yeah please do so. Btw jkim@ has made a similar patch but did not commit it
yet and I see no big differences between both - so first come first serve.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: Preferred controller types

[Bernhard Fröhlich]

Am 16.01.2014 22:33 schrieb Mike Tancsa m...@sentex.net:

 On 1/16/2014 2:59 PM, Mike Tancsa wrote:
  VBoxManage storagectl rc5i386 --name SATA --add sata --controller
  IntelAHCI --portcount 4 --bootable on
  VBoxManage storageattach rc5i386 --storagectl SATA --port 0 --device
  0 --type hdd --medium FreeBSD-10.0-RC5-i386-20140108-r260430.vmdk

 OK, next problem. If I set the disks to SATA, doing something simple
 like an SVN checkout causes all sorts of disk errors and then a panic.
 If I instead set the controller to just IDE, all is OK.

 What is the optimal chipset and driver config for FreeBSD as a host and
 guest ?

Defaults should be preferred and you should try to avoid ICH9. I was told
from upstream that ich9 is still not the default because it just doesn't
work reliable enough in all cases. So be carefull with that.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: VirtualBox 4.3.6 + FreeBSD 10 + clang, [SUCCESS]

[Bernhard Fröhlich]

Am 11.01.2014 03:49 schrieb Craig Rodrigues rodr...@freebsd.org:

 Hi,

 I had problems with the virtualbox-ose-4.22 port
 under FreeBSD 10.0-RC5, where VirtualBox would occasionally
 crash.
 It looks like the mix of QT C++ libraries compiled with clang,
 vs. the virtualbox-ose port compiled with g++46 was not a good mix

I still think that this is a problem that needs to be fixed in Qt or even
better in our ports tree. The decision to compile parts of the portstree
with the base compiler and other parts with various compilers from ports is
what causes all this issues. Hacking virtualbox cures the symptoms but does
not fix the cause.

 After reading this post:

http://lists.freebsd.org/pipermail/freebsd-emulation/2013-December/011171.html

 I obtained Jung-uk Kim's port Makefiles for VirtualBox and
 I managed to compile a build of VirtualBox 4.3.6 on my system which is not
 crashing.

 This is what I did:

 (1)   Delete the virtualbox-ose port from my system:

 pkg delete virtualbox-ose
 pkg delete virtualbox-ose-kmod

 (2)   Delete the gsoap port from my system

 pkg delete gsoap

 (3)  Make sure that a valid FreeBSD src tree exists under /usr/src,
otherwise
   the build will fail.

 (4)  Check out jkim's tree from redports:

 mkdir -p /tmp/xy
 cd /tmp/xy
 svn co https://svn.redports.org/jkim

 (5)   Build and install gsoap from jkim's port (you need to do this
because the version of gsoap in the ports tree will result in failed
compilation):

 cd /tmp/xy/jkim/devel/gsoap
 make
 make install

Really? From what I was told the current gsoap should work fine with the
patch that he included for the new gsoap in his tree.

 (6)  Build and install virtualbox-ose and virtualbox-ose-kmod ports.

 cd /tmp/xy/jkim/emulators/virtualbox-ose
 make
 make install
 cd /tmp/xy/jkim/emulators/virtualbox-ose-kmod
 make
 make install

That is the wrong order. You need to install kmod first or virtualbox will
pull in kmod from the portstree in /usr/ports.

 After doing this, I got a build of VirtualBox that:
 - built against clang, does not depend on g++ libraries
 - no need to unset QT_PLUGIN_PATH
 - works and doesn't crash :)

 Thank you for doing this Jung-uk, it was quite a lot of work
 to port VirtualBox to clang!

I still think this is the wrong approach and I won't maintain all those
clang patches in the official port. The problem that I see is that we are
diverging from upstream vbox too much and end up maintaining a very special
usecase and a few dozen patches on our own. We would be the only one to
build with clang so with every release we need to update our patches and
add more to keep it building with clang. This will need someone that want's
to do it for the next few years.

Since the beginning of vbox on FreeBSD we tried to stay close to upstream
sources and push patches to upstream first. This has worked good for us and
has created a good relationship to them.

So we have 3 options:

- I step down and wish you all the best. There are a few smart people
working on vbox now so it should not be an issue for the project.

- Someone clones the vbox ports and maintains the clang version in the
portstree.

- We try to push as many patches upstream and nag them until they accept
them. This might also interest some Mac OS X people.

I will talk to the vbox developers to find out what they think of clang and
if someone is working on updating the recompiler from qemu which would make
a full clang build possible.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: ports/185584: emulators/virtualbox-ose does not build on 10-stable

[Bernhard Fröhlich]

The following reply was made to PR ports/185584; it has been noted by GNATS.

From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= de...@bluelife.at
To: bug-follo...@freebsd.org, marko.cu...@mimar.rs
Cc:  
Subject: Re: ports/185584: emulators/virtualbox-ose does not build on 10-stable
Date: Thu, 9 Jan 2014 07:15:37 +0100

 --089e013d0960bfda4804ef8389db
 Content-Type: text/plain; charset=ISO-8859-1
 
 virtualbox requires the kernel sources to be installed. It looks like you
 haven't so please install them and retry.
 
 --089e013d0960bfda4804ef8389db
 Content-Type: text/html; charset=ISO-8859-1
 
 p dir=ltrvirtualbox requires the kernel sources to be installed. It looks 
like you haven#39;t so please install them and retry./p
 
 --089e013d0960bfda4804ef8389db--
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: ports/185584: emulators/virtualbox-ose does not build on 10-stable

[Bernhard Fröhlich]

The following reply was made to PR ports/185584; it has been noted by GNATS.

From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= de...@bluelife.at
To: =?UTF-8?B?TWFya28gQ3VwYcSH?= marko.cu...@mimar.rs
Cc: bug-follo...@freebsd.org
Subject: Re: ports/185584: emulators/virtualbox-ose does not build on 10-stable
Date: Thu, 9 Jan 2014 21:33:27 +0100

 --001a11c2fcb89225da04ef8f854a
 Content-Type: text/plain; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 Am 09.01.2014 17:31 schrieb Marko Cupa=C4=87 marko.cu...@mimar.rs:
 
  On Thu, 9 Jan 2014 08:55:10 +0100
  Bernhard Fr=C3=B6hlich de...@bluelife.at wrote:
 
   SRC_BASE should be what you are looking for.
 
  Hi Bernhard,
 
  As my shell is tcsh, I did (as root):
  # setenv SRC_BASE /usr/src/stable/10/
 
  Afterwards portmaster built and installed virtualbox-ose fine.
 
  Thanx,
  --
  Marko Cupa=C4=87
 
 I did not try this but it should also work if you add this variable to
 /etc/make.conf to make this setting permanent.
 
 --001a11c2fcb89225da04ef8f854a
 Content-Type: text/html; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 p dir=3Dltrbr
 Am 09.01.2014 17:31 schrieb quot;Marko Cupa=C4=87quot; lt;a href=3Dmai=
 lto:marko.cu...@mimar.rsmarko.cu...@mimar.rs/agt;:br
 gt;br
 gt; On Thu, 9 Jan 2014 08:55:10 +0100br
 gt; Bernhard Fr=C3=B6hlich lt;a href=3Dmailto:de...@bluelife.at;decke@=
 bluelife.at/agt; wrote:br
 gt;br
 gt; gt; SRC_BASE should be what you are looking for.br
 gt;br
 gt; Hi Bernhard,br
 gt;br
 gt; As my shell is tcsh, I did (as root):br
 gt; # setenv SRC_BASE /usr/src/stable/10/br
 gt;br
 gt; Afterwards portmaster built and installed virtualbox-ose fine.br
 gt;br
 gt; Thanx,br
 gt; --br
 gt; Marko Cupa=C4=87/p
 p dir=3DltrI did not try this but it should also work if you add this v=
 ariable to /etc/make.conf to make this setting permanent.br
 /p
 
 --001a11c2fcb89225da04ef8f854a--
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: virtualbox-ose: missing OpenGL dependency

[Bernhard Fröhlich]

On Wed, Jan 8, 2014 at 12:29 PM, Jimmy Olgeni olg...@olgeni.com wrote:

 Hello,

 After the latest QT4 changes I noticed that VirtualBox needs a dependency on
 graphics/qt4-opengl, so here it is (checked on poudriere):

 Index: Makefile
 ===
 --- Makefile(revision 339028)
 +++ Makefile(working copy)
 @@ -27,7 +27,8 @@
 python:${PORTSDIR}/lang/python
  LIB_DEPENDS=   libpng.so:${PORTSDIR}/graphics/png \
 libxslt.so:${PORTSDIR}/textproc/libxslt \
 -   libcurl.so:${PORTSDIR}/ftp/curl
 +   libcurl.so:${PORTSDIR}/ftp/curl \
 +   libQtOpenGL.so:${PORTSDIR}/graphics/qt4-opengl
  RUN_DEPENDS=
 ${KMODDIR}/vboxdrv.ko:${PORTSDIR}/emulators/virtualbox-ose-kmod \
 cdrecord:${PORTSDIR}/sysutils/cdrtools

You might be correct but the patch looks wrong to me so I propose the following.

Index: emulators/virtualbox-ose/Makefile
===
--- emulators/virtualbox-ose/Makefile(revision 339142)
+++ emulators/virtualbox-ose/Makefile(working copy)
@@ -124,7 +124,7 @@

 .if ${PORT_OPTIONS:MQT4}
 QT_NONSTANDARD=yes
-USE_QT4=gui network moc_build uic_build rcc_build linguist
+USE_QT4=gui network moc_build opengl uic_build rcc_build linguist
 INSTALLS_ICONS=yes
 VBOX_FRONTENDS+=VirtualBox VBoxTestOGL

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: ports/185579: emulators/virtualbox-ose: add graphics/qt4-opengl dependency

[Bernhard Fröhlich]

The following reply was made to PR ports/185579; it has been noted by GNATS.

From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= de...@bluelife.at
To: bug-follo...@freebsd.org, olg...@freebsd.org
Cc:  
Subject: Re: ports/185579: emulators/virtualbox-ose: add graphics/qt4-opengl 
dependency
Date: Wed, 8 Jan 2014 16:04:45 +0100

 You might be correct but the patch looks wrong to me so I propose the follo=
 wing.
 
 Index: emulators/virtualbox-ose/
 Makefile
 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
 --- emulators/virtualbox-ose/Makefile(revision 339142)
 +++ emulators/virtualbox-ose/Makefile(working copy)
 @@ -124,7 +124,7 @@
 
  .if ${PORT_OPTIONS:MQT4}
  QT_NONSTANDARD=3Dyes
 -USE_QT4=3Dgui network moc_build uic_build rcc_build linguist
 +USE_QT4=3Dgui network moc_build opengl uic_build rcc_build linguist
  INSTALLS_ICONS=3Dyes
  VBOX_FRONTENDS+=3DVirtualBox VBoxTestOGL
 
 
 --=20
 Bernhard Fr=F6hlich
 http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: vboxvideo issues

[Bernhard Fröhlich]

This looks suspicious to me but I don't know how to fix it yet.

[24.612] (EE) AIGLX error: vboxvideo does not export required DRI
extension

It might help to disable this 3D aiglx stuff in the xserver.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.6

[Bernhard Fröhlich]

On Fri, Jan 3, 2014 at 7:39 PM, Mike Tancsa m...@sentex.net wrote:
 On 1/3/2014 10:15 AM, Bernhard Fröhlich wrote:
 - Update phpvirtualbox to 4.3-1

 Hi,
 virtualbox compiled fine, but the phpvirtualbox gives these errors

 make install gives


 ===  Building package for phpvirtualbox-4.3.1
 Creating package
 /usr/home/mdtancsa/virtualbox-cft-4.3.6-20140103/www/phpvirtualbox/work/phpvirtualbox-4.3.1.tbz
 Registering depends: php5-json-5.4.23 php5-soap-5.4.23
 php5-session-5.4.23 php5-simplexml-5.4.23 php5-5.4.23 apache22-2.2.26
 apr-1.4.8.1.5.3 gdbm-1.11 gettext-0.18.3.1 libxml2-2.8.0_3
 libiconv-1.14_1 db42-4.2.52_5 mysql55-client-5.5.35 sqlite3-3.8.1
 pcre-8.33 perl5.14-5.14.4_4 expat-2.1.0.
 Creating bzip'd tar ball in
 '/usr/home/mdtancsa/virtualbox-cft-4.3.6-20140103/www/phpvirtualbox/work/phpvirtualbox-4.3.1.tbz'
 tar: www/phpvirtualbox/config.php-example: Cannot stat: No such file or
 directory
 tar: www/phpvirtualbox/CHANGELOG.txt: Cannot stat: No such file or directory
 tar: www/phpvirtualbox/GPLv3.txt: Cannot stat: No such file or directory
 tar: www/phpvirtualbox/LICENSE.txt: Cannot stat: No such file or directory
 tar: www/phpvirtualbox/README.txt: Cannot stat: No such file or directory
 tar: www/phpvirtualbox/css/jquery-ui.css: Cannot stat: No such file or
 directory
 tar: www/phpvirtualbox/css/jquery.projectPlugins.css: Cannot stat: No
 such file or directory
 tar: www/phpvirtualbox/css/layout.css: Cannot stat: No such file or
 directory
 tar: www/phpvirtualbox/css/tipped.css: Cannot stat: No such file or
 directory
 tar: www/phpvirtualbox/images/30white.png: Cannot stat: No such file or
 directory
 tar: www/phpvirtualbox/images/50px-Question_icon.svg.png: Cannot stat:
 No such file or directory
 tar: www/phpvirtualbox/images/50px-Warning_icon.svg.png: Cannot stat: No
 such file or directory
 tar: www/phpvirtualbox/images/arrow_grad_dn.png: Cannot stat: No such
 file or directory
 tar: www/phpvirtualbox/images/arrow_grad_left.png: Cannot stat: No such
 file or directory
 tar: www/phpvirtualbox/images/arrow_grad_right.png: Cannot stat: No such
 file or directory

Fixed now.

https://redports.org/changeset/21361

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.0

[Bernhard Fröhlich]

On Fri, Nov 1, 2013 at 2:36 PM, Volodymyr Kostyrko c.kw...@gmail.com wrote:
 20.10.2013 19:25, Bernhard Fröhlich wrote:

 Hi virtualbox users!


 Just one more thing that freaks me out a lot.

 I'm using host-only networking with host machine been a gateway and a
 firewall for all the guests. But:

 # rcorder /etc/rc.d/* /usr/local/etc/rc.d/* | grep
 '\(named\|dhcp\|vboxnet\)'
 /etc/rc.d/named
 /usr/local/etc/rc.d/isc-dhcpd
 /usr/local/etc/rc.d/isc-dhcpd6
 /usr/local/etc/rc.d/vboxnet

 If everything starts automatically named and dhcpd will ignore all vboxnet0
 interfaces as they are actually created after they are searched.

 Moving NETWORKING from REQUIRE to BEFORE fixes this and doesn't have any
 side effects on vboxnet startup. FILESYSTEMS and ldconfig are correct, as we
 need to launch VBoxManage to create interfaces and bring them up.

Done.
https://redports.org/changeset/21298

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

[Call for Testers] VirtualBox 4.3.6

[Bernhard Fröhlich]

Hi virtualbox users!

Almost 10 weeks have passed since the last cft with 4.3.0 and we have
made a lot of improvements since then so here we are to see what they
are worth!

I have already killed VirtualBox 4.1.x and prepared the tree for the
upcoming commit of 4.3 which will happen hopefully very soon. The
mess with FreeBSD 10.0 has also significantly improved and all relevant
patches were committed to the official portstree.
We have also pushed a lot of patches upstream already so the number
of ports patches for 4.3 has decreased a bit.

This release would not have been possible without the awesome
feedback and help on emulation@ and all people that did send patches:
Mikhail Tsatsenko, Peter Jeremy, David Morgan, Mario Lobo, Jung-uk Kim,
Daniel Lorch, William Grzybowski, Volodymyr Kostyrko.

If you are interested in helping with virtualbox maintenance and
development or have noticed a bug you can easily find us on IRC.

Changes in the Port:
- Update to 4.3.6
- Update phpvirtualbox to 4.3-1
- Fix pulseaudio option
- Adopt USES=kmod
- Convert USE_PYDISTUTILS=easy_install to USE_PYDISTUTILS=yes
- Add USE_PYTHON_BUILD=yes because if PYTHON option is disabled we could
- Fix startup order of vboxnet and move NETWORKING to BEFORE section
- Fix building with GCC from ports on 10 to correctly use libstdc++
from GCC and not from base.
- Add missing file to fix undefined symbol in kernel modules kernel:
link_elf_obj: symbol RTThreadCtxHooksAreRegistered undefined
- Disable stripping away RPATH on FreeBSD for Hardened-R3 binaries
- kBuild: Replace hardcoded freebsd strings with KBUILD_TARGET in do-install

Changes in VirtualBox 4.3:
https://www.virtualbox.org/wiki/Changelog

VirtualBox 4.3.6 Ports:
http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.3.6-20140103.tar.gz

IRC: #freebsd-vbox on Freenode

Bernhard on behalf of the VirtualBox on FreeBSD Team!

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.6

[Bernhard Fröhlich]

Am 03.01.2014 19:15 schrieb Thomas Hoffmann trh...@gmail.com:

 On Fri, Jan 3, 2014 at 10:15 AM, Bernhard Fröhlich de...@freebsd.org
wrote:

 Hi virtualbox users!

 Almost 10 weeks have passed since the last cft with 4.3.0 and we have
 made a lot of improvements since then so here we are to see what they
 are worth!

 I have already killed VirtualBox 4.1.x and prepared the tree for the
 upcoming commit of 4.3 which will happen hopefully very soon. The
 mess with FreeBSD 10.0 has also significantly improved and all relevant
 patches were committed to the official portstree.
 We have also pushed a lot of patches upstream already so the number
 of ports patches for 4.3 has decreased a bit.

 This release would not have been possible without the awesome
 feedback and help on emulation@ and all people that did send patches:
 Mikhail Tsatsenko, Peter Jeremy, David Morgan, Mario Lobo, Jung-uk Kim,
 Daniel Lorch, William Grzybowski, Volodymyr Kostyrko.

 If you are interested in helping with virtualbox maintenance and
 development or have noticed a bug you can easily find us on IRC.

 Bernhard on behalf of the VirtualBox on FreeBSD Team!

 --
 Bernhard Froehlich


 First time I've been in a position to respond to a CFT for virtualbox.
Got it installed on 10.0-RC4 and everything looks good so far. Is there
anything in particular you wanted us to test or should we just abuse it
mercilessly as we would under normal use?

No there are no specific usecases we are asking for right now. If you have
some known bugs it would be good to check if they still exist.

As usual with call for testers be carefull with your data and create
backups before use and don't put it in production.

 Also, I took the liberty of posting info on your CFT to the FreeBSD
forums. Thought that might get a few more folks involved in the testing
that would not have been otherwise. Hope that was okay.

Thanks, the more feedback the better!
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.6

[Bernhard Fröhlich]

Am 03.01.2014 19:39 schrieb Mike Tancsa m...@sentex.net:

 On 1/3/2014 10:15 AM, Bernhard Fröhlich wrote:
  - Update phpvirtualbox to 4.3-1

 Hi,
 virtualbox compiled fine, but the phpvirtualbox gives these errors

 make install gives


 ===  Building package for phpvirtualbox-4.3.1
 Creating package

/usr/home/mdtancsa/virtualbox-cft-4.3.6-20140103/www/phpvirtualbox/work/phpvirtualbox-4.3.1.tbz
 Registering depends: php5-json-5.4.23 php5-soap-5.4.23
 php5-session-5.4.23 php5-simplexml-5.4.23 php5-5.4.23 apache22-2.2.26
 apr-1.4.8.1.5.3 gdbm-1.11 gettext-0.18.3.1 libxml2-2.8.0_3
 libiconv-1.14_1 db42-4.2.52_5 mysql55-client-5.5.35 sqlite3-3.8.1
 pcre-8.33 perl5.14-5.14.4_4 expat-2.1.0.
 Creating bzip'd tar ball in

'/usr/home/mdtancsa/virtualbox-cft-4.3.6-20140103/www/phpvirtualbox/work/phpvirtualbox-4.3.1.tbz'
 tar: www/phpvirtualbox/config.php-example: Cannot stat: No such file or
 directory
 tar: www/phpvirtualbox/CHANGELOG.txt: Cannot stat: No such file or
directory
 tar: www/phpvirtualbox/GPLv3.txt: Cannot stat: No such file or directory
 tar: www/phpvirtualbox/LICENSE.txt: Cannot stat: No such file or directory
 tar: www/phpvirtualbox/README.txt: Cannot stat: No such file or directory
 tar: www/phpvirtualbox/css/jquery-ui.css: Cannot stat: No such file or
 directory
 tar: www/phpvirtualbox/css/jquery.projectPlugins.css: Cannot stat: No
 such file or directory
 tar: www/phpvirtualbox/css/layout.css: Cannot stat: No such file or
 directory
 tar: www/phpvirtualbox/css/tipped.css: Cannot stat: No such file or
 directory
 tar: www/phpvirtualbox/images/30white.png: Cannot stat: No such file or
 directory
 tar: www/phpvirtualbox/images/50px-Question_icon.svg.png: Cannot stat:
 No such file or directory
 tar: www/phpvirtualbox/images/50px-Warning_icon.svg.png: Cannot stat: No
 such file or directory
 tar: www/phpvirtualbox/images/arrow_grad_dn.png: Cannot stat: No such
 file or directory
 tar: www/phpvirtualbox/images/arrow_grad_left.png: Cannot stat: No such
 file or directory
 tar: www/phpvirtualbox/images/arrow_grad_right.png: Cannot stat: No such
 file or directory

Sorry for that, I noticed that a few minutes after sending out the cft.
It's likely something trivial and stupid.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: Problem with compat9x

[Bernhard Fröhlich]

Am 18.12.2013 20:02 schrieb Jung-uk Kim j...@freebsd.org:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 2013-12-17 05:56:01 -0500, Bernhard Fröhlich wrote:
  On Tue, Dec 17, 2013 at 12:41 AM, Jung-uk Kim j...@freebsd.org
  wrote:
  On 2013-12-16 14:57:55 -0500, Bernhard Fröhlich wrote:
 
  Yes I am aware of that and if you look at the commit history
  you will see that I have tried to fix that issue with the last
  commit. It has fixed the issue for a couple of vbox binaries
  (VBoxSVC, VBoxManage) but some are still broken. (VBoxHeadless,
  VirtualBox)
 
  The conflicts entry for compat9x was there already and I will
  need to add it again as it seems.
 
  BTW, I have a real fix for the problem, i.e., build with Clang
  (well, as much as possible).  In fact, only couple of files
  (under src/recompiler) are absolutely needed to be compiled with
  GCC in 4.3.x.  Therefore, there is no need for libstdc++.so
  dependency at all.
 
  Here are my experimental ports (based on official vbox@ ports,
  i.e., https://redports.org/browser/virtualbox/emulators)
 
  http://redports.org/browser/jkim/emulators
 
  Probably I don't understand what you want to archive but I don't
  think patching virtualbox to compile 95% of it with clang and still
  having to compile the remaining 5% with gcc is of any benefit.

 % find VirtualBox-4.3.4 -type f \( -name *.c -or -name *.cpp \) |
 wc -l
 6187
 % find VirtualBox-4.3.4/src/recompiler -type f \( -name *.c -or
 - -name *.cpp \) | wc -l
   28

 It's at least 99%. ;-)

 Seriously, my point is we need to reduce libstdc++.so dependency from
 ports tree at all cost because '-rpath' is really asking for serious
 trouble in the long run (*unless* the binary is completely
 self-contained, of course), IMHO.  I had very unpleasant experience
 with LibreOffice and I learned it the hard way.  Whatever I do with
 the port, people always complained that something is broken in a weird
 way.  Almost every time, I found some *.so from its dependencies are
 built with different C++ headers and runtime.  Imagine you have foo.so
 built with g++48 and bar.so built with g++46 and an executable built
 with libc++.so and requiring them both, directly or indirectly, for
 example.  No fun at all. :-(

Yes, I agree that it is a problem if we start mixing compilers. But wait we
are already way past that point because we introduced clang as default
compiler. There are quite a few more ports that break in strange ways
because of that mix.

  We need to carry all the clang patches in our port which makes it a
  big beast and have likely no chance to get those workarounds
  included upstream because they won't accept patches for a compiler
  that can't fully build vbox.

 Patches are not too big.  In fact, many patches are also beneficial to
 GCC build because most of them fix compiler warnings with GCC, too.  I
 don't see any problem of submitting those patches.

I have no problem to send patches which fix real problems but I don't want
us to be like debian where people push boatloads of questionable patches on
top of a 3rd party project.

 Actually, the recompiler (based on ancient QEMU) must be updated to
 remove GCC dependency in the first place, i.e., the infamous global
 register, IMHO.  FYI, recent QEMU can be built with Clang just fine.

Yes I know about that and seriously the only way to get that done is by
talking to upstream. If someone provides patches for that I would like to
see them committed upstream first. The recompiler is a core part of vbox so
I don't think we should be the testbed for such experiments just because we
like to build stuff with clang.

  The issue that this thread talks about can be fixed in a much
  simpler way. In fact the VBoxHeadless and VirtualBox binaries do
  not have a RPATH at all - so all we need to do is fix the vbox
  buildsystem to add the RPATH to those binaries too like they
  already do for VBoxSVC and VBoxManage.

 Obviously, I do not agree with the simpler fix. ;-)

It was the only fix I could provide in time for 10.0. Yes, rpath is not the
magic bullet but it gives us time to work on better fixes.

Please don't get me wrong. I am actually very happy with clang as a
compiler and I use it also for some of my own code. But I still think it is
the wrong choice for ports and we have created a lot of problems with that
which will need a lot of our attention and time in the future. We are still
depending very strong on the base compiler which we shouldn't. We are now
adding hacks and crap like that rpath stuff or even heavily patch ports -
for nothing! IMHO using a gcc48 as ports compiler would be the way to go.

(this mail is my personal opinion)
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: Problem with compat9x

[Bernhard Fröhlich]

On Tue, Dec 17, 2013 at 12:41 AM, Jung-uk Kim j...@freebsd.org wrote:
 On 2013-12-16 14:57:55 -0500, Bernhard Fröhlich wrote:

 Yes I am aware of that and if you look at the commit history you
 will see that I have tried to fix that issue with the last commit.
 It has fixed the issue for a couple of vbox binaries (VBoxSVC,
 VBoxManage) but some are still broken. (VBoxHeadless, VirtualBox)

 The conflicts entry for compat9x was there already and I will need
 to add it again as it seems.

 BTW, I have a real fix for the problem, i.e., build with Clang (well,
 as much as possible).  In fact, only couple of files (under
 src/recompiler) are absolutely needed to be compiled with GCC in
 4.3.x.  Therefore, there is no need for libstdc++.so dependency at all.

 Here are my experimental ports (based on official vbox@ ports, i.e.,
 https://redports.org/browser/virtualbox/emulators)

 http://redports.org/browser/jkim/emulators

Probably I don't understand what you want to archive but I don't think
patching virtualbox to compile 95% of it with clang and still having to
compile the remaining 5% with gcc is of any benefit. We need to carry
all the clang patches in our port which makes it a big beast and have
likely no chance to get those workarounds included upstream because
they won't accept patches for a compiler that can't fully build vbox.

The issue that this thread talks about can be fixed in a much simpler
way. In fact the VBoxHeadless and VirtualBox binaries do not have a
RPATH at all - so all we need to do is fix the vbox buildsystem to add
the RPATH to those binaries too like they already do for VBoxSVC and
VBoxManage.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: virtualbox-ose segfaults on 10.0

[Bernhard Fröhlich]

Thanks a lot for your help! I have committed a patch now that should fix this
issue once and for all.

http://svnweb.freebsd.org/ports?view=revisionrevision=336768

The analysis has shown that the vbox buildsystem has a strange check as
part of their hardening that strips away rpath for Hardened-R3
binaries. It looks
like that is supposed to protect against world writable RPATH paths which would
allow a user to inject malicious shared objects. Our gcc48 path is definitely a
safe place so I decided to disable that check for FreeBSD.

I will send that patch upstream and discuss the implications with the vbox
developers to see if that has some additional risks.


On Sat, Dec 14, 2013 at 1:25 AM, Joe Maloney jpm...@gmail.com wrote:
 [jmaloney@jm-desk-pc] ~% sudo ldd /usr/local/bin/VirtualBox
 Password:
 /usr/local/bin/VirtualBox:
 libthr.so.3 = /lib/libthr.so.3 (0x800822000)
 libstdc++.so.6 = /usr/local/lib/gcc46/libstdc++.so.6 (0x800a47000)
 libm.so.5 = /lib/libm.so.5 (0x800d4b000)
 libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x800f71000)
 libc.so.7 = /lib/libc.so.7 (0x80117e000)

 On Dec 13, 2013, at 5:02 PM, Bernhard Fröhlich de...@bluelife.at wrote:


 Am 12.12.2013 21:24 schrieb Joe Maloney jpm...@gmail.com:

 I cannot get the qt4 interface to start in FreeBSD 10.  VboxManage seems
 to work fine.  This was just tested with the latest port a few hours ago
 after Makefile change 336267 Virtualbox 4.2.20.  Below is a backtrace.

 Joe Maloney

 [jmaloney@jm-desk-pc] ~% sudo gdb /usr/local/lib/virtualbox/VirtualBox
 GNU gdb 6.1.1 [FreeBSD]
 Copyright 2004 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and you
 are
 welcome to change it and/or distribute copies of it under certain
 conditions.
 Type show copying to see the conditions.
 There is absolutely no warranty for GDB.  Type show warranty for
 details.
 This GDB was configured as amd64-marcel-freebsd...
 (gdb) run
 Starting program: /usr/local/lib/virtualbox/VirtualBox
 [New LWP 101456]
 [New Thread 801c06400 (LWP 101456/VirtualBox)]
 Type Manifest File: /root/.VirtualBox/xpti.dat
 nsNativeComponentLoader: autoregistering begins.
 nsNativeComponentLoader: autoregistering succeeded
 nNCL: registering deferred (0)
 [New Thread 801c11400 (LWP 100154/VirtualBox)]
 [New Thread 801c0b400 (LWP 101680/VirtualBox)]

 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 801c06400 (LWP 101456/VirtualBox)]
 0x in ?? ()
 (gdb) backtrace
 #0  0x in ?? ()
 #1  0x000800afc072 in __dynamic_cast (src_ptr=0x7fffc7d0,
 src_type=0x8080087c0, dst_type=0x808d1cea0, src2dst=0)
 at ../../.././../gcc-4.6.4/libstdc++-v3/libsupc++/dyncast.cc:61
 #2  0x00081142e759 in QtCurve::Style::eventFilter ()
 from /usr/local/lib/qt4/plugins/styles/qtcurve.so
 #3  0x000807c987cd in
 QCoreApplicationPrivate::sendThroughObjectEventFilters ()
 from /usr/local/lib/qt4/libQtCore.so.4
 #4  0x00080822750a in QApplicationPrivate::notify_helper ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #5  0x00080822a1f8 in QApplication::notify ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #6  0x000807c984e5 in QCoreApplication::notifyInternal ()
 from /usr/local/lib/qt4/libQtCore.so.4
 #7  0x000808266ec8 in QWidgetPrivate::propagatePaletteChange ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #8  0x00080826baa1 in QWidget::setBackgroundRole ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #9  0x00081142a33f in QtCurve::Style::polish ()
 from /usr/local/lib/qt4/plugins/styles/qtcurve.so
 #10 0x000808273e21 in QWidget::event ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #11 0x00080864567f in QMenuBar::event ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #12 0x00080822751b in QApplicationPrivate::notify_helper ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #13 0x00080822a1f8 in QApplication::notify ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #14 0x000807c984e5 in QCoreApplication::notifyInternal ()
 from /usr/local/lib/qt4/libQtCore.so.4
 #15 0x00080826965e in QWidget::ensurePolished ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #16 0x00080826970f in QWidget::ensurePolished ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #17 0x00080824f39d in QLayout::totalMinimumSize ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #18 0x000808273569 in QWidget::minimumSizeHint ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #19 0x00080548c8cc in UISelectorWindow::loadSettings
 (this=0x801ed4000)

 at
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Frontends/VirtualBox/src/selector/UISelectorWindow.cpp:135
 #20 0x000805485d4e in UISelectorWindow (this=0x801ed4000,
 ppSelf=0x805c98300, pParent=0x0, flags={i = -10976})

 at
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Frontends/VirtualBox/src/selector/UISelectorWindow.cpp:102
 #21 0x0008053d32fa in VBoxGlobal::selectorWnd (this=0x805c981e0)
 from /usr/local/lib/virtualbox/VirtualBox.so
 #22

Re: VirtualBox-4.3.4 on 10-RC1: link_elf_obj: symbol RTThreadCtxHooksAreRegistered undefined

[Bernhard Fröhlich]

Am 18.12.2013 04:03 schrieb Гуляев Гоша gosha-n...@yandex.ru:

 Hi All!
 I tryin use VirtualBox 4.3.4 on latest -STABLE
 FreeBSD home 10.0-PRERELEASE FreeBSD 10.0-PRERELEASE #0: Wed Dec 18
01:32:15 MSK 2013 user@home:/usr/obj/usr/src/sys/SERV  amd64

 pkg info | grep -i virt
 virtualbox-ose-4.3.4   A general-purpose full virtualizer for x86
hardware
 virtualbox-ose-kmod-4.3.4  VirtualBox kernel module for FreeBSD

 And when I tryin to load vboxdrv (manually or on boot) it gives an error:
 Dec 18 08:35:56 home kernel: link_elf_obj: symbol
RTThreadCtxHooksAreRegistered undefined
 Dec 18 08:35:56 home kernel: linker_load_file: Unsupported file type

 Kernel and its sources are synced.

 What can cause that error?


That bug was fixed already. I will create another call for testers soon so
you can either wait for that or:

svn co https://svn.redports.org/virtualbox

Thanks for the report!
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: ports/183739: emulators/virtualbox-ose-kmod fails to build on freebsd10/i386

[Bernhard Fröhlich]

The following reply was made to PR ports/183739; it has been noted by GNATS.

From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= de...@bluelife.at
To: bug-follo...@freebsd.org, k...@matpockuh.ru
Cc:  
Subject: Re: ports/183739: emulators/virtualbox-ose-kmod fails to build on 
freebsd10/i386
Date: Mon, 16 Dec 2013 16:59:32 +0100

 I have tried to reproduce that on FreeBSD 10.0-RC1/i386 and It seems to hav=
 e
 been fixed. Could someone please verify that?
 
 https://redports.org/buildarchive/20131216141726-28728/
 
 --=20
 Bernhard Fr=F6hlich
 http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: Problem with compat9x

[Bernhard Fröhlich]

Am 16.12.2013 19:40 schrieb Jason Bacon jwba...@tds.net:


 Are you aware that the latest VirtualBox won't start on 10.0 is compat9x
is installed?

 Compat9x is required by openjdk7, BTW.  Removing openjdk7 and compat9x
eliminates the problem.  Reinstalling them brings it back. I tried
installing virtualbox-ose using pkg and from source with the same results.

 Regards,

 Jason
 ~~

 FreeBSD oyster bacon ~/Books/Computer-books/HPC/Common 403: VirtualBox
 VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
 VirtualBox: dlopen(/usr/local/lib/virtualbox/VBoxRT.so,) failed:
/usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required by
/usr/local/lib/virtualbox/VBoxRT.so not found

 VirtualBox: Tip! It may help to reinstall VirtualBox.

 FreeBSD oyster bacon ~/Books/Computer-books/HPC/Common 408: pkg info
virtualbox-ose 'compat*'
 virtualbox-ose-4.2.20_1
 compat9x-amd64-9.2.902000.201310

 FreeBSD oyster bacon ~/Books/Computer-books/HPC/Common 409: uname -a
 FreeBSD oyster.jbacon.dyndns.org 10.0-RC1 FreeBSD 10.0-RC1 #0 r259068:
Sat Dec  7 17:45:20 UTC 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC
 amd64

Yes I am aware of that and if you look at the commit history you will see
that I have tried to fix that issue with the last commit. It has fixed the
issue for a couple of vbox binaries (VBoxSVC, VBoxManage) but some are
still broken. (VBoxHeadless, VirtualBox)

The conflicts entry for compat9x was there already and I will need to add
it again as it seems.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: virtualbox-ose-kmod not compiling under 10.0-RC1

[Bernhard Fröhlich]

Am 15.12.2013 03:12 schrieb Marcus Reid mar...@blazingdot.com:

 On Sat, Dec 14, 2013 at 09:15:53AM +0100, Bernhard Fr?hlich wrote:
  Am 14.12.2013 00:47 schrieb Marcus Reid [1]mar...@blazingdot.com:
  
   Hello,
  
   Does virtualbox-ose-kmod build for you under 10.0-RC1?  I get
   another one of those vm_map_find() got 9 expected 10 errors.
  
   Thanks,
  
   Marcus
 
  Please post the full error log


/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.2.20/out/freebsd.amd64/release/bin/src/vboxdrv/r0drv/freebsd/alloc-r0drv-freebsd.c:83:76:
error:
   too few arguments to function call, expected 10, have 9
  cbAllocated, TRUE, VM_PROT_ALL,
VM_PROT_ALL, 0);

 ^
 @/vm/vm_map.h:368:1: note: 'vm_map_find' declared here
 int vm_map_find(vm_map_t, vm_object_t, vm_ooffset_t, vm_offset_t *,
vm_size_t,
 ^
 1 error generated.
 *** Error code 1

 Stop.
 make[3]: stopped in
/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.2.20/out/freebsd.amd64/release/bin/src/vboxdrv
 *** Error code 1

 Stop.
 make[2]: stopped in
/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.2.20/out/freebsd.amd64/release/bin/src
 *** Error code 1

 Stop.
 make[1]: stopped in /usr/ports/emulators/virtualbox-ose-kmod
 *** Error code 1

 Stop.
 make: stopped in /usr/ports/emulators/virtualbox-ose-kmod


  the architecture you are running and

 FreeBSD luna 10.0-RC1 FreeBSD 10.0-RC1 #0 r259068: Sat Dec  7 17:45:20
UTC 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

  the exact version of the vbox port.

 Latest.

 emulators/virtualbox-ose: r336467
 emulators/virtualbox-ose-kmod: r336107

 Thanks,

 Marcus

This seriously looks like your kernel sources do not match the running
kernel.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: virtualbox-ose-kmod not compiling under 10.0-RC1

[Bernhard Fröhlich]

Am 14.12.2013 00:47 schrieb Marcus Reid mar...@blazingdot.com:

 Hello,

 Does virtualbox-ose-kmod build for you under 10.0-RC1?  I get another
 one of those vm_map_find() got 9 expected 10 errors.

 Thanks,

 Marcus

Please post the full error log, the architecture you are running and the
exact version of the vbox port.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [VBox] Why VirtualBox process is so large?

[Bernhard Fröhlich]

On Fri, Dec 13, 2013 at 11:02 AM, Yuri y...@rawbw.com wrote:
 I have the VM that is allocated 512MB of base memory for the guest, but its
 total memory size on host is 1263MB. This seems excessive.
 What is the normal memory overhead for the VM? Is there a way to reduce it?
 Documentation doesn't elaborate on this.

 virtualbox-4.2.18
 9.2

The used RAM is usually VM RAM + GPU RAM + (QT4 GUI) + overhead. How
did you measure those 1263MB on the host?

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [VBox] Why VirtualBox process is so large?

[Bernhard Fröhlich]

Am 13.12.2013 18:13 schrieb Yuri y...@rawbw.com:

 On 12/13/2013 02:02, Yuri wrote:

 I have the VM that is allocated 512MB of base memory for the guest, but
its total memory size on host is 1263MB. This seems excessive.
 What is the normal memory overhead for the VM? Is there a way to reduce
it?
 Documentation doesn't elaborate on this.


 512MB machine looks in ps(1) like this (linux guest):
 5717 yuri 21  200  1263M   444M select  0   9:06 88.48%
VirtualBox
 And 1024MB machine looks like this (FreeBSD guest):
 13565 yuri   18  200  1720M  1135M uwait   5  71:13 4.05%
VirtualBox

 Process sizes shouldn't be that high in both cases. My guess is that VBox
takes freedom to allocate an additional disk cache maybe? Then this should
be configurable. What other memory could this be? Leak?

 As a comparison, VMWare lists the sample overhead memories:
http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.resmgmt.doc_50%2FGUID-B42C72C1-F8D5-40DC-93D1-FB31849B1114.html
 For 1GB machine with 1CPU it would be ~26MB. We need to understand why
VBox goes so much higher.

This is a bug on your side. Please look at the ps manpage to learn about
the different columns and what they mean.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: virtualbox-ose segfaults on 10.0

[Bernhard Fröhlich]

Am 12.12.2013 21:24 schrieb Joe Maloney jpm...@gmail.com:

 I cannot get the qt4 interface to start in FreeBSD 10.  VboxManage seems
 to work fine.  This was just tested with the latest port a few hours ago
 after Makefile change 336267 Virtualbox 4.2.20.  Below is a backtrace.

 Joe Maloney

 [jmaloney@jm-desk-pc] ~% sudo gdb /usr/local/lib/virtualbox/VirtualBox
 GNU gdb 6.1.1 [FreeBSD]
 Copyright 2004 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and you
 are
 welcome to change it and/or distribute copies of it under certain
 conditions.
 Type show copying to see the conditions.
 There is absolutely no warranty for GDB.  Type show warranty for
 details.
 This GDB was configured as amd64-marcel-freebsd...
 (gdb) run
 Starting program: /usr/local/lib/virtualbox/VirtualBox
 [New LWP 101456]
 [New Thread 801c06400 (LWP 101456/VirtualBox)]
 Type Manifest File: /root/.VirtualBox/xpti.dat
 nsNativeComponentLoader: autoregistering begins.
 nsNativeComponentLoader: autoregistering succeeded
 nNCL: registering deferred (0)
 [New Thread 801c11400 (LWP 100154/VirtualBox)]
 [New Thread 801c0b400 (LWP 101680/VirtualBox)]

 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 801c06400 (LWP 101456/VirtualBox)]
 0x in ?? ()
 (gdb) backtrace
 #0  0x in ?? ()
 #1  0x000800afc072 in __dynamic_cast (src_ptr=0x7fffc7d0,
 src_type=0x8080087c0, dst_type=0x808d1cea0, src2dst=0)
 at ../../.././../gcc-4.6.4/libstdc++-v3/libsupc++/dyncast.cc:61
 #2  0x00081142e759 in QtCurve::Style::eventFilter ()
 from /usr/local/lib/qt4/plugins/styles/qtcurve.so
 #3  0x000807c987cd in
 QCoreApplicationPrivate::sendThroughObjectEventFilters ()
 from /usr/local/lib/qt4/libQtCore.so.4
 #4  0x00080822750a in QApplicationPrivate::notify_helper ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #5  0x00080822a1f8 in QApplication::notify ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #6  0x000807c984e5 in QCoreApplication::notifyInternal ()
 from /usr/local/lib/qt4/libQtCore.so.4
 #7  0x000808266ec8 in QWidgetPrivate::propagatePaletteChange ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #8  0x00080826baa1 in QWidget::setBackgroundRole ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #9  0x00081142a33f in QtCurve::Style::polish ()
 from /usr/local/lib/qt4/plugins/styles/qtcurve.so
 #10 0x000808273e21 in QWidget::event ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #11 0x00080864567f in QMenuBar::event ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #12 0x00080822751b in QApplicationPrivate::notify_helper ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #13 0x00080822a1f8 in QApplication::notify ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #14 0x000807c984e5 in QCoreApplication::notifyInternal ()
 from /usr/local/lib/qt4/libQtCore.so.4
 #15 0x00080826965e in QWidget::ensurePolished ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #16 0x00080826970f in QWidget::ensurePolished ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #17 0x00080824f39d in QLayout::totalMinimumSize ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #18 0x000808273569 in QWidget::minimumSizeHint ()
 from /usr/local/lib/qt4/libQtGui.so.4
 #19 0x00080548c8cc in UISelectorWindow::loadSettings
 (this=0x801ed4000)

 at
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Frontends/VirtualBox/src/selector/UISelectorWindow.cpp:135
 #20 0x000805485d4e in UISelectorWindow (this=0x801ed4000,
 ppSelf=0x805c98300, pParent=0x0, flags={i = -10976})

 at
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Frontends/VirtualBox/src/selector/UISelectorWindow.cpp:102
 #21 0x0008053d32fa in VBoxGlobal::selectorWnd (this=0x805c981e0)
 from /usr/local/lib/virtualbox/VirtualBox.so
 #22 0x000805367f84 in TrustedMain (argc=1, argv=0x7fffd8b8) at
 qglobal.h:1510
 #23 0x004024cb in SUPR3HardenedMain (pszProgName=0x404d14
 VirtualBox, fFlags=1, argc=1, argv=0x7fffd8b8,
 envp=0x7fffd8c8)

 at
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/HostDrivers/Support/SUPR3HardenedMain.cpp:346
 #24 0x004013cf in main (argc=1, argv=0x7fffd8b8,
 envp=0x7fffd8c8)

 at
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/src/VBox/Frontends/VirtualBox/src/hardenedmain.cpp:32

Could you please send me the output of: ldd /usr/local/binVirtualBox
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: VirtualBox errors when I try to run (dlopen(/usr/local/lib/virtualbox/VBoxRT.so, ))

[Bernhard Fröhlich]

On Sun, Dec 8, 2013 at 8:15 PM, Mark Felder f...@freebsd.org wrote:


 On Sat, Dec 7, 2013, at 2:02, Bernhard Fröhlich wrote:
 Am 06.12.2013 23:24 schrieb Eitan Adler li...@eitanadler.com:
 
  On Fri, Dec 6, 2013 at 4:04 PM, Bernhard Fröhlich de...@bluelife.at
 wrote:
  
   Am 06.12.2013 21:45 schrieb Eitan Adler li...@eitanadler.com:
  
  
  
   I get the following when try to run VirtualBox.
  
   VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
   VirtualBox: dlopen(/usr/local/lib/virtualbox/VBoxRT.so,) failed:
   /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required
   by /usr/local/lib/virtualbox/VBoxRT.so not found
  
   %pkg info -x compat9x
   compat9x-amd64-9.2.902000.201310
   %pkg info -x virtualbox
   virtualbox-ose-4.2.18_1
   virtualbox-ose-kmod-4.2.18
  
   Any ideas how for to fix this?
  
   Deinstall the compat port(s) and it will work again.
 
  I need the compat port for Java.  Is it possible to have VirtualBox
  ignore the compat libs? why is it looking their anyway?

 I think it's a similar problem as described in ports/182468 and for some
 reason rtld seems to pickup libs from compat which might be correct in
 general but it's causing problems for us.


 We discussed this in IRC the other day, Bernard. Look at the rpath (
 readelf -d )of /usr/local/lib/virtualbox/VBoxRT.so -- it's wrong. It's
 only listing /usr/local/lib/virtualbox.

 /usr/ports/emulators/virtualbox-ose  make -V LDFLAGS
  -Wl,-rpath=/usr/local/lib/gcc46

 Why aren't the virtualbox binaries ignoring those LDFLAGS?

Should be fixed in r336267 now.

http://svnweb.freebsd.org/ports?view=revisionrevision=336267

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: VirtualBox bridged network and 10.0

[Bernhard Fröhlich]

On Thu, Dec 12, 2013 at 4:45 PM, Warren Block wbl...@wonkity.com wrote:
 On Thu, 12 Dec 2013, Mikaël Urankar wrote:

 You need to have a valid /root/.VirtualBox/VirtualBox.xml file, see my
 previous mail:

 http://lists.freebsd.org/pipermail/freebsd-emulation/2013-November/011050.html


 Thank you, that works!

 I notice this file also exists on my 9.x system, with contents that indicate
 it was created by VirtualBox.  Maybe the port should create this file?

No this was a bug and it's fixed in 4.2.20_1. If you are interested in
the details:

http://svnweb.freebsd.org/ports?view=revisionrevision=336267

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: FreeBSD Port: emulators/virtualbox-ose

[Bernhard Fröhlich]

Am 11.12.2013 21:04 schrieb Mike Jakubik 
mike.jaku...@intertainservices.com:

 Hello,

 I've updated to the recent 4.2.20 version only to find a runtime error
due to libstdc++, I see the recent commit made to fix this on 10, however I
am running 9-stable and do not have compat9x installed. I wish thisport did
not need gcc to compile, it always seems to be a problem.

I can only repeat myself. It will not happen any day soon because clang
does not support global register variables and they do not seem to have any
interest to implement that.

 $ VirtualBox
 VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
 VirtualBox: dlopen(/usr/local/lib/virtualbox/VBoxRT.so,) failed:
/usr/lib/libstdc++.so.6: version GLIBCXX_3.4.15 required by
/usr/local/lib/virtualbox/VBoxRT.so not found

Your setup is very strange but it's about the same issue as on 10 as it
seems. With the update to 4.2.20 I have added a change that should add the
gcc path to the ports gcc of libstdc++.so.6 to the vbox rpath but it seems
to have no effect for you.

Could you please send me the following output just to verify:
strings /usr/lib/libstdc++.so.6 | grep GLIBCXX

On my FreeBSD 10 machine there is no such file so I wonder if that might be
a leftover file from a base update.

 $ uname -a
 FreeBSD freebsd.local 9.2-STABLE FreeBSD 9.2-STABLE #0: Wed Dec 11
13:51:20 EST 2013 mjakubik@freebsd.local:/usr/obj/usr/src/sys/FREEBSD  amd64

 $ pkg info|grep virtualbox
 virtualbox-ose-4.2.20  A general-purpose full virtualizer for x86
hardware
 virtualbox-ose-kmod-4.2.20 VirtualBox kernel module for FreeBSD

 $ pkg info|grep gcc
 gcc-4.6.4  GNU Compiler Collection 4.6

 /etc/make.comf

 WITH_CLANG_IS_CC=true
 WITHOUT_GCC=true
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: FreeBSD Port: emulators/virtualbox-ose

[Bernhard Fröhlich]

Am 11.12.2013 21:42 schrieb Mike Jakubik 
mike.jaku...@intertainservices.com:

 On 12/11/13 15:32, Bernhard Fröhlich wrote:

 I can only repeat myself. It will not happen any day soon because clang
 does not support global register variables and they do not seem to have
any
 interest to implement that.


 Got it.

 Could you please send me the following output just to verify:
 strings /usr/lib/libstdc++.so.6 | grep GLIBCXX

 $ strings /usr/lib/libstdc++.so.6 | grep GLIBCX


 GLIBCXX_3.4
 GLIBCXX_3.4.1
 GLIBCXX_3.4.2
 GLIBCXX_3.4.3
 GLIBCXX_3.4.4
 GLIBCXX_3.4.5
 GLIBCXX_3.4.6
 GLIBCXX_3.4.7
 GLIBCXX_3.4.8
 GLIBCXX_3.4.9
 GLIBCXX_FORCE_NEW

 make delete-old and delete-old-libs does not remove anything from my
system at this point, i am going to try compile again but with gcc47 this
time.

 Thanks!

That definitely is the libstdc++ from our ancient gcc 4.2 in base. Could
you try to temporary rename the so and try to start vbix again? Don't
forget to rename it afterwards if there are any binaries that still need it.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: FreeBSD Port: emulators/virtualbox-ose

[Bernhard Fröhlich]

Am 11.12.2013 22:16 schrieb Mike Jakubik 
mike.jaku...@intertainservices.com:

 On 12/11/13 15:51, Bernhard Fröhlich wrote:


 That definitely is the libstdc++ from our ancient gcc 4.2 in base. Could
you try to temporary rename the so and try to start vbix again? Don't
forget to rename it afterwards if there are any binaries that still need it.


 Renaming /usr/lib/libstdc++.so.6 addresses the problem. Do you know a way
to check if anything else might need this?

 Thank you.

You could either try manually with ldd which so a binary needs or I think
bsdadmin scrips contains some libcheck script that can check that in bulk.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: ports/182468: [patch] lang/gcc builds unrunnable emulators/virtualbox-ose

[Bernhard Fröhlich]

The following reply was made to PR ports/182468; it has been noted by GNATS.

From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= de...@bluelife.at
To: bug-follo...@freebsd.org, pe...@rulingia.com
Cc:  
Subject: Re: ports/182468: [patch] lang/gcc builds unrunnable 
emulators/virtualbox-ose
Date: Tue, 10 Dec 2013 21:46:01 +0100

 I know that what I have committed is not the ideal solution but I
 consider it the
 best I we have right now. So I take the full blame for it. I want to
 see now if it
 improves the situation and if yes then I will talk to gerald@ to provide us=
  a
 supported variable.
 
 --=20
 Bernhard Fr=F6hlich
 http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: VirtualBox errors when I try to run (dlopen(/usr/local/lib/virtualbox/VBoxRT.so, ))

[Bernhard Fröhlich]

Am 06.12.2013 23:24 schrieb Eitan Adler li...@eitanadler.com:

 On Fri, Dec 6, 2013 at 4:04 PM, Bernhard Fröhlich de...@bluelife.at
wrote:
 
  Am 06.12.2013 21:45 schrieb Eitan Adler li...@eitanadler.com:
 
 
 
  I get the following when try to run VirtualBox.
 
  VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
  VirtualBox: dlopen(/usr/local/lib/virtualbox/VBoxRT.so,) failed:
  /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required
  by /usr/local/lib/virtualbox/VBoxRT.so not found
 
  %pkg info -x compat9x
  compat9x-amd64-9.2.902000.201310
  %pkg info -x virtualbox
  virtualbox-ose-4.2.18_1
  virtualbox-ose-kmod-4.2.18
 
  Any ideas how for to fix this?
 
  Deinstall the compat port(s) and it will work again.

 I need the compat port for Java.  Is it possible to have VirtualBox
 ignore the compat libs? why is it looking their anyway?

I think it's a similar problem as described in ports/182468 and for some
reason rtld seems to pickup libs from compat which might be correct in
general but it's causing problems for us.

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/182468
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: VirtualBox errors when I try to run (dlopen(/usr/local/lib/virtualbox/VBoxRT.so, ))

[Bernhard Fröhlich]

Am 06.12.2013 21:45 schrieb Eitan Adler li...@eitanadler.com:

 I get the following when try to run VirtualBox.

 VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
 VirtualBox: dlopen(/usr/local/lib/virtualbox/VBoxRT.so,) failed:
 /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required
 by /usr/local/lib/virtualbox/VBoxRT.so not found

 %pkg info -x compat9x
 compat9x-amd64-9.2.902000.201310
 %pkg info -x virtualbox
 virtualbox-ose-4.2.18_1
 virtualbox-ose-kmod-4.2.18

 Any ideas how for to fix this?

Deinstall the compat port(s) and it will work again.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.2 : Success

[Bernhard Fröhlich]

On Mon, Dec 2, 2013 at 2:48 AM, Mario Lobo l...@bsd.com.br wrote:
 On Fri, 29 Nov 2013 14:42:49 +0100
 Mikaël Urankar mikael.uran...@gmail.com wrote:

 Hi,

 Please CC: me on replies, I am not subscribed to freebsd-emulation.

 VirtualBox-4.3.2 works fine on my environment :
 FreeBSD desktop-016.xxx 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r258424M:
 Thu Nov 21 09:54:40 CET 2013
 m...@desktop-016.xx:/usr/obj/usr/src/sys/ACHERON  amd64

 I need the following file in the root folder (if I don't put the
 Global tag I have this error message : Failed to create the
 VirtualBox COM object) :
 cat /root/.VirtualBox/VirtualBox.xml
 ?xml version=1.0?
 VirtualBox xmlns=http://www.innotek.de/VirtualBox-settings;
 version=1.12-freebsd
   Global
   /Global
 /VirtualBox

 On my user session :
  - I need to unsetenv QT_PLUGIN_PATH to prevent VirtualBox from
 segfault'ing (I'm running KDE) session
  - I've cleaned my user's VirtualBox.xml config file : I've removed
 some MachineEntry uuid that were giving me the infamous Failed to
 create the VirtualBox COM object

 Thanks for your work,
 WBR
 Mikaël
 ___
 freebsd-emulation@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
 To unsubscribe, send any mail to
 freebsd-emulation-unsubscr...@freebsd.org

 I wish i could say the same.

 I switched from FBSD 8.4 to 9.2 and still can't compile 4.3.x. 4.3.4
 doesn't even apply the patches correctly. The previous 4.3.x at least
 did that.

I wonder where you have that 4.3.4 port from. But it might be that you
have messed it up or did not use the only trustworthy source for vbox [1]
ports or just copied it over an existing port.

[1] svn co https://svn.redports.org/virtualbox

 4.2.20 doesn't compile either. It ends with this error:

 /usr/bin/ld: cannot find -ldl
 kmk: ***
 [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/VirtualBox/VirtualBox.so]
 Error 1

 Dispite my attempt to remove -ldl (which applies to only to linux,
 according to what i googled) from all occurences I could find, it
 somehow keeps sneaking in again.

There is no 4.2.20 port yet so I can't say much about that except
that I don't know how your port looks like and I can't support stuff
I don't know. If you want to fiddle around with vbox port development
please join us on IRC. (#freebsd-vbox on freenode)

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.2 : Success

[Bernhard Fröhlich]

On Tue, Dec 3, 2013 at 1:14 PM, Bernhard Fröhlich de...@freebsd.org wrote:
 On Mon, Dec 2, 2013 at 2:48 AM, Mario Lobo l...@bsd.com.br wrote:
 On Fri, 29 Nov 2013 14:42:49 +0100
 Mikaël Urankar mikael.uran...@gmail.com wrote:

 Hi,

 Please CC: me on replies, I am not subscribed to freebsd-emulation.

 VirtualBox-4.3.2 works fine on my environment :
 FreeBSD desktop-016.xxx 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r258424M:
 Thu Nov 21 09:54:40 CET 2013
 m...@desktop-016.xx:/usr/obj/usr/src/sys/ACHERON  amd64

 I need the following file in the root folder (if I don't put the
 Global tag I have this error message : Failed to create the
 VirtualBox COM object) :
 cat /root/.VirtualBox/VirtualBox.xml
 ?xml version=1.0?
 VirtualBox xmlns=http://www.innotek.de/VirtualBox-settings;
 version=1.12-freebsd
   Global
   /Global
 /VirtualBox

 On my user session :
  - I need to unsetenv QT_PLUGIN_PATH to prevent VirtualBox from
 segfault'ing (I'm running KDE) session
  - I've cleaned my user's VirtualBox.xml config file : I've removed
 some MachineEntry uuid that were giving me the infamous Failed to
 create the VirtualBox COM object

 Thanks for your work,
 WBR
 Mikaël
 ___
 freebsd-emulation@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
 To unsubscribe, send any mail to
 freebsd-emulation-unsubscr...@freebsd.org

 I wish i could say the same.

 I switched from FBSD 8.4 to 9.2 and still can't compile 4.3.x. 4.3.4
 doesn't even apply the patches correctly. The previous 4.3.x at least
 did that.

 I wonder where you have that 4.3.4 port from. But it might be that you
 have messed it up or did not use the only trustworthy source for vbox [1]
 ports or just copied it over an existing port.

 [1] svn co https://svn.redports.org/virtualbox

 4.2.20 doesn't compile either. It ends with this error:

 /usr/bin/ld: cannot find -ldl
 kmk: ***
 [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.20/out/freebsd.amd64/release/obj/VirtualBox/VirtualBox.so]
 Error 1

 Dispite my attempt to remove -ldl (which applies to only to linux,
 according to what i googled) from all occurences I could find, it
 somehow keeps sneaking in again.

Btw this has already been fixed in our development port I think.

https://redports.org/changeset/20207/virtualbox

 There is no 4.2.20 port yet so I can't say much about that except
 that I don't know how your port looks like and I can't support stuff
 I don't know. If you want to fiddle around with vbox port development
 please join us on IRC. (#freebsd-vbox on freenode)

 --
 Bernhard Froehlich
 http://www.bluelife.at/

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor

[Bernhard Fröhlich]

On Tue, Nov 26, 2013 at 3:50 PM, Matthias Apitz g...@unixarea.de wrote:

 Hello,

 After getting finally compiled and install virtualbox:

 # pkg_info | fgrep virtualbox
 virtualbox-ose-4.3.2 A general-purpose full virtualizer for x86 hardware
 virtualbox-ose-kmod-4.3.0 VirtualBox kernel module for FreeBSD

 # uname -a
 FreeBSD aurora.Sisis.de 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #1: Fri Oct 18
 12:10:57 CEST 2013 g...@aurora.sisis.de:/usr/obj/usr/src/sys/GENERIC
 i386

 The VirtualBox crashes on startup with the following bt in gdb:

 #0  0x in ?? ()
 [New Thread 28803080 (LWP 100232/VirtualBox)]
 (gdb) bt
 #0  0x in ?? ()
 #1  0x2813c10e in __dynamic_cast (src_ptr=0x289ca650,
 src_type=0x2dcc4bc0, dst_type=0x2dcc4c10, src2dst=0)
 at ../../.././../gcc-4.6.3/libstdc++-v3/libsupc++/dyncast.cc:61
 #2  0x2d9a6842 in KConfigGroup::reparent () from
 /usr/local/kde4/lib/libkdecore.so.7
 #3  0x2d99e82d in KConfigGroup::KConfigGroup () from
 /usr/local/kde4/lib/libkdecore.so.7
 #4  0x2da907c3 in KStandardDirs::addCustomized () from
 /usr/local/kde4/lib/libkdecore.so.7
 #5  0x2da82e96 in KComponentData::KComponentData () from
 /usr/local/kde4/lib/libkdecore.so.7
 #6  0x2da82c7c in KComponentData::KComponentData () from
 /usr/local/kde4/lib/libkdecore.so.7
 #7  0x2da82581 in KGlobal::findDirectChild_helper () from
 /usr/local/kde4/lib/libkdecore.so.7
 #8  0x2da81528 in KGlobal::dirs () from
 /usr/local/kde4/lib/libkdecore.so.7
 #9  0x2da815f8 in KGlobal::config () from
 /usr/local/kde4/lib/libkdecore.so.7
 #10 0x2cf295d6 in qt_plugin_instance () from
 /usr/local/kde4/lib/kde4/plugins/gui_platform/libkde.so
 #11 0x2a537711 in QApplicationPrivate::x11_apply_settings () from
 /usr/local/lib/qt4/libQtGui.so.4
 #12 0x2a53fc5d in qt_set_x11_resources () from
 /usr/local/lib/qt4/libQtGui.so.4
 #13 0x2a53d8be in qt_init () from /usr/local/lib/qt4/libQtGui.so.4
 #14 0x2a4bc1fa in QApplicationPrivate::construct () from
 /usr/local/lib/qt4/libQtGui.so.4
 #15 0x2a4bcbf6 in QApplication::QApplication () from
 /usr/local/lib/qt4/libQtGui.so.4
 #16 0x29335dc9 in TrustedMain (argc=1, argv=0xbfbfd524) at CIShared.h:52
 #17 0xbfbfd3f0 in ?? ()
 #18 0x28966200 in ?? ()
 #19 0xbfbfd490 in ?? ()
 #20 0xbfbfd524 in ?? ()
 #21 0x28829800 in ?? ()
 #22 0x in ?? ()
 (gdb)

 Any ideas?

This looks like a libstdc++ bug that is triggered by Qt and might
already be fixed
in more recent 10-stable. So please try to update to 10.0-BETA3 first.

 Btw: I have had to

 # pkg_delete -f compat8x-i386-8.4.804000.201309_1

 to get its shared lib out of the way;

Yeah that is a known issue. I guess I need to add the compat8x, 9x, 10x ports
to the conflicting list in vbox.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor

[Bernhard Fröhlich]

On Tue, Nov 26, 2013 at 4:03 PM, Matthias Apitz g...@unixarea.de wrote:
 El día Tuesday, November 26, 2013 a las 03:54:57PM +0100, Bernhard Fr?hlich 
 escribió:

 On Tue, Nov 26, 2013 at 3:50 PM, Matthias Apitz g...@unixarea.de wrote:
 
  The VirtualBox crashes on startup with the following bt in gdb:
 
  #0  0x in ?? ()
  [New Thread 28803080 (LWP 100232/VirtualBox)]
  (gdb) bt
  #0  0x in ?? ()
  #1  0x2813c10e in __dynamic_cast (src_ptr=0x289ca650,
  src_type=0x2dcc4bc0, dst_type=0x2dcc4c10, src2dst=0)
  at ../../.././../gcc-4.6.3/libstdc++-v3/libsupc++/dyncast.cc:61
  #2  0x2d9a6842 in KConfigGroup::reparent () from
  /usr/local/kde4/lib/libkdecore.so.7
  #3  0x2d99e82d in KConfigGroup::KConfigGroup () from
  /usr/local/kde4/lib/libkdecore.so.7
  #4  0x2da907c3 in KStandardDirs::addCustomized () from
  /usr/local/kde4/lib/libkdecore.so.7
  #5  0x2da82e96 in KComponentData::KComponentData () from
  /usr/local/kde4/lib/libkdecore.so.7
  #6  0x2da82c7c in KComponentData::KComponentData () from
  /usr/local/kde4/lib/libkdecore.so.7
  #7  0x2da82581 in KGlobal::findDirectChild_helper () from
  /usr/local/kde4/lib/libkdecore.so.7
  #8  0x2da81528 in KGlobal::dirs () from
  /usr/local/kde4/lib/libkdecore.so.7
  #9  0x2da815f8 in KGlobal::config () from
  /usr/local/kde4/lib/libkdecore.so.7
  #10 0x2cf295d6 in qt_plugin_instance () from
  /usr/local/kde4/lib/kde4/plugins/gui_platform/libkde.so
  #11 0x2a537711 in QApplicationPrivate::x11_apply_settings () from
  /usr/local/lib/qt4/libQtGui.so.4
  #12 0x2a53fc5d in qt_set_x11_resources () from
  /usr/local/lib/qt4/libQtGui.so.4
  #13 0x2a53d8be in qt_init () from /usr/local/lib/qt4/libQtGui.so.4
  #14 0x2a4bc1fa in QApplicationPrivate::construct () from
  /usr/local/lib/qt4/libQtGui.so.4
  #15 0x2a4bcbf6 in QApplication::QApplication () from
  /usr/local/lib/qt4/libQtGui.so.4
  #16 0x29335dc9 in TrustedMain (argc=1, argv=0xbfbfd524) at CIShared.h:52
 ...

 This looks like a libstdc++ bug that is triggered by Qt and might
 already be fixed
 in more recent 10-stable. So please try to update to 10.0-BETA3 first.

 My kernel and userland are r255948 (October 1st) and the ports are from
 r328930 (as well October 1st). Do you really think that this is to old?

Yeah there have been quite a number of fixes between ALPHA1 and BETA3.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: ports/184163: emulators/virtualbox-ose - failt port instalation

[Bernhard Fröhlich]

The following reply was made to PR ports/184163; it has been noted by GNATS.

From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= de...@bluelife.at
To: bug-follo...@freebsd.org, echaluk...@gmail.com
Cc:  
Subject: Re: ports/184163: emulators/virtualbox-ose - failt port instalation
Date: Mon, 25 Nov 2013 14:15:56 +0100

 It looks like you do not have any FreeBSD kernel sourcecode installed.
 Could you please verify that your /usr/src is not empty?
 
 --=20
 Bernhard Fr=F6hlich
 http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: ports/183085: emulators/virtualbox-ose failed to work on FreeBSD 10-BETA1

[Bernhard Fröhlich]

Am 20.11.2013 18:42 schrieb Photo stuff w-in...@xs4all.nl:

 The following reply was made to PR ports/183085; it has been noted by
GNATS.

 From: Photo stuff w-in...@xs4all.nl
 To: bug-follo...@freebsd.org, gosha-n...@yandex.ru
 Cc:
 Subject: Re: ports/183085: emulators/virtualbox-ose failed to work on
FreeBSD
  10-BETA1
 Date: Wed, 20 Nov 2013 17:49:50 +0100

  L.S.

  I can report that on FreeBSD 10.0 Beta 2, Virtualbox
  virtualbox-ose-4.2.18_1 fails with the same messages:

  
  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.
  ---

  Also, removing .Virtualbox directory which is mentioned in various
  places on the web going back for a few years, does not work for me
either.

  Starting VBoxSVC in one xterm, then typing VirtualBox in another gives
  the error message that it can't read the VirtualBox.xml. Well, of
  course if doesn't exist it can't be read.

  So creating a minimal VirtualBox.xml in the .VirtualBox directory that
  was created after the failed start, was what I tried and it worked. Even
  the most minimal one such as what Bernhard Froehlich suggested (removing
  the 2 times '3D' that I see on the bugreport via the web) works.

  I then added a virtual image etc. VirtualBox seems to work fine when the
  xml file is there.

It is really strange that this only seems to affect FreeBSD 10 and I have
no clue why. To my knowledge this code that creates the xml file has not
changed for quite a while and worked fine up to now.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: ports/182468: [patch] lang/gcc builds unrunnable emulators/virtualbox-ose

[Bernhard Fröhlich]

The following reply was made to PR ports/182468; it has been noted by GNATS.

From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= de...@bluelife.at
To: bug-follo...@freebsd.org, pe...@rulingia.com
Cc:  
Subject: Re: ports/182468: [patch] lang/gcc builds unrunnable 
emulators/virtualbox-ose
Date: Fri, 15 Nov 2013 10:57:10 +0100

 There is still a very similar error when compat8x or compat9x ports are
 installed and the patch does not seem to help in that case.
 
 VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
 VirtualBox: dlopen(/usr/local/lib/virtualbox/VBoxRT.so,) failed:
 /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15 required
 by /usr/local/lib/virtualbox/VBoxRT.so not found
 
 --=20
 Bernhard Fr=F6hlich
 http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.0: cannot reference symbol `X86TSS64_size' in preprocessor

[Bernhard Fröhlich]

On Thu, Nov 14, 2013 at 10:50 AM, Matthias Apitz g...@unixarea.de wrote:
 El día Wednesday, November 13, 2013 a las 04:40:17PM +0100, Bernhard Fr?hlich 
 escribió:

  @/usr/local/bin/kmk_redirect -wo
  /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o.dep
  -- yasm -f elf32 -DASM_FORMAT_ELF -D__YASM__ -Worphan-labels  -g dwarf2
  -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/
  -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/include/
  -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/PATM/
  -I/usr/include/ -I/usr/X11R6/include/ -I/usr/local/include/
  -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/dtrace/
  -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/
  -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/
  -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_DEBUGGER
  -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_X86 -D__X86__ -DIN_RING3
  -DHC_ARCH_BITS=32 -DGC_ARCH_BITS=64 -DIN_VMM_R3 -DIN_DIS -DIN_GMM_R3
  -DIN_DBG -DVBOX_IN_VMM -DVBOX_WITH_FIRST_IEM_STEP -DVBOX_WITH_REM
  -DVBOX_WITH_MULTI_CORE -DVBOX_WITH_PCI_PASSTHROUGH -DVBOX_WITH_SAFE_STR
  -DVBOX_WITH_RAW_RING1 -DVBOX_WITH_USB -DVBOX_WITH_PDM_ASYNC_COMPLETION
  -DVBOX_WITH_NETSHAPER -DVBOX_WITH_RAW_MODE -DVBOX_WITH_RAW_MODE_NOT_R0
  -o
  /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o
  /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/VMMR3/PATMA.asm
  -M
  ...

 We are currently investigating what is failing there and the vbox developers
 suggested to execute the failed command manually and add the option -e
 to the command line switches and post the resulting output. This would
 show the preprocessor file which is passed to yasm and would help to
 narrow it down.

 I have created a small shell script with the failing command, which does
 not give much more information:

 # sh kmk.sh
 + /usr/local/bin/kmk_redirect -wo
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o.dep
 -- yasm -f elf32 -DASM_FORMAT_ELF -D__YASM__ -Worphan-labels -g dwarf2
 -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/
 -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/include/
 -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/PATM/
 -I/usr/include/ -I/usr/X11R6/include/ -I/usr/local/include/
 -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/dtrace/
 -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/
 -I/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/
 -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_DEBUGGER
 -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_X86 -D__X86__ -DIN_RING3
 -DHC_ARCH_BITS=32 -DGC_ARCH_BITS=64 -DIN_VMM_R3 -DIN_DIS -DIN_GMM_R3
 -DIN_DBG -DVBOX_IN_VMM -DVBOX_WITH_FIRST_IEM_STEP -DVBOX_WITH_REM
 -DVBOX_WITH_MULTI_CORE -DVBOX_WITH_PCI_PASSTHROUGH -DVBOX_WITH_SAFE_STR
 -DVBOX_WITH_RAW_RING1 -DVBOX_WITH_USB -DVBOX_WITH_PDM_ASYNC_COMPLETION
 -DVBOX_WITH_NETSHAPER -DVBOX_WITH_RAW_MODE -DVBOX_WITH_RAW_MODE_NOT_R0
 -o
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.x86/release/obj/VBoxVMM/VMMR3/PATMA.o
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/VMMR3/PATMA.asm
 -M -e
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:143:
 error: (AssertCompileSizeML:2) cannot reference symbol `X86TSS16_size'
 in preprocessor
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:143:
 warning: (AssertCompileSizeML:5) X86TSS16 is 1 bytes instead of 44
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:206:
 error: (AssertCompileSizeML:2) cannot reference symbol `X86TSS64_size'
 in preprocessor
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:206:
 warning: (AssertCompileSizeML:5) X86TSS64 is 1 bytes instead of 136

 The problems are raised by these lines in the file:
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac

 struc X86TSS16
 .selPrevresw 1
 .sp0resw 1
 .ss0resw 1
 .sp1resw 1
 .ss1resw 1
 .sp2resw 1
 .ss2resw 1
 .ip resw 1
 .flags  resw 1
 .ax resw 1
 .cx resw 1
 .dx resw 1
 .bx resw 1
 .sp resw 1
 .bp resw 1
 .si resw 1
 .di resw 1
 .es resw 1
 .cs 

Re: ports/182471: emulators/virtualbox-ose gets SIGBUS with VNC

[Bernhard Fröhlich]

The following reply was made to PR ports/182471; it has been noted by GNATS.

From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= de...@bluelife.at
To: bug-follo...@freebsd.org, pe...@rulingia.com
Cc:  
Subject: Re: ports/182471: emulators/virtualbox-ose gets SIGBUS with VNC
Date: Wed, 13 Nov 2013 13:36:38 +0100

 Please try to generate a coredump and a stacktrace from it. The vbox binari=
 es
 all have uid bit set so per default FreeBSD does not generate a coredump fo=
 r
 them. You can temporary set a sysctl flag to overwrite that:
 
 sysctl kern.sugid_coredump=3D1
 
 --=20
 Bernhard Fr=F6hlich
 http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: ports/183739: emulators/virtualbox-ose-kmod fails to build on freebsd10/i386

[Bernhard Fröhlich]

The following reply was made to PR ports/183739; it has been noted by GNATS.

From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= de...@bluelife.at
To: bug-follo...@freebsd.org, k...@matpockuh.ru
Cc:  
Subject: Re: ports/183739: emulators/virtualbox-ose-kmod fails to build on 
freebsd10/i386
Date: Wed, 13 Nov 2013 16:55:19 +0100

 Could you please try to verify that this issue still exists on FreeBSD
 10.0-BETA3
 because I tried it and it worked fine. It might be that this was
 header pollution was
 fixed in the base system already.
 
 --=20
 Bernhard Fr=F6hlich
 http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.0

[Bernhard Fröhlich]

On Wed, Nov 13, 2013 at 7:08 AM, Beeblebrox zap...@berentweb.com wrote:
 Some other people are having a different issue:
 http://forums.freebsd.org/showthread.php?s=c98122338b797e16534a4716158f0381t=43174

It might be worth to try creating an default VirtualBox.xml file manually:

~/.VirtualBox/VirtualBox.xml

VirtualBox xmlns=http://www.innotek.de/VirtualBox-settings;
version=1.12-freebsd
/VirtualBox

Some people have reported that it works for them but I don't know yet
why this only seems to affect FreeBSD 10 and worked fine in the past.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.0

[Bernhard Fröhlich]

On Thu, Oct 24, 2013 at 6:02 PM, Volodymyr Kostyrko c.kw...@gmail.com wrote:
 20.10.2013 19:25, Bernhard Fröhlich wrote:

 Hi virtualbox users!

 This is again a call for testers to get some feedback before we commit
 VirtualBox 4.3 to the portstree. As usual the stable 4.2.18 port will
 still
 be available as emulators/virtualbox-ose-legacy.


 I optionized pulse (e.g ripped relevant part from old version):

 .if ${PORT_OPTIONS:MPULSEAUDIO}
 PULSEAUDIO_LIB_DEPENDS= libpulse.so:${PORTSDIR}/audio/pulseaudio
 PULSEAUDIO_CONFIGURE_ENABLE=  pulse
 .else
 CONFIGURE_ARGS+=--disable-pulse
 .endif

 Compilation seems to go on until:

 kBuild: Compiling VBoxSVC -
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:
 In function 'int getDefaultIfaceIndex(short unsigned int*, int)':
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:94:39:
 error: 'malloc' was not declared in this scope
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:98:18:
 error: 'free' was not declared in this scope
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:133:30:
 error: 'free' was not declared in this scope
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:139:14:
 error: 'free' was not declared in this scope
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:
 In function 'int NetIfList(std::listComObjPtrHostNetworkInterface )':
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:205:39:
 error: 'malloc' was not declared in this scope
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:209:18:
 error: 'free' was not declared in this scope
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:217:18:
 error: 'free' was not declared in this scope
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:291:16:
 warning: suggest explicit braces to avoid ambiguous 'else' [-Wparentheses]
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:303:14:
 error: 'free' was not declared in this scope
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:
 In function 'int NetIfGetConfigByName(PNETIFINFO)':
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:328:39:
 error: 'malloc' was not declared in this scope
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:332:18:
 error: 'free' was not declared in this scope
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:340:18:
 error: 'free' was not declared in this scope
 /tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/Main/src-server/freebsd/NetIf-freebsd.cpp:404:14:
 error: 'free' was not declared in this scope
 kmk: ***
 [/tmp/ports/home/arcade/work/vb/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxSVC/src-server/freebsd/NetIf-freebsd.o]
 Error 1

 Missing #include stdlib.h?

Thanks a lot! Mikhail has already committed fixes for both problems in our
development repository on redports.

https://svn.redports.org/virtualbox

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.0

[Bernhard Fröhlich]

On Mon, Oct 21, 2013 at 1:13 AM, Mike C. miguelmcl...@gmail.com wrote:


 On 10/20/13 17:25, Bernhard Fröhlich wrote:
 Hi virtualbox users!

 This is again a call for testers to get some feedback before we commit
 VirtualBox 4.3 to the portstree. As usual the stable 4.2.18 port will still
 be available as emulators/virtualbox-ose-legacy.

 I am not sure yet if we will be able to commit 4.3 to the tree before the
 freeze/slush for FreeBSD 10.0 but the feedback for this CFT will tell us.

 If you are interested in helping with virtualbox maintenance and
 development or have noticed a bug you can easily find us on IRC.

 This release was mainly ported and tested by Mikhail Tsatsenko so
 please join me in thanking him for the heavy lifting!

 Changes in the Port:
 - New vboxwatchdog startscript
 - Remove old cruft for FreeBSD 7.x and 8.1
 - Convert LIB_DEPENDS to new shlib format
 - Adopt OPTIONS_SUB

 Changes since VirtualBox 4.2.18:
 https://www.virtualbox.org/wiki/Changelog

 VirtualBox 4.3.0 Ports:
 http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.3.0-20131020.tar.gz

 IRC: #freebsd-vbox on Freenode

 Bernhard on behalf of the VirtualBox on FreeBSD Team!



 Fails to compile for me:

 kBuild: Compiling VBoxVMM -
 /ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/VMMR3/PATMA.asm
 /ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:143:
 error: (AssertCompileSizeML:2) cannot reference symbol `X86TSS16_size'
 in preprocessor
 /ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:143:
 warning: (AssertCompileSizeML:5) X86TSS16 is 1 bytes instead of 44
 /ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:206:
 error: (AssertCompileSizeML:2) cannot reference symbol `X86TSS64_size'
 in preprocessor
 /ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:206:
 warning: (AssertCompileSizeML:5) X86TSS64 is 1 bytes instead of 136
 kmk: ***
 [/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.o]
 Error 1
 The failing command:
 @/usr/local/bin/kmk_redirect -wo
 /ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.o.dep
 -- yasm -f elf64 -DASM_FORMAT_ELF -D__YASM__ -Worphan-labels  -g dwarf2
 -I/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/
 -I/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/include/
 -I/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/PATM/
 -I/usr/include/ -I/usr/X11R6/include/ -I/usr/local/include/
 -I/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/dtrace/
 -I/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/ 
 -I/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/
 -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_DEBUGGER
 -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_AMD64 -D__AMD64__ -DIN_RING3
 -DHC_ARCH_BITS=64 -DGC_ARCH_BITS=64 -DPIC -DIN_VMM_R3 -DIN_DIS
 -DIN_GMM_R3 -DIN_DBG -DVBOX_IN_VMM -DVBOX_WITH_FIRST_IEM_STEP
 -DVBOX_WITH_REM -DVBOX_WITH_MULTI_CORE -DVBOX_WITH_PCI_PASSTHROUGH
 -DVBOX_WITH_SAFE_STR -DVBOX_WITH_RAW_RING1 -DVBOX_WITH_USB
 -DVBOX_WITH_PDM_ASYNC_COMPLETION -DVBOX_WITH_NETSHAPER
 -DVBOX_WITH_RAW_MODE -DVBOX_WITH_RAW_MODE_NOT_R0 -o
 /ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.o
 /ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/VMMR3/PATMA.asm
 -M
 kmk: *** Deleting file
 `/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.o'
 kmk: ***
 [/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.o]
 Deleting file
 `/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.lst'
 *** Error code 2

 Stop.
 make[2]: stopped in /data/ports/emulators/virtualbox-ose
 *** Error code 1

 Stop.
 make[1]: stopped in /data/ports/emulators/virtualbox-ose
 *** Error code 1

 Stop.

We are currently investigating what is failing there and the vbox developers
suggested to execute the failed command manually and add the option -e
to the command line switches and post the resulting output. This would
show the preprocessor file which is passed to yasm and would help to
narrow it down.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.0

[Bernhard Fröhlich]

We are currently investigating what is failing there and the vbox developers
suggested to execute the failed command manually and add the option -e
to the command line switches and post the resulting output. This would
show the preprocessor file which is passed to yasm and would help to
narrow it down.

On Mon, Nov 11, 2013 at 2:33 PM, Mario Lobo l...@bsd.com.br wrote:
 How about these? Any clues?
 I've been trying to figure this out for days and I'm still stuck.

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

 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:143:
 error: (AssertCompileSizeML:2) cannot reference symbol `X86TSS16_size' in
 preprocessor
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:143:
 warning: (AssertCompileSizeML:5) X86TSS16 is 1 bytes instead of 44
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:206:
 error: (AssertCompileSizeML:2) cannot reference symbol `X86TSS64_size' in
 preprocessor
 /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/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.0/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.o]
 Error 1

 Thanks,

 Mario Lobo

 2013/11/9 Mike C. miguelmcl...@gmail.com



 On 11/09/13 07:00, Bernhard Fröhlich wrote:
 
  Am 04.11.2013 16:35 schrieb Mike C. miguelmcl...@gmail.com
  mailto:miguelmcl...@gmail.com:
 
 
 
  On 11/04/13 09:21, Volodymyr Kostyrko wrote:
   02.11.2013 22:11, Mike C. wrote:
   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?
  
  
   I used the same options to compile and it and the include change, I
   was
   able to compile and install, but I still get the same problem with
  4.2...
   I need to run VirtualBox with root or sudo -u myuser...
  
   Have you added your user to vboxusers group? What kind of errors you
   see? Is kernel module loaded?
  
 
  the user in the vboxusers and kernel modules are loaded.
 
  Its a very weird behavior, because with sudo -u myuser I still using my
  regular user!
 
  What I guess is a segfault
  pid 2941 (VirtualBox), uid 1001: exited on signal 11
 
  gdb:
  Copying output to gdb.txt.
  (gdb) run
  Starting program: /usr/local/bin/VirtualBox
  (no debugging symbols found)...[New LWP 100371]
  VirtualBox: Error -10 in SUPR3HardenedMain!
  VirtualBox: Effective UID is not root (euid=1001 egid=1001 uid=1001
  gid=1001)
 
  This is it! Please have a look at /usr/local/lib/virtualbox and
  /usr/local/bin/VirtualBox and check that they are owned by root and the
  suid bit is set. I don't know yet who is stripping that but it could be
  that you are building the port as non-root or the ports staging does
  something stupid.
 

 I'M building with root and the permissions are the default (this was
 reported before several times, its not just with 4.3, 4.2 had the same
 behavior with FreeBSD10)

 -rwsr-xr-x  1 root  vboxusers  27712 Nov  2 17:15
 /usr/local/lib/virtualbox/VirtualBox


 lrwxr-xr-x  1 root  wheel  36 Nov  2 17:15 /usr/local/bin/VirtualBox -
 /usr/local/lib/virtualbox/VirtualBox

 Thanks

 --
 ___
 freebsd-emulation@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
 To unsubscribe, send any mail to
 freebsd-emulation-unsubscr...@freebsd.org




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



-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.0

[Bernhard Fröhlich]

Am 04.11.2013 16:35 schrieb Mike C. miguelmcl...@gmail.com:



 On 11/04/13 09:21, Volodymyr Kostyrko wrote:
  02.11.2013 22:11, Mike C. wrote:
  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?
 
 
  I used the same options to compile and it and the include change, I was
  able to compile and install, but I still get the same problem with
4.2...
  I need to run VirtualBox with root or sudo -u myuser...
 
  Have you added your user to vboxusers group? What kind of errors you
  see? Is kernel module loaded?
 

 the user in the vboxusers and kernel modules are loaded.

 Its a very weird behavior, because with sudo -u myuser I still using my
 regular user!

 What I guess is a segfault
 pid 2941 (VirtualBox), uid 1001: exited on signal 11

 gdb:
 Copying output to gdb.txt.
 (gdb) run
 Starting program: /usr/local/bin/VirtualBox
 (no debugging symbols found)...[New LWP 100371]
 VirtualBox: Error -10 in SUPR3HardenedMain!
 VirtualBox: Effective UID is not root (euid=1001 egid=1001 uid=1001
 gid=1001)

This is it! Please have a look at /usr/local/lib/virtualbox and
/usr/local/bin/VirtualBox and check that they are owned by root and the
suid bit is set. I don't know yet who is stripping that but it could be
that you are building the port as non-root or the ports staging does
something stupid.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: Building on Freebsd-10.0

[Bernhard Fröhlich]

On Wed, Oct 30, 2013 at 2:15 AM, Sam Fourman Jr. sfour...@gmail.com wrote:
 On Oct 29, 2013 8:51 PM, Karol Barski ka...@barski.eu wrote:

 Hi,

 I've tried to build emulators/virtualbox-ose-additions port on
 FreeBSD-10.0-BETA2 with no success.
 After while of searching I found out that problem is that virtualbox links
 to libsupc++ and in FreeBSD default std C++ library used in libcxxrt.

 In attachement You can find corrected Makefile which solved situation for
 me.

 Basically in post-patch target in makefile I'm replacing of supc++ to
 cxxrt
 for makefiles in worktree which linked it when OSVERSION is greater than
 1000.
 I have tested this only on FreeBSD-10.0-BETA1 and FreeBSD-10.0-BETA2.

 ---
 .if ${OSVERSION}  100
 @${REINPLACE_CMD} -e 's|supc\+\+|cxxrt|' ${WRKSRC}/Config.kmk \
  ${WRKSRC}/src/VBox/Additions/x11/VBoxClient/Makefile.kmk
 .endif
 


 Just for refrence, I have the same issues on HEAD and 10.x I can't get vbox
 in a usable state, even on a fresh install.
 It seems vbox is completley broken on anything that isn't 9.2

That is true to some degree. I try to keep vbox compile properly on 10 but since
I do not have a proper 10 box to really do runtime testing it stays as
it is unless
I migrate my laptop to 10 or someone other steps up to look into the issues.

It is a chicken and egg problem and the only way to solve that is by
volunteering
or at least helping with _proper_ bug reports. Up to now the only bugreports for
10 that I have are too less technical that anyone could look deepter
into it without
reproducing it.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

[Call for Testers] VirtualBox 4.3.0

[Bernhard Fröhlich]

Hi virtualbox users!

This is again a call for testers to get some feedback before we commit
VirtualBox 4.3 to the portstree. As usual the stable 4.2.18 port will still
be available as emulators/virtualbox-ose-legacy.

I am not sure yet if we will be able to commit 4.3 to the tree before the
freeze/slush for FreeBSD 10.0 but the feedback for this CFT will tell us.

If you are interested in helping with virtualbox maintenance and
development or have noticed a bug you can easily find us on IRC.

This release was mainly ported and tested by Mikhail Tsatsenko so
please join me in thanking him for the heavy lifting!

Changes in the Port:
- New vboxwatchdog startscript
- Remove old cruft for FreeBSD 7.x and 8.1
- Convert LIB_DEPENDS to new shlib format
- Adopt OPTIONS_SUB

Changes since VirtualBox 4.2.18:
https://www.virtualbox.org/wiki/Changelog

VirtualBox 4.3.0 Ports:
http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.3.0-20131020.tar.gz

IRC: #freebsd-vbox on Freenode

Bernhard on behalf of the VirtualBox on FreeBSD Team!

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.3.0

[Bernhard Fröhlich]

Am 20.10.2013 19:19 schrieb Гуляев Гоша gosha-n...@yandex.ru:


 20.10.2013, 22:25, Bernhard Fröhlich de...@freebsd.org:

 Hi virtualbox users!

 This is again a call for testers to get some feedback before we commit
 VirtualBox 4.3 to the portstree. As usual the stable 4.2.18 port will
still
 be available as emulators/virtualbox-ose-legacy.

 I am not sure yet if we will be able to commit 4.3 to the tree before the
 freeze/slush for FreeBSD 10.0 but the feedback for this CFT will tell us.

 If you are interested in helping with virtualbox maintenance and
 development or have noticed a bug you can easily find us on IRC.

 This release was mainly ported and tested by Mikhail Tsatsenko so
 please join me in thanking him for the heavy lifting!

 Changes in the Port:
 - New vboxwatchdog startscript
 - Remove old cruft for FreeBSD 7.x and 8.1
 - Convert LIB_DEPENDS to new shlib format
 - Adopt OPTIONS_SUB

 Changes since VirtualBox 4.2.18:
 https://www.virtualbox.org/wiki/Changelog

 VirtualBox 4.3.0 Ports:

http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.3.0-20131020.tar.gz

 IRC: #freebsd-vbox on Freenode

 Bernhard on behalf of the VirtualBox on FreeBSD Team!

 --
 Bernhard Froehlich
 http://www.bluelife.at/
 ___
 freebsd-emulation@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
 To unsubscribe, send any mail to 
freebsd-emulation-unsubscr...@freebsd.org

 Hi Bernhard!
 There is my unsuccessfull report: It stops on pulseAudio search.
 For what VirtualBox needed pulseAudio? Can it be optional?
 If pulseaudio must be present, is it possible to add it as
auto-installing dependency?

Pulse audio is an optional dependency and off per default I think. It might
be a typo in the option conversation.

 My OS:
 uname -a
 FreeBSD BSD-VBOX 10.0-BETA1 FreeBSD 10.0-BETA1 #0: Thu Oct 17 22:04:29
MSK 2013 mike@BSD-VBOX:/usr/obj/usr/src/sys/BSDSERV amd64
 Thanks for your work!

 == ERROR LOG ==
 === Running ldconfig
 /sbin/ldconfig -m /usr/local/lib
 === Registering installation for libvpx-1.1.0 as automatic
 Installing libvpx-1.1.0... done
 === Returning to build of virtualbox-ose-4.3.0
 === virtualbox-ose-4.3.0 depends on shared library: glib-2.0 - found
 === virtualbox-ose-4.3.0 depends on shared library: pcre - found
 === virtualbox-ose-4.3.0 depends on shared library: IDL-2.0 - found
 === Configuring for virtualbox-ose-4.3.0
 === FreeBSD 10 autotools fix applied to
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/configure
 === FreeBSD 10 autotools fix applied to
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/RDP/client/configure
 === FreeBSD 10 autotools fix applied to
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/libs/xpcom18a4/nsprpub/configure
 === FreeBSD 10 autotools fix applied to
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/libs/libpng-1.2.8/configure
 === FreeBSD 10 autotools fix applied to
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/libs/liblzf-3.4/configure
 === FreeBSD 10 autotools fix applied to
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/libs/zlib-1.2.6/configure
 === FreeBSD 10 autotools fix applied to
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/libs/libxml2-2.6.31/configure
 === FreeBSD 10 autotools fix applied to
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/libs/libxml2-2.6.31/aclocal.m4
 === FreeBSD 10 autotools fix applied to
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/libs/libxml2-2.6.31/acinclude.m4
 Checking for environment: Determined build machine: freebsd.amd64, target
machine: freebsd.amd64, OK.
 Checking for kBuild: found, OK.
 Checking for gcc: found version 4.6.3, OK.
 Checking for Open Watcom:
 ** Open Watcom was not found!
 Checking for iasl: found version 20130823, OK.
 Checking for xslt: found, OK.
 Checking for mkisofs: found mkisofs 3.00 (amd64-unknown-freebsd10.0)
Copyright (C) 1993-1997 Eric Youngdale (C) 1997-2010 Jrg Schilling, OK.
 Checking for pthread: found, OK.
 Checking for libxml2: found version 2.8.0, OK.
 Checking for libIDL: found version 0.8.14, OK.
 Checking for ssl: found version OpenSSL 1.0.1e-freebsd 11 Feb 2013, OK.
 Checking for libcurl: found version 7.32.0, OK.
 Checking for libvpx: found version 1.1.0, OK.
 Checking for zlib: found version 1.2.8, OK.
 Checking for libpng: found version 1.5.17, OK.
 Checking for Python support: found version 2.7.5, OK.
 Checking for Java support: OK.
 Checking for PulseAudio:
 pulse not found at -I/usr/local/include -L/usr/local/lib -lpulse or pulse
headers not found
 Check the file
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/configure.log for
detailed error information.
 Check
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/configure.log for
details
 === Script configure failed unexpectedly.
 Please report the problem to v

Re: [Call for Testers] VirtualBox 4.3.0

[Bernhard Fröhlich]

Am 21.10.2013 01:13 schrieb Mike C. miguelmcl...@gmail.com:



 On 10/20/13 17:25, Bernhard Fröhlich wrote:
  Hi virtualbox users!
 
  This is again a call for testers to get some feedback before we commit
  VirtualBox 4.3 to the portstree. As usual the stable 4.2.18 port will
still
  be available as emulators/virtualbox-ose-legacy.
 
  I am not sure yet if we will be able to commit 4.3 to the tree before
the
  freeze/slush for FreeBSD 10.0 but the feedback for this CFT will tell
us.
 
  If you are interested in helping with virtualbox maintenance and
  development or have noticed a bug you can easily find us on IRC.
 
  This release was mainly ported and tested by Mikhail Tsatsenko so
  please join me in thanking him for the heavy lifting!
 
  Changes in the Port:
  - New vboxwatchdog startscript
  - Remove old cruft for FreeBSD 7.x and 8.1
  - Convert LIB_DEPENDS to new shlib format
  - Adopt OPTIONS_SUB
 
  Changes since VirtualBox 4.2.18:
  https://www.virtualbox.org/wiki/Changelog
 
  VirtualBox 4.3.0 Ports:
 
http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.3.0-20131020.tar.gz
 
  IRC: #freebsd-vbox on Freenode
 
  Bernhard on behalf of the VirtualBox on FreeBSD Team!
 


 Fails to compile for me:

 kBuild: Compiling VBoxVMM -

/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/VMMR3/PATMA.asm

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

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

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

/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/iprt/x86extra.mac:206:
 warning: (AssertCompileSizeML:5) X86TSS64 is 1 bytes instead of 136
 kmk: ***

[/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.o]
 Error 1
 The failing command:
 @/usr/local/bin/kmk_redirect -wo

/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.o.dep
 -- yasm -f elf64 -DASM_FORMAT_ELF -D__YASM__ -Worphan-labels  -g dwarf2

-I/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/

-I/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/include/

-I/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/PATM/
 -I/usr/include/ -I/usr/X11R6/include/ -I/usr/local/include/

-I/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/dtrace/
 -I/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/include/
-I/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/
 -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_DEBUGGER
 -DRT_OS_FREEBSD -D__FREEBSD__ -DRT_ARCH_AMD64 -D__AMD64__ -DIN_RING3
 -DHC_ARCH_BITS=64 -DGC_ARCH_BITS=64 -DPIC -DIN_VMM_R3 -DIN_DIS
 -DIN_GMM_R3 -DIN_DBG -DVBOX_IN_VMM -DVBOX_WITH_FIRST_IEM_STEP
 -DVBOX_WITH_REM -DVBOX_WITH_MULTI_CORE -DVBOX_WITH_PCI_PASSTHROUGH
 -DVBOX_WITH_SAFE_STR -DVBOX_WITH_RAW_RING1 -DVBOX_WITH_USB
 -DVBOX_WITH_PDM_ASYNC_COMPLETION -DVBOX_WITH_NETSHAPER
 -DVBOX_WITH_RAW_MODE -DVBOX_WITH_RAW_MODE_NOT_R0 -o

/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.o

/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/src/VBox/VMM/VMMR3/PATMA.asm
 -M
 kmk: *** Deleting file

`/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.o'
 kmk: ***

[/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.o]
 Deleting file

`/ram/data/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.0/out/freebsd.amd64/release/obj/VBoxVMM/VMMR3/PATMA.lst'
 *** Error code 2

 Stop.
 make[2]: stopped in /data/ports/emulators/virtualbox-ose
 *** Error code 1

 Stop.
 make[1]: stopped in /data/ports/emulators/virtualbox-ose
 *** Error code 1

 Stop.

Could you please tell me on which FreeBSD version and architecture that
happens and which compiler is used?
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: VirtualBox not working on 10-Beta1

[Bernhard Fröhlich]

Am 17.10.2013 21:21 schrieb Гуляев Гоша gosha-n...@yandex.ru:

Hi!

I have a troubles with VirtualBox on my PC:

Hardware: 8Gb RAM , Intel Core Quad 6300

OS: FreeBSD 10-Beta1 AMD64 (today's svnup'ed and rebuilded world and
kernel)

uname -a: FreeBSD BSD-VBOX 10.0-BETA1 FreeBSD 10.0-BETA1 #0: Thu Oct 17
22:04:29 MSK 2013 mike@BSD-VBOX:/usr/obj/usr/src/sys/BSDSERV amd64

I do:

1. svnup system sources

2. steps to buildworld and install it

3. Install VirtualBox 4.2.18

options for install: DBUS, UDPTUNNEL, VNC

4. add to /boot/loader.conf

vboxdrv_load=YES

5. add to /etc/rc.conf

vboxnet_enable=YES

dbus_enable=YES

6. add my user to vboxusers

7. after reboot:

kldstat | grep -i vbox

3 3 0x80aa3000 51400 vboxdrv.ko
4 2 0x80c12000 29c0 vboxnetflt.ko
7 1 0x80c2 3f30 vboxnetadp.ko

8. When I try to do something with VboxManage, I get that error:

VboxManage list ostypes

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.

9.cat ~/.VirtualBox/VBoxSVC.log
VirtualBox XPCOM Server 4.2.18_OSE r88780 freebsd.amd64 (Oct 17 2013
22:49:51) release log
00:00:00.000869 main Log opened 2013-10-17T17:27:38.818569000Z
00:00:00.000901 main OS Product: FreeBSD
00:00:00.000914 main OS Release: 10.0-BETA1
00:00:00.000926 main OS Version: FreeBSD 10.0-BETA1 #0: Thu Oct 17
22:04:29 MSK 2013 mike@BSD-VBOX:/usr/obj/usr/src/sys/BSDSERV
00:00:00.000939 main Host RAM: 8181MB total, 8040MB available
00:00:00.000946 main Executable: /usr/local/lib/virtualbox/VBoxSVC
00:00:00.000948 main Process ID: 838
00:00:00.000950 main Package type: BSD_64BITS_GENERIC (OSE)

What I do wrong or it is problem with 10-Stable?

It sounds more like a problem that we usually see when you start vbox as
root which leaves some files in /tmp root permissions. But it's really hard
to make a good guess without an proper error message.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: Virtualbox Settings don't show any window (FreeBSD-10 current)

[Bernhard Fröhlich]

Sorry but I forgot one important thing - please rebuild the virtualbox-ose
port with debug option enabled.

Am 25.09.2013 16:35 schrieb Miguel Clara miguelmcl...@gmail.com:

 Here it goes (I'm not sure if this is the expected output though, because
I see a permission denied there...
 The file permission for VirtualBox are odd, and if I change then it won't
run at all.


 % gdb /usr/local/lib/virtualbox/VirtualBox VirtualBox.core
 GNU gdb 6.1.1 [FreeBSD]
 Copyright 2004 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and you
are
 welcome to change it and/or distribute copies of it under certain
conditions.
 Type show copying to see the conditions.
 There is absolutely no warranty for GDB. Type show warranty for details.
 This GDB was configured as
amd64-marcel-freebsd.../usr/local/lib/virtualbox/VirtualBox: Permission
denied.

 Core was generated by `VirtualBox'.
 Program terminated with signal 11, Segmentation fault.
 #0 0x in ?? ()
 (gdb) backtrace
 #0 0x in ?? ()
 #1 0x000800afd042 in ?? ()
 #2 0x000801dda9c0 in ?? ()
 #3 0x7fffacf0 in ?? ()
 #4 0x in ?? ()


 On Wed, Sep 25, 2013 at 11:06 AM, Bernhard Fröhlich de...@freebsd.org
wrote:

 On Wed, Sep 25, 2013 at 3:44 AM, Miguel C. miguelmcl...@gmail.com
wrote:
 
  Alpha 2 is not an option, please see:
http://lists.freebsd.org/pipermail/freebsd-current/2013-September/044792.html
 
  However I've updated to r255788, recompiled and now I get a
Segmentation fault trying to run VirtualBox...var/messages only shows that
the process exited on signal 11... where else can I see more info?

 Signal 11 is SIGSEGV (segmentation violation) so a coredump and
stacktrace
 would help. Since virtualbox is a suid root binary no coredump is
created per
 default.

 You need to set:

 sysctl kern.sugid_coredump=1

 and then start virtualbox and let it crash. Then you should get a
coredump that
 you can open with gdb and obtain a stacktrace.

 Something like:
 gdb /usr/local/lib/virtualbox/VirtualBox VirtualBox.core
 in the interactive prompt type: backtrace and send us the stacktrace.

 --
 Bernhard Froehlich
 http://www.bluelife.at/


___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: qemu-devel - no kvm accelerator

[Bernhard Fröhlich]

Am 07.09.2013 17:39 schrieb Beeblebrox zap...@berentweb.com:

  You need to install virtualbox-ose on the Host and
 virtualbox-ose-additions inside FreeBSD guests

 I'm aware of that - the problem is, currently my host and guest are the
same
 machine and I want to be able to share files between host/guest FreeBSD
and
 vm-run O/S. There's a very simple way I'm sure.

There is no way to be both vbox host and guest at the same time with the
same kernel. The kernel modules for host and guest share the same
codebase/symbols/locks which is asking for trouble and unsupported from
upstream.

  The virtualbox-ose port has an VNC option which privides a VNC server
per
  VM that you can connect to.
 My question was: How does the client boot into awareness that it should
look
 for the VNC server? Where is the VNC server preference or per-VM selection
 boot-loader provided? What is being used: direct PXE/Grub/BTX? You can't
 just turn on your laptop and magically connect to the VM by VNC...

Sorry but I really don't understand your configuration and needs so you
either need to describe what you have and what you want or the only help
that I can provide are generic tips and technical info.

That vnc option enables a vnc server per vm that exports the console for
that vm. It can be configured via the GUI on which port the vnc server
should listen and authentication stuff. From the vm side there is no extra
configuration or support required. You can connect to the vnc port as soon
as the vm is running and will get the same output as in the Qt GUI. For
detailed configuration please have a look at the vbox handbook.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: Virtualbox deadlocks on starting guest

[Bernhard Fröhlich]

I would start by updating to the latest virtualbox version and please
make sure that the
virtualbox-ose-kmod port is compiled with DEBUG option enabled. This
will add debugging
symbols to the kernel module.
Then it would be good to obtain a kernel stacktrace via a kernel
crashdump or break to the
kernel debugger when the deadlock happens. Probably you need to
recompile your kernel
with those debugging knobs:

http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-deadlocks.html

Btw do you run BHyVe and VirtualBox on the same machine? This sounds
like the beginning
of lot's of problems. You could try to unload all byhve kernel modules
and see if the
problem still persists after that.


On Mon, Jul 8, 2013 at 5:14 AM, hiren panchasara
hiren.panchas...@gmail.com wrote:
 Anyone? any pointers to debug this?

 cheers,
 Hiren

 On Sat, Jul 6, 2013 at 12:28 PM, hiren panchasara
 hiren.panchas...@gmail.com wrote:
 Hi all,

 I have:

 flymockour-l7% uname -a
 FreeBSD flymockour-l7.corp.yahoo.com 10.0-CURRENT FreeBSD 10.0-CURRENT
 #4 r252757M: Thu Jul  4 23:06:03 PDT 2013
 r...@flymockour-l7.corp.yahoo.com:/usr/obj/usr/home/hirenp/head/sys/GENERIC
  amd64
 flymockour-l7%
 flymockour-l7% pkg info | grep -i virtualbox
 virtualbox-ose-4.2.14_1A general-purpose full virtualizer for
 x86 hardware
 virtualbox-ose-kmod-4.2.14 VirtualBox kernel module for FreeBSD
 flymockour-l7%
 flymockour-l7% groups
 wheel operator vboxusers fuse

 flymockour-l7% kldstat | grep -i vbox
 121 0x82a6 519b8vboxdrv.ko
 flymockour-l7% kldstat | grep -i vmm
 111 0x828dd000 182c50   vmm.ko
 flymockour-l7%

 I start virtualbox as myself (not root) from cli and whenever I try to
 launch any guest (be it freebsd, ubuntu or windows) laptop deadlocks
 right away and I have to hard reset.

 This has been happening for many months but now I have decided to sit
 down and fix it.

 I believe I am missing something simple as I do not see any other such 
 reports.

 cheers,
 Hiren
 ___
 freebsd-emulation@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
 To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: virtualbox-ose: problem after update to 4.2.14

[Bernhard Fröhlich]

Am 24.06.2013 19:41 schrieb Mark Felder f...@feld.me:



 On Mon, Jun 24, 2013, at 12:36, kalth...@googlemail.com wrote:
 
  Is anybody having similar problems?
 

 Yes, just tried to reproduce this and it certainly is a problem. You
 can't drag the bar to change memory nor can you type in the text box.
 This is a rather large regression.

 CC'd vbox@

Thanks, I will talk to upstream and see if we need to add a fix for the
port or reroll the release.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [PATCH] VLAN trunking support in VirtualBox vboxnetflt

[Bernhard Fröhlich]

Thanks a lot for the fix! I've added it to the kmod port in our
testing repository
and it will be included in the next update for vbox 4.1.14.

https://redports.org/changeset/13816

On Sun, May 26, 2013 at 6:17 PM, Landon Fuller land...@plausible.coop wrote:
 Hello,

 This patch has been in the vbox kmod port for some time now, and I've been 
 running it without incident; however, I recently ran into a configuration 
 that the patch does not correctly handle:
 - A single host interface (eg, em0) bridged to a VM
 - VLANs also configured on the host interface (em0.vlan0, em0.vlan1)

 The packet flow in this situation should be:
 - The ng filter is handed a packet from em0
 - The filter re-adds the VLAN header to the top of the packet and 
 strips the M_VLANTAG flag
 - After passing to the virtual switch, the packet is re-injected into 
 the host via ether_demux().
 - ether_demux() extracts the embedded VLAN tag and hands the packet 
 off to vlan_input_p().

 As it turns out, ether_demux() does not handle frames with embedded VLAN 
 tags, and at this point, the packet is dropped, rather than being routed to 
 the host's VLAN handling:
 
 http://lists.freebsd.org/pipermail/freebsd-net/2011-October/030201.html

 The result is as follows:
 - Packets received via the host interface are handled correctly.
 - Packets (including VLAN tagged packets) are passed to sub-VMs 
 correctly.
 - Packets that *should* be handled by vlan* sub-interfaces on the 
 host are never received by those interfaces as they're dropped in 
 ether_demux().

 This worked in my existing configuration because the host and the VMs 
 actually use two different VLAN trunks (em0 and em1), and so em0 packets 
 being dropped after injection into the virtual switch does not affect the 
 host's handling of packets on em1.

 I've attached an updated patch that should resolve this issue; I'm currently 
 testing it locally on my home deployment and so far it is working fine. The 
 patch simply restores the VLAN flags and stripped ethernet header after 
 injecting the packet into the virtual ethernet switch. With this change in 
 place, ether_demux() correctly hands the packet off to vlan_input_p().

 Cheers,
 Landon




 On Apr 13, 2012, at 2:51 PM, Landon J Fuller land...@plausible.coop wrote:

 Howdy,

 I was looking into trunking VLANs into a virtual machine via bridging, and 
 noted that transmit of 802.1q tagged packets worked from the guest VM, but 
 upon reception, the VLAN tag seemed to be stripped before the packets hit 
 the guest's interface.

 Taking a look at the netgraph-based bridging implementation, it looks like 
 the VLAN tag is not being re-inserted at the head of the ethernet frame 
 prior to handing off the to VirtualBox, and VBox doesn't seem to have an 
 equivalent 'ether_vtag' field in its INTNETSG struct to handle this.

 Thus, to preserve the VLAN tag, I modified vboxNetFltFreeBSDMBufToSG() to 
 ether_vlanencap() to insert the VLAN tag before handing off to VBox. With 
 this in place, I was able to successfully trunk VLANs to a virtual machine.

 Some caveats:
   - If using virtio-kmod's if_vtnet, you must set vlanhwfilter (or 
 promisc) flags on the guest interface before virtualbox will pass the VLAN 
 tagged packets through. Otherwise, the VBox virtio-net device implementation 
 will filter out the incoming packets before handing them to the VM hardware.
   - VBox's em(4) host implementation does not appear to support 
 'hardware' VLAN tagging, but it does declare it. If using a em(4) 
 virtualized NIC, you must set -vlanhwtag on the guest interface.

 I welcome someone(s) with more experience than I eyeballing the (tiny) 
 attached patch. I'm also especially concerned as to whether this should be 
 considered supported functionality in VBox, or I'm just getting lucky with 
 the virtio-net code path.

 Thanks,
 Landon

 patch-src-VBox-HostDrivers-VBoxNetFlt-freebsd-VBoxNetFlt-freebsd.c___
 freebsd-emulation@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
 To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org


 ___
 freebsd-emulation@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
 To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org



-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: VirtualBox unable to start guests

[Bernhard Fröhlich]

Am 30.05.2013 16:17 schrieb Denny Lin dennyli...@hs.ntnu.edu.tw:

 Hi,

 I installed VirtualBox 4.2.12 on 10-CURRENT amd64 (default options
 except NLS is disabled). Guests won't start even though vboxdrv.ko has
 been loaded. I've tried both FreeBSD 9.1 and MINIX.

 The error log shows:
 00:00:12.519373 AssertLogRel
/tmpfs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.12/src/VBox/HostDrivers/Support/SUPLib.cpp(1726)
int supLoadModuleResolveImport(RTLDRMODINTERNAL*, const char*, const char*,
unsigned int, RTUINTPTR*, void*): NULL
 00:00:12.519380 VMMR0.r0 is importing SUPSemEventSignal which we couldn't
find
 00:00:12.519652 pdmR3LoadR0U: pszName=VMMR0.r0 rc=VERR_SYMBOL_NOT_FOUND
szErr=supLoadModule returned VERR_SYMBOL_NOT_FOUND
 00:00:12.519663 VMSetError:
/tmpfs/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.2.12/src/VBox/VMM/VMMR3/VM.cpp(602)
int vmR3CreateU(UVM*, uint32_t, int (*)(VM*, void*), void*);
rc=VERR_SYMBOL_NOT_FOUND
 00:00:12.519667 VMSetError: Failed to load VMMR0.r0
 00:00:12.519749 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005)
aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console}
aText={Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND)}, preserve=false
 00:00:12.520097 Using XKB for keycode to scan code conversion
 00:00:12.526110 Power up failed (vrc=VERR_SYMBOL_NOT_FOUND,
rc=NS_ERROR_FAILURE (0X80004005))

 Any help would be greatly appreciated.

It looks pretty obvious what went wrong:

00:00:12.519380 VMMR0.r0 is importing SUPSemEventSignal which we couldn't
find

So I would start looking in /var/log/messages and then grep the vbox code
for that SUPSemEventSignal function and have a look at the build logs just
in case something went unnoticed.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [VBOX] Failure while attaching the physical hard drive to the guest

[Bernhard Fröhlich]

Am 04.05.2013 03:20 schrieb Yuri y...@rawbw.com:

 I have a Linux guest with VDI hard drive.
 I want to attach the physical (on host) hard drive to this guest.

 So I created the ada3.vmdk pointing to /dev/ada3:
 VBoxManage internalcommands createrawvmdk -filename ada3.vmdk -rawdisk
/dev/ada3
 Then I ran this command to attach ada3.vmdk to the machine Mint-mate-32:
 VBoxManage storageattach Mint-mate-32 --storagectl SATA --port 1
--device 0 --type hdd --medium /home/yuri/VirtualBox
VMs/Mint-mate-32/ada3.vmdk

 This added another HardDrive in Mint-mate-32.vbox:
 HardDisk uuid={408da1c6-8939-42d3-a03b-da6d3c4d36ad}
location=ada3.vmdk format=VMDK type=Normal/
 And also this hard drive's description under StorageController
name=SATA type=AHCI PortCount=2 useHostIOCache=false
Bootable=true IDE0MasterEmulationPort=0 IDE0SlaveEmulationPort=1
IDE1MasterEmulationPort=2 IDE1SlaveEmulationPort=3:
  AttachedDevice type=HardDisk port=1 device=0
 Image uuid={408da1c6-8939-42d3-a03b-da6d3c4d36ad}/
   /AttachedDevice

 However, this machine fails to start now: VERR_ACCESS_DENIED on ada3.vmdk
 No further explanation, except NS_ERROR_FAILURE (0x80004005)
 Log provides no further insight also.

 Hard drive is recognized by the host system as:
 ada3 at ahcich7 bus 0 scbus7 target 0 lun 0
 ada3: WDC WD1600BEVT-22ZCT0 11.01A11 ATA-8 SATA 2.x device
 ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
 ada3: Command Queueing enabled
 ada3: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C)

 How can I get information what the error actually is?
 Is such operation reasonable? Is it supposed to work?

 Yuri

My first guess is that permissions for /dev/ada3 are not sufficient for
your vbox user.
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: ports/174976: fix for IPv6 port setting

[Bernhard Fröhlich]

I've just committed your patch to the vbox testing repository.

http://redports.org/changeset/11692

On Tue, Apr 16, 2013 at 5:01 PM, Stefan Bethke s...@lassitu.de wrote:
 With the following patch, VirtualBox uses the vrde properties VNCAddress4, 
 VNCAddress6, VNCPort4, and VNCPort6, and passes their values to libvncserver. 
  For example:
 $ VBoxManage modifyvm Ubuntu --vrdeproperty VNCPort4=5902
 $ VBoxManage modifyvm Ubuntu --vrdeproperty VNCPort6=5902

 --
 Stefan Bethke s...@lassitu.de   Fon +49 151 14070811



-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: VirtualBox with FreeBSD Guest: custom kernel

[Bernhard Fröhlich]

Am 15.04.2013 05:13 schrieb Marc Fournier scra...@hub.org:


 Are there any optimizations suggested for running FreeBSD Guest within
VirtualBox on a FreeBSD Host?   Not running X in there or anything, just a
straight shell …

It is probably hidden too good to find it easily.

https://wiki.freebsd.org/VirtualBox/Tuning
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: 9.1 AMD64 multitasking efficiency low

[Bernhard Fröhlich]

On Mon, Feb 11, 2013 at 4:48 PM, CeDeROM cede...@tlen.pl wrote:
 On Mon, Feb 11, 2013 at 4:41 PM, Bernhard Fröhlich de...@freebsd.org wrote:
 You can try to switch to emulators/virtualbox-ose-legacy which is
 VirtualBox 4.1.x
 just to rule out that this is a vbox regression. Just be sure to power
 down the VMs
 first.
 It would be interesting to watch if the machine starts to swap when that is 
 all
 running.

 Hello Bernhard, thank you for your hints, I can try with VBox 4.1, but
 first I will try to get rid of the Ext2 from my system. On another
 machine I have switched to UFS2 and the speed increased noticably. I
 will let you know when I transfer all of those GB of data :-)

 Yes it looks like the cause of the hangup is the swap rush/deadlock
 but I could not verify it as the machine was unresponsive. Still both
 machines use 1GB of RAM per VM so still 2GB should be free. With other
 applications running and the OS taking 1GB itself (what I have seen on
 some other posts) this may happen :-(

VBox itself also needs some RAM and the emulated Graphics Card which
can easily be 128M per VM.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: incorrect usage of callout_reset in vbox 4.2.4 ?

[Bernhard Fröhlich]

On Thu, Dec 13, 2012 at 2:08 PM, Andriy Gapon a...@freebsd.org wrote:

 It looks like in timer-r0drv-freebsd.c the code tries to pass absolute time 
 as a
 timeout parameter to callout_reset while that function actually expects 
 relative
 time (period).

 I am testing the following patch, but I am sure that the code can be made more
 efficient.

 --- timer-r0drv-freebsd.c.orig  2012-12-12 20:13:27.623202784 +0200
 +++ timer-r0drv-freebsd.c   2012-12-12 20:19:43.368202795 +0200
 @@ -172,15 +172,16 @@
  /*
   * Calc when it should start firing.
   */
 -u64First += RTTimeNanoTS();
 +const uint64_t u64Now = RTTimeNanoTS();
 +u64First += u64Now;

  pTimer-fSuspended = false;
  pTimer-iTick = 0;
  pTimer-u64StartTS = u64First;
  pTimer-u64NextTS = u64First;

 -tv.tv_sec  =  u64First / 10;
 -tv.tv_usec = (u64First % 10) / 1000;
 +tv.tv_sec  =  (u64First - u64Now) / 10;
 +tv.tv_usec = ((u64First - u64Now) % 10) / 1000;
  callout_reset(pTimer-Callout, tvtohz(tv), rtTimerFreeBSDCallback, 
 pTimer);

  return VINF_SUCCESS;
 @@ -247,8 +248,8 @@
  if (pTimer-u64NextTS  u64NanoTS)
  pTimer-u64NextTS = u64NanoTS + RTTimerGetSystemGranularity() / 
 2;

 -tv.tv_sec = pTimer-u64NextTS / 10;
 -tv.tv_usec = (pTimer-u64NextTS % 10) / 1000;
 +tv.tv_sec = (pTimer-u64NextTS - u64NanoTS) / 10;
 +tv.tv_usec = ((pTimer-u64NextTS - u64NanoTS) % 10) / 1000;
  callout_reset(pTimer-Callout, tvtohz(tv), rtTimerFreeBSDCallback, 
 pTimer);
  }

What is your results from that tests? Is the patch correct so should we include
it into the port?

-- 
Bernhard Fröhlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.2.0

[Bernhard Fröhlich]

On Fri, Sep 21, 2012 at 4:43 PM, Daniel Braniss da...@cs.huji.ac.il wrote:
 I install vboxdrv.ko in /usr/local/modules via:
 cd virtualbox-ose-kmod
 make KMODDIR=/usr/local/modules install
 but when installing in virtualbox-ose
 there is no KMODDIR, and hence make install fails

Sorry for that very long response time. I have made a patch that should fix that
issue but haven't yet tested it so if you can please give that a try.

https://github.com/decke/freebsd-vbox/commit/cd1a793d24fb27525830275bea5cce2cfb4eb3fd

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: VirtualBox-4.2.4: guest crashes when USB device is shared with it: Assertion Expression: PDMCritSectIsOwner

[Bernhard Fröhlich]

I've added it to our list of known problems.
https://redports.org/wiki/Users/virtualbox/todo

On Fri, Nov 9, 2012 at 8:59 AM, Yuri y...@rawbw.com wrote:
 I have amd64 host with Ubuntu 64bit guest. It is very stable without USB
 sharing. But once I do, machine crashes after 5-30 minutes.
 See the log below.
 During crashes shared USB device was likely active.

 Yuri


 --- end of guest log ---
 00:00:35.198316 Guest Additions capability report: (0x5) seamless: yes,
 hostWindowMapping: no, graphics: yes
 00:00:35.199866 Initializing X11 clipboard backend
 00:00:35.412590 Shared clipboard: starting shared clipboard thread
 01:08:25.861539 VUSB: attached '00081b407700[proxy 04e8:6860]' to port 2
 01:20:06.101018
 01:20:06.101020 !!Assertion Failed!!
 01:20:06.101021 Expression:
 PDMCritSectIsOwner(pOhci-pDevInsR3-pCritSectRoR3)
 01:20:06.101023 Location  :
 /usr/home/yuri/vbox/emulators/virtualbox-ose/work/VirtualBox-4.2.4/src/VBox/Devices/USB/DevOHCI.cpp(2505)
 bool ohciRhXferError(VUSBIROOTHUBPORT*, VUSBURB*)

 ___
 freebsd-emulation@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
 To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org



-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.2.4

[Bernhard Fröhlich]

On Wed, Nov 7, 2012 at 4:21 AM, Brandon Gooch
jamesbrandongo...@gmail.com wrote:
 On Tue, Oct 30, 2012 at 2:16 AM, Bernhard Fröhlich de...@freebsd.org wrote:
 Hi virtualbox users!

 This is again a call for testers to get some feedback before we commit
 VirtualBox 4.2 to the portstree. If you already run VirtualBox 4.2.0 you
 should definitely update to 4.2.4 because they fixed quite a few serious
 bugs upstream.

 Our plan is still to commit 4.2 to the portstree as soon as FreeBSD 9.1
 is out the door.

 If you are interested in helping with virtualbox maintenance and
 development or have noticed a bug you can easily find us on IRC.


 Please update devel/kBuild-devel before updating any of the virtualbox
 ports and ensure that your Kernel sources match your running kernel
 before building the virtualbox-ose-kmod port.

 Changes since VirtualBox 4.1:
 https://www.virtualbox.org/wiki/Changelog

 VirtualBox 4.2.4 and 4.1.22 (legacy) Ports:
 http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.2.4-20121030.tar.gz

 IRC: #freebsd-vbox on Freenode


 Bernhard on behalf of the new VirtualBox on FreeBSD Team!

 --
 Bernhard Froehlich
 http://www.bluelife.at/

 I've updated to 4.2.4 on my system running HEAD. I've hit one annoying issue.

 I've been running the 4.2.0 Call for Testing for a while now, and it
 worked very well.

 After updating to 4.2.4 and updating the guest additions on several
 Linux guests, I've found that 3D acceleration is broken. The guest on
 which I didn't update the guest additions (so it's still running
 version 4.2.0 guest additions),  3D acceleration works great.

 This is a nuisance on systems which had some form of compositing
 enabled (e.g. compiz) because the login process (GDM in this case)
 just spins indefinitely waiting on (I presume) the window manager to
 fire up.

 Anyone else seeing this?

Hm haven't checked that recently. The only thing that changed between 4.2.0
and 4.2.2 from FreeBSD side was that we have enabled DRM in the additions
for FreeBSD guests but that should not affect Linux guests at all.

I will check if I can reproduce that.

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.2.4

[Bernhard Fröhlich]

On Fr.,   2. Nov. 2012 10:29:55 CET, Bâkır EMRE bakir.e...@tubitak.gov.tr 
wrote:

  On 2012-10-30 04:16, Bernhard Fröhlich wrote:
   Hi virtualbox users!
   
   This is again a call for testers to get some feedback before we
   commit VirtualBox 4.2 to the portstree. If you already run
   VirtualBox 4.2.0 you should definitely update to 4.2.4 because they
   fixed quite a few serious bugs upstream.
   
   Our plan is still to commit 4.2 to the portstree as soon as FreeBSD
   9.1 is out the door.
   
   If you are interested in helping with virtualbox maintenance and
   development or have noticed a bug you can easily find us on IRC.
   
   
   Please update devel/kBuild-devel before updating any of the
   virtualbox ports and ensure that your Kernel sources match your
   running kernel before building the virtualbox-ose-kmod port.
   
   Changes since VirtualBox 4.1:
   https://www.virtualbox.org/wiki/Changelog
   
   VirtualBox 4.2.4 and 4.1.22 (legacy) Ports:
   
   http://people.freebsd.org/~decke/virtualbox/virtualbox-cft-4.2.4-20121030.tar.gz

   
   
   IRC: #freebsd-vbox on Freenode
   
   
   Bernhard on behalf of the new VirtualBox on FreeBSD Team! 
 virtualbox 4.2.4 still working with my previous VMs, butVBoxHeadless 
 doesn't support VNC in 4.2.4.
 
 libvncserver installed
 
 [root@VBOX ~]pkg_info |grep vnc
 libvncserver-0.9.9_2 Provide an easy API to write one's own vnc server
 
 anxd my config parameters are same in 4.2.4 and 4.1.22 versions
 
 [root@VBOX /usr/ports/emulators/virtualbox-ose]# make
 ===   License GPLv2 accepted by the user
 ===   Found saved configuration for virtualbox-ose-4.2.4
 ===   Extracting for virtualbox-ose-4.2.4
 = SHA256 Checksum OK for VirtualBox-4.2.4.tar.bz2.
 ===   Patching for virtualbox-ose-4.2.4
 ===   Applying FreeBSD patches for virtualbox-ose-4.2.4
 ===     virtualbox-ose-4.2.4 depends on executable: yasm - found
 ===     virtualbox-ose-4.2.4 depends on executable: as86 - found
 ===     virtualbox-ose-4.2.4 depends on executable: xsltproc - found
 ===     virtualbox-ose-4.2.4 depends on executable: kmk - found
 ===     virtualbox-ose-4.2.4 depends on executable: gtar - found
 ===     virtualbox-ose-4.2.4 depends on executable: soapcpp2 - found
 ===     virtualbox-ose-4.2.4 depends on file: 
 /usr/local/bin/easy_install-2.7 - found
 ===     virtualbox-ose-4.2.4 depends on file: /usr/local/bin/python2.7 - 
 found
 ===     virtualbox-ose-4.2.4 depends on executable: pkgconf - found
 ===     virtualbox-ose-4.2.4 depends on executable: cdrecord - found
 ===     virtualbox-ose-4.2.4 depends on shared library: png15 - found
 ===     virtualbox-ose-4.2.4 depends on shared library: xslt.2 - found
 ===     virtualbox-ose-4.2.4 depends on shared library: curl.6 - found
 ===     virtualbox-ose-4.2.4 depends on shared library: dbus-1.3 - found
 ===     virtualbox-ose-4.2.4 depends on shared library: vncserver.0 -
 found ===     virtualbox-ose-4.2.4 depends on shared library: glib-2.0.0
 - found ===     virtualbox-ose-4.2.4 depends on shared library: IDL-2.0 -
 found
 
 After building virtualbox-ose-4.2.4, VBoxHeadless doesn't offer vnc
 support
 
 [root@VBOX ~]# VBoxHeadless
 Oracle VM VirtualBox Headless Interface 4.2.4_OSE
 (C) 2008-2012 Oracle Corporation
 All rights reserved.
 
 Usage:
         -s, -startvm, --startvm name|uuid     Start given VM (required
 argument)       -v, -vrde, --vrde on|off|config             Enable (default) 
 or
 disable   the VRDE
 ...
 
 
 But old version have vnc support with same compile options
 
 [root@VBOX ~]# VBoxHeadless
 Oracle VM VirtualBox Headless Interface 4.1.22_OSE
 (C) 2008-2012 Oracle Corporation
 All rights reserved.
 
 Usage:
         -s, -startvm, --startvm name|uuid     Start given VM (required
 argument)       -n, --vnc                                                     
     Enable the built in
 VNC server       -m, --vncport port                                   TCP 
 port number to
 use for the   VNC server
         -o, --vncpass pw                                       Set the VNC 
server password
         -v, -vrde, --vrde on|off|config             Enable (default) or 
disable 
 the VRDE

vnc support has been changed and is a proper vbox plugin now. It uses the VRDE 
interface which is also used by the binary VRDP plugin and now also shares the 
same configuration.

-- 
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org

Re: [Call for Testers] VirtualBox 4.2.4

[Bernhard Fröhlich]

On Wed, Oct 31, 2012 at 8:42 AM, Mike Jakubik
mike.jaku...@intertainservices.com wrote:
 On 2012-10-30 08:07 PM, Jason Andresen wrote:

 On Oct 30, 2012, at 15:56, Bernhard Fröhlich de...@freebsd.org wrote:

 Clang does not support global registered variables so it's not supposed
 to
 work.


 Is this a feature?  Is there a reason why clang couldn't be updated
 to support this if actual software is using it?


 It is a feature, but it appears to be a dirty one. Below is a link to a
 supposed Apple developer explaining the lack of this feature. I'm not a
 programmer but a humble sysadmin, so i do not know if this is true.

 http://nondot.org/sabre/LLVMNotes/GlobalRegisterVariables.txt


That problem also prevents QEMU from being build correctly with LLVM.

I'm just quoting the LLVM Users Manual:

clang does not support global register variables; this is unlikely to be
implemented soon because it requires additional LLVM backend support.

http://clang.llvm.org/docs/UsersManual.html

-- 
Bernhard Froehlich
http://www.bluelife.at/
___
freebsd-emulation@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org