thr3ads.net - Xen users - [Xen-users] Do systems have to be IDENTICAL for live migration? [Jul 2010]

If this information is useful, please help other people find it:
Share via:

James Pifer

2010-Jul-02 01:01 UTC

[Xen-users] Do systems have to be IDENTICAL for live migration?

I have several systems running 64bit SLES11SP1. I''m trying to Live
Migrate between a couple of them and it''s not working, although the
same
VM will run on each one starting it manually. 

The system are not identical. Would one expect migration to work
between these two systems? See below. 

Thanks,
James

The first system is a ProLiant DL360 G6:
Proc 1:2533 MHz
Execution technology:4/4 cores; 8 maximum threads
Memory technology:64-bit capable
Processor 1 Internal L1 Cache:128 KB
Processor 1 Internal L2 Cache:1024 KB
Processor 1 Internal L3 Cache:8192 KB

Proc 2:2533 MHz
Execution technology:4/4 cores; 8 maximum threads
Memory technology:64-bit capable
Processor 2 Internal L1 Cache:128 KB
Processor 2 Internal L2 Cache:1024 KB
Processor 2 Internal L3 Cache:8192 KB


The second system is a ProLiant DL360 G5:
Proc 1:2500 MHz
Execution technology:4/4 cores; 4 threads
Memory technology:64-bit capable
Processor 1 Internal L1 Cache:128 KB
Processor 1 Internal L2 Cache:12288 KB

Proc 2:2500 MHz
Execution technology:4/4 cores; 4 threads
Memory technology:64-bit capable
Processor 2 Internal L1 Cache:128 KB
Processor 2 Internal L2 Cache:12288 KB



