xm crashed with Error in <module>()

[Andrey Zonov]

# xm
ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory)
Traceback (most recent call last):
  File "/usr/sbin/xm", line 8, in <module>
    from xen.xm import main
  File "/usr/lib/python2.5/site-packages/xen/xm/main.py", line 61, in <module>
    xc = xen.lowlevel.xc.xc()
xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on privileged command interface (2 = No such file or directory)')

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/sbin/xm
InterpreterPath: /usr/bin/python2.5
Package: xen-utils-3.3 3.3.0-1ubuntu6
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python2.5 /usr/sbin/xm
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=ru_RU.UTF-8
 LANGUAGE=ru_RU:ru:en_GB:en
PythonArgs: ['/usr/sbin/xm']
SourcePackage: xen-3.3
Title: xm crashed with Error in <module>()
Uname: Linux 2.6.27-4-server i686
UserGroups:

[Evan Broder (broder)]

You have to be using a kernel that's dom0 capable to use Xen. Are you? Intrepid and Jaunty don't ship a dom0 kernel, so you'll either have to build your own or grab the -xen kernel from Hardy.

What does `uname -r` say?

[Uxorious (uxorious)]

Hi Evan,

Yeah like I just posted in the bug, I noticed that it wasn't booting
into the hypervisor.

> Intrepid and Jaunty don't ship a dom0 kernel

Wow! Didn't know that. That kinda sucks :-(

> so you'll either have to
> build your own or grab the -xen kernel from Hardy.

Yeah I was looking at building my own right now ... but I might grab
the Hardy one since that will be quicker!

All this work and I probably won't end up using it in the end ... I
think passthrough of a GFX card isn't working yet :-(

Regards,
-Jeppe

On Thu, Apr 16, 2009 at 8:23 PM, Evan Broder <email address hidden> wrote:
> You have to be using a kernel that's dom0 capable to use Xen. Are you?
> Intrepid and Jaunty don't ship a dom0 kernel, so you'll either have to
> build your own or grab the -xen kernel from Hardy.
>
> What does `uname -r` say?
>
> ** Changed in: xen-3.3 (Ubuntu)
>       Status: New => Invalid
>
> --
> xm crashed with Error in <module>()
> https://bugs.launchpad.net/bugs/273283
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “xen-3.3” source package in Ubuntu: Invalid
>
> Bug description:
> # xm
> ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory)
> Traceback (most recent call last):
>  File "/usr/sbin/xm", line 8, in <module>
>    from xen.xm import main
>  File "/usr/lib/python2.5/site-packages/xen/xm/main.py", line 61, in <module>
>    xc = xen.lowlevel.xc.xc()
> xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on privileged command interface (2 = No such file or directory)')
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: Ubuntu 8.10
> ExecutablePath: /usr/sbin/xm
> InterpreterPath: /usr/bin/python2.5
> Package: xen-utils-3.3 3.3.0-1ubuntu6
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/bin/python2.5 /usr/sbin/xm
> ProcEnviron:
>  SHELL=/bin/bash
>  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
>  LANG=ru_RU.UTF-8
>  LANGUAGE=ru_RU:ru:en_GB:en
> PythonArgs: ['/usr/sbin/xm']
> SourcePackage: xen-3.3
> Title: xm crashed with Error in <module>()
> Uname: Linux 2.6.27-4-server i686
> UserGroups:
>

[Evan Broder (broder)]

Jeppe -
  I think it should basically just work to duplicate your sources.list with entries for hardy instead of intrepid/jaunty and do `aptitude install linux-image-xen`, but I'm not entirely sure.

