[vbox-dev] API changes in 4.3

[Ian Moore]

Thanks for the clarification of UnrestrictedExecution. The problems with
IMedium->variant and IMedium->capabilities went away after a reboot.
Strange though, still.

--Ian


On Tue, Oct 15, 2013 at 4:55 PM, Alexey Eromenko <al4321 at gmail.com> wrote:

> UnrestrictedExecution refers to 16-bit hardware virtualization on
> newer Intel CPUs. (2nd gen Core iSomethingMeaningless [2600])
>
> HWVirtExProperty... I don't about it. I'm not aware of shared VT-x, so
> it seems to be always exclusive. Basically you can't run MS VirtualPC
> and VBox sametime on Windows hosts or KVM and VBox on Linux hosts.
>
> On Tue, Oct 15, 2013 at 2:52 PM, Ian Moore <imooreyahoo at gmail.com> wrote:
> > Hello,
> >
> > It looks like there is an undocumented change. HWVirtExProperty
> 'Exclusive'
> > no longer exists and 'UnrestrictedExecution' is now present. Should I
> assume
> > that Exclusive is now named UnrestrictedExecution?
> >
> > It also looks like IMedium->variant and IMedium->capabilities are broken
> via
> > vboxwebsrv. If I understand correctly, this should return an array of
> long
> > values that correspond to the enumeration mappings. Instead, these
> appear to
> > return an array of strings. Here is the raw soap request and response:
> >
> >             [__last_request] => <?xml version="1.0" encoding="UTF-8"?>
> > <SOAP-ENV:Envelope
> > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:ns1="http://www.virtualbox.org/
> "><SOAP-ENV:Body><ns1:IMedium_getVariant><_this>518fcea9b848e314-00000000000004cf</_this></ns1:IMedium_getVariant></SOAP-ENV:Body></SOAP-ENV:Envelope>
> >
> >             [__last_response] => <?xml version="1.0" encoding="UTF-8"?>
> > <SOAP-ENV:Envelope
> > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > xmlns:vbox="http://www.virtualbox.org/
> "><SOAP-ENV:Body><vbox:IMedium_getVariantResponse><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Diff</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><ret!
>
>  urnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval></vbox:IMedium_getVariantResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
> >         )
> >
> > Not only is it an array of strings, but there are many duplicates.
> >
> > IMedium->capabilities exhibits similar behavior. Then again, I may be
> doing
> > something wrong.
> >
> > --Ian
> >
> > _______________________________________________
> > vbox-dev mailing list
> > vbox-dev at virtualbox.org
> > https://www.virtualbox.org/mailman/listinfo/vbox-dev
> >
>
>
>
> --
> -Alexey Eromenko "Technologov"
>
> _______________________________________________
> vbox-dev mailing list
> vbox-dev at virtualbox.org
> https://www.virtualbox.org/mailman/listinfo/vbox-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20131015/817bf4f8/attachment.html>