On Thu, Nov 21, 2013 at 05:22:35PM +0100, Michal Skrivanek wrote:
>
> >> ok, that looks ok. Might be text parsing issue.
> >> And "virsh capabilities" output?
> >> what's the vdsm you're using?
> >
> > virsh capabilities" output is a bit long, see attachment
> >
> > # rpm -q vdsm
> > vdsm-4.10.3-18.fc19.x86_64
>
> hmm, works well on my box
> try master, though this code didn't change since 2012
>
> the code in vdsm/caps.py is pretty straightforward:
> caps = minidom.parseString(capabilities)
> for archTag in caps.getElementsByTagName('arch'):
> if archTag.getAttribute('name') == 'x86_64':
> return [m.firstChild.data for m in archTag.childNodes
> if m.nodeName == 'machine']
>
>
> try to uninstall qemu Alpha support if it changes a thing or not...
As Michal noted, Vdsm parses the attached capabilities as it should.
Maybe it receives something else from libvirt. Could you add some
logging and report?
diff --git a/vdsm/caps.py b/vdsm/caps.py
index 5599522..4daca46 100644
--- a/vdsm/caps.py
+++ b/vdsm/caps.py
@@ -136,6 +136,7 @@ def _getCpuTopology(capabilities):
def _getEmulatedMachines(capabilities=None):
if capabilities is None:
capabilities = _getCapsXMLStr()
+ logging.debug('caps: %s', capabilities)
caps = minidom.parseString(capabilities)
for archTag in caps.getElementsByTagName('arch'):
if archTag.getAttribute('name') == 'x86_64':
Maybe you can add some logging
_______________________________________________
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
