> 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:
>
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: /bugs.launchpad .net/bugs/ 273283 python2. 5/site- packages/ xen/xm/ main.py" , line 61, in <module> xc.xc() xc.Error: (1, 'Internal error', 'Could not obtain handle on privileged command interface (2 = No such file or directory)') local/sbin: /usr/local/ bin:/usr/ sbin:/usr/ bin:/sbin: /bin:/usr/ games ru_RU:ru: en_GB:en
> 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:/
> 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/
> xc = xen.lowlevel.
> xen.lowlevel.
>
> 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/
> LANG=ru_RU.UTF-8
> LANGUAGE=
> PythonArgs: ['/usr/sbin/xm']
> SourcePackage: xen-3.3
> Title: xm crashed with Error in <module>()
> Uname: Linux 2.6.27-4-server i686
> UserGroups:
>