When I tried to Live Migrate a VM from system one to system two I got:
[2010-07-01 12:06:49 5660] DEBUG (XendDomainInfo:237)
XendDomainInfo.restore([''domain'', [''domid'',
''3''], [''cpu_weight'',
''256''], [''cpu_cap'', ''0''],
[''pool_name'', ''Pool-0''],
[''bootloader''], [''vcpus'',
''2''], [''node'', ''8002''],
[''cpus'', [[], []]], [''on_poweroff'',
''destroy''], [''description''],
[''on_crash'', ''destroy''],
[''uuid'',
''92b1b8f4-94aa-d393-92a4-3d78262bf092''],
[''bootloader_args''], [''name'',
''chsimp2''], [''on_reboot'',
''restart''], [''maxmem'',
''2048''], [''memory'',
''2048''], [''shadow_memory'',
''18''], [''vcpu_avail'',
''3''], [''features''],
[''on_xend_start'', ''ignore''],
[''on_xend_stop'', ''ignore''],
[''start_time'', ''1277985922.2''],
[''cpu_time'', ''2433.09449026''],
[''online_vcpus'', ''2''],
[''image'', [''hvm'',
[''kernel''], [''superpages'',
''0''], [''videoram'', ''4''],
[''hpet'', ''0''], [''stdvga'',
''0''], [''loader'',
''/usr/lib/xen/boot/hvmloader''],
[''xen_platform_pci'', ''1''],
[''rtc_timeoffset'', ''0''],
[''pci'', []], [''hap'', ''1''],
[''localtime'', ''0''],
[''timer_mode'', ''1''],
[''pci_msitranslate'', ''1''],
[''oos'', ''1''], [''apic'',
''0''], [''sdl'', ''0''],
[''usbdevice'', ''tablet''],
[''vpt_align'', ''1''],
[''extid'', ''0''],
[''vncunused'', ''1''],
[''boot'', ''c''], [''pae'',
''1''], [''viridian'', ''0''],
[''acpi'', ''1''], [''vnc'',
''1''], [''nographic'', ''0''],
[''nomigrate'', ''0''],
[''usb'', ''1''], [''tsc_mode'',
''0''], [''guest_os_type'',
''default''], [''device_model'',
''/usr/lib64/xen/bin/qemu-dm''],
[''pci_power_mgmt'', ''0''],
[''xauthority'', ''/root/.Xauthority''],
[''isa'', ''0''], [''notes'',
[''SUSPEND_CANCEL'', ''1'']]]],
[''status'', ''2''], [''state'',
''-b----''], [''store_mfn'',
''1044476''], [''device'',
[''vif'', [''bridge'', ''br0''],
[''mac'', ''00:16:3e:1f:ea:77''],
[''script'', ''/etc/xen/scripts/vif-bridge''],
[''uuid'',
''53301d91-5283-d69d-4b7d-5beb3deee963''],
[''backend'', ''0'']]],
[''device'', [''console'',
[''protocol'', ''vt100''],
[''location'', ''4''],
[''uuid'',
''b02891b0-855e-fc59-9744-5685e1950c19'']]],
[''device'', [''vbd'',
[''protocol'', ''x86_32-abi''],
[''uuid'',
''31c2d623-a977-4e81-5ecc-2ab09907f76e''],
[''bootable'', ''1''], [''dev'',
''hda:disk''], [''uname'',
''phy:/dev/disk/by-id/scsi-200d0b29d2d002200''],
[''mode'', ''w''], [''backend'',
''0''], [''VDI'']]],
[''device'', [''vfb'',
[''vncunused'', ''1''],
[''vnc'', ''1''], [''uuid'',
''e40219c2-a740-c910-2840-be3a2aaa9548''],
[''location'', ''127.0.0.1:5902'']]],
[''change_home_server'', ''False'']])
[2010-07-01 12:06:49 5660] DEBUG (XendDomainInfo:2543)
XendDomainInfo.constructDomain
[2010-07-01 12:06:49 5660] DEBUG (balloon:239) Balloon: 31107320 KiB free; need
16384; done.
[2010-07-01 12:06:49 5660] DEBUG (XendDomain:465) Adding Domain: 1
[2010-07-01 12:06:49 5660] DEBUG (XendDomainInfo:3470) Storing VM details:
{''on_xend_stop'': ''ignore'',
''pool_name'': ''Pool-0'',
''shadow_memory'': ''18'',
''uuid'':
''92b1b8f4-94aa-d393-92a4-3d78262bf092'',
''on_reboot'': ''restart'',
''start_time'': ''1277985922.2'',
''on_poweroff'': ''destroy'',
''bootloader_args'': '''',
''on_xend_start'': ''ignore'',
''on_crash'': ''destroy'',
''xend/restart_count'': ''0'',
''vcpus'': ''2'',
''vcpu_avail'': ''3'',
''bootloader'': '''', ''image'':
''(hvm (kernel ) (superpages 0) (videoram 4) (hpet 0) (stdvga 0) (loader
/usr/lib/xen/boot/hvmloader) (xen_platform_pci 1) (rtc_timeoffset 0) (pci ())
(hap 1) (localtime 0) (timer_mode 1) (pci_msitranslate 1) (oos 1) (apic 0) (sdl
0) (usbdevice tablet) (vpt_align 1) (extid 0) (vncunused 1) (boot c) (pae 1)
(viridian 0) (acpi 1) (vnc 1) (nographic 0) (nomigrate 0) (usb 1) (tsc_mode 0)
(guest_os_type default) (device_model /usr/lib64/xen/bin/qemu-dm)
(pci_power_mgmt 0) (xauthority /root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL
1)))'', ''name'': ''chsimp2''}
[2010-07-01 12:06:49 5660] INFO (XendDomainInfo:2402) createDevice: console :
{''protocol'': ''vt100'',
''location'': ''4'', ''uuid'':
''b02891b0-855e-fc59-9744-5685e1950c19''}
[2010-07-01 12:06:49 5660] DEBUG (DevController:95) DevController: writing
{''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/console/1/0''} to
/local/domain/1/device/console/0.
[2010-07-01 12:06:49 5660] DEBUG (DevController:97) DevController: writing
{''domain'': ''chsimp2'',
''frontend'':
''/local/domain/1/device/console/0'', ''uuid'':
''b02891b0-855e-fc59-9744-5685e1950c19'',
''frontend-id'': ''1'',
''state'': ''1'', ''location'':
''4'', ''online'': ''1'',
''protocol'': ''vt100''} to
/local/domain/0/backend/console/1/0.
[2010-07-01 12:06:49 5660] INFO (XendDomainInfo:2402) createDevice: vfb :
{''vncunused'': ''1'',
''other_config'': {''vncunused'':
''1'', ''vnc'': ''1''},
''vnc'': ''1'', ''uuid'':
''e40219c2-a740-c910-2840-be3a2aaa9548'',
''location'': ''127.0.0.1:5902''}
[2010-07-01 12:06:49 5660] DEBUG (DevController:95) DevController: writing
{''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vfb/1/0''} to
/local/domain/1/device/vfb/0.
[2010-07-01 12:06:49 5660] DEBUG (DevController:97) DevController: writing
{''vncunused'': ''1'',
''domain'': ''chsimp2'',
''frontend'': ''/local/domain/1/device/vfb/0'',
''uuid'':
''e40219c2-a740-c910-2840-be3a2aaa9548'',
''frontend-id'': ''1'',
''state'': ''1'', ''location'':
''127.0.0.1:5902'', ''online'':
''1'', ''vnc'': ''1''} to
/local/domain/0/backend/vfb/1/0.
[2010-07-01 12:06:49 5660] INFO (XendDomainInfo:2402) createDevice: vbd :
{''protocol'': ''x86_32-abi'',
''uuid'':
''31c2d623-a977-4e81-5ecc-2ab09907f76e'',
''bootable'': 1, ''driver'':
''paravirtualised'', ''dev'':
''hda:disk'', ''uname'':
''phy:/dev/disk/by-id/scsi-200d0b29d2d002200'',
''mode'': ''w'', ''backend'':
''0''}
[2010-07-01 12:06:49 5660] DEBUG (DevController:95) DevController: writing
{''virtual-device'': ''768'',
''protocol'': ''x86_32-abi'',
''device-type'': ''disk'',
''backend-id'': ''0'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/1/768''} to
/local/domain/1/device/vbd/768.
[2010-07-01 12:06:49 5660] DEBUG (DevController:97) DevController: writing
{''domain'': ''chsimp2'',
''frontend'':
''/local/domain/1/device/vbd/768'', ''uuid'':
''31c2d623-a977-4e81-5ecc-2ab09907f76e'',
''bootable'': ''1'', ''dev'':
''hda'', ''state'': ''1'',
''params'':
''/dev/disk/by-id/scsi-200d0b29d2d002200'',
''mode'': ''w'', ''online'':
''1'', ''frontend-id'': ''1'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/1/768.
[2010-07-01 12:06:49 5660] INFO (XendDomainInfo:2402) createDevice: vif :
{''bridge'': ''br0'', ''mac'':
''00:16:3e:1f:ea:77'', ''script'':
''/etc/xen/scripts/vif-bridge'', ''uuid'':
''53301d91-5283-d69d-4b7d-5beb3deee963'',
''backend'': ''0''}
[2010-07-01 12:06:49 5660] DEBUG (DevController:95) DevController: writing
{''backend-id'': ''0'', ''mac'':
''00:16:3e:1f:ea:77'', ''handle'':
''0'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vif/1/0''} to
/local/domain/1/device/vif/0.
[2010-07-01 12:06:49 5660] DEBUG (DevController:97) DevController: writing
{''bridge'': ''br0'',
''domain'': ''chsimp2'',
''handle'': ''0'', ''uuid'':
''53301d91-5283-d69d-4b7d-5beb3deee963'',
''script'': ''/etc/xen/scripts/vif-bridge'',
''mac'': ''00:16:3e:1f:ea:77'',
''frontend-id'': ''1'',
''state'': ''1'', ''online'':
''1'', ''frontend'':
''/local/domain/1/device/vif/0''} to
/local/domain/0/backend/vif/1/0.
[2010-07-01 12:06:49 5660] DEBUG (XendDomainInfo:1835) Storing domain details:
{''console/port'': ''4'',
''description'': '''',
''console/limit'': ''1048576'',
''image/suspend-cancel'': ''1'',
''domid'': ''1'', ''vm'':
''/vm/92b1b8f4-94aa-d393-92a4-3d78262bf092'',
''cpu/0/availability'': ''online'',
''memory/target'': ''2097152'',
''control/platform-feature-multiprocessor-suspend'':
''1'', ''console/type'':
''ioemu'', ''cpu/1/availability'':
''online'', ''store/port'':
''3'', ''name'': ''chsimp2''}
[2010-07-01 12:06:49 5660] INFO (XendCheckpoint:343) restore hvm domain 1,
apic=0, pae=1
[2010-07-01 12:06:49 5660] DEBUG (image:339) No VNC passwd configured for vfb
access
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: boot, val: c
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: fda, val: None
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: fdb, val: None
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: soundhw, val: None
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: localtime, val: 0
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: serial, val: None
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: std-vga, val: 0
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: isa, val: 0
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: acpi, val: 1
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: usb, val: 1
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: usbdevice, val: tablet
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: gfx_passthru, val: None
[2010-07-01 12:06:49 5660] INFO (image:833) Need to create platform
device.[domid:1]
[2010-07-01 12:06:49 5660] DEBUG (XendCheckpoint:361) restore:shadow=0x12,
_static_max=0x80000000, _static_min=0x0,
[2010-07-01 12:06:49 5660] DEBUG (XendCheckpoint:380) [xc_restore]:
/usr/lib64/xen/bin/xc_restore 17 1 3 4 1 1 0 0
[2010-07-01 12:06:49 5660] INFO (XendCheckpoint:482) xc_domain_restore start:
p2m_size = 100000
[2010-07-01 12:06:49 5660] INFO (XendCheckpoint:482) Reloading memory pages:  
0%
[2010-07-01 12:08:12 5660] INFO (XendCheckpoint:482) Read 1448 bytes of QEMU
data
[2010-07-01 12:08:12 5660] INFO (XendCheckpoint:482) Read 5544 bytes of QEMU
data
[2010-07-01 12:08:12 5660] INFO (XendCheckpoint:482) Read 9 bytes of QEMU data
[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482) ERROR Internal error: Error
when reading batch size
[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482) ERROR Internal error: error
when buffering batch, finishing
[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482) 
[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482) Writing 7001 bytes of QEMU
data
[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482) ERROR Internal error: error
setting the HVM context
[2010-07-01 12:08:14 5660] INFO (XendCheckpoint:482) Restore exit with rc=1
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:3111) XendDomainInfo.destroy:
domid=1
[2010-07-01 12:08:14 5660] ERROR (XendDomainInfo:3125) XendDomainInfo.destroy:
domain destruction failed.
Traceback (most recent call last):
  File
"/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line
3118, in destroy
    xc.domain_pause(self.domid)
Error: (3, ''No such process'')
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2451) No device model
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2453) Releasing devices
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2459) Removing vif/0
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:1289)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2459) Removing console/0
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:1289)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2459) Removing vbd/768
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:1289)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2459) Removing vfb/0
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:1289)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2010-07-01 12:08:14 5660] INFO (XendDomain:1108) Domain chsimp2
(92b1b8f4-94aa-d393-92a4-3d78262bf092) deleted.
[2010-07-01 12:08:14 5660] ERROR (XendCheckpoint:416)
/usr/lib64/xen/bin/xc_restore 17 1 3 4 1 1 0 0 failed
Traceback (most recent call last):
  File
"/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line
384, in restore
    forkHelper(cmd, fd, handler.handler, True)
  File
"/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line
470, in forkHelper
    raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_restore 17 1 3 4 1 1 0 0 failed
[2010-07-01 12:08:14 5660] ERROR (XendDomain:1176) Restore failed
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py",
line 1160, in domain_restore_fd
    dominfo = XendCheckpoint.restore(self, fd, paused=paused,
relocating=relocating)
  File
"/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line
417, in restore
    raise exn
XendError: /usr/lib64/xen/bin/xc_restore 17 1 3 4 1 1 0 0 failed



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

James Pifer

2010-Jul-07 12:21 UTC

head link

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

On Thu, 2010-07-01 at 21:01 -0400, James Pifer wrote:> I have several systems running 64bit SLES11SP1. I''m trying to Live
> Migrate between a couple of them and it''s not working, although
the same
> VM will run on each one starting it manually. 
> 
> The system are not identical. Would one expect migration to work
> between these two systems? See below. 
> 
> Thanks,
> James
Just an update to this. I can migrate from the DL360 G5 (8 CPU) to the
DL360 G6 (16 CPU) but not the other way around. 

Is that expected? Is the CPU count the issue possibly?

Thanks,
James


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

James Pifer

2010-Jul-07 12:33 UTC

head link

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

On Wed, 2010-07-07 at 09:30 -0300, Cristian Colombo
wrote:> Maybe in .cfg file you have the domUs confired to use more than 8
> cores....
> 
No, I don''t have any that use over 4. 

James


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Nick Couchman

2010-Jul-07 14:53 UTC

head link

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

>>> On 2010/07/07 at 06:21, James Pifer <jep@obrien-pifer.com>
wrote:
> On Thu, 2010-07-01 at 21:01 -0400, James Pifer wrote:
>> I have several systems running 64bit SLES11SP1. I'm trying to Live
>> Migrate between a couple of them and it's not working, although the
same>> VM will run on each one starting it manually. 
>> 
>> The system are not identical. Would one expect migration to work
>> between these two systems? See below. 
>> 
>> Thanks,
>> James
> 
> Just an update to this. I can migrate from the DL360 G5 (8 CPU) to
the> DL360 G6 (16 CPU) but not the other way around. 
> 
> Is that expected? Is the CPU count the issue possibly?
> 
> Thanks,
> James
Could you more clearly define "not working" - error messages, log
entries, etc.?  Sometimes CPU differences can prevent live migration
from working properly, but there are other factors, too.  It would be
useful to know what Xen says about why live migration is failing.  Also,
could you specify exactly what CPUs are in those boxes?  I don't use HP,
but I know with Dell servers the model/generation of server you're using
can have a wide range of processors in it, so just specifying the server
model/brand does not really tell anything useful.

-Nick


--------
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient.  If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information.  In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way.  If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox.  Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

James Pifer

2010-Jul-07 15:25 UTC

head link

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

> Could you more clearly define "not working" - error messages, log
> entries, etc.?  Sometimes CPU differences can prevent live migration
> from working properly, but there are other factors, too.  It would be
> useful to know what Xen says about why live migration is failing.  Also,
> could you specify exactly what CPUs are in those boxes?  I don''t
use HP,
> but I know with Dell servers the model/generation of server you''re
using
> can have a wide range of processors in it, so just specifying the server
> model/brand does not really tell anything useful.
> 
> -Nick
Hi Nick. I actually had all of this in the original post, but cut it in
replies. See below.

Thanks,
James

The first system is a ProLiant DL360 G6:
Proc 1:2533 MHz
Execution technology:4/4 cores; 8 maximum threads
Memory technology:64-bit capable
Processor 1 Internal L1 Cache:128 KB
Processor 1 Internal L2 Cache:1024 KB
Processor 1 Internal L3 Cache:8192 KB

Proc 2:2533 MHz
Execution technology:4/4 cores; 8 maximum threads
Memory technology:64-bit capable
Processor 2 Internal L1 Cache:128 KB
Processor 2 Internal L2 Cache:1024 KB
Processor 2 Internal L3 Cache:8192 KB


The second system is a ProLiant DL360 G5:
Proc 1:2500 MHz
Execution technology:4/4 cores; 4 threads
Memory technology:64-bit capable
Processor 1 Internal L1 Cache:128 KB
Processor 1 Internal L2 Cache:12288 KB

Proc 2:2500 MHz
Execution technology:4/4 cores; 4 threads
Memory technology:64-bit capable
Processor 2 Internal L1 Cache:128 KB
Processor 2 Internal L2 Cache:12288 KB



When I tried to Live Migrate a VM from system one to system two I got:
[2010-07-01 12:06:49 5660] DEBUG (XendDomainInfo:237)
XendDomainInfo.restore([''domain'', [''domid'',
''3''], [''cpu_weight'',
''256''], [''cpu_cap'', ''0''],
[''pool_name'', ''Pool-0''],
[''bootloader''], [''vcpus'',
''2''], [''node'', ''8002''],
[''cpus'', [[], []]], [''on_poweroff'',
''destroy''], [''description''],
[''on_crash'', ''destroy''],
[''uuid'',
''92b1b8f4-94aa-d393-92a4-3d78262bf092''],
[''bootloader_args''], [''name'',
''chsimp2''], [''on_reboot'',
''restart''], [''maxmem'',
''2048''], [''memory'',
''2048''], [''shadow_memory'',
''18''], [''vcpu_avail'',
''3''], [''features''],
[''on_xend_start'', ''ignore''],
[''on_xend_stop'', ''ignore''],
[''start_time'', ''1277985922.2''],
[''cpu_time'', ''2433.09449026''],
[''online_vcpus'', ''2''],
[''image'', [''hvm'',
[''kernel''], [''superpages'',
''0''], [''videoram'', ''4''],
[''hpet'', ''0''], [''stdvga'',
''0''], [''loader'',
''/usr/lib/xen/boot/hvmloader''],
[''xen_platform_pci'', ''1''],
[''rtc_timeoffset'', ''0''],
[''pci'', []], [''hap'', ''1''],
[''localtime'', ''0''],
[''timer_mode'', ''1''],
[''pci_msitranslate'', ''1''],
[''oos'', ''1''], [''apic'',
''0''], [''sdl'', ''0''],
[''usbdevice'', ''tablet''],
[''vpt_align'', ''1''],
[''extid'', ''0''],
[''vncunused'', ''1''],
[''boot'', ''c''], [''pae'',
''1''], [''viridian'', ''0''],
[''acpi'', ''1''], [''vnc'',
''1''], [''nographic'', ''0''],
[''nomigrate'', ''0''],
[''usb'', ''1''], [''tsc_mode'',
''0''], [''guest_os_type'',
''default''], [''device_model'',
''/usr/lib64/xen/bin/qemu-dm''],
[''pci_power_mgmt'', ''0''],
[''xauthority'', ''/root/.Xauthority''],
[''isa'', ''0''], [''notes'',
[''SUSPEND_CANCEL'', ''1'']]]],
[''status'', ''2''], [''state'',
''-b----''], [''store_mfn'',
''1044476''], [''device'',
[''vif'', [''bridge'', ''br0''],
[''mac'', ''00:16:3e:1f:ea:77''],
[''script'', ''/etc/xen/scripts/vif-bridge''],
[''uuid'',
''53301d91-5283-d69d-4b7d-5beb3deee963''],
[''backend'', ''0'']]],
[''device'', [''console'',
[''protocol'', ''vt100''],
[''location'', ''4''],
[''uuid'',
''b02891b0-855e-fc59-9744-5685e1950c19'']]],
[''device'', [''vbd'',
[''protocol'', ''x86_32-abi''],
[''uuid'',
''31c2d623-a977-4e81-5ecc-2ab09907f76e''],
[''bootable'', ''1''], [''dev'',
''hda:disk''], [''uname'',
''phy:/dev/disk/by-id/scsi-200d0b29d2d002200''],
[''mode'', ''w''], [''backend'',
''0''], [''VDI'']]],
[''device'', [''vfb'',
[''vncunused'', ''1''],
[''vnc'', ''1''], [''uuid'',
''e40219c2-a740-c910-2840-be3a2aaa9548''],
[''location'', ''127.0.0.1:5902'']]],
[''change_home_server'', ''False'']])
[2010-07-01 12:06:49 5660] DEBUG (XendDomainInfo:2543)
XendDomainInfo.constructDomain
[2010-07-01 12:06:49 5660] DEBUG (balloon:239) Balloon: 31107320 KiB free; need
16384; done.
[2010-07-01 12:06:49 5660] DEBUG (XendDomain:465) Adding Domain: 1
[2010-07-01 12:06:49 5660] DEBUG (XendDomainInfo:3470) Storing VM details:
{''on_xend_stop'': ''ignore'',
''pool_name'': ''Pool-0'',
''shadow_memory'': ''18'',
''uuid'':
''92b1b8f4-94aa-d393-92a4-3d78262bf092'',
''on_reboot'': ''restart'',
''start_time'': ''1277985922.2'',
''on_poweroff'': ''destroy'',
''bootloader_args'': '''',
''on_xend_start'': ''ignore'',
''on_crash'': ''destroy'',
''xend/restart_count'': ''0'',
''vcpus'': ''2'',
''vcpu_avail'': ''3'',
''bootloader'': '''', ''image'':
''(hvm (kernel ) (superpages 0) (videoram 4) (hpet 0) (stdvga 0) (loader
/usr/lib/xen/boot/hvmloader) (xen_platform_pci 1) (rtc_timeoffset 0) (pci ())
(hap 1) (localtime 0) (timer_mode 1) (pci_msitranslate 1) (oos 1) (apic 0) (sdl
0) (usbdevice tablet) (vpt_align 1) (extid 0) (vncunused 1) (boot c) (pae 1)
(viridian 0) (acpi 1) (vnc 1) (nographic 0) (nomigrate 0) (usb 1) (tsc_mode 0)
(guest_os_type default) (device_model /usr/lib64/xen/bin/qemu-dm)
(pci_power_mgmt 0) (xauthority /root/.Xauthority) (isa 0) (notes (SUSPEND_CANCEL
1)))'', ''name'': ''chsimp2''}
[2010-07-01 12:06:49 5660] INFO (XendDomainInfo:2402) createDevice: console :
{''protocol'': ''vt100'',
''location'': ''4'', ''uuid'':
''b02891b0-855e-fc59-9744-5685e1950c19''}
[2010-07-01 12:06:49 5660] DEBUG (DevController:95) DevController: writing
{''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/console/1/0''} to
/local/domain/1/device/console/0.
[2010-07-01 12:06:49 5660] DEBUG (DevController:97) DevController: writing
{''domain'': ''chsimp2'',
''frontend'':
''/local/domain/1/device/console/0'', ''uuid'':
''b02891b0-855e-fc59-9744-5685e1950c19'',
''frontend-id'': ''1'',
''state'': ''1'', ''location'':
''4'', ''online'': ''1'',
''protocol'': ''vt100''} to
/local/domain/0/backend/console/1/0.
[2010-07-01 12:06:49 5660] INFO (XendDomainInfo:2402) createDevice: vfb :
{''vncunused'': ''1'',
''other_config'': {''vncunused'':
''1'', ''vnc'': ''1''},
''vnc'': ''1'', ''uuid'':
''e40219c2-a740-c910-2840-be3a2aaa9548'',
''location'': ''127.0.0.1:5902''}
[2010-07-01 12:06:49 5660] DEBUG (DevController:95) DevController: writing
{''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vfb/1/0''} to
/local/domain/1/device/vfb/0.
[2010-07-01 12:06:49 5660] DEBUG (DevController:97) DevController: writing
{''vncunused'': ''1'',
''domain'': ''chsimp2'',
''frontend'': ''/local/domain/1/device/vfb/0'',
''uuid'':
''e40219c2-a740-c910-2840-be3a2aaa9548'',
''frontend-id'': ''1'',
''state'': ''1'', ''location'':
''127.0.0.1:5902'', ''online'':
''1'', ''vnc'': ''1''} to
/local/domain/0/backend/vfb/1/0.
[2010-07-01 12:06:49 5660] INFO (XendDomainInfo:2402) createDevice: vbd :
{''protocol'': ''x86_32-abi'',
''uuid'':
''31c2d623-a977-4e81-5ecc-2ab09907f76e'',
''bootable'': 1, ''driver'':
''paravirtualised'', ''dev'':
''hda:disk'', ''uname'':
''phy:/dev/disk/by-id/scsi-200d0b29d2d002200'',
''mode'': ''w'', ''backend'':
''0''}
[2010-07-01 12:06:49 5660] DEBUG (DevController:95) DevController: writing
{''virtual-device'': ''768'',
''protocol'': ''x86_32-abi'',
''device-type'': ''disk'',
''backend-id'': ''0'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/1/768''} to
/local/domain/1/device/vbd/768.
[2010-07-01 12:06:49 5660] DEBUG (DevController:97) DevController: writing
{''domain'': ''chsimp2'',
''frontend'':
''/local/domain/1/device/vbd/768'', ''uuid'':
''31c2d623-a977-4e81-5ecc-2ab09907f76e'',
''bootable'': ''1'', ''dev'':
''hda'', ''state'': ''1'',
''params'':
''/dev/disk/by-id/scsi-200d0b29d2d002200'',
''mode'': ''w'', ''online'':
''1'', ''frontend-id'': ''1'',
''type'': ''phy''} to
/local/domain/0/backend/vbd/1/768.
[2010-07-01 12:06:49 5660] INFO (XendDomainInfo:2402) createDevice: vif :
{''bridge'': ''br0'', ''mac'':
''00:16:3e:1f:ea:77'', ''script'':
''/etc/xen/scripts/vif-bridge'', ''uuid'':
''53301d91-5283-d69d-4b7d-5beb3deee963'',
''backend'': ''0''}
[2010-07-01 12:06:49 5660] DEBUG (DevController:95) DevController: writing
{''backend-id'': ''0'', ''mac'':
''00:16:3e:1f:ea:77'', ''handle'':
''0'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vif/1/0''} to
/local/domain/1/device/vif/0.
[2010-07-01 12:06:49 5660] DEBUG (DevController:97) DevController: writing
{''bridge'': ''br0'',
''domain'': ''chsimp2'',
''handle'': ''0'', ''uuid'':
''53301d91-5283-d69d-4b7d-5beb3deee963'',
''script'': ''/etc/xen/scripts/vif-bridge'',
''mac'': ''00:16:3e:1f:ea:77'',
''frontend-id'': ''1'',
''state'': ''1'', ''online'':
''1'', ''frontend'':
''/local/domain/1/device/vif/0''} to
/local/domain/0/backend/vif/1/0.
[2010-07-01 12:06:49 5660] DEBUG (XendDomainInfo:1835) Storing domain details:
{''console/port'': ''4'',
''description'': '''',
''console/limit'': ''1048576'',
''image/suspend-cancel'': ''1'',
''domid'': ''1'', ''vm'':
''/vm/92b1b8f4-94aa-d393-92a4-3d78262bf092'',
''cpu/0/availability'': ''online'',
''memory/target'': ''2097152'',
''control/platform-feature-multiprocessor-suspend'':
''1'', ''console/type'':
''ioemu'', ''cpu/1/availability'':
''online'', ''store/port'':
''3'', ''name'': ''chsimp2''}
[2010-07-01 12:06:49 5660] INFO (XendCheckpoint:343) restore hvm domain 1,
apic=0, pae=1
[2010-07-01 12:06:49 5660] DEBUG (image:339) No VNC passwd configured for vfb
access
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: boot, val: c
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: fda, val: None
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: fdb, val: None
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: soundhw, val: None
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: localtime, val: 0
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: serial, val: None
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: std-vga, val: 0
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: isa, val: 0
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: acpi, val: 1
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: usb, val: 1
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: usbdevice, val: tablet
[2010-07-01 12:06:49 5660] DEBUG (image:901) args: gfx_passthru, val: None
[2010-07-01 12:06:49 5660] INFO (image:833) Need to create platform
device.[domid:1]
[2010-07-01 12:06:49 5660] DEBUG (XendCheckpoint:361) restore:shadow=0x12,
_static_max=0x80000000, _static_min=0x0,
[2010-07-01 12:06:49 5660] DEBUG (XendCheckpoint:380) [xc_restore]:
/usr/lib64/xen/bin/xc_restore 17 1 3 4 1 1 0 0
[2010-07-01 12:06:49 5660] INFO (XendCheckpoint:482) xc_domain_restore start:
p2m_size = 100000
[2010-07-01 12:06:49 5660] INFO (XendCheckpoint:482) Reloading memory pages:  
0%
[2010-07-01 12:08:12 5660] INFO (XendCheckpoint:482) Read 1448 bytes of QEMU
data
[2010-07-01 12:08:12 5660] INFO (XendCheckpoint:482) Read 5544 bytes of QEMU
data
[2010-07-01 12:08:12 5660] INFO (XendCheckpoint:482) Read 9 bytes of QEMU data
[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482) ERROR Internal error: Error
when reading batch size
[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482) ERROR Internal error: error
when buffering batch, finishing
[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482) 
[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482) Writing 7001 bytes of QEMU
data
[2010-07-01 12:08:13 5660] INFO (XendCheckpoint:482) ERROR Internal error: error
setting the HVM context
[2010-07-01 12:08:14 5660] INFO (XendCheckpoint:482) Restore exit with rc=1
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:3111) XendDomainInfo.destroy:
domid=1
[2010-07-01 12:08:14 5660] ERROR (XendDomainInfo:3125) XendDomainInfo.destroy:
domain destruction failed.
Traceback (most recent call last):
  File
"/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py", line
3118, in destroy
    xc.domain_pause(self.domid)
Error: (3, ''No such process'')
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2451) No device model
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2453) Releasing devices
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2459) Removing vif/0
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:1289)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2459) Removing console/0
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:1289)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2459) Removing vbd/768
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:1289)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:2459) Removing vfb/0
[2010-07-01 12:08:14 5660] DEBUG (XendDomainInfo:1289)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2010-07-01 12:08:14 5660] INFO (XendDomain:1108) Domain chsimp2
(92b1b8f4-94aa-d393-92a4-3d78262bf092) deleted.
[2010-07-01 12:08:14 5660] ERROR (XendCheckpoint:416)
/usr/lib64/xen/bin/xc_restore 17 1 3 4 1 1 0 0 failed
Traceback (most recent call last):
  File
