[Xen-devel] r: (1, 'Internal error', 'panic: xc_dom_core.c:273: xc_dom_do_gunzip: inflate failed (rc=-3)').. only on Intel hardware and only under 32-bit dom0

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

The combination is bit awkward so not sure why this is happening, but with
Xen 4.1.x hypervisor (64-bit), with a 32-bit dom0 (3.3-rcX or 3.2) and with a 
3.3-rcX or 3.2 domU
I get this:

sh-4.1# Feb 20 17:47:41 tst006 init: reloading /etc/inittab
xl info
host                   : tst006.dumpdata.com
release                : 3.3.0-rc4
version                : #1 SMP PREEMPT Mi686
nr_cpus                : 2
nr_nodes               : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 2333
hw_caps                : 
bfebfbff:20100800:00000000:00000940:0000e3fd:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 4085
free_memory            : 717
free_cpus              : 0
xen_major              : 4
xen_minor              : 1
xen_extra              : -120220
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=0xff800000
xen_changeset          : Mon Feb 13 17:57:47 2012 +0000 23225:f2543f449a49
xen_commandline        : com1=115200,8n1 cpufreq=verbose apic=debug 
apic_verbosity=debug console=com1,vga loglvl=all guest_loglvl=all apic=debug
cc_compiler            : gcc version 4.4.4 20100503 (Red Hat 4.4.4-2) (GCC) 
cc_compile_by          : konrad
cc_compile_domain      : dumpdata.com
cc_compile_date        : Mon Feb 20 12:25:42 EST 2012
xend_config_format     : 4
sh-4.1# xm create /mnt/lab/latest/test.xm 
Using config file "/mnt/lab/latest/test.xm".
Error: (1, 'Internal error', 'panic: xc_dom_core.c:273: xc_dom_do_gunzip: 
inflate failed (rc=-3)')

And only on Intel.. and only if it is a 32-bit dom0. If I do the same test with 
a 64-bit dom0 I do not see this problem.

Any thoughts of what it might be or what I should try out? My thought
was to swap out the hypervisor (use a Xen 4.0) or unstable and see if I get the 
same result.
But maybe there is something obvious out there?


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