[vbox-dev] Fwd: Re: [VBox-users] teleporting...

[Klaus Espenlaub]

Hi Geoff,

On 12.11.2013 20:14, Geoff Nordli wrote:
>
> Any thoughts on how teleporting works across different chipsets/cpu types?

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 *before* 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

>
> thanks,
>
> Geoff
>
> On 13-11-06 01:39 AM, Frank Mehnert wrote:
>> Hi,
>>
>> On Wednesday 06 November 2013 01:45:42 Fernando Cassia wrote:
>>> On Tue, Nov 5, 2013 at 8:38 PM, Eric S. Johansson <esj at harvee.org> wrote:
>>>> Is
>>>> there any way to create a small template/configuration file etc. to use
>>>> to create the receiving VM?
>>> I'd suggest you use the "export to ovf" option to export the vm as an
>>> appliance, then re-import the base vm into a new vm for the target ...
>>>
>>> I havent tried it myself, but I cant imagine a reason for it not to work...
>> also be sure that the source machine and the target machine share the
>> VM disk image, that is, the VM on both boxes should access the disk images
>> through some network, for example located on an NFS partition.
>>
>>
>
> Hi Frank.
>
> Since we don't have the synthcpu option anymore, how does that work now
> across systems with different chipsets/cpus types?
>
> thanks,
>
> Geoff
>
>
>