"/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line
384, in restore
    forkHelper(cmd, fd, handler.handler, True)
  File
"/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line
470, in forkHelper
    raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_restore 17 1 3 4 1 1 0 0 failed
[2010-07-01 12:08:14 5660] ERROR (XendDomain:1176) Restore failed
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py",
line 1160, in domain_restore_fd
    dominfo = XendCheckpoint.restore(self, fd, paused=paused,
relocating=relocating)
  File
"/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line
417, in restore
    raise exn
XendError: /usr/lib64/xen/bin/xc_restore 17 1 3 4 1 1 0 0 failed


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Nick Couchman

2010-Jul-07 17:03 UTC

head link

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

> 
> Hi Nick. I actually had all of this in the original post, but cut it
in> replies. See below.
> 
> Thanks,
> James
> 
> The first system is a ProLiant DL360 G6:
Sorry I missed the OP.  Could you post the actual model number of the
processors?  For example, Intel Xeon X3540?    The info you have there
is good, but still doesn't give much information about possible
architecture differences between the two.

-Nick


--------
This e-mail may contain confidential and privileged material for the sole use of
the intended recipient.  If this email is not intended for you, or you are not
responsible for the delivery of this message to the intended recipient, please
note that this message may contain SEAKR Engineering (SEAKR)
Privileged/Proprietary Information.  In such a case, you are strictly prohibited
from downloading, photocopying, distributing or otherwise using this message,
its contents or attachments in any way.  If you have received this message in
error, please notify us immediately by replying to this e-mail and delete the
message from your mailbox.  Information contained in this message that does not
relate to the business of SEAKR is neither endorsed by nor attributable to
SEAKR.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

