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

RE: [Xen-users] New DomU on older Dom0



Can you post how your config file NEW looks like? 

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Danilo Godec
> Sent: 19 March 2009 08:58
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] New DomU on older Dom0
> 
> Hi,
> 
> I have a Xen server running OpenSuSE 10.2, with Xen version
> 3.0.3_11774.
> It's happily hosting two DomU's running the same OS / kernel.
> 
> Now I tried to create a new DomU running a newer OS - OpenSuSE 11.1. It
> comes with Xen version 3.3.1_18494_03.
> 
> Unfortunately for me, it doesn't work - this is what I get:
> > xen1:/etc/xen/vm # xm create NEW
> > Using config file "NEW".
> > Error: (22, 'Invalid argument')
> And this is what I get in /var/log/xen/xend.log:
> 
> > [2009-03-19 16:53:48 xend.XendDomainInfo 9949] DEBUG
> > (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'EBA2'],
> > ['memory', 512], ['vcpus', 1], ['bootloader',
> > '/usr/lib/xen/boot/domUloader.py'], ['bootloader_args',
> > '--entry=xvdb1:/boot/vmlinuz-xen,/boot/initrd-xen --root=/dev/xvda1
> > --disks="[[\'phy:mapper/system-EBA2\', \'xvda1\', \'w\', None],
> > [\'file:/etc/xen/images/EBA2/disk0\', \'xvdb\', \'w\', None]]"'],
> > ['image', ['linux', ['ramdisk', '/var/lib/xen/tmp/initrd.jKJoMU'],
> > ['kernel', '/var/lib/xen/tmp/vmlinuz.31cMnu'], ['args', '3'],
> ['root',
> > '/dev/xvda1 xencons=tty clock=jiffies mem=4096m']]], ['device',
> > ['vbd', ['uname', 'phy:mapper/system-EBA2'], ['dev', 'xvda1'],
> > ['mode', 'w']]], ['device', ['vbd', ['uname',
> > 'file:/etc/xen/images/EBA2/disk0'], ['dev', 'xvdb'], ['mode', 'w']]],
> > ['device', ['vif', ['bridge', 'xenbr0'], ['mac',
> '00:16:3e:00:00:fe']]]])
> > [2009-03-19 16:53:48 xend.XendDomainInfo 9949] DEBUG
> > (XendDomainInfo:296) parseConfig: config is ['vm', ['name', 'EBA2'],
> > ['memory', 512], ['vcpus', 1], ['bootloader',
> > '/usr/lib/xen/boot/domUloader.py'], ['bootloader_args',
> > '--entry=xvdb1:/boot/vmlinuz-xen,/boot/initrd-xen --root=/dev/xvda1
> > --disks="[[\'phy:mapper/system-EBA2\', \'xvda1\', \'w\', None],
> > [\'file:/etc/xen/images/EBA2/disk0\', \'xvdb\', \'w\', None]]"'],
> > ['image', ['linux', ['ramdisk', '/var/lib/xen/tmp/initrd.jKJoMU'],
> > ['kernel', '/var/lib/xen/tmp/vmlinuz.31cMnu'], ['args', '3'],
> ['root',
> > '/dev/xvda1 xencons=tty clock=jiffies mem=4096m']]], ['device',
> > ['vbd', ['uname', 'phy:mapper/system-EBA2'], ['dev', 'xvda1'],
> > ['mode', 'w']]], ['device', ['vbd', ['uname',
> > 'file:/etc/xen/images/EBA2/disk0'], ['dev', 'xvdb'], ['mode', 'w']]],
> > ['device', ['vif', ['bridge', 'xenbr0'], ['mac',
> '00:16:3e:00:00:fe']]]]
> > [2009-03-19 16:53:48 xend.XendDomainInfo 9949] DEBUG
> > (XendDomainInfo:395) parseConfig: result is {'shadow_memory': None,
> > 'uuid': None, 'on_crash': None, 'on_reboot': None, 'localtime': None,
> > 'image': ['linux', ['ramdisk', '/var/lib/xen/tmp/initrd.jKJoMU'],
> > ['kernel', '/var/lib/xen/tmp/vmlinuz.31cMnu'], ['args', '3'],
> ['root',
> > '/dev/xvda1 xencons=tty clock=jiffies mem=4096m']], 'on_poweroff':
> > None, 'bootloader_args':
> > '--entry=xvdb1:/boot/vmlinuz-xen,/boot/initrd-xen --root=/dev/xvda1
> > --disks="[[\'phy:mapper/system-EBA2\', \'xvda1\', \'w\', None],
> > [\'file:/etc/xen/images/EBA2/disk0\', \'xvdb\', \'w\', None]]"',
> > 'cpus': None, 'name': 'EBA2', 'backend': [], 'vcpus': 1,
> 'cpu_weight':
> > None, 'features': None, 'vcpu_avail': None, 'memory': 512, 'device':
> > [('vbd', ['vbd', ['uname', 'phy:mapper/system-EBA2'], ['dev',
> > 'xvda1'], ['mode', 'w']]), ('vbd', ['vbd', ['uname',
> > 'file:/etc/xen/images/EBA2/disk0'], ['dev', 'xvdb'], ['mode', 'w']]),
> > ('vif', ['vif', ['bridge', 'xenbr0'], ['mac',
> '00:16:3e:00:00:fe']])],
> > 'bootloader': '/usr/lib/xen/boot/domUloader.py', 'cpu': None,
> > 'maxmem': None}
> > [2009-03-19 16:53:48 xend.XendDomainInfo 9949] DEBUG
> > (XendDomainInfo:1274) XendDomainInfo.construct: None
> > [2009-03-19 16:53:48 xend.XendDomainInfo 9949] DEBUG
> > (XendDomainInfo:1306) XendDomainInfo.initDomain: 18 1.0
> > [2009-03-19 16:53:48 xend 9949] DEBUG (balloon:146) Balloon: 786696
> > KiB free; need 524288; done.
> > [2009-03-19 16:53:48 xend 9949] INFO (image:136) buildDomain os=linux
> > dom=18 vcpus=1
> > [2009-03-19 16:53:48 xend 9949] DEBUG (image:191) dom            = 18
> > [2009-03-19 16:53:48 xend 9949] DEBUG (image:192) image          =
> > /var/lib/xen/tmp/vmlinuz.31cMnu
> > [2009-03-19 16:53:48 xend 9949] DEBUG (image:193) store_evtchn   = 1
> > [2009-03-19 16:53:48 xend 9949] DEBUG (image:194) console_evtchn = 2
> > [2009-03-19 16:53:48 xend 9949] DEBUG (image:195) cmdline        =
> > root=/dev/xvda1 xencons=tty clock=jiffies mem=4096m 3
> > [2009-03-19 16:53:48 xend 9949] DEBUG (image:196) ramdisk        =
> > /var/lib/xen/tmp/initrd.jKJoMU
> > [2009-03-19 16:53:48 xend 9949] DEBUG (image:197) vcpus          = 1
> > [2009-03-19 16:53:48 xend 9949] DEBUG (image:198) features       =
> > [2009-03-19 16:53:48 xend.XendDomainInfo 9949] ERROR
> > (XendDomainInfo:202) Domain construction failed
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> > line 195, in create
> >     vm.initDomain()
> >   File "/usr/lib/python2.5/site-packages/xen/xend/XendDomainInfo.py",
> > line 1384, in initDomain
> >     raise VmError(str(exn))
> > VmError: (22, 'Invalid argument')
> > [2009-03-19 16:53:48 xend.XendDomainInfo 9949] DEBUG
> > (XendDomainInfo:1470) XendDomainInfo.destroy: domid=18
> > [2009-03-19 16:53:48 xend.XendDomainInfo 9949] DEBUG
> > (XendDomainInfo:1478) XendDomainInfo.destroyDomain(18)
> 
> Is there anything I can do to make it work - besides upgrading the Dom0
> or running an older kernel on my new DomU?
> 
>  Thanks, Danilo
> 
> 
> _______________________________________________
> 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

 


Rackspace

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