Fedora 10 x_64
by gregg mogul
I have installed fedora 10 and am trying to get xen working. When I try to load xend I get the following error...
xend
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/xend", line 16, in <module>
from xen.xend.server import SrvDaemon
File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDaemon.py", line 26, in <module>
import relocate
File "/usr/lib64/python2.5/site-packages/xen/xend/server/relocate.py", line 28, in <module>
from xen.xend import XendDomain
File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomain.py", line 35, in <module>
from xen.xend import XendOptions, XendCheckpoint, XendDomainInfo
File "/usr/lib64/python2.5/site-packages/xen/xend/XendCheckpoint.py", line 20, in <module>
from xen.xend import balloon, sxp, image
File "/usr/lib64/python2.5/site-packages/xen/xend/image.py", line 44, 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)')
SeLinux is disabled. Is there some config file I am missing?
Thanks in advance
_________________________________________________________________
Send e-mail faster without improving your typing skills.
http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_spee...
15 years, 4 months
4gb seg fix error
by Guillaume
hi,
I'im stuck with an error with a fedora 9&10 domU error :this error is
common and i can find workaround/solution on forums and ML, but no one
help me.
I try to rename/delete the /lib/tls directory, echo "hwcap 0
nosegneg" > /etc/ld.conf.so.d/nosegneg.conf, but it does nothing.
I read somewhere that installing "libc6-xen" will correct this
behavior but i was unable to find this package.
Does someone have an idea ?
My config is :
dom0 = debian etch
domU1 = fedora 9
domU2 = fedora 10
The 2 fedora distrib have this error reported in syslog.
>>Dec 11 20:22:27 valinor kernel: printk: 646140 messages suppressed.
>>Dec 11 20:22:27 valinor kernel: 4gb seg fixup, process bash (pid 3999), cs:ip 73:0022a7e5
thanks.
--
Guillaume
15 years, 4 months
Re: [Fedora-xen] RHEL Update Virt-Manager VNC Problems
by Jim Klein
Sorry, I should have mentioned that I did all that. Interestingly, it seems to be related to the subnet I am in (am using ssh to connect to the host.) I am investigating further, but it appears that If I am on the same subnet as the host, it works. I was working before on the other end of an ipsec tunnel, where I got no love. Pretty sure this all worked before, but will need to spend some more time digging to figure it out.
----- Original Message -----
From: "Daniel P. Berrange" <berrange(a)redhat.com>
To: "Jim Klein" <jklein(a)saugus.k12.ca.us>
Cc: "fedora-xen" <fedora-xen(a)redhat.com>
Sent: Monday, December 1, 2008 2:27:22 AM GMT -08:00 US/Canada Pacific
Subject: Re: [Fedora-xen] RHEL Update Virt-Manager VNC Problems
On Sun, Nov 30, 2008 at 07:02:00PM -0800, Jim Klein wrote:
> Just updated all my RHEL4 VMs and RHEL 5 hosts, and virt-manager can no
> longer connect to the consoles on the vms. Tried recreating VNC adapters
> in virt-manager to no avail. VMs running kernel 2.6.9-78.0.8.ELxenU. Must
> be missing something, but not sure where to look. Any assistance would be
> greatly appreciated.
Use 'virsh dumpxml' to look at the running domain config. It should show
you a element like "<graphics type='vnc' port='5900'/>". If the port
number is -1, then its failed to start VNC for some reason. If the graphics
tag is missing completely then the config file is wrong.
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
15 years, 5 months
RHEL Update Virt-Manager VNC Problems
by Jim Klein
Just updated all my RHEL4 VMs and RHEL 5 hosts, and virt-manager can no longer connect to the consoles on the vms. Tried recreating VNC adapters in virt-manager to no avail. VMs running kernel 2.6.9-78.0.8.ELxenU. Must be missing something, but not sure where to look. Any assistance would be greatly appreciated.
15 years, 5 months