When Ubuntu stopped supporting Xen, the official patchset for a dom0 kernel was for 2.6.18, and the Ubuntu kernel team had been forward-porting it all the way up to 2.6.24. My understanding is that they just got tired of doing that (since kvm was becoming Ubuntu's preferred virtualization platform), so they stopped forward-porting.

I think the Xen developers have submitted a patch for dom0 to the LKML, and are just waiting for it to be merged in. Word on the street is that that may happen for 2.6.30, which means there's a chance of seeing dom0 kernels in Karmic again. But we'll see.

[Uxorious (uxorious)]

Hi Evan,

> I think it should basically just work to duplicate your sources.list with entries for hardy instead of intrepid/jaunty
> and do `aptitude install linux-image-xen`, but I'm not entirely sure.

Looking at packages.ubuntu.org, it seems the last xen-image-* package
was in Gutsy!

> (since kvm was becoming Ubuntu's preferred virtualization platform)

Ah yes I was going to ask which solution they were leaning towards. Thanks.

Like I said, I'm not sure it's even feasible for me to use VM until
PCI passthrough for GFX cards is working, so I should probably either
try something simple to see if it's acceptable - or dive in trying to
help get the feature working :)

Thanks for helping out and being generally nice about everything.

Regards,
-Jeppe

On Thu, Apr 16, 2009 at 9:12 PM, Evan Broder <email address hidden> wrote:
> Jeppe -
>  I think it should basically just work to duplicate your sources.list with entries for hardy instead of intrepid/jaunty and do `aptitude install linux-image-xen`, but I'm not entirely sure.
>
> When Ubuntu stopped supporting Xen, the official patchset for a dom0
> kernel was for 2.6.18, and the Ubuntu kernel team had been forward-
> porting it all the way up to 2.6.24. My understanding is that they just
> got tired of doing that (since kvm was becoming Ubuntu's preferred
> virtualization platform), so they stopped forward-porting.
>
> I think the Xen developers have submitted a patch for dom0 to the LKML,
> and are just waiting for it to be merged in. Word on the street is that
> that may happen for 2.6.30, which means there's a chance of seeing dom0
> kernels in Karmic again. But we'll see.
>
> --
> xm crashed with Error in <module>()
> https://bugs.launchpad.net/bugs/273283
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “xen-3.3” source package in Ubuntu: Invalid
>
> Bug description:
> # xm
> ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory)
> Traceback (most recent call last):
>  File "/usr/sbin/xm", line 8, in <module>
>    from xen.xm import main
>  File "/usr/lib/python2.5/site-packages/xen/xm/main.py", line 61, in <module>
>    xc = xen.lowlevel.xc.xc()
> xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on privileged command interface (2 = No such file or directory)')
>
> ProblemType: Crash
> Architecture: i386
> DistroRelease: Ubuntu 8.10
> ExecutablePath: /usr/sbin/xm
> InterpreterPath: /usr/bin/python2.5
> Package: xen-utils-3.3 3.3.0-1ubuntu6
> ProcAttrCurrent: unconfined
> ProcCmdline: /usr/bin/python2.5 /usr/sbin/xm
> ProcEnviron:
>  SHELL=/bin/bash
>  PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
>  LANG=ru_RU.UTF-8
>  LANGUAGE=ru_RU:ru:en_GB:en
> PythonArgs: ['/usr/sbin/xm']
> SourcePackage: xen-3.3
> Title: xm crashed with Error in <module>()
> Uname: Linux 2.6.27-4-server i686
> UserGroups:
>

[Evan Broder (broder)]

Uxorious wrote:
> Looking at packages.ubuntu.org, it seems the last xen-image-* package
> was in Gutsy!

You want linux-image-xen, not xen-image -
http://packages.ubuntu.com/search?keywords=linux-image-xen

[Uxorious (uxorious)]

>> Looking at packages.ubuntu.org, it seems the last xen-image-* package
>> was in Gutsy!
>
> You want linux-image-xen, not xen-image -
> http://packages.ubuntu.com/search?keywords=linux-image-xen

I tried those, and it didn't work.
The Xen hypervisor starts up, and it gets pretty much all the way
through the boot.
Then when X starts up, the machine just dies.

