Re: [Xen-devel] Re: [Xen-users] Problem with restore/migration with Xen 4.0.0 and Jeremy kernel (2.6.32.12)

[Pierre POMES <ppomes@xxxxxxxxxxxx>]

Le 2010-05-13 15:44, Pierre POMES a écrit :

I will compile again my dom0 pvops kernel,  and triple check kernel config.  I will also try without DRBD backends.

If I have new results, I will ket you know.

I compiled a new kernel. This time, I started from the Ubuntu lucid "-server" config, on which  I set specific CONFIG_XEN* options.  My previous kernel was build starting from "-generic" config, with the same CONFIG_XEN* settings.  I can send you both config if you wish.

Config diff is (left is new config) :

root@narbonne:~#  diff /boot/config-2.6.32.12-it-xen /root/config-2.6.32.12-it-xen_2.0
4c4
< # Thu May 13 22:31:10 2010
---
> # Tue May 11 22:27:57 2010
215,216c215,216
< CONFIG_DEFAULT_DEADLINE=y
< # CONFIG_DEFAULT_CFQ is not set
---
> # CONFIG_DEFAULT_DEADLINE is not set
> CONFIG_DEFAULT_CFQ=y
218c218
< CONFIG_DEFAULT_IOSCHED="deadline"
---
> CONFIG_DEFAULT_IOSCHED="cfq"
312,313c312,313
< CONFIG_PREEMPT_NONE=y
< # CONFIG_PREEMPT_VOLUNTARY is not set
---
> # CONFIG_PREEMPT_NONE is not set
> CONFIG_PREEMPT_VOLUNTARY=y
343d342
< CONFIG_ARCH_MEMORY_PROBE=y
354,356c353
< CONFIG_MEMORY_HOTPLUG=y
< CONFIG_MEMORY_HOTPLUG_SPARSE=y
< CONFIG_MEMORY_HOTREMOVE=y
---
> # CONFIG_MEMORY_HOTPLUG is not set
400d396
< CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y
447d442
< CONFIG_ACPI_HOTPLUG_MEMORY=m
1385c1380
< CONFIG_VIRTIO_BLK=y
---
> CONFIG_VIRTIO_BLK=m
1445c1440
< CONFIG_SCSI_SPI_ATTRS=y
---
> CONFIG_SCSI_SPI_ATTRS=m
1515c1510
< CONFIG_SCSI_SYM53C8XX_2=y
---
> CONFIG_SCSI_SYM53C8XX_2=m
2114c2109
< CONFIG_VIRTIO_NET=y
---
> CONFIG_VIRTIO_NET=m
4621a4617
> # CONFIG_DEBUG_KMEMLEAK is not set
4887,4889c4883,4885
< CONFIG_VIRTIO=y
< CONFIG_VIRTIO_RING=y
< CONFIG_VIRTIO_PCI=y
---
> CONFIG_VIRTIO=m
> CONFIG_VIRTIO_RING=m
> CONFIG_VIRTIO_PCI=m

My domu is still on top of DRBD.

This time, live migration and restore are really better. They are still slower than xenlinux kernel : from several tests, what is taking 10s in xenlinux kernel now needs around 15s (instead of 30/40s or more initially with my previous opvs config)

BUT : During live migration, at the end of the process, domu is still freezing (domu is 256MB RAM, there is no activity on it), from 10 to 20 seconds, and clock inside the domy may vary a few seconds (up to 5).

I also have some hangs during migration with xenlinux kernel, but they are really shorter, and clock variation seems to be smallers (around 1 second).

About clock with Xen 4, is it still possible to have the same clock for dom0 and all domus ? (independant_clock=0 in Xen 3.x)

Pierre

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