Re: [Xen-users] Problem installing CentOS DomU.

["--[ UxBoD ]--" <uxbod@xxxxxxxxxxxx>]

Hi,

I am running a 64bit Dom0 on CentOS 5.1 and use the stock YUM packages.  All my 
DomUs are 32 bit and they do crash quite often.  The suggestion I received from 
here was either wait till CentOS 5.2 comes out with 3.2 included, or compile 
from source.

I have compiled that source and that was fine, but I am worried about 
installing over the top of the distro packages.

Regards,

-- 
--[ UxBoD ]--
// PGP Key: "curl -s http://www.splatnix.net/uxbod.asc | gpg --import"
// Fingerprint: F57A 0CBD DD19 79E9 1FCC A612 CB36 D89D 2C5A 3A84
// Keyserver: www.keyserver.net Key-ID: 0x2C5A3A84
// Phone: +44 845 869 2749 SIP Phone: uxbod@xxxxxxxxxxxxxxxx

----- "Jia Rao" <rickenrao@xxxxxxxxx> wrote:

> Hi all,
> 
> I have a Dell server with dual-core 2.4 GHz Xeon processor (3060). I
> install the 64 bit CentOS 5 Dom0 and Xen 3.1 with no problem. The HVM
> fully virtualized 64 bit DomU was also installed successfully.
> However, when I install the para-virtualized CentOS 64 bit DomU, I
> received the following error message:
> 
> [root@localhost ~]# xm create /etc/xen/VM_para.cfg
> Using config file "/etc/xen/VM_para.cfg".
> Xend has probably crashed! Invalid or missing HTTP status code.
> 
> The content of Xend.log is:
> 
> [2008-02-20 23:44:00 xend.XendDomainInfo 16686] DEBUG
> (XendDomainInfo:1349) XendDomainInfo.construct: None
> [2008-02-20 23:44:00 xend 16686] DEBUG (balloon:127) Balloon: 521740
> KiB free; need 2048; done.
> [2008-02-20 23:44:00 xend.XendDomainInfo 16686] DEBUG
> (XendDomainInfo:1397) XendDomainInfo.initDomain: 10 1.0
> [2008-02-20 23:44:00 xend.XendDomainInfo 16686] DEBUG
> (XendDomainInfo:1436) _initDomain:shadow_memory=0x0, maxmem=0x200,
> memory=0x200.
> [2008-02-20 23:44:00 xend 16686] DEBUG (balloon:133) Balloon: 521732
> KiB free; 0 to scrub; need 524288; retries: 20.
> [2008-02-20 23:44:00 xend 16686] DEBUG (balloon:148) Balloon: setting
> dom0 target to 997 MiB.
> [2008-02-20 23:44:00 xend.XendDomainInfo 16686] DEBUG
> (XendDomainInfo:1078) Setting memory target of domain Domain-0 (0) to
> 997 MiB.
> [2008-02-20 23:44:00 xend 16686] DEBUG (balloon:127) Balloon: 524804
> KiB free; need 524288; done.
> [2008-02-20 23:44:00 xend 16686] INFO (image:136) buildDomain os=linux
> dom=10 vcpus=1
> [2008-02-20 23:44:00 xend 16686] DEBUG (image:201) domid = 10
> [2008-02-20 23:44:00 xend 16686] DEBUG (image:202) memsize = 512
> [2008-02-20 23:44:00 xend 16686] DEBUG (image:203) image =
> /boot/vmlinuz-2.6.18-64-xen
> [2008-02-20 23:44:00 xend 16686] DEBUG (image:204) store_evtchn = 1
> [2008-02-20 23:44:00 xend 16686] DEBUG (image:205) console_evtchn = 2
> [2008-02-20 23:44:00 xend 16686] DEBUG (image:206) cmdline = ip=
> MailScanner warning: numerical links are often malicious:
> 172.21.4.196:1 .2.3.4::::eth0:off root=/dev/sda1 ro xencons=tty
> [2008-02-20 23:44:00 xend 16686] DEBUG (image:207) ramdisk =
> [2008-02-20 23:44:00 xend 16686] DEBUG (image:208) vcpus = 1
> [2008-02-20 23:44:00 xend 16686] DEBUG (image:209) features =
> [2008-02-20 23:44:01 xend 3076] CRITICAL (SrvDaemon:195) Xend died due
> to signal 11! Restarting it.
> [2008-02-20 23:44:01 xend 18652] INFO (SrvDaemon:283) Xend Daemon
> started
> 
> Nothing in xend-debug.log.
> 
> This seems a common problem and many asked about it, but without
> solutions.
> 
> Both Xen and the para kernels are compiled from source using the
> script provided with Xen. Dom0 and DomU use the same kernel.
> 
> My configuration for the para VM is :
> 
> kernel = '/boot/vmlinuz-2.6.18-64-xen'
> #ramdisk = '/boot/initrd-2.6.18-xen.img'
> memory = '512'
> root = '/dev/sda1 ro'
> disk = [ 'file:/var/lib/xen/images/VM_para_disk.img,sda1,w',
> 'file:/var/lib/xen/images/VM_para_swap.img,sda2,w' ]
> name = 'VM_para'
> vif = [ '' ]
> ip = " MailScanner warning: numerical links are often malicious:
> 172.21.4.196 "
> extra='xencons=tty'
> 
> on_poweroff = 'destroy'
> on_reboot = 'restart'
> on_crash = 'restart'
> 
> I saw from the xen wiki that xen does not support 64 bit domU even the
> dom0 is 64 bit. But I did successfully installed HVM 64 bit dom0.
> Does Xen support para-virtualized domU? Does anyone know what is my
> problem with the 64 bit domU? (I tried 32 bit domU, the same problem.)
> .
> 
> Thanks very much,
> Jia.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


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