Description of problem:
After upgrading to virt-manager/virt-manager-common 1.0.0-3.fc20, I can't view the VM console or VM details in virt-manager. I receive the following error on the screen:
Error launching details: 'NoneType' object has no attribute 'cpus'
Version-Release number of selected component (if applicable):
Working version: 0.10.0-5.git1ffcc0cc.fc20
Non-working version: 1.0.0-3.fc20
I build Xen HVM VM's in virt-manager 0.10.0-5 and was able to view/edit details and view the VM console without issues. After upgrading to virt-manager 1.0.0-3, I could no longer view/edit details or view the VM console. I was given the "Error launching details: 'NoneType' object has no attribute 'cpus'" error in virt-manager.
Steps to Reproduce:
1. Build a Xen VM in virt-manager 1.0.0-3
2. When the installation begins, you'll see the previously mentioned error
3. The VM will boot successfully but you can't view console/details in virt-manager
Error -> 'NoneType' object has no attribute 'cpus'
I'd expect to see the standard virt-manager window containing the VM console and details.
This affects PV and HVM Xen VM's from what I've seen. Downgrading to virt-manager 0.10.0-5 fixes all the problems. Restarting libvirtd had no effect.
Full traceback from virt-manager --debug:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 803, in _show_vm_helper
details = self._get_details_dialog(uri, uuid)
File "/usr/share/virt-manager/virtManager/engine.py", line 760, in _get_details_dialog
obj = vmmDetails(con.get_vm(uuid))
File "/usr/share/virt-manager/virtManager/details.py", line 530, in __init__
File "/usr/share/virt-manager/virtManager/details.py", line 990, in init_details
for name in [c.model for c in cpu_values.cpus]:
AttributeError: 'NoneType' object has no attribute 'cpus'
[Tue, 04 Mar 2014 22:13:31 virt-manager 21019] DEBUG (error:84) error dialog message:
summary=Error launching details: 'NoneType' object has no attribute 'cpus'
details=Error launching details: 'NoneType' object has no attribute 'cpus'
Fixed upstream now
Author: Cole Robinson <firstname.lastname@example.org>
Date: Thu Mar 6 11:31:09 2014 -0500
details: Fix fallback if fetching CPU models fails (bz 1072704)
Just made the edits from Cole's commit on my server and that fixed the bug. I'm able to view VM consoles and details without issue.
virt-manager-1.0.0-4.fc20 has been submitted as an update for Fedora 20.
virt-manager-1.0.0-5.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing virt-manager-1.0.0-5.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
virt-manager-1.0.0-5.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1075044 has been marked as a duplicate of this bug. ***