Xen users - Mar 2013 - Possible bug in Xen 4.2.1 when rebooting domU after save/restore

Hello,

After saving and restoring a DomU (teste on the same server), doing a reboot
to the newly restored domU will cause it to crash. This happens on PV and
PVHVM domUs. 
I am using qemu upstream for the HVM guests, but I don''t really think
it
matters as long as PV guests behave the same.
I want to confirm this if possible, before submitting a bug report and more
details.
I am using CentOS 6 with this mirrorlist:
http://www.crc.id.au/repo/mirrorlist-el6.txt

To reproduce:

xl save [domid] ./somefile
xl restore -d path_to_domU.cfg ./somefile
xl reboot [newdomid]


xl info:
host                   : xenrotest
release                : 3.8.2-3.el6xen.x86_64
version                : #1 SMP Sat Mar 9 20:43:07 EST 2013
machine                : x86_64
nr_cpus                : 8
max_cpu_id             : 7
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 2
cpu_mhz                : 3192
hw_caps                :
bfebfbff:28100800:00000000:00003f40:17bae3ff:00000000:00000001:00000000
virt_caps              : hvm hvm_directio
total_memory           : 16361
free_memory            : 15121
sharing_freed_memory   : 0
sharing_used_memory    : 0
free_cpus              : 0
xen_major              : 4
xen_minor              : 2
xen_extra              : .1
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
xen_commandline        : dom0_mem=1024M cpufreq=xen dom0_max_vcpus=1
dom0_vcpus_pin log_lvl=all guest_loglvl=all
cc_compiler            : gcc (GCC) 4.4.6 20120305 (Red Hat 4.4.6-4)
cc_compile_by          : mockbuild
cc_compile_domain      : crc.id.au
cc_compile_date        : Sat Feb 16 19:16:38 EST 2013
xend_config_format     : 4


Xen xl log, after issuing the reboot command:

Domain 8 needs to be cleaned up: destroying the domain
Done. Rebooting now
xc: error: 0-length read: Internal error
xc: error: read_exact_timed failed (read rc: 0, errno: 0): Internal error
xc: error: read: p2m_size (0 = Success): Internal error
libxl: error: libxl_create.c:820:libxl__xc_domain_restore_done: restoring
domain: Success
libxl: error: libxl_create.c:902:domcreate_rebuild_done: cannot (re-)build
domain: -3
libxl: error: libxl.c:1394:libxl__destroy_domid: non-existant domain 9
libxl: error: libxl.c:1358:domain_destroy_callback: unable to destroy guest
with domid 9
libxl: error: libxl_create.c:1153:domcreate_destruction_cb: unable to
destroy domain 9 following failed creation


xl save/restore and other details can be attached if needed. 

Regards,
Cristian Tomoiaga





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

Hello,

After saving and restoring a DomU (teste on the same server), doing a reboot
to the newly restored domU will cause it to crash. This happens on PV and
PVHVM domUs. 
I am using qemu upstream for the HVM guests, but I don''t really think
it
matters as long as PV guests behave the same.
I want to confirm this if possible, before submitting a bug report and more
details.
I am using CentOS 6 with this mirrorlist:
http://www.crc.id.au/repo/mirrorlist-el6.txt

To reproduce:

xl save [domid] ./somefile
xl restore -d path_to_domU.cfg ./somefile
xl reboot [newdomid]


xl info:
host                   : xenrotest
release                : 3.8.2-3.el6xen.x86_64
version                : #1 SMP Sat Mar 9 20:43:07 EST 2013
machine                : x86_64
nr_cpus                : 8
max_cpu_id             : 7
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 2
cpu_mhz                : 3192
hw_caps                :
bfebfbff:28100800:00000000:00003f40:17bae3ff:00000000:00000001:00000000
virt_caps              : hvm hvm_directio
total_memory           : 16361
free_memory            : 15121
sharing_freed_memory   : 0
sharing_used_memory    : 0
free_cpus              : 0
xen_major              : 4
xen_minor              : 2
xen_extra              : .1
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
xen_commandline        : dom0_mem=1024M cpufreq=xen dom0_max_vcpus=1
dom0_vcpus_pin log_lvl=all guest_loglvl=all
cc_compiler            : gcc (GCC) 4.4.6 20120305 (Red Hat 4.4.6-4)
cc_compile_by          : mockbuild
cc_compile_domain      : crc.id.au
cc_compile_date        : Sat Feb 16 19:16:38 EST 2013
xend_config_format     : 4


Xen xl log, after issuing the reboot command:

Domain 8 needs to be cleaned up: destroying the domain
Done. Rebooting now
xc: error: 0-length read: Internal error
xc: error: read_exact_timed failed (read rc: 0, errno: 0): Internal error
xc: error: read: p2m_size (0 = Success): Internal error
libxl: error: libxl_create.c:820:libxl__xc_domain_restore_done: restoring
domain: Success
libxl: error: libxl_create.c:902:domcreate_rebuild_done: cannot (re-)build
domain: -3
libxl: error: libxl.c:1394:libxl__destroy_domid: non-existant domain 9
libxl: error: libxl.c:1358:domain_destroy_callback: unable to destroy guest
with domid 9
libxl: error: libxl_create.c:1153:domcreate_destruction_cb: unable to
destroy domain 9 following failed creation


xl save/restore and other details can be attached if needed. 

Regards,
Cristian Tomoiaga



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