WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] PV on Centos 5 64-bit

To: Jens-Petter Salvesen <jens-petter.salvesen@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] PV on Centos 5 64-bit
From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
Date: Wed, 14 Nov 2007 11:26:18 +0000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 14 Nov 2007 03:25:24 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=QPyLuFoS7MfNpoH/DJcJfkapzY2BKFP1ogmg0M+NpAA=; b=eNrnFKvQjxot3amCCfRt5KVG29mbpl1FKM2gex5pGpn5tvwKYjWgMnm9MgpYBBEnpZ0oJAumXBTPcqL4zn0FPx70Q6jKbSHtUT5p3/JETl0Yp6CiEF0AN4HRtJb2VfC/XLjwjcA2wT18RkNywE/8PFVTospMibzOdtew7HCVuds=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=fUgl8+O7mcr5amJlq6CUM2zcRruo8UtkIboMnpTzOkqaK2WPKpUXSW63ScV5z6fkKwkQMFPkqvQyn+xB5pFQUyKMI7YJKaDkGyWB8AVsIBJRH2jpRIVfVlUXUlHmkGF8+u8BLK+9xPB8XFXxwwYIy2XVExow0XtwTjooIHIjhQo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <5A6326FE9B1B3244AC5255B47DA262A13A05FD@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <5A6326FE9B1B3244AC5255B47DA262A13A05FD@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.6 (Windows/20070728)
Jens-Petter Salvesen wrote:
Hi,
I'm having a very difficult time getting paravirtualized Xen running on
Centos 5 64bit and I'm hoping someone can spot what I'm doing wrong.
I've been attemping to do this for a few days now and I'm really not
seeing what I'm doing wrong.
Here's what I've done: 1. Installed Centos 5 64-bit on the Dom0
2. Installed a fully virtualized DomU running Centos 5 64-bit.
3. Created a new configuration file that will create a paravirtualized
DomU.
Why aren't you using virt-install? Did you want to duplicate the virtual system entirely?

Also, if you're using pygrub, you don't have to state a kernel. I don't know if it breaks things, but it's confusing at best.


The DomU boots and runs in fully virtualized mode. However, the
paravirutalized DomU refuses to boot.
Here are the relevant configurations: 1. The fully virtualized config

# Automatically generated xen config file
name = "vm_oracle"
builder = "hvm"
memory = "2000"
disk = [ 'phy:/dev/BigMamaVolGroup/VMOracleSysDisk,hda,w', ]
vif = [ 'type=ioemu, mac=00:16:3e:67:38:e4, bridge=xenbr0', ]
uuid = "d0e7d705-aa8c-c2c0-8926-bc03d3f9d56a"
device_model = "/usr/lib64/xen/bin/qemu-dm"
kernel = "/usr/lib/xen/boot/hvmloader"
vnc=1
vncunused=1
apic=1
acpi=1
pae=1
vcpus=2
serial = "pty" # enable serial console
on_reboot   = 'restart'
on_crash    = 'restart'

2. The paravirtualized config

# Automatically generated xen config file
name = "vm_oracle_para"
builder = "linux"
memory = "2000"
disk = [ 'phy:/dev/BigMamaVolGroup/VMOracleSysDisk,hda,w', ]
vif = [ 'type=ioemu, mac=00:16:3e:67:38:e4, bridge=xenbr0', ]
uuid = "d0e7d705-aa8c-c2c0-8926-bc03d3f9d56a"
#pae=1
kernel="/boot/vmlinuz-2.6.18-8.1.15.el5.centos.plusxen"
bootloader="/usr/bin/pygrub"
vcpus=2
serial = "pty" # enable serial console
on_reboot   = 'restart'
on_crash    = 'preserve'


Also on Dom0:
[root@bigmama xen]# uname -a
Linux bigmama.secana.local 2.6.18-8.1.15.el5.centos.plusxen #1 SMP Thu
Oct 25 07:21:34 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
[root@bigmama xen]# arch
x86_64




Then, I try to create the vm_oracle_para DomU, choosing the same kernel
as the Dom0. (The vm_oracle is of course not running)

[root@bigmama xen]# xm create -c vm_oracle_para
Using config file "./vm_oracle_para".
Going to boot CentOS (2.6.18-8.1.15.el5.centos.plusxen)
  kernel: /xen.gz-2.6.18-8.1.15.el5.centos.plus
Error: (22, 'Invalid argument')

Hmm! Let's look at the logs:

