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

[Xen-users] Re: Error creating domain: (22, 'Invalid argument')


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Christoph Dwertmann <nermal@xxxxxxx>
  • Date: Thu, 4 May 2006 16:08:38 +0000 (UTC)
  • Delivery-date: Thu, 04 May 2006 09:20:44 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Henning Sprang <henning_sprang <at> gmx.de> writes:
> 
> Demetri Mouratis wrote:
> > I'm running into this on FC5:
> > 
> > [root <at> db4 ~]# xm create -c xendomain1
> > Using config file "/etc/xen/xendomain1".
> > Going to boot Fedora Core (2.6.15-1.2054_FC5smp)
> >   kernel: /vmlinuz-2.6.15-1.2054_FC5smp
> >   initrd: /initrd-2.6.15-1.2054_FC5smp.img
> > Error: Error creating domain: (22, 'Invalid argument')
> 
> What does the xend-debug.log say?
> 
> > The physical hardware is 2GB and I'm creating xen guests running:
> 
> What is a 2GB physical hardware? Can you explain? Probably you mean RAM 
> or Harddisk, but I don't see what it has to do with your problem. the 
> PAE extensions you mention are only needed with more than 4GB of RAM, so 
> I don't see why you should need it.
> 
> > 
> > xenguest-install.py -n xendomain1 -f /home/xen/xendomain1 -s 25 -r 256 
> > -l http://ops1.rnmd.net/fedora/core/5/i386/os -x ks= 
> > http://ops1.rnmd.net/kickstart/cfgs/ks-fedora-core-5-xen-guest.cfg 
> > <http://ops1.rnmd.net/kickstart/cfgs/ks-fedora-core-5-xen-guest.cfg>
> 
> That's a a fedora-specific script, and it might be better supported on 
> the fedora-xen mailing list. If it creates a xen config that is unable 
> to be started, it has some bug probably.
> 
> Henning

Hi!

I also see this error message after upgrading to the latest Xen unstable 
changeset 9925 (I did a "hg pull -u" today). With my previous Xen version 
(changeset 9515) I had no problems. Going back to 9515 is a workaround for now.

Console error message:
Error: (22, 'Invalid argument')

Config file:
kernel = "/boot/vmlinuz-2.6.16-xenU"
memory = 80

/var/log/xend.log:

[2006-05-04 18:00:04 xend.XendDomainInfo] DEBUG (XendDomainInfo:1373) 
XendDomainInfo.destroy: domid=4
[2006-05-04 18:00:04 xend.XendDomainInfo] DEBUG (XendDomainInfo:1381) 
XendDomainInfo.destroyDomain(4)
[2006-05-04 18:00:04 xend] ERROR (xmlrpclib2:124) (22, 'Invalid argument')
Traceback (most recent call last):
  
File "/usr/src/xen-unstable.hg/dist/install/usr/lib/python/xen/util/
xmlrpclib2.py", 
line 103, in _marshaled_dispatch
    response = self._dispatch(method, params)
  File "/usr/lib/python2.3/SimpleXMLRPCServer.py", line 407, in _dispatch
    return func(*params)
  
File "/usr/src/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/server/
XMLRPCServer.py", 
line 63, in domain_create
    info = XendDomain.instance().domain_create(config)
  
File "/usr/src/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/
XendDomain.py", 
line 228, in domain_create
    dominfo = XendDomainInfo.create(config)
  
File "/usr/src/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/
XendDomainInfo.py", 
line 189, in create
    vm.initDomain()
  
File "/usr/src/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/
XendDomainInfo.py", 
line 1269, in initDomain
    self.createChannels()
  
File "/usr/src/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/
XendDomainInfo.py", 
line 1416, in createChannels
    self.store_port = self.createChannel()
  
File "/usr/src/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/
XendDomainInfo.py", 
line 1424, in createChannel
    return xc.evtchn_alloc_unbound(dom=self.domid, remote_dom=0)
error: (22, 'Invalid argument')

Is this a Xen bug?

Cheers,

Christoph



_______________________________________________
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®.