RE: [Xen-users] domain crashes with xen 3.1 on creation - Error: (22, 'Invalid argument')

["Philippe Trolliet" <p.trolliet@xxxxxxxxxxxxxxx>]

now i´m totally confused. i looked into the example config files in
dist/install/etc/xen/ and saw that those example config files are using the
same syntax as in xen 3.0. but i found a html-document in docs/misc where
another configuration syntax is mentioned.
please help

regards
philippe

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of Schober
> Walter
> Sent: Montag, 28. Mai 2007 15:38
> To: Philippe Trolliet
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] domain crashes with xen 3.1 on creation -
> Error: (22,'Invalid argument')
>
>
> Where the hell did you get this info from? I'm searching for
> hours now for a man page or something that helps me converting
> from 3.0.4 to 3.1...
>
> Thanks!
> W.
>
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Philippe Trolliet
> Sent: Friday, May 25, 2007 3:14 PM
> To: Xen-Users
> Subject: RE: [Xen-users] domain crashes with xen 3.1 on creation
> - Error: (22,'Invalid argument')
>
> ok, i see the syntax of those files changed.
> i changed my config to:
> ------------------------------------------
> (vm
>     (name mails)
>     (memory 512)
>     (image
>         (linux
>             (kernel /boot/vmlinuz-2.6.18-xen)
>             (root /dev/sda1)
>             (args 'rw fastboot 4')
>         )
>     )
>     (device (vif))
>     (device (vbd (uname phy:/dev/VolGroup00/MailserverRoot) (dev
> sda1) (mode
> w)))
>     (device (vbd (uname phy:/dev/VolGroup00/MailserverVar) (dev
> sda2) (mode
> w)))
>     (device (vbd (uname phy:/dev/VolGroup00/MailserverSwap) (dev
> sda3) (mode
> w)))
> )
> ------------------------------------------
>
> i still get following error:
>
> Using config file "./mailserver-FC6-new".
> Error: Errors were found at line 2 while processing ./mailserver-FC6-new:
>             (name mails)
>
> regards
> philippe
>
> > -----Original Message-----
> > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of Philippe
> > Trolliet
> > Sent: Freitag, 25. Mai 2007 14:56
> > To: Xen-Users
> > Subject: [Xen-users] domain crashes with xen 3.1 on creation - Error:
> > (22,'Invalid argument')
> >
> >
> > hi,
> > i recently installed xen 3.1. i´m using my config created for a
> domU with
> > xen 3.0.3. in xen 3.0.3 it worked. i copied the new kernel
> modules to the
> > appropriate directory on the domU.
> >
> > here my config:
> > ---------------------------------
> > name = "mailserver-FC6"
> > kernel = "/boot/vmlinuz-2.6.18-xen"
> > ramdisk = "/boot/xen-initrd-domU.img"
> > memory = 512
> > disk = ['phy:/dev/VolGroup00/MailserverRoot,sda1,w',
> > 'phy:/dev/VolGroup00/MailserverVar,sda2,w',
> > 'phy:/dev/VolGroup00/MailserverSwap,sda3,w']
> > root = "/dev/sda1"
> > extra = "ro selinux=0 3"
> > # vcpus = 1
> > # vif = [ 'mac=00:16:3e:1a:c5:ad, bridge=xenbr0' ]
> > # nographic=1
> > ---------------------------------
> >
> > when i want to create the domU i get following error on the console:
> >
> > Error: (22, 'Invalid argument')
> >
> >
> > here the log:
> >
> > [2007-05-25 14:49:08 xend.XendDomainInfo 3624] DEBUG
> (XendDomainInfo:190)
> > XendDomainInfo.create(['vm', ['name', 'mailserver-FC6'],
> ['memory', 512],
> > ['vcpus', 1], ['image', ['linux', ['kernel',
> '/boot/vmlinuz-2.6.18-xen'],
> > ['ramdisk', '/boot/xen-initrd-domU.img'], ['root',
> '/dev/sda1'], ['args',
> > 'ro selinux=0 3']]], ['device', ['vbd', ['uname',
> > 'phy:/dev/VolGroup00/MailserverRoot'], ['dev', 'sda1'], ['mode', 'w']]],
> > ['device', ['vbd', ['uname',
> 'phy:/dev/VolGroup00/MailserverVar'], ['dev',
> > 'sda2'], ['mode', 'w']]], ['device', ['vbd', ['uname',
> > 'phy:/dev/VolGroup00/MailserverSwap'], ['dev', 'sda3'],
> ['mode', 'w']]]])
> > [2007-05-25 14:49:08 xend.XendDomainInfo 3624] DEBUG
> (XendDomainInfo:296)
> > parseConfig: config is ['vm', ['name', 'mailserver-FC6'],
> ['memory', 512],
> > ['vcpus', 1], ['image', ['linux', ['kernel',
> '/boot/vmlinuz-2.6.18-xen'],
> > ['ramdisk', '/boot/xen-initrd-domU.img'], ['root',
> '/dev/sda1'], ['args',
> > 'ro selinux=0 3']]], ['device', ['vbd', ['uname',
> > 'phy:/dev/VolGroup00/MailserverRoot'], ['dev', 'sda1'], ['mode', 'w']]],
> > ['device', ['vbd', ['uname',
> 'phy:/dev/VolGroup00/MailserverVar'], ['dev',
> > 'sda2'], ['mode', 'w']]], ['device', ['vbd', ['uname',
> > 'phy:/dev/VolGroup00/MailserverSwap'], ['dev', 'sda3'], ['mode', 'w']]]]
> > [2007-05-25 14:49:08 xend.XendDomainInfo 3624] 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', '/boot/vmlinuz-2.6.18-xen'], ['ramdisk',
> > '/boot/xen-initrd-domU.img'], ['root', '/dev/sda1'], ['args', 'ro
> > selinux=0
> > 3']], 'on_poweroff': None, 'bootloader_args': None, 'cpus':
> None, 'name':
> > 'mailserver-FC6', 'backend': [], 'vcpus': 1, 'cpu_weight': None,
> > 'features':
> > None, 'vcpu_avail': None, 'memory': 512, 'device': [('vbd', ['vbd',
> > ['uname', 'phy:/dev/VolGroup00/MailserverRoot'], ['dev',
> 'sda1'], ['mode',
> > 'w']]), ('vbd', ['vbd', ['uname', 'phy:/dev/VolGroup00/MailserverVar'],
> > ['dev', 'sda2'], ['mode', 'w']]), ('vbd', ['vbd', ['uname',
> > 'phy:/dev/VolGroup00/MailserverSwap'], ['dev', 'sda3'],
> ['mode', 'w']])],
> > 'bootloader': None, 'cpu': None, 'maxmem': None}
> > [2007-05-25 14:49:08 xend.XendDomainInfo 3624] DEBUG
> (XendDomainInfo:1264)
> > XendDomainInfo.construct: None
> > [2007-05-25 14:49:08 xend.XendDomainInfo 3624] ERROR
> (XendDomainInfo:202)
> > Domain construction failed
> > Traceback (most recent call last):
> >   File
> "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
> > 194, in create
> >     vm.construct()
> >   File
> "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
> > 1268, in construct
> >     handle = uuid.fromString(self.info['uuid']))
> > Error: (22, 'Invalid argument')
> > [2007-05-25 14:49:08 xend.XendDomainInfo 3624] DEBUG
> (XendDomainInfo:1463)
> > XendDomainInfo.destroy: domid=None
> > [2007-05-25 14:49:08 xend 3624] ERROR (xmlrpclib2:184) (22, 'Invalid
> > argument')
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.4/site-packages/xen/util/xmlrpclib2.py",
> > line 162,
> > in _marshaled_dispatch
> >     response = self._dispatch(method, params)
> >   File "/usr/lib/python2.4/SimpleXMLRPCServer.py", line 406, in
> _dispatch
> >     return func(*params)
> >   File
> "/usr/lib/python2.4/site-packages/xen/xend/server/XMLRPCServer.py",
> > line 64, in domain_create
> >     info = XendDomain.instance().domain_create(config)
> >   File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py",
> > line 228,
> > in domain_create
> >     dominfo = XendDomainInfo.create(config)
> >   File
> "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
> > 194, in create
> >     vm.construct()
> >   File
> "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
> > 1268, in construct
> >     handle = uuid.fromString(self.info['uuid']))
> > Error: (22, 'Invalid argument')
> >
> >
> > are there errors in the python library or what´s the problem here?
> > thanks
> >
> > regards
> > philippe
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
> > __________ NOD32 2292 (20070525) Information __________
> >
> > This message was checked by NOD32 antivirus system.
> > http://www.eset.com
> >
> >
>
>
> _______________________________________________
> 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
>
> __________ NOD32 2296 (20070529) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>


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