Bug 825992
| Summary: | Guest stuck at "Wait For Launch" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Chao Yang <chayang> | ||||
| Component: | vdsm | Assignee: | Dan Kenigsberg <dkenigsb> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Haim <hateya> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.3 | CC: | abaron, bazulay, danken, hateya, iheim, yeylon, ykaul | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | virt | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-06-07 09:48:39 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
it appears that vdsm fails to communicate with libvirt; what is the status of the service ? does virhs -r capabilities works ? does libvirt service restart works for you ? (In reply to comment #2) > it appears that vdsm fails to communicate with libvirt; what is the status > of the service ? does virhs -r capabilities works ? does libvirt service > restart works for you ? vdsmd and libvirtd are running. virsh -r capabilities works. restart libvirt service works, the guests in "Wait For Launch" status previously are now running. (In reply to comment #3) > (In reply to comment #2) > > it appears that vdsm fails to communicate with libvirt; what is the status > > of the service ? does virhs -r capabilities works ? does libvirt service > > restart works for you ? > > vdsmd and libvirtd are running. virsh -r capabilities works. restart libvirt > service works, the guests in "Wait For Launch" status previously are now > running. we need to understand what caused vdsm to loose connection to libvirt service, do you have a reproducer ? What's the version of libvirt? I recall that there was a recenet rpc bug in libvirt that blocked SI4 build. (In reply to comment #5) > What's the version of libvirt? I recall that there was a recenet rpc bug in > libvirt that blocked SI4 build. libvirt-0.9.10-20.el6.x86_64 (In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > it appears that vdsm fails to communicate with libvirt; what is the status > > > of the service ? does virhs -r capabilities works ? does libvirt service > > > restart works for you ? > > > > vdsmd and libvirtd are running. virsh -r capabilities works. restart libvirt > > service works, the guests in "Wait For Launch" status previously are now > > running. > > we need to understand what caused vdsm to loose connection to libvirt > service, do you have a reproducer ? Not sure if it is a reliable reproducer, I just started VM from a template, then it happened. > lrwxrwxrwx. 1 root root 8 May 29 14:13 /dev/f84b4e6a-f186-490c-9478-483261e15682
> /2438c346-9769-48f6-b861-372f94f91a06 -> ../dm-10"
permissions here are root/root. iirc they should be vdsm.
how did you get to this?
though it probably should have failed runnning the guest, rather than hang it.
(In reply to comment #8) > > lrwxrwxrwx. 1 root root 8 May 29 14:13 /dev/f84b4e6a-f186-490c-9478-483261e15682 > > /2438c346-9769-48f6-b861-372f94f91a06 -> ../dm-10" > > permissions here are root/root. iirc they should be vdsm. > how did you get to this? > though it probably should have failed runnning the guest, rather than hang > it. I don't know, I just created an iscsi storage from WPFClient, then New VMs on this storage. ls tells this file is owned by root but getfact tells vdsm. # ls -l /dev/f84b4e6a-f186-490c-9478-483261e15682/2438c346-9769-48f6-b861-372f94f91a06lrwxrwxrwx. 1 root root 8 May 29 14:13 /dev/f84b4e6a-f186-490c-9478-483261e15682/2438c346-9769-48f6-b861-372f94f91a06 -> ../dm-10 # getfacl /dev/f84b4e6a-f186-490c-9478-483261e15682/2438c346-9769-48f6-b861-372f94f91a06 getfacl: Removing leading '/' from absolute path names # file: dev/f84b4e6a-f186-490c-9478-483261e15682/2438c346-9769-48f6-b861-372f94f91a06 # owner: vdsm # group: qemu user::rw- group::rw- other::--- (In reply to comment #6) > (In reply to comment #5) > > What's the version of libvirt? I recall that there was a recenet rpc bug in > > libvirt that blocked SI4 build. > > libvirt-0.9.10-20.el6.x86_64 please try -21, I suspect a dup of bug 821468 (In reply to comment #11) > (In reply to comment #6) > > (In reply to comment #5) > > > What's the version of libvirt? I recall that there was a recenet rpc bug in > > > libvirt that blocked SI4 build. > > > > libvirt-0.9.10-20.el6.x86_64 > > please try -21, I suspect a dup of bug 821468 I have already upgraded to -21. If still reproducible, will update here. chayang - please re-open if reproduced with -21 libvirt |
Created attachment 587369 [details] libvirt and vdsm log Description of problem: I created two VMs from existing templates, then click on start, but they get stuck at "Wait for Launch". Threre is io error as well as libvirt error in vdsm.log: IOError: [Errno 2] No such file or directory: '/dev/f84b4e6a-f186-490c-9478-483261e15682/2438c346-9769-48f6-b861-372f94f91a06' but I checked, this file exists: # ls -l /dev/f84b4e6a-f186-490c-9478-483261e15682/2438c346-9769-48f6-b861-372f94f91a06 lrwxrwxrwx. 1 root root 8 May 29 14:13 /dev/f84b4e6a-f186-490c-9478-483261e15682/2438c346-9769-48f6-b861-372f94f91a06 -> ../dm-10 Version-Release number of selected component (if applicable): qemu-kvm-rhev-0.12.1.2-2.294.el6.x86_64 libvirt-0.9.10-20.el6.x86_64 vdsm-4.9.6-13.el6.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: