| Summary: | Timed out during operation | ||
|---|---|---|---|
| Product: | [Community] Virtualization Tools | Reporter: | C Jackson <cpjackson88> |
| Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | crobinso, dallan, xen-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-10-15 22:23:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
C Jackson
2012-02-09 15:53:12 UTC
Since you filed this as an upstream bug, please make sure you are using the latest libvirt release. If not, file this bug with your distro. What distro are you using? What libvirt version? What hypervisor? Any error output in /var/log/libvirt/qemu/$vmname.log (In reply to comment #0) > Version-Release number of selected component (if applicable): Latest Versions Latest Versions can mean a lot of different things to different people. What is the output of virsh version? One thing that you can do to gather more information about what's happening is to turn up the debug level on libvirt (see http://libvirt.org/logging.html for the details of how to do that) and attach the libvirt log. Note, though, that the debug logs can get very large very quickly, so make sure you keep an eye on the file size and turn down the log level when you're done testing. Closing INSUFFICIENT_DATA |