Xen devel - Mar 2006 - domU''s on SLES 10.0b3 crashing dom0

Hi all,

I installed SLES 10.0b3 with XEN on some test-systems and created a SLES 
10.0b3-image for use with domU''s.

The installation and booting of this domU was no problem, but on some 
systems the host dom0 restarts if I generate some IP-traffic from the guest.

This happens on an old AMD Athlon 1,3GHz, an old Intel P3 and an Intel 
desktop with P4 HT/VT/EM64T but not on an Intel server with Xeon 
HT/VT/EM64T.

I also tried SLES 10.0b5 (and b4), but the package-management is not 
working yet, the installation is not correct (on the first try during 
the installation only CD1 was installed, on the second try the 
installation asked for all CDs but continued in textmode), I''m not able
to install packages later because yast doesn''t show anything to
install,
heartbeat didn''t work anylonger (only tried in b4) and the script 
"/usr/sbin/xenmon.py" is not working anymore (doesn''t show
any
cpu-load). The good thing with beta5 was that the SLES 10.0b3-guests 
where running quite stable, even with network-load!

Next step was updating the SLES 10.0b3 installation with the newer 
SLES10-i586-changeset8910.tar.bz2 .

Unfortunately I already had no success to install the new kernel with 
"yast -i  kernel-xen-2.6.16_rc3_git6-2.i586.rpm", I get the following
error:
-------------------------------
ERROR(InstTarget:E_RpmDB_subprocess_failed)
---
Including:      initramfs fsck.ext3.ext3
Bootsplash:     SuSE-SLES (1280x1024)1024)
/etc/bootsplash/themes/SuSE-NLD/animations/throbber.mng: No such file or 
directory
1446 blocks
Unknown option: force
SYNOPSIS: /sbin/update-bootloader {--image file} [--initrd file] 
[--default] [--previous] {--add|--remove}
Unknown option: refresh
SYNOPSIS: /sbin/update-bootloader {--image file} [--initrd file] 
[--default] [--previous] {--add|--remove}
error: %post(kernel-xen-2.6.16_rc3_git6-2.i586) scriptlet failed, exit 
status 1
-------------------------------

But I was able to install the other packages from the tar.bz2!

Now my Linux-domU''s are running stable, they don''t crash my
dom0, but
I''m not able to start vmx-guest anymore:

# xm create -f w2k3cit.vmx
Using config file "w2k3cit.vmx".
Error: Error creating domain: unknown image type: vmx

and the xenmon.py is not running anymore too:

# python xenmon.py
xenbaked: no process killed
ms_per_sample = 100
ERROR: Failed to mmap trace buffers (14 = Bad address)

Does s.b. has an idea how to get SLES 10.0b3 als host more stable or how 
to get b5 running better?

Thanks a lot for your answer,
-- 

Chau y hasta luego,

Thorolf

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

Thorolf Godawa wrote:
> I also tried SLES 10.0b5 (and b4), but the package-management is not 
> working yet, the installation is not correct (on the first try during the 
> installation only CD1 was installed, on the second try the installation 
> asked for all CDs but continued in textmode), I''m not able
Sounds similar to the "Most annoying bugs" in 10.1 Beta 5:
http://en.opensuse.org/Bugs:Most_Annoying_Bugs#SUSE_Linux_10.1_Beta5

Quote:
"The CD 1 needs to remain in the cd drive after installing from it. Do not 
remove it during the reboot and wait for YaST to request CD 2.. Otherwise 
the installation of packages from CD 2-5 will fail afterwards"


Best Regards,
Michael Paesold 



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

Hi,

 >"The CD 1 needs to remain in the cd drive after installing from it.
I''m sure I did so both times, the only difference between the 
installations was, that the first time I went away after starting it and 
for the second I was sitting in front of the pc ;-)

Right now I installed Ubuntu 5.10 and Xen 3.1.0 and everything runs like 
it should exept that my python-script is not able to import a library:

Traceback (most recent call last):
   File "/usr/sbin/xentop2h.py", line 52, in ?
     from xen.xend.XendClient import server
ImportError: No module named xen.xend.XendClient

Unfortunately even if I get this fixed, this is not a final solution 
because it has to run with SLES 10 too!
-- 

Chau y hasta luego,

Thorolf

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