Bug 1006394
| Summary: | after update machines fail to up with spice client interface | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Felipe Diefenbach <felipe.diefenbach> |
| Component: | vdsm | Assignee: | Dan Kenigsberg <danken> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Haim <hateya> |
| Severity: | medium | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 3.2 | CC: | abaron, acathrow, bazulay, felipe.diefenbach, gianluca.cecchi, iheim, mgoldboi, michal.skrivanek, yeylon |
| Target Milestone: | --- | ||
| 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: | 2013-09-23 07:27:34 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: | |||
| Bug Depends On: | 1006511 | ||
| Bug Blocks: | |||
|
Description
Felipe Diefenbach
2013-09-10 14:34:24 UTC
Hello, I have the same problem now. Let me know how can I help to debug and put a working fix in Fedora 18 stable repo. My installation is al-in-one with all updates for f18 repo and ovirt repo but without the latest security patch (so I have engine-setup 3.2.2-1.1 and not 3.2.3-1.fc18). I would like to fix this before applying the security fix or updating to upcoming 3.3 Thanks, Gianluca If *instead* of chmod'ing server-key.pem, would you chown it to vdsm:qemu, and report if the VM starts? see also bug 1008328, seems to be a libvirt issue pending new fedora packages (bug 1006511) Would you check if upgrading to libvirt-0.10.2.8-1.fc18 is indeed enough to solve your pains? If note, please reopen bug. I previously reverted to 0.10.2.6-1 and oVirt worked again. Now: $ sudo yum --enablerepo=updates-testing update libvirt Updated: libvirt.x86_64 0:0.10.2.8-1.fc18 Dependency Updated: libvirt-client.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon-config-network.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon-config-nwfilter.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon-driver-interface.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon-driver-libxl.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon-driver-lxc.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon-driver-network.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon-driver-nodedev.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon-driver-nwfilter.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon-driver-qemu.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon-driver-secret.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon-driver-storage.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon-driver-uml.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon-driver-xen.x86_64 0:0.10.2.8-1.fc18 libvirt-daemon-kvm.x86_64 0:0.10.2.8-1.fc18 libvirt-lock-sanlock.x86_64 0:0.10.2.8-1.fc18 libvirt-python.x86_64 0:0.10.2.8-1.fc18 Also rebooted the server and I confirm I'm able to start a WIndows XP vm in oVirt. Also directly starting a vm from virsh now works and doesn't give any more the previous permission denied error closing as this should be in 3.3 (doing so in bulk, so may be incorrect) |