Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QEMU/KVM stopped working after the last system update #784

Closed
ghost opened this issue May 22, 2019 · 5 comments
Closed

QEMU/KVM stopped working after the last system update #784

ghost opened this issue May 22, 2019 · 5 comments
Labels
bug duplicate Previous report exists

Comments

@ghost
Copy link

ghost commented May 22, 2019

Hi. When I try to boot a Windows 10 ISO, i get this error:

Error starting an installation:constructor returned NULL

Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 1999, in _finish_clicked self._start_install(self._guest) File "/usr/share/virt-manager/virtManager/create.py", line 2092, in _start_install progWin.run() File "/usr/share/virt-manager/virtManager/asyncjob.py", line 284, in run Gdk.Cursor.new_from_name(gdk_window.get_display(), "progress")) TypeError: constructor returned NULL

Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/details.py", line 372, in get_instance key = "%s+%s" % (vm.conn.get_uri(), vm.get_uuid()) AttributeError: 'NoneType' object has no attribute 'conn'

Reinstalled kvm-host and kvm-extras but this problem persists.

@ghost ghost added bug new labels May 22, 2019
@znmeb
Copy link

znmeb commented May 22, 2019

I can confirm this - I thought it was a kvm kernel module problem but it is probably something else. Intel folks - are there changelogs we can look at if we want to try troubleshooting this ourselves?

@bryteise
Copy link
Member

Oo there might not be. @gtkramer @phmccarty thoughts on getting release notes published on the website. Would you prefer release notes on the mailing list? Since we try to release twice a day it seems like it might be just noise a lot of folks would rather avoid. Perhaps a separate mailing list though.

@mrkz mrkz added the duplicate Previous report exists label May 22, 2019
@mrkz
Copy link

mrkz commented May 22, 2019

Hello, This is a duplicate of #782

As stated in a comment there, we'll have virt-manager downgraded while I get the new version to work out of the box.

are there changelogs we can look at if we want to try troubleshooting this ourselves?

@znmeb Please consider opening a new issue with this request, so it's not lost once I close this report.

@mrkz mrkz closed this as completed May 22, 2019
@mrkz
Copy link

mrkz commented May 23, 2019

@znmeb @mariojuniorjp release 29590 (or later) should have virt-manager back to a working state.

thanks for your bug report 🎉

@ghost
Copy link
Author

ghost commented May 23, 2019

@znmeb @mariojuniorjp release 29590 (or later) should have virt-manager back to a working state.

thanks for your bug report tada

You're welcome!

@ahkok ahkok removed the new label Jun 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug duplicate Previous report exists
Projects
None yet
Development

No branches or pull requests

4 participants