Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: VirtualBox 3.0 Beta 2 Brings SMP Performance Boosts

  1. #11
    Join Date
    Jan 2008
    Posts
    772

    Default

    Quote Originally Posted by Yfrwlf View Post
    If vbox uses Wine libraries then they have to [contribute patches back to Wine] by copyright law.
    No, they don't. Per the GPL, they need only provide corresponding source code alongside any binaries that they distribute (or provide the "written offer to distribute", which seems to not be used very often); there is no requirement that they send anything back upstream. Stallman has even criticized such a requirement in other licenses.

  2. #12
    Join Date
    Jul 2008
    Location
    Germany
    Posts
    651

    Default

    But its not an Bug vom my system its a bug in VB. Its works with vmware(player, server), Qemu(KVM), vbox 2.1.4 and lower. on 2.2.0 and higher linux 64bit works fine to but only windows not. Currently i can only use vmware.

    Quote Originally Posted by deanjo View Post
    Well XP64 guest's most certainly do boot fine in vbox (got it running in a X2, Phenom and Phenom II systems). The issue you are having here looks almost identical to one I experienced with vbox months back. Turned out (after many hours of long distance with Asus engineering) that the board I was using had a BIOS issue. AMD-V was "enabled" in the bios but would only work with the built in IGP. If a add in card was used it would disable the amd-v support but still say it was enabled in the bios settings. A BIOS update corrected it once the issue was found.

  3. #13

    Default

    Quote Originally Posted by Louise View Post
    In this regards, doesn't the GPL just say that if you use or make changes to GPL code, you have to release the source?

    What I meant was, it would be cool if SUn submitted patches back to WINE, so the fixes that Sun makes doesn't end only in Virtual Box.
    The wine 3d code sun imported is just in their svn repository (see d3d8/d3d9/wined3d at http://www.virtualbox.org/browser/tr.../Graphics/Wine). They haven't done anything to our 3D code except for adding a sun license header to it. The libraries make use of all the wined3d to wgl porting I did and have done nothing special themselves except for bundling the dlls.

    It would certainly be nice though if they would free some of their developers to work with us to improve WineD3D. It would help both Wine and VirtualBox a lot.
    Last edited by Thunderbird; 06-26-2009 at 05:01 AM.

  4. #14
    Join Date
    May 2007
    Location
    Third Rock from the Sun
    Posts
    6,583

    Default

    Quote Originally Posted by Nille View Post
    But its not an Bug vom my system its a bug in VB. Its works with vmware(player, server), Qemu(KVM), vbox 2.1.4 and lower. on 2.2.0 and higher linux 64bit works fine to but only windows not. Currently i can only use vmware.
    You can't use VMWare for judging if AMD-V is correctly enabled in the bios. It will fall back to software emulation (more accurately fall back to binary translation) upon a AMD-V failure. If you want to check to see if it is a BIOS issue or not and you have 64-bit windows installed try running the AMD Hyper-V ready test. It will accurately tell you if your system has a fully functional AMD-V bios or not.

    You can see the bug report here.

    http://www.virtualbox.org/ticket/2290

    and the test here:

    http://support.amd.com/us/Processor_...ck_Utility.zip
    Last edited by deanjo; 06-26-2009 at 10:20 AM.

  5. #15
    Join Date
    Jul 2008
    Location
    Germany
    Posts
    651

    Default

    Its 100% an Bug in VirtualBox. I have say the Problem exsist since VirtualBox 2.2.X and only Windows guests are broken. About Software fallback this is only for 32bit Guests aviable and not for 64bit but my Linux 64bit guests works fine. About the Tool by AMD it say its enable and the Tool from Vmware say its enable and working. In the past all Windows 64bit are woking but after updating to VirtualBox 2.2.X they broken.

    http://img193.imageshack.us/img193/5690/amdv.png

    I know my english is horibile but i hope now its clear

    Quote Originally Posted by deanjo View Post
    You can't use VMWare for judging if AMD-V is correctly enabled in the bios. It will fall back to software emulation (more accurately fall back to binary translation) upon a AMD-V failure. If you want to check to see if it is a BIOS issue or not and you have 64-bit windows installed try running the AMD Hyper-V ready test. It will accurately tell you if your system has a fully functional AMD-V bios or not.

    You can see the bug report here.

    http://www.virtualbox.org/ticket/2290

    and the test here:

    http://support.amd.com/us/Processor_...ck_Utility.zip

  6. #16
    Join Date
    Jul 2008
    Posts
    565

    Default

    Quote Originally Posted by Thunderbird View Post
    The wine 3d code sun imported is just in their svn repository (see d3d8/d3d9/wined3d at http://www.virtualbox.org/browser/tr.../Graphics/Wine). They haven't done anything to our 3D code except for adding a sun license header to it. The libraries make use of all the wined3d to wgl porting I did and have done nothing special themselves except for bundling the dlls.

    It would certainly be nice though if they would free some of their developers to work with us to improve WineD3D. It would help both Wine and VirtualBox a lot.
    OK OK yes you are all right, wasn't thinking, but yes if they make modification, it'd be nice for them to upload it back to Wine as well. Glad someone is keeping an eye on VB's file stores then just in case they forget about submitting any improvements back to the Wine project.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •