<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 13-11-14 04:38 AM, Klaus Espenlaub
wrote:<br>
</div>
<blockquote cite="mid:5284C457.9070204@oracle.com" type="cite">
<pre wrap="">The chipset isn't relevant, but any VM which needs to be teleported
across CPU types has to be configured properly, limiting the CPUID
features to a compatible subset of both CPUs <b class="moz-txt-star"><span class="moz-txt-tag">*</span>before<span class="moz-txt-tag">*</span></b> starting the VM on
the original system.
If that's done properly then it's even possible to teleport between CPU
vendors.
The synthetic CPI setting was intended to avoid many complicated issues,
but it turned out to be not usable for a number of guest OSes, as they
simply refuse to run on such all fake CPUs. So currently you have to do
the CPUID research yourself, especially if you don't want to
unnecessarily strip out features.
Klaus</pre>
</blockquote>
<br>
Thanks Klaus.<br>
<br>
Do you have any documentation you can refer to and the process to
make this work on vbox?<br>
<br>
There is quite a bit of info on masking with other hypervisors. <br>
<br>
I am more interested in the process to do it in vbox. <br>
<br>
Geoff <br>
<br>
<br>
</body>
</html>