This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: Jia Rao <rickenrao@xxxxxxxxx>
Subject: Re: [Xen-users] Problem installing CentOS DomU.
From: Sadique Puthen <sputhenp@xxxxxxxxxx>
Date: Thu, 21 Feb 2008 12:36:16 +0530
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 20 Feb 2008 23:07:15 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <994429490802202056x517b5db3x4fb885bd3ff36c2f@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <994429490802202056x517b5db3x4fb885bd3ff36c2f@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20070926)
Jia Rao 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.

You need a proper initrd image to work with this.

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= <>.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' ]

Better you use tap:aio: instead of file:.

name    = 'VM_para'
vif  = [ '' ]
ip = " <>"

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.

This is not true.

But I did successfully installed HVM 64 bit dom0.
Does Xen support para-virtualized domU?

Xen supports 64bit paravirt domu on 64bit dom0. And even 32bit dom0.

Does anyone know what is my problem with the 64 bit domU? (I tried 32 bit domU, the same problem.) .

The problem here is the way you are doing things. There is no need you compile xen-3.1 from source and take risk to make xen working on a Centos-5.1. CentOS-5.1 provides xen support in the distribution (which is xen-3.1). All that you need to do is "yum install kernel-xen xen virt-manager". Then use virt-manager to create and manage guests.

If you want to run xen-3.2, it's ok to compile it from source. Otherwise I recommend using the xen provided with the distribution.


Thanks very much,

Xen-users mailing list

Xen-users mailing list