James Pifer

2010-Jul-07 17:15 UTC

head link

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

On Wed, 2010-07-07 at 11:03 -0600, Nick Couchman wrote:> > 
> > Hi Nick. I actually had all of this in the original post, but cut it
> in
> > replies. See below.
> > 
> > Thanks,
> > James
> > 
> > The first system is a ProLiant DL360 G6:
> 
> Sorry I missed the OP.  Could you post the actual model number of the
> processors?  For example, Intel Xeon X3540?    The info you have there
> is good, but still doesn''t give much information about possible
> architecture differences between the two.
> 
> -Nick
> 

How''s this? 

Thanks,
James



Server1 (x16)

# cat /proc/cpuinfo
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 26
model name	: Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz
stepping	: 5
cpu MHz		: 2533.490
cache size	: 8192 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 11
wp		: yes
flags		: fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush
acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good
nonstop_tsc aperfmperf pni est ssse3 cx16 sse4_1 sse4_2 popcnt
hypervisor lahf_lm ida
bogomips	: 5068.68
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management:



Server2 (x8)

# cat /proc/cpuinfo
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Intel(R) Xeon(R) CPU           E5420  @ 2.50GHz
stepping	: 6
cpu MHz		: 2500.170
cache size	: 6144 KB
physical id	: 0
siblings	: 1
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush acpi mmx
fxsr sse sse2 ss ht syscall lm constant_tsc rep_good aperfmperf pni est ssse3
cx16 sse4_1 hypervisor lahf_lm
bogomips	: 5010.36
clflush size	: 64
cache_alignment	: 64
address sizes	: 38 bits physical, 48 bits virtual
power management:




