[prev in list] [next in list] [prev in thread] [next in thread]
List: vbox-dev
Subject: Re: [vbox-dev] API changes in 4.3
From: Ramshankar <ramshankar.venkataraman () oracle ! com>
Date: 2013-10-16 7:41:07
Message-ID: 525E4313.8090406 () oracle ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
The VT-x/AMD-V Exclusive setting allows VirtualBox to exclusive use
hardware virtualization and not share it with other parallel hypervisors
in the system (i.e. expected to run simultaneously with VirtualBox).
Exclusive is the default for Linux and Solaris hosts (has always been
this way). On Windows and OS X hosts, VirtualBox, by default, is
configured such that it can be run in parallel with other hypervisors
*provided* the other hypervisor also shares the hardware virtualization
resource in a compatible manner.
Regards,
Ram.
On 10/16/2013 03:40 AM, Ian Moore wrote:
> 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@gmail.com
> <mailto:al4321@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@gmail.com
> <mailto:imooreyahoo@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_getVariantRespo \
> nse><returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standar \
> d</returnval><returnval>Standard</returnval><returnval>Standard</returnval><returnva \
> l>Standard</returnval><returnval>Standard</returnval><returnval>Standard</returnval> \
> <returnval>Standard</returnval><returnval>Standard</returnval><returnval>Standard</r \
> eturnval><returnval>Standard</returnval><returnval>Standard</returnval><returnval>St \
> andard</returnval><returnval>Standard</returnval><returnval>Standard</returnval><ret \
> urnval>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@virtualbox.org <mailto:vbox-dev@virtualbox.org>
> > https://www.virtualbox.org/mailman/listinfo/vbox-dev
> >
>
>
>
> --
> -Alexey Eromenko "Technologov"
>
> _______________________________________________
> vbox-dev mailing list
> vbox-dev@virtualbox.org <mailto:vbox-dev@virtualbox.org>
> https://www.virtualbox.org/mailman/listinfo/vbox-dev
>
>
>
>
> _______________________________________________
> vbox-dev mailing list
> vbox-dev@virtualbox.org
> https://www.virtualbox.org/mailman/listinfo/vbox-dev
[Attachment #5 (text/html)]
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">The VT-x/AMD-V Exclusive setting allows
VirtualBox to exclusive use hardware virtualization and not share
it with other parallel hypervisors in the system (i.e. expected to
run simultaneously with VirtualBox).<br>
<br>
Exclusive is the default for Linux and Solaris hosts (has always
been this way). On Windows and OS X hosts, VirtualBox, by default,
is configured such that it can be run in parallel with other
hypervisors *provided* the other hypervisor also shares the
hardware virtualization resource in a compatible manner.<br>
<br>
Regards,<br>
Ram.<br>
<br>
<br>
On 10/16/2013 03:40 AM, Ian Moore wrote:<br>
</div>
<blockquote
cite="mid:CAKf_KmR9ntr+t6KpgdzEvpacsDovyykvrbMK_odFgy1JM_tr7Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Thanks for the clarification of UnrestrictedExecution. The
problems with IMedium->variant and IMedium->capabilities
went away after a reboot. Strange though, still.<br>
<br>
</div>
--Ian<br>
</div>
<div class="gmail_extra">
<br>
<br>
<div class="gmail_quote">On Tue, Oct 15, 2013 at 4:55 PM, Alexey
Eromenko <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:al4321@gmail.com" \
target="_blank">al4321@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
UnrestrictedExecution refers to 16-bit hardware
virtualization on<br>
newer Intel CPUs. (2nd gen Core iSomethingMeaningless
[2600])<br>
<br>
HWVirtExProperty... I don't about it. I'm not aware of
shared VT-x, so<br>
it seems to be always exclusive. Basically you can't run MS
VirtualPC<br>
and VBox sametime on Windows hosts or KVM and VBox on Linux
hosts.<br>
<div class="im"><br>
On Tue, Oct 15, 2013 at 2:52 PM, Ian Moore <<a
moz-do-not-send="true"
href="mailto:imooreyahoo@gmail.com">imooreyahoo@gmail.com</a>>
wrote:<br>
> Hello,<br>
><br>
> It looks like there is an undocumented change.
HWVirtExProperty 'Exclusive'<br>
> no longer exists and 'UnrestrictedExecution' is now
present. Should I assume<br>
> that Exclusive is now named UnrestrictedExecution?<br>
><br>
> It also looks like IMedium->variant and
IMedium->capabilities are broken via<br>
> vboxwebsrv. If I understand correctly, this should
return an array of long<br>
> values that correspond to the enumeration mappings.
Instead, these appear to<br>
> return an array of strings. Here is the raw soap
request and response:<br>
><br>
> [__last_request] => \
<?xml version="1.0" encoding="UTF-8"?><br>
> <SOAP-ENV:Envelope<br>
> xmlns:SOAP-ENV="<a moz-do-not-send="true"
href="http://schemas.xmlsoap.org/soap/envelope/"
target="_blank">http://schemas.xmlsoap.org/soap/envelope/</a>"<br>
> xmlns:ns1="<a moz-do-not-send="true"
href="http://www.virtualbox.org/" \
target="_blank">http://www.virtualbox.org/</a>"><SOAP-ENV:Body><ns1:IMediu \
m_getVariant><_this>518fcea9b848e314-00000000000004cf</_this></ns1:IMedium_getVariant></SOAP-ENV:Body></SOAP-ENV:Envelope><br>
><br>
> [__last_response] => \
<?xml version="1.0" encoding="UTF-8"?><br>
> <SOAP-ENV:Envelope<br>
> xmlns:SOAP-ENV="<a moz-do-not-send="true"
href="http://schemas.xmlsoap.org/soap/envelope/"
target="_blank">http://schemas.xmlsoap.org/soap/envelope/</a>"<br>
> xmlns:SOAP-ENC="<a moz-do-not-send="true"
href="http://schemas.xmlsoap.org/soap/encoding/"
target="_blank">http://schemas.xmlsoap.org/soap/encoding/</a>"<br>
> xmlns:xsi="<a moz-do-not-send="true"
href="http://www.w3.org/2001/XMLSchema-instance"
target="_blank">http://www.w3.org/2001/XMLSchema-instance</a>"<br>
> xmlns:xsd="<a moz-do-not-send="true"
href="http://www.w3.org/2001/XMLSchema" \
target="_blank">http://www.w3.org/2001/XMLSchema</a>"<br> </div>
> xmlns:vbox="<a moz-do-not-send="true"
href="http://www.virtualbox.org/" \
target="_blank">http://www.virtualbox.org/</a>"><SOAP-ENV:Body><vbox:IMedi \
um_getVariantResponse><returnval>Standard</returnval><returnval>S \
tandard</returnval><returnval>Standard</returnval><returnval>S \
tandard</returnval><returnval>Standard</returnval><returnval>S \
tandard</returnval><returnval>Standard</returnval><returnval>S \
tandard</returnval><returnval>Standard</returnval><returnval>S \
tandard</returnval><returnval>Standard</returnval><returnval>S \
tandard</returnval><returnval>Standard</returnval><returnval>S \
tandard</returnval><returnval>Standard</returnval><returnval>S \
tandard</returnval><returnval>Standard</returnval><returnval>D \
iff</returnval><returnval>Standard</returnval><returnval>! \
Standard&l t;/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!<br> \
<div class="im"> urnval>Standard</returnval><returnval>Standard< \
;/returnval><returnval>Standard</returnval></vbox:IMedium_getVariantResponse></SOAP-ENV:Body></SOAP-ENV:Envelope><br>
> )<br>
><br>
> Not only is it an array of strings, but there are
many duplicates.<br>
><br>
> IMedium->capabilities exhibits similar behavior.
Then again, I may be doing<br>
> something wrong.<br>
><br>
> --Ian<br>
><br>
</div>
> _______________________________________________<br>
> vbox-dev mailing list<br>
> <a moz-do-not-send="true"
href="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a><br>
> <a moz-do-not-send="true"
href="https://www.virtualbox.org/mailman/listinfo/vbox-dev"
target="_blank">https://www.virtualbox.org/mailman/listinfo/vbox-dev</a><br>
><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
-Alexey Eromenko "Technologov"<br>
<br>
_______________________________________________<br>
vbox-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a><br>
<a moz-do-not-send="true"
href="https://www.virtualbox.org/mailman/listinfo/vbox-dev"
target="_blank">https://www.virtualbox.org/mailman/listinfo/vbox-dev</a><br>
</font></span></blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
vbox-dev mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a> <a \
class="moz-txt-link-freetext" \
href="https://www.virtualbox.org/mailman/listinfo/vbox-dev">https://www.virtualbox.org/mailman/listinfo/vbox-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>
_______________________________________________
vbox-dev mailing list
vbox-dev@virtualbox.org
https://www.virtualbox.org/mailman/listinfo/vbox-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic