On Fri, Apr 26, 2013 at 10:11 PM, Michael Thayer
wrote:
>> On 26/04/13 20:16, Vladimir Filipović wrote:
>>> Is there a straightforward way to build VBox on one platform,
>>> targeting another? Specifically, I'm trying to build the Mac version
>>> in a Linux environment.
>>
>> Short answer: no, tho
On 26/04/13 21:41, Michael Thayer wrote:
> On 26/04/13 20:16, Vladimir Filipović wrote:
>> Is there a straightforward way to build VBox on one platform,
>> targeting another? Specifically, I'm trying to build the Mac version
>> in a Linux environment.
>>
>> At a very superficial read, the ./configu
Hello Vladimir,
On 26/04/13 20:16, Vladimir Filipović wrote:
> Is there a straightforward way to build VBox on one platform,
> targeting another? Specifically, I'm trying to build the Mac version
> in a Linux environment.
>
> At a very superficial read, the ./configure script seems to make
> assum
Hi,
Is there a straightforward way to build VBox on one platform,
targeting another? Specifically, I'm trying to build the Mac version
in a Linux environment.
At a very superficial read, the ./configure script seems to make
assumptions that the build environment will also be the running
environme
I guess that explains that indeed. I think I've tried disabling the TCP seg
offload months ago but I just can't remember exactly.
Regardless, thank you for your reply - at least it's not just me.
On 26 April 2013 15:32, Ivo Smits wrote:
> Hello Max,
>
> There was apparently a bug in the VirtIO
Hello Max,
There was apparently a bug in the VirtIO code, which has just been fixed
in VirtualBox 4.2.12 (according to the changelog,
https://www.virtualbox.org/wiki/Changelog). I recently discovered my
VirtIO network interfaces were slow as well, probably because of the
same bug. Still runni