_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Ravi Giri

2010-Jul-08 08:37 UTC

head link

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

On Wed, Jul 7, 2010 at 10:45 PM, James Pifer <jep@obrien-pifer.com> wrote:

AFAIK, Intel processors with ''FlexMigration'' support allow
live
migration across different processor generations
> Server1 (x16)
> model name      : Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz
Xeon 5500 series (this is obviously the G6 system) has FlexMigration
> Server2 (x8)
> model name      : Intel(R) Xeon(R) CPU           E5420  @ 2.50GHz
Xeon 5400 series (this is obviously the G5 system) does not have FlexMigration

That''s why you''re able to livemigrate from G5 to G6 and not
the other way.

FlexMigration essentially allows live migration across processors even
with some differences in instruction sets.

This is specific to the processor though, there may be other
dependencies with respect to the rest of the server platform that
could cause livemigration between two dislike systems to fail.

Regards,
--
Ravi

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Bart Coninckx

2010-Jul-08 09:00 UTC

head link

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

On Thursday 08 July 2010 10:37:05 Ravi Giri wrote:> On Wed, Jul 7, 2010 at 10:45 PM, James Pifer <jep@obrien-pifer.com>
wrote:
> 
> AFAIK, Intel processors with ''FlexMigration'' support
allow live
> migration across different processor generations
> 
> > Server1 (x16)
> > model name      : Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz
> 
> Xeon 5500 series (this is obviously the G6 system) has FlexMigration
> 
> > Server2 (x8)
> > model name      : Intel(R) Xeon(R) CPU           E5420  @ 2.50GHz
> 
> Xeon 5400 series (this is obviously the G5 system) does not have
>  FlexMigration
> 
> That''s why you''re able to livemigrate from G5 to G6 and
not the other way.
> 
> FlexMigration essentially allows live migration across processors even
> with some differences in instruction sets.
> 
> This is specific to the processor though, there may be other
> dependencies with respect to the rest of the server platform that
> could cause livemigration between two dislike systems to fail.
> 
> Regards,
> --
> Ravi
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
I''m live migrating in between a HP DL 380 G6 machine and an old Dell
Poweredge
860 that has no FlexMigration (AFAIK). This is on Xen 3.2 though.

