Bug 500968
| Summary: | virt-manager traceback on shutdown of qemu-kvm -no-acpi guest | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adrin Jalali <adrin.jalali> | ||||||
| Component: | libvirt | Assignee: | Daniel Veillard <veillard> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | rawhide | CC: | berrange, clalance, crobinso, itamar, markmc, mnowak, veillard, virt-maint | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-09-21 17:08:17 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 480594 | ||||||||
| Attachments: |
|
||||||||
That sounds like qemu may have crashed handling the "info balloon" monitor command. What version of qemu-system-x86 is this? Could you attach the logfile for the guest from /var/log/qemu/ ? Also, it may be worth trying libvirt-0.6.2-10.fc11 from updates-testing: https://admin.fedoraproject.org/updates/libvirt-0.6.2-10.fc11 Created attachment 345330 [details]
qemu log file
and: qemu-system-x86-0.10.4-5.fc11.x86_64
also I can not update to libvirt-0.6.2-10.f11 because I can not find related libvirt-python rpm. Thanks Adrin http://kojipkgs.fedoraproject.org/packages/libvirt/0.6.2/10.fc11/x86_64/libvirt-0.6.2-10.fc11.x86_64.rpm http://kojipkgs.fedoraproject.org/packages/libvirt/0.6.2/10.fc11/x86_64/libvirt-python-0.6.2-10.fc11.x86_64.rpm Also, could you try getting a libvirtd logfile by setting log_level/log_outputs in /etc/libvirt/libvirtd.conf as described in: https://fedoraproject.org/wiki/Reporting_virtualization_bugs#libvirt Created attachment 345359 [details]
libvirtd.log
I've also updated those two libvirt packages, but I get the same result. Okay, I can reproduce - the key is that this is a guest which doesn't have ACPI enabled. With -no-acpi, qemu will exit immediately when issued the system_powerdown command. Then when virt-manager does a virDomainGetInfo(), libvirtd detects an error on the monitor fd and returns an error rather than handling it as a normal guest shutdown. This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Moving to Rawhide version. Reproducible with: libvirt-0.7.1-1.fc12.x86_64 qemu-system-x86-0.10.92-4.fc12.x86_64 virt-manager-0.8.0-3.fc12.noarch I think 519667 was also covering this, and the issue should be fixed with latest rawhide libvirt versions. *** This bug has been marked as a duplicate of bug 519667 *** |
Using virt-manager-0.7.0-4.fc11.x86_64 libvirt-0.6.2-8.fc11.x86_64 libvirt-python-0.6.2-8.fc11.x86_64 python-virtinst-0.400.3-8.fc11.noarch virt-viewer-0.0.3-4.fc11.x86_64 Installed a windows XP on kvm, when I try to shutdown virtual machine using toolbar button, not shutting down machine inside windows, I get this: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 507, in shutdown_domain vm.shutdown() File "/usr/share/virt-manager/virtManager/domain.py", line 566, in shutdown self._update_status() File "/usr/share/virt-manager/virtManager/domain.py", line 217, in _update_status info = self.vm.info() File "/usr/lib64/python2.6/site-packages/libvirt.py", line 523, in info if ret is None: raise libvirtError ('virDomainGetInfo() failed', dom=self) libvirtError: operation failed: could not query memory balloon allocation and virtual machine is powered off immediately.