thr3ads.net - Xen users - [Xen-users] Error creating domain: (22, ''Invalid argument'') [May 2006]

If this information is useful, please help other people find it:
Share via:

Demetri Mouratis

2006-May-04 07:08 UTC

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

I''m running into this on FC5:

[root@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'')

The physical hardware is 2GB and I''m creating xen guests running:

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


The research I''ve done seems to indicate the error is something related
to
PAE being on/off across the dom0/domUs.  Cat /proc/cpuinfo on dom0 verifies
that PAE is on.

What is the problem here?

Thanks.


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

Henning Sprang

2006-May-04 09:24 UTC

head link

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

Demetri Mouratis wrote:> I''m running into this on FC5:
> 
> [root@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



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

Christoph Dwertmann

2006-May-04 16:08 UTC

head link

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

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@lists.xensource.com
http://lists.xensource.com/xen-users

Demetri Mouratis

2006-May-04 16:12 UTC

head link

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

On 5/4/06, Henning Sprang <henning_sprang@gmx.de>
wrote:>
> Demetri Mouratis wrote:
> > I''m running into this on FC5:
> >
> > [root@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
>
>
> Henning,
Thanks for the reply.  It was a bit of a late night last night ;-)

You are correct, the 2GB I specified was physical RAM.  I agree I don''t
need
PAE.  The thing is, the BIOS has it enabled and the kernels available from
the FC 5 project have it enabled by default.  I need to stick with a RPM for
the kernels/userspace utilities, else roll my own and maintain it.  That
said, I''m not opposed to tracking this down by compiling
kernels/userspace
utilities from source.

I''ve used the Fedora script successfully on another Xeon box.  This db4
box
happens to be Pentium D at 3.00 GHz.  This is why I suspect some interplay
between PAE and Xen is breaking things.

Thanks.


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

Demetri Mouratis

2006-May-04 19:39 UTC

head link

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

On 5/4/06, Christoph Dwertmann <nermal@tzi.org>
wrote:>
> 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@lists.xensource.com
> http://lists.xensource.com/xen-users



Open a bug with Fedora on it this morning including log output:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190707

Am I right that this is related to PAE?

Thanks.


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

Puthiyaparambil, Aravindh

2006-May-04 22:51 UTC

head link

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

I have seen this error when trying to bring up bring up a non-PAE DomU
on a PAE hypervisor or vice-versa. If that''s the case then it will be
clearly indicated in /var/log/xend-debug.log.

 

Aravindh Puthiyaparambil
Xen Development Team
Unisys

 

________________________________

From: Demetri Mouratis [mailto:dmourati.xen.users@gmail.com] 
Sent: Thursday, May 04, 2006 3:40 PM
To: Christoph Dwertmann
Cc: xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: Error creating domain: (22, ''Invalid
argument'')

 

 

On 5/4/06, Christoph Dwertmann <nermal@tzi.org> wrote:

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<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@lists.xensource.com
http://lists.xensource.com/xen-users


 

 

Open a bug with Fedora on it this morning including log output:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190707 

Am I right that this is related to PAE?

Thanks.



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

Xen users - May 2006 - Error creating domain: (22, ''Invalid argument'')

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

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

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

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

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

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