B.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Dustin Henning

2010-Jul-08 13:39 UTC

head link

RE: [Xen-users] Do systems have to be IDENTICAL for live migration?

I thought it was discussed in a previous thread that as long as all
processors have the same capabilities (additional capabilities being
irrelevant) as the processor that the VM started on a live migration would
be fine.  It could be that the destination processor has to have the same
capabilities as the current processor regardless of whether or not this was
the processor the VM was originally started on (again, additional
capabilities would be irrelevant, not assisting or preventing in the
migration).  However, the thread I refer to would have some age (months to
years) on it, and it may have been related to a previous Xen limitation vs a
processor limitation as is now being discussed.
	Dustin

-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Bart Coninckx
Sent: Thursday, July 08, 2010 05:01
To: xen-users@lists.xensource.com
Cc: Ravi Giri
Subject: Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

On Thursday 08 July 2010 10:37:05 Ravi Giri wrote:> On Wed, Jul 7, 2010 at 10:45 PM, James Pifer <jep@obrien-pifer.com>
wrote:
> 
> AFAIK, Intel processors with ''FlexMigration'' support
allow live
> migration across different processor generations
> 
> > Server1 (x16)
> > model name      : Intel(R) Xeon(R) CPU           E5540  @ 2.53GHz
> 
> Xeon 5500 series (this is obviously the G6 system) has FlexMigration
> 
> > Server2 (x8)
> > model name      : Intel(R) Xeon(R) CPU           E5420  @ 2.50GHz
> 
> Xeon 5400 series (this is obviously the G5 system) does not have
>  FlexMigration
> 
> That''s why you''re able to livemigrate from G5 to G6 and
not the other way.
> 
> FlexMigration essentially allows live migration across processors even
> with some differences in instruction sets.
> 
> This is specific to the processor though, there may be other
> dependencies with respect to the rest of the server platform that
> could cause livemigration between two dislike systems to fail.
> 
> Regards,
> --
> Ravi
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
I''m live migrating in between a HP DL 380 G6 machine and an old Dell
Poweredge 
860 that has no FlexMigration (AFAIK). This is on Xen 3.2 though.

