[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] can't start RH4 domU on RH5 dom0 Error: (22, 'Invalid argument')

  • To: Andrey Dmitriev <admitriev@xxxxxxxxxxx>
  • From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
  • Date: Tue, 17 Jul 2007 12:17:42 +0100
  • Cc: mark.williamson@xxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 17 Jul 2007 04:15:20 -0700
  • 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=D8Tpt8t2Q7HWHntR5X7ZPeHTARGOm+9dqbQsi5TOo41ob1uZoarNHex7PbF3EDAZb/lK3qi7oUt9bKX/s/cPdRdtF8QO4IBUFJ7y+wS1AkqoXVFF5cgDWvem25aVFmHBT7jb4EA4tKTN/qTv0IXcoIFpPpJfoex3D0Uo/slcOnQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Andrey Dmitriev wrote:
Modified my config file as

[root@mt-mail1 xen]# more /etc/xen/scalix2
#kernel = "/boot/vmlinuz"
#ramdisk = "/boot/initrd.img"

memory = 512
name   = "hating-xen"

vif    = ['ip = "", bridge=xenbr0']

disk   = [

BTW, it boots fine with vmlinuz, which is a CentOS xen kernel. However, it goes right into some installation, which I can't seem to get out of. Does it really matter which kernel I run? And how can I avoid the installation menus.

I also just discovered that I boot fine with vmlinuz-2.6.18-8.1.6.el5xen, but it pukes on mounting file systems.

[root@mt-mail1 xen]# more xend.log
[2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'hating-xen'], ['memory', 512 ], ['vcpus', 1], ['image', ['linux', ['kernel', '/mnt/software/vmlinuz-2.6.9-55.ELxenU']]], ['device', ['vbd', ['uname', '/dev/XEN/scalixroot '], ['dev', 'sda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', '/dev/XEN/scalixvar'], ['dev', 'sda3'], ['mode', 'w']]], ['device', ['vbd' , ['uname', '/dev/XEN/scalixswap'], ['dev', 'sda2'], ['mode', 'w']]], ['device', ['vif', ['ip', '""'], ['bridge', 'xenbr0']]]]) [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG (XendDomainInfo:296) parseConfig: config is ['vm', ['name', 'hating-xen'], ['memory', 51 2], ['vcpus', 1], ['image', ['linux', ['kernel', '/mnt/software/vmlinuz-2.6.9-55.ELxenU']]], ['device', ['vbd', ['uname', '/dev/XEN/scalixroo t'], ['dev', 'sda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', '/dev/XEN/scalixvar'], ['dev', 'sda3'], ['mode', 'w']]], ['device', ['vbd ', ['uname', '/dev/XEN/scalixswap'], ['dev', 'sda2'], ['mode', 'w']]], ['device', ['vif', ['ip', '""'], ['bridge', 'xenbr0']]]] [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG (XendDomainInfo:397) parseConfig: result is {'shadow_memory': None, 'start_time': None, 'uuid': None, 'on_crash': None, 'on_reboot': None, 'localtime': None, 'image': ['linux', ['kernel', '/mnt/software/vmlinuz-2.6.9-55.ELxenU']] , 'on_poweroff': None, 'bootloader_args': None, 'cpus': None, 'name': 'hating-xen', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features' : None, 'vcpu_avail': None, 'memory': 512, 'device': [('vbd', ['vbd', ['uname', '/dev/XEN/scalixroot'], ['dev', 'sda1'], ['mode', 'w']]), ('v bd', ['vbd', ['uname', '/dev/XEN/scalixvar'], ['dev', 'sda3'], ['mode', 'w']]), ('vbd', ['vbd', ['uname', '/dev/XEN/scalixswap'], ['dev', 'sd a2'], ['mode', 'w']]), ('vif', ['vif', ['ip', '""'], ['bridge', 'xenbr0']])], 'bootloader': None, 'cpu': None, 'maxmem': None} [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG (XendDomainInfo:1264) XendDomainInfo.construct: None [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG (XendDomainInfo:1296) XendDomainInfo.initDomain: 7 1.0 [2007-07-16 23:59:37 xend 3202] DEBUG (balloon:127) Balloon: 524528 KiB free; need 524288; done. [2007-07-16 23:59:37 xend 3202] INFO (image:136) buildDomain os=linux dom=7 vcpus=1
[2007-07-16 23:59:37 xend 3202] DEBUG (image:199) dom            = 7
[2007-07-16 23:59:37 xend 3202] DEBUG (image:200) image = /mnt/software/vmlinuz-2.6.9-55.ELxenU
[2007-07-16 23:59:37 xend 3202] DEBUG (image:201) store_evtchn   = 1
[2007-07-16 23:59:37 xend 3202] DEBUG (image:202) console_evtchn = 2
[2007-07-16 23:59:37 xend 3202] DEBUG (image:203) cmdline        =
[2007-07-16 23:59:37 xend 3202] DEBUG (image:204) ramdisk        =
[2007-07-16 23:59:37 xend 3202] DEBUG (image:205) vcpus          = 1
[2007-07-16 23:59:37 xend 3202] DEBUG (image:206) features       =
[2007-07-16 23:59:37 xend.XendDomainInfo 3202] 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
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1377, in initDomain
    raise VmError(str(exn))
VmError: (22, 'Invalid argument')
[2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG (XendDomainInfo:1463) XendDomainInfo.destroy: domid=7 [2007-07-16 23:59:37 xend.XendDomainInfo 3202] DEBUG (XendDomainInfo:1471) XendDomainInfo.destroyDomain(7)

-----Original Message-----
From: Mark Williamson [mailto:mark.williamson@xxxxxxxxxxxx] Sent: Tuesday, June 26, 2007 8:13 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Cc: Andrey Dmitriev
Subject: Re: [Xen-users] can't start RH4 domU on RH5 dom0 Error: (22, 'Invalid argument')

Someone help.... what am I missing.. has to be something simple.


Please post the contents of your /var/log/xen/xend.log


[root@mt-mail1 ~]# xm create /dev/null
kernel=/mnt/software/vmlinuz-2.6.9-55.ELxenU name=ramdisk vcpus=2
memory=412 root=/dev/ram
Using config file "/dev/null".
Error: (22, 'Invalid argument')

[root@mt-mail1 ~]# xm create scalix2
Using config file "/etc/xen/scalix2".
Error: (22, 'Invalid argument')

more /etc/xen/scalix2
kernel = "/mnt/software/vmlinuz-2.6.9-55.ELxenU"
memory = 512
name   = "hating-xen"

vif    = ['ip = "", bridge=xen-br0']

disk   = ['file:/mnt/software/RHEL4-U5-x86_64-ES-disc1.iso,cdrom,r',
          'phy:XEN/XEN-scalixroot ,sda1,w'

cdrom = "/mnt/software/RHEL4-U5-x86_64-ES-disc1.iso"
root   = "/dev/sda1 "

Can you use virt-install to get pygrub set up, and that way you use a grub and kernel from the Xen guest domain itself?

I've moved away from doiing that sort of "sda1", "sda2", "sda3" filesystem allocation: I use "xvda" or "sda" so I can do more synchronous snapshots, and use kpartx to get access to individual file systems from Dom0.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.