Oh well.

Regards,
-Jeppe

[Priya Bhat (pbhat)]

Hey!

I need some help on this. I am running:

Ubuntu 9.10 and
Kernel 2.6.31-15-generic-pae

When I try to run any xm command, I have the same error as mentioned above, namely:

pbhat@pbhat-acis:~$ xm list
ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory)
Traceback (most recent call last):
File "/usr/sbin/xm", line 8, in <module>
from xen.xm import main
File "/usr/lib/python2.6/dist-packages/xen/xm/main.py", line 61, in <module>
xc = xen.lowlevel.xc.xc()
xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on privileged command interface (2 = No such file or directory)')

I understand that my kernel not being able to support Dom0. However I do not know how to go about solving the problem. Could someone elaborate on where I need to put the earlier kernel (hardy) version so that dom0 can use it to boot and which files I need to edit? I am new at this and I apologize if these questions seems naive.

Thanks
pr

Thanks
pr

[Andrey Zonov (andrey-zonov)]

Hi!

Try to install linux-image-xen from debian
http://packages.debian.org/lenny/linux-image-xen-amd64

Priya Bhat пишет:
> Hey!
>
> I need some help on this. I am running:
>
> Ubuntu 9.10 and
> Kernel 2.6.31-15-generic-pae
>
> When I try to run any xm command, I have the same error as mentioned
> above, namely:
>
> pbhat@pbhat-acis:~$ xm list
> ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory)
> Traceback (most recent call last):
> File "/usr/sbin/xm", line 8, in <module>
> from xen.xm import main
> File "/usr/lib/python2.6/dist-packages/xen/xm/main.py", line 61, in <module>
> xc = xen.lowlevel.xc.xc()
> xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on privileged command interface (2 = No such file or directory)')
>
>
> I understand that my kernel not being able to support Dom0. However I do
> not know how to go about solving the problem. Could someone elaborate on
> where I need to put the earlier kernel (hardy) version so that dom0 can
> use it to boot and which files I need to edit? I am new at this and I
> apologize if these questions seems naive.
>
> Thanks
> pr
>
> Thanks
> pr
>
>

[padam-CZ (pavel-adam-foto)]

Спосибо тебе за помощ.

--

Pavel ADAM

WWW galerie:
               http://www.bezezbrane.cz/album
               http://www.picasaweb.google.com/BezeZbrane
               http://www.picasaweb.google.com/pavel.adam.foto

e-mail: <email address hidden>
JABBER: <email address hidden>
SKYPE: pavel.adam-007
GSM: ([phone]

     ЧЕХИА

***************************************************
Andrey Zonov píše v St 02. 12. 2009 v 19:51 +0000:
> Hi!
>
> Try to install linux-image-xen from debian
> http://packages.debian.org/lenny/linux-image-xen-amd64
>
> Priya Bhat пишет:
> > Hey!
> >
> > I need some help on this. I am running:
> >
> > Ubuntu 9.10 and
> > Kernel 2.6.31-15-generic-pae
> >
> > When I try to run any xm command, I have the same error as mentioned
> > above, namely:
> >
> > pbhat@pbhat-acis:~$ xm list
> > ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory)
> > Traceback (most recent call last):
> > File "/usr/sbin/xm", line 8, in <module>
> > from xen.xm import main
> > File "/usr/lib/python2.6/dist-packages/xen/xm/main.py", line 61, in <module>
> > xc = xen.lowlevel.xc.xc()
> > xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on privileged command interface (2 = No such file or directory)')
> >
> >
> > I understand that my kernel not being able to support Dom0. However I do
> > not know how to go about solving the problem. Could someone elaborate on
> > where I need to put the earlier kernel (hardy) version so that dom0 can
> > use it to boot and which files I need to edit? I am new at this and I
> > apologize if these questions seems naive.
> >
> > Thanks
> > pr
> >
> > Thanks
> > pr
> >
> >
>