B.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Ravi Giri

2010-Jul-08 14:20 UTC

head link

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

On Thu, Jul 8, 2010 at 7:09 PM, Dustin Henning
<Dustin.Henning@prd-inc.com> wrote:>        I thought it was discussed in a previous thread that as long as all
> processors have the same capabilities (additional capabilities being
> irrelevant) as the processor that the VM started on a live migration would
> be fine.  It could be that the destination processor has to have the same
I assume this is still true,
>> On Thursday 08 July 2010 10:37:05 Ravi Giri wrote:
>> Xeon 5500 series (this is obviously the G6 system) has FlexMigration
I looked up the documentation on this, and I was wrong in stating the above.

The doc says "Intel® VT FlexMigration supports live VM migration
across all Intel® Core™ microarchitecture-based servers. It is
included in the new Intel® Xeon® processor 5400 series, and provides
backward compatibility for live VM migration with current dualcore
Intel® Core™ microarchitecture products (Xeon 5100 and Xeon 3000) and
forward compatibility with future dual- and multi-core processors"

My bad. Since the OP is trying livemigration across Xeon 5400 and 5500
series, processor difference cannot be the cause of the livemigration
failure.

Regards,
--
Ravi

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Maybe Matching Threads

Search for more seemingly similar threads

Xen users - Jul 2010 - Do systems have to be IDENTICAL for live migration?

[Xen-users] Do systems have to be IDENTICAL for live migration?

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

RE: [Xen-users] Do systems have to be IDENTICAL for live migration?

Re: [Xen-users] Do systems have to be IDENTICAL for live migration?

Maybe Matching Threads