On 18/12/2010, at 9:25 AM, Matthias Bolte wrote: > 2010/12/17 Matthias Bolte <matthias.bolte@xxxxxxxxxxxxxx>: >> This series makes the VirtualBox driver work on Windows. >> >> On non-Windows systems VirtualBox uses XPCOM, on Windows it uses MSCOM >> (Microsoft COM). XPCOM and MSCOM are slightly different. This series >> adds a new glue layer for MSCOM. >> >> The main difference is the representation of arrays. A new vboxArray >> type hides the differences from the general driver code. >> >> I've tested this with the 3.x series of VirtualBox. Testing with 2.x >> revealed that 2.x and 3.x represent IIDs differently. This problem is >> not fixed by this series and will need some additional work. Therefore, >> the VirtualBox driver only works with the 3.x series on Windows for now. >> >> VirtualBox 4.x seems to stay in line with the 3.x COM API. I expect it >> to work properly on Windows once we've added general support for it. >> >> Matthias >> > > I've pushed the whole series now. Thanks again to Eric for his fast review :) Hey good work. People have asked about VBox support on Windows now that we're putting together a windows installer. I was thinking it might take a while, so this is very welcome. :) -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list