Created attachment 606750 [details] libvirt.log under /var/log/vdsm dir Description of problem: can not start guest in rhevm with newest libvirt package, but working well using libvirt-0.10.0-0rc0.el6.x86_64 Version-Release number of selected component (if applicable): # rpm -qa libvirt qemu-kvm-rhev kernel vdsm spice-server vdsm-4.9.6-30.0.el6_3.x86_64 spice-server-0.10.1-10.el6.x86_64 libvirt-0.10.0-0rc1.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.303.el6.x86_64 kernel-2.6.32-298.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Register a host to rhevm with above packages. 2. New a guest in rhevm 3. Run once or just Run it. 4. check vdsm.log Actual results: Get error:libvirtError: internal error Process exited while reading console log output: char device redirected to /dev/pts/1 do_spice_init: starting 0.10.1 reds_init_socket: reds_init_socket: binding socket to 10.66.5.143:5900 failed failed to initialize spice server Expected results: Work well Additional info: Works well with: # rpm -qa libvirt qemu-kvm-rhev kernel vdsm spice-server vdsm-4.9.6-30.0.el6_3.x86_64 spice-server-0.10.1-10.el6.x86_64 libvirt-0.10.0-0rc0.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.303.el6.x86_64 kernel-2.6.32-298.el6.x86_64 So tag as regression.
Created attachment 606751 [details] vdsm.log under /var/log/vdsm dir
This problem maybe due to new libvirt package missing some operation of spice-server, because guest can start with VNC Display using the same versions of packages.
Get similar error even with no vdsm package, when using spice to display the guest. # virsh dumpxml qcow2 ...... <channel type='spicevmc'> <target type='virtio' name='com.redhat.spice.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <graphics type='spice' autoport='yes' listen='0' keymap='en-us' passwdValidTo='2022-02-27T19:46:10' connected='disconnect'> <listen type='address' address='0'/> <channel name='main' mode='secure'/> <channel name='inputs' mode='secure'/> </graphics> ..... # virsh start qcow2 error: Failed to start domain qcow2 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/2 do_spice_init: starting 0.10.1 reds_init_socket: reds_init_socket: binding socket to 0:5900 failed failed to initialize spice server
Hi, I was trying all day, but with no luck, all the machines are still starting, no spice error occurred. Could you post a debug log from libvirt when you are trying to start the machine? Preferably with virsh and both /etc/libvirt/libvirtd.log and /etc/libvirt/qemu/<machinename>.log, please. Thanks, Martin
Hi Martin, I am using RHEVM to reproduce the bug, and got some logs. Please see the attachments. Thanks, EricLee
Created attachment 607141 [details] vdsm.log
Created attachment 607142 [details] libvirtd.log
Created attachment 607143 [details] libvirt.log
Created attachment 607144 [details] ../qemu/guest.log
(In reply to comment #9) This log helped a lot, thanks. Fix is already pushed, so moving to POST based on this commit: commit 340196c46fc8f4f266d16deb2c70a76d84368584 Author: Martin Kletzander <mkletzan> Date: Mon Aug 27 09:41:36 2012 +0200 qemu: fix regression with spice tls port allocation
Verified the bug with libvirt-0.10.0-1.el6. Steps as Description, guest with spice console can start normally in RHEVM. Moving to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0276.html