[root@bigmama xen]# xm log | tail -100
....
[2007-11-14 10:44:53 xend.XendDomainInfo 8352] DEBUG
(XendDomainInfo:190) XendDomainInfo.create([\047vm\047, [\047name\047,
\047vm_oracle_para\047], [\047memory\047, \0472000\047],
[\047on_reboot\047, \047restart\047], [\047on_crash\047,
\047preserve\047], [\047vcpus\047, 2], [\047uuid\047,
\047d0e7d705-aa8c-c2c0-8926-bc03d3f9d56a\047], [\047bootloader\047,
\047/usr/bin/pygrub\047], [\047image\047, [\047linux\047,
[\047kernel\047, \047/var/lib/xen/vmlinuz.wLlJ26\047], [\047args\047,
\047None\047]]], [\047device\047, [\047vbd\047, [\047uname\047,
\047phy:/dev/BigMamaVolGroup/VMOracleSysDisk\047], [\047dev\047,
\047hda\047], [\047mode\047, \047w\047]]], [\047device\047,
[\047vif\047, [\047bridge\047, \047xenbr0\047], [\047mac\047,
\04700:16:3e:67:38:e4\047], [\047type\047, \047ioemu\047]]]])
[2007-11-14 10:44:53 xend.XendDomainInfo 8352] DEBUG
(XendDomainInfo:296) parseConfig: config is [\047vm\047, [\047name\047,
\047vm_oracle_para\047], [\047memory\047, \0472000\047],
[\047on_reboot\047, \047restart\047], [\047on_crash\047,
\047preserve\047], [\047vcpus\047, 2], [\047uuid\047,
\047d0e7d705-aa8c-c2c0-8926-bc03d3f9d56a\047], [\047bootloader\047,
\047/usr/bin/pygrub\047], [\047image\047, [\047linux\047,
[\047kernel\047, \047/var/lib/xen/vmlinuz.wLlJ26\047], [\047args\047,
\047None\047]]], [\047device\047, [\047vbd\047, [\047uname\047,
\047phy:/dev/BigMamaVolGroup/VMOracleSysDisk\047], [\047dev\047,
\047hda\047], [\047mode\047, \047w\047]]], [\047device\047,
[\047vif\047, [\047bridge\047, \047xenbr0\047], [\047mac\047,
\04700:16:3e:67:38:e4\047], [\047type\047, \047ioemu\047]]]]
[2007-11-14 10:44:53 xend.XendDomainInfo 8352] DEBUG
(XendDomainInfo:397) parseConfig: result is {\047shadow_memory\047:
None, \047start_time\047: None, \047uuid\047:
\047d0e7d705-aa8c-c2c0-8926-bc03d3f9d56a\047, \047on_crash\047:
\047preserve\047, \047on_reboot\047: \047restart\047, \047localtime\047:
None, \047image\047: [\047linux\047, [\047kernel\047,
\047/var/lib/xen/vmlinuz.wLlJ26\047], [\047args\047, \047None\047]],
\047on_poweroff\047: None, \047bootloader_args\047: None, \047cpus\047:
None, \047name\047: \047vm_oracle_para\047, \047backend\047: [],
\047vcpus\047: 2, \047cpu_weight\047: None, \047features\047: None,
\047vcpu_avail\047: None, \047memory\047: 2000, \047device\047:
[(\047vbd\047, [\047vbd\047, [\047uname\047,
\047phy:/dev/BigMamaVolGroup/VMOracleSysDisk\047], [\047dev\047,
\047hda\047], [\047mode\047, \047w\047]]), (\047vif\047, [\047vif\047,
[\047bridge\047, \047xenbr0\047], [\047mac\047,
\04700:16:3e:67:38:e4\047], [\047type\047, \047ioemu\047]])],
\047bootloader\047: \047/usr/bin/pygrub\047, \047cpu\047: None,
\047maxmem\047: None}
[2007-11-14 10:44:53 xend.XendDomainInfo 8352] DEBUG
(XendDomainInfo:1264) XendDomainInfo.construct: None
[2007-11-14 10:44:53 xend.XendDomainInfo 8352] DEBUG
(XendDomainInfo:1296) XendDomainInfo.initDomain: 70 1.0
[2007-11-14 10:44:53 xend 8352] DEBUG (balloon:127) Balloon: 4125180 KiB
free; need 2048000; done.
[2007-11-14 10:44:53 xend 8352] INFO (image:136) buildDomain os=linux
dom=70 vcpus=2
[2007-11-14 10:44:53 xend 8352] DEBUG (image:199) dom            = 70
[2007-11-14 10:44:53 xend 8352] DEBUG (image:200) image          =
/var/lib/xen/vmlinuz.wLlJ26
[2007-11-14 10:44:53 xend 8352] DEBUG (image:201) store_evtchn   = 1
[2007-11-14 10:44:53 xend 8352] DEBUG (image:202) console_evtchn = 2
[2007-11-14 10:44:53 xend 8352] DEBUG (image:203) cmdline        =  None
[2007-11-14 10:44:53 xend 8352] DEBUG (image:204) ramdisk        =
[2007-11-14 10:44:53 xend 8352] DEBUG (image:205) vcpus          = 2
[2007-11-14 10:44:53 xend 8352] DEBUG (image:206) features       =
[2007-11-14 10:44:53 xend.XendDomainInfo 8352] ERROR
(XendDomainInfo:202) Domain construction failed
Traceback (most recent call last):
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 195, in create
    vm.initDomain()
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1377, in initDomain
    raise VmError(str(exn))
VmError: (22, \047Invalid argument\047)
[2007-11-14 10:44:53 xend.XendDomainInfo 8352] DEBUG
(XendDomainInfo:1463) XendDomainInfo.destroy: domid=70
[2007-11-14 10:44:53 xend.XendDomainInfo 8352] DEBUG
(XendDomainInfo:1471) XendDomainInfo.destroyDomain(70)

.. and..
[root@bigmama xen]# tail -2 /var/log/xen/xend-debug.log
ERROR: Kernel not a Xen-compatible Elf image.
ERROR: Error constructing guest OS




If I start vm_oracle (not vm_oracle_para), I'll get this:

[root@vm-oracle ~]# uname -a
Linux vm-oracle.secana.local 2.6.18-8.1.15.el5.centos.plus #1 SMP Thu
Oct 25 06:48:46 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux
[root@vm-oracle ~]# arch
x86_64

I've set up grub to boot by defailt non-xen kernel in order to
accomodate booting both in fully virtualized and paravirtualized mode. I
use pygrub to boot the xen-kernel when trying to boot in paravirtualized
mode.

As you probably spotted, I'm using LVM on the Dom0 to provide physical
storage for my virtual block devices.



Can anyone provide a link til a guide, or can anyone tell me what I'm
doing wrong, please?

Best regards,
Jens-Petter Salvesen

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


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

<Prev in Thread] Current Thread [Next in Thread>