Red Hat Bugzilla – Bug 758646
Xend fails to start with NVidia NV44 GeForce 6200 card
Last modified: 2013-02-11 16:40:00 EST
Description of problem:
I installed F16 x86_64 with Xen and I'm trying to boot via
Xen 4.1.2. Apparently the boot occurs normalmene but eventually
the system stops loading.
The only message that I have about the problem is the xend.log, shown below.
I really do not know what that means.
Note: I'm using qemu + kvm without any problems.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
[2011-11-29 17:10:03 1105] INFO (SrvDaemon:339) Xend Daemon started
[2011-11-29 17:10:03 1105] INFO (SrvDaemon:343) Xend changeset: unavailable.
[2011-11-29 17:10:03 1105] ERROR (SrvDaemon:356) Exception starting xend (no element found: line 1, column 0)
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/xen/xend/server/SrvDaemon.py", line 348, in run
servers = SrvServer.create()
File "/usr/lib64/python2.7/site-packages/xen/xend/server/SrvServer.py", line 258, in create
File "/usr/lib64/python2.7/site-packages/xen/xend/server/SrvRoot.py", line 40, in __init__
File "/usr/lib64/python2.7/site-packages/xen/web/SrvDir.py", line 84, in get
val = val.getobj()
File "/usr/lib64/python2.7/site-packages/xen/web/SrvDir.py", line 52, in getobj
self.obj = klassobj()
File "/usr/lib64/python2.7/site-packages/xen/xend/server/SrvNode.py", line 30, in __init__
self.xn = XendNode.instance()
File "/usr/lib64/python2.7/site-packages/xen/xend/XendNode.py", line 1181, in instance
inst = XendNode()
File "/usr/lib64/python2.7/site-packages/xen/xend/XendNode.py", line 71, in __init__
saved_host = self.state_store.load_state('host')
File "/usr/lib64/python2.7/site-packages/xen/xend/XendStateStore.py", line 104, in load_state
dom = minidom.parse(xml_path)
File "/usr/lib64/python2.7/site-packages/_xmlplus/dom/minidom.py", line 1915, in parse
File "/usr/lib64/python2.7/site-packages/_xmlplus/dom/expatbuilder.py", line 926, in parse
result = builder.parseFile(fp)
File "/usr/lib64/python2.7/site-packages/_xmlplus/dom/expatbuilder.py", line 211, in parseFile
ExpatError: no element found: line 1, column 0
I found the origin of problem: The interface NVidia NV44 GeForce 6200 (NX6200TC).
Xen won't start if this interface is installed.
Removing it of system the Xen is booting normally.
Xen packets installed
OK.. I thought it would be this one: http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1680
which I think MA Young has already put in the xen package?
This looks similar (though not identical) to Bug 767742 .
Volnei, could you confirm whether the latest Xen has this issue?
Up to when I had the that interface installed on my machine the problem always did.
Then I removed the interface, and never more I used.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Sounds like this should have been fixed, closing as CURRENTRELEASE