Good Day All, I am running the latest version of oVirt for Fedora 18 (3.2.2) I have re-installed just in case but still get this error below : VM freenas is down. Exit message: internal error process exited while connecting to monitor: ((null):3390): Spice-Warning **: reds.c:3247:reds_init_ssl: Could not use private key file qemu-kvm: failed to initialize spice server . It is an All-In-One installation. Have no idea what certiciates are supposed to be where. Any help ? Much appreciated. Regards Shaun
Shaun Glass wrote:
Good Day All,
I am running the latest version of oVirt for Fedora 18 (3.2.2)
I have re-installed just in case but still get this error below :
VM freenas is down. Exit message: internal error process exited while connecting to monitor: ((null):3390): Spice-Warning **: reds.c:3247:reds_init_ssl: Could not use private key file qemu-kvm: failed to initialize spice server .
Got the same error on one of my hosts which I incidentally I just upgraded and before the upgrade it did work. On my other hosts which isn't upgraded yet I can still start VMs. The differences are minimal but either libvirt of qemu is probably having a problem. Reinstalling will give you the latest packages WITH the problem so that won't help. I'll try to add logs tomorrow. Regards, Joop -- irc: jvandewege
On Sun, Sep 01, 2013 at 08:41:24PM +0200, Joop wrote:
Shaun Glass wrote:
Good Day All,
I am running the latest version of oVirt for Fedora 18 (3.2.2)
I have re-installed just in case but still get this error below :
VM freenas is down. Exit message: internal error process exited while connecting to monitor: ((null):3390): Spice-Warning **: reds.c:3247:reds_init_ssl: Could not use private key file qemu-kvm: failed to initialize spice server .
Got the same error on one of my hosts which I incidentally I just upgraded and before the upgrade it did work. On my other hosts which isn't upgraded yet I can still start VMs. The differences are minimal but either libvirt of qemu is probably having a problem. Reinstalling will give you the latest packages WITH the problem so that won't help. I'll try to add logs tomorrow.
Please include qemu logs from /var/log/libvirt/qemu/<vmname>.log, and the qemu/libvirt versions on the working setup and the failing one.
Dan Kenigsberg wrote:
On Sun, Sep 01, 2013 at 08:41:24PM +0200, Joop wrote:
Shaun Glass wrote:
Good Day All,
I am running the latest version of oVirt for Fedora 18 (3.2.2)
I have re-installed just in case but still get this error below :
VM freenas is down. Exit message: internal error process exited while connecting to monitor: ((null):3390): Spice-Warning **: reds.c:3247:reds_init_ssl: Could not use private key file qemu-kvm: failed to initialize spice server .
Got the same error on one of my hosts which I incidentally I just upgraded and before the upgrade it did work. On my other hosts which isn't upgraded yet I can still start VMs. The differences are minimal but either libvirt of qemu is probably having a problem. Reinstalling will give you the latest packages WITH the problem so that won't help. I'll try to add logs tomorrow.
Please include qemu logs from /var/log/libvirt/qemu/<vmname>.log, and the qemu/libvirt versions on the working setup and the failing one.
OK, here come the logs. Logs and packages might seem strange at first but don't worry to much about that. The *working* files are from a rather standard install of F18 and the *nonw* are from a F18 install which used to be a allinone but has been 'converted' to an engine/host, thats why it has a quite a few more packages. This worked until I did yum update! Can't go back because yum downgrade will go back to the base packages and there are requirements because of other packages and thus won't work. Regards, Joop 2013-09-02 15:12:02.988+0000: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name test06-puzzle-it-local -S -M pc-0.14 -cpu Nehalem,+vmx -enable-kvm -m 1024 -smp 2,sockets=1,cores=2,threads=1 -uuid a4d1cbed-3daa-4669-8f1d-3a6cdd4337a9 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=18-1,serial=dee2fbc8-b54c-46dc-87c1-fa2ea3784c1f,uuid=a4d1cbed-3daa-4669-8f1d-3a6cdd4337a9 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/test06-puzzle-it-local.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2013-09-02T15:12:02,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/ccf85fab-6d36-4db9-bffd-e55b78bcf100/4897d9dc-f651-466d-bbe6-9f884892f77f/images/3b0de05b-3b7d-4664-8e6c-a11be5c5ee83/27eee563-2b6e-4663-99a8-4c420bed1068,if=none,id=drive-virtio-disk0,format=qcow2,serial=3b0de05b-3b7d-4664-8e6c-a11be5c5ee83,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:a8:0b:f5,bus=pci.0,addr=0x3,bootindex=1 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/test06-puzzle-it-local.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/test06-puzzle-it-local.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -spice port=5900,tls-port=5901,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir -k en-us -vga qxl -global qxl-vga.vram_size=67108864 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 spice-server-0.12.2-3.fc18.x86_64 spice-vdagent-0.14.0-1.fc18.x86_64 ipxe-roms-qemu-20120328-2.gitaac9718.fc18.noarch libvirt-daemon-driver-qemu-0.10.2.4-1.fc18.x86_64 qemu-common-1.2.2-11.fc18.x86_64 qemu-img-1.2.2-11.fc18.x86_64 qemu-kvm-1.2.2-11.fc18.x86_64 qemu-kvm-tools-1.2.2-11.fc18.x86_64 qemu-system-x86-1.2.2-11.fc18.x86_64 libvirt-0.10.2.4-1.fc18.x86_64 libvirt-client-0.10.2.4-1.fc18.x86_64 libvirt-daemon-0.10.2.4-1.fc18.x86_64 libvirt-daemon-config-network-0.10.2.4-1.fc18.x86_64 libvirt-daemon-config-nwfilter-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-interface-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-libxl-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-lxc-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-network-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-nodedev-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-nwfilter-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-qemu-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-secret-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-storage-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-uml-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-xen-0.10.2.4-1.fc18.x86_64 libvirt-lock-sanlock-0.10.2.4-1.fc18.x86_64 libvirt-python-0.10.2.4-1.fc18.x86_64 spice-glib-0.18-2.fc18.x86_64 spice-gtk3-0.18-2.fc18.x86_64 spice-parent-15-6.fc18.noarch spice-server-0.12.0-1.fc18.x86_64 spice-vdagent-0.14.0-1.fc18.x86_64 spice-xpi-2.8-1.fc18.x86_64 libvirt-0.10.2.7-1.fc18.x86_64 libvirt-client-0.10.2.7-1.fc18.x86_64 libvirt-daemon-0.10.2.7-1.fc18.x86_64 libvirt-daemon-config-network-0.10.2.7-1.fc18.x86_64 libvirt-daemon-config-nwfilter-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-interface-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-libxl-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-lxc-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-network-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-nodedev-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-nwfilter-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-qemu-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-secret-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-storage-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-uml-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-xen-0.10.2.7-1.fc18.x86_64 libvirt-daemon-kvm-0.10.2.7-1.fc18.x86_64 libvirt-daemon-qemu-0.10.2.7-1.fc18.x86_64 libvirt-devel-0.10.2.7-1.fc18.x86_64 libvirt-docs-0.10.2.7-1.fc18.x86_64 libvirt-gconfig-0.1.6-1.fc18.x86_64 libvirt-gconfig-devel-0.1.6-1.fc18.x86_64 libvirt-glib-0.1.6-1.fc18.x86_64 libvirt-glib-devel-0.1.6-1.fc18.x86_64 libvirt-gobject-0.1.6-1.fc18.x86_64 libvirt-gobject-devel-0.1.6-1.fc18.x86_64 libvirt-lock-sanlock-0.10.2.7-1.fc18.x86_64 libvirt-python-0.10.2.7-1.fc18.x86_64 ipxe-roms-qemu-20120328-2.gitaac9718.fc18.noarch libvirt-daemon-driver-qemu-0.10.2.7-1.fc18.x86_64 libvirt-daemon-qemu-0.10.2.7-1.fc18.x86_64 qemu-1.2.2-13.fc18.x86_64 qemu-common-1.2.2-13.fc18.x86_64 qemu-img-1.2.2-13.fc18.x86_64 qemu-kvm-1.2.2-13.fc18.x86_64 qemu-system-alpha-1.2.2-13.fc18.x86_64 qemu-system-arm-1.2.2-13.fc18.x86_64 qemu-system-cris-1.2.2-13.fc18.x86_64 qemu-system-lm32-1.2.2-13.fc18.x86_64 qemu-system-m68k-1.2.2-13.fc18.x86_64 qemu-system-microblaze-1.2.2-13.fc18.x86_64 qemu-system-mips-1.2.2-13.fc18.x86_64 qemu-system-or32-1.2.2-13.fc18.x86_64 qemu-system-ppc-1.2.2-13.fc18.x86_64 qemu-system-s390x-1.2.2-13.fc18.x86_64 qemu-system-sh4-1.2.2-13.fc18.x86_64 qemu-system-sparc-1.2.2-13.fc18.x86_64 qemu-system-unicore32-1.2.2-13.fc18.x86_64 qemu-system-x86-1.2.2-13.fc18.x86_64 qemu-system-xtensa-1.2.2-13.fc18.x86_64 qemu-user-1.2.2-13.fc18.x86_64 2013-09-02 14:14:46.460+0000: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name test06-puzzle-it-local -S -M pc-0.14 -cpu Nehalem,+vmx -enable-kvm -m 1024 -smp 2,sockets=1,cores=2,threads=1 -uuid a4d1cbed-3daa-4669-8f1d-3a6cdd4337a9 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=18-1,serial=03000200-0400-0500-0006-000700080009,uuid=a4d1cbed-3daa-4669-8f1d-3a6cdd4337a9 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/test06-puzzle-it-local.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2013-09-02T14:14:46,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/ccf85fab-6d36-4db9-bffd-e55b78bcf100/4897d9dc-f651-466d-bbe6-9f884892f77f/images/3b0de05b-3b7d-4664-8e6c-a11be5c5ee83/27eee563-2b6e-4663-99a8-4c420bed1068,if=none,id=drive-virtio-disk0,format=qcow2,serial=3b0de05b-3b7d-4664-8e6c-a11be5c5ee83,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:a8:0b:f5,bus=pci.0,addr=0x3,bootindex=1 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/test06-puzzle-it-local.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/test06-puzzle-it-local.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -spice port=5901,tls-port=5902,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir -k en-us -vga qxl -global qxl-vga.vram_size=67108864 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 ((null):4547): Spice-Warning **: reds.c:3317:reds_init_ssl: Could not use private key file qemu-kvm: -drive file=/rhev/data-center/ccf85fab-6d36-4db9-bffd-e55b78bcf100/4897d9dc-f651-466d-bbe6-9f884892f77f/images/3b0de05b-3b7d-4664-8e6c-a11be5c5ee83/27eee563-2b6e-4663-99a8-4c420bed1068,if=none,id=drive-virtio-disk0,format=qcow2,serial=3b0de05b-3b7d-4664-8e6c-a11be5c5ee83,cache=none,werror=stop,rerror=stop,aio=threads: could not open disk image /rhev/data-center/ccf85fab-6d36-4db9-bffd-e55b78bcf100/4897d9dc-f651-466d-bbe6-9f884892f77f/images/3b0de05b-3b7d-4664-8e6c-a11be5c5ee83/27eee563-2b6e-4663-99a8-4c420bed1068: Permission denied 2013-09-02 14:14:46.677+0000: shutting down
On Mon, Sep 02, 2013 at 03:41:41PM +0200, Joop wrote:
On Sun, Sep 01, 2013 at 08:41:24PM +0200, Joop wrote:
Shaun Glass wrote:
Good Day All,
I am running the latest version of oVirt for Fedora 18 (3.2.2)
I have re-installed just in case but still get this error below :
VM freenas is down. Exit message: internal error process exited while connecting to monitor: ((null):3390): Spice-Warning **: reds.c:3247:reds_init_ssl: Could not use private key file qemu-kvm: failed to initialize spice server .
Got the same error on one of my hosts which I incidentally I just upgraded and before the upgrade it did work. On my other hosts which isn't upgraded yet I can still start VMs. The differences are minimal but either libvirt of qemu is probably having a problem. Reinstalling will give you the latest packages WITH the problem so that won't help. I'll try to add logs tomorrow.
Please include qemu logs from /var/log/libvirt/qemu/<vmname>.log, and the qemu/libvirt versions on the working setup and the failing one. OK, here come the logs. Logs and packages might seem strange at first but don't worry to much about that. The *working* files are from a rather standard install of F18 and the *nonw* are from a F18 install which used to be a allinone but has been 'converted' to an engine/host, thats why it has a quite a few more packages. This worked until I did yum update! Can't go back because yum downgrade will go back to the base
Dan Kenigsberg wrote: packages and there are requirements because of other packages and thus won't work.
Regards,
Joop
2013-09-02 15:12:02.988+0000: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name test06-puzzle-it-local -S -M pc-0.14 -cpu Nehalem,+vmx -enable-kvm -m 1024 -smp 2,sockets=1,cores=2,threads=1 -uuid a4d1cbed-3daa-4669-8f1d-3a6cdd4337a9 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=18-1,serial=dee2fbc8-b54c-46dc-87c1-fa2ea3784c1f,uuid=a4d1cbed-3daa-4669-8f1d-3a6cdd4337a9 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/test06-puzzle-it-local.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2013-09-02T15:12:02,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/ccf85fab-6d36-4db9-bffd-e55b78bcf100/4897d9dc-f651-466d-bbe6-9f884892f77f/images/3b0de05b-3b7d-4664-8e6c-a11be5c5ee83/27eee563-2b6e-4663-99a8-4c420bed1068,if=none,id=drive-virtio-disk0,format=qcow2,serial=3b0de05b-3b7d-4664-8e6c-a11be5c5ee83,cache=none,werror=stop,rerror=stop,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:a8:0b:f5,bus=pci.0,addr=0x3,bootindex=1 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/test06-puzzle-it-local.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/test06-puzzle-it-local.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -spice port=5900,tls-port=5901,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir -k en-us -vga qxl -global qxl-vga.vram_size=67108864 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
spice-server-0.12.2-3.fc18.x86_64 spice-vdagent-0.14.0-1.fc18.x86_64
ipxe-roms-qemu-20120328-2.gitaac9718.fc18.noarch libvirt-daemon-driver-qemu-0.10.2.4-1.fc18.x86_64 qemu-common-1.2.2-11.fc18.x86_64 qemu-img-1.2.2-11.fc18.x86_64 qemu-kvm-1.2.2-11.fc18.x86_64 qemu-kvm-tools-1.2.2-11.fc18.x86_64 qemu-system-x86-1.2.2-11.fc18.x86_64
libvirt-0.10.2.4-1.fc18.x86_64 libvirt-client-0.10.2.4-1.fc18.x86_64 libvirt-daemon-0.10.2.4-1.fc18.x86_64 libvirt-daemon-config-network-0.10.2.4-1.fc18.x86_64 libvirt-daemon-config-nwfilter-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-interface-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-libxl-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-lxc-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-network-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-nodedev-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-nwfilter-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-qemu-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-secret-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-storage-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-uml-0.10.2.4-1.fc18.x86_64 libvirt-daemon-driver-xen-0.10.2.4-1.fc18.x86_64 libvirt-lock-sanlock-0.10.2.4-1.fc18.x86_64 libvirt-python-0.10.2.4-1.fc18.x86_64
spice-glib-0.18-2.fc18.x86_64 spice-gtk3-0.18-2.fc18.x86_64 spice-parent-15-6.fc18.noarch spice-server-0.12.0-1.fc18.x86_64 spice-vdagent-0.14.0-1.fc18.x86_64 spice-xpi-2.8-1.fc18.x86_64
libvirt-0.10.2.7-1.fc18.x86_64 libvirt-client-0.10.2.7-1.fc18.x86_64 libvirt-daemon-0.10.2.7-1.fc18.x86_64 libvirt-daemon-config-network-0.10.2.7-1.fc18.x86_64 libvirt-daemon-config-nwfilter-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-interface-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-libxl-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-lxc-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-network-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-nodedev-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-nwfilter-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-qemu-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-secret-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-storage-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-uml-0.10.2.7-1.fc18.x86_64 libvirt-daemon-driver-xen-0.10.2.7-1.fc18.x86_64 libvirt-daemon-kvm-0.10.2.7-1.fc18.x86_64 libvirt-daemon-qemu-0.10.2.7-1.fc18.x86_64 libvirt-devel-0.10.2.7-1.fc18.x86_64 libvirt-docs-0.10.2.7-1.fc18.x86_64 libvirt-gconfig-0.1.6-1.fc18.x86_64 libvirt-gconfig-devel-0.1.6-1.fc18.x86_64 libvirt-glib-0.1.6-1.fc18.x86_64 libvirt-glib-devel-0.1.6-1.fc18.x86_64 libvirt-gobject-0.1.6-1.fc18.x86_64 libvirt-gobject-devel-0.1.6-1.fc18.x86_64 libvirt-lock-sanlock-0.10.2.7-1.fc18.x86_64 libvirt-python-0.10.2.7-1.fc18.x86_64
ipxe-roms-qemu-20120328-2.gitaac9718.fc18.noarch libvirt-daemon-driver-qemu-0.10.2.7-1.fc18.x86_64 libvirt-daemon-qemu-0.10.2.7-1.fc18.x86_64 qemu-1.2.2-13.fc18.x86_64 qemu-common-1.2.2-13.fc18.x86_64 qemu-img-1.2.2-13.fc18.x86_64 qemu-kvm-1.2.2-13.fc18.x86_64 qemu-system-alpha-1.2.2-13.fc18.x86_64 qemu-system-arm-1.2.2-13.fc18.x86_64 qemu-system-cris-1.2.2-13.fc18.x86_64 qemu-system-lm32-1.2.2-13.fc18.x86_64 qemu-system-m68k-1.2.2-13.fc18.x86_64 qemu-system-microblaze-1.2.2-13.fc18.x86_64 qemu-system-mips-1.2.2-13.fc18.x86_64 qemu-system-or32-1.2.2-13.fc18.x86_64 qemu-system-ppc-1.2.2-13.fc18.x86_64 qemu-system-s390x-1.2.2-13.fc18.x86_64 qemu-system-sh4-1.2.2-13.fc18.x86_64 qemu-system-sparc-1.2.2-13.fc18.x86_64 qemu-system-unicore32-1.2.2-13.fc18.x86_64 qemu-system-x86-1.2.2-13.fc18.x86_64 qemu-system-xtensa-1.2.2-13.fc18.x86_64 qemu-user-1.2.2-13.fc18.x86_64
2013-09-02 14:14:46.460+0000: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name test06-puzzle-it-local ((null):4547): Spice-Warning **: reds.c:3317:reds_init_ssl: Could not use private key file qemu-kvm: -drive file=/rhev/data-center/ccf85fab-6d36-4db9-bffd-e55b78bcf100/4897d9dc-f651-466d-bbe6-9f884892f77f/images/3b0de05b-3b7d-4664-8e6c-a11be5c5ee83/27eee563-2b6e-4663-99a8-4c420bed1068,if=none,id=drive-virtio-disk0,format=qcow2,serial=3b0de05b-3b7d-4664-8e6c-a11be5c5ee83,cache=none,werror=stop,rerror=stop,aio=threads: could not open disk image /rhev/data-center/ccf85fab-6d36-4db9-bffd-e55b78bcf100/4897d9dc-f651-466d-bbe6-9f884892f77f/images/3b0de05b-3b7d-4664-8e6c-a11be5c5ee83/27eee563-2b6e-4663-99a8-4c420bed1068: Permission denied 2013-09-02 14:14:46.677+0000: shutting down
I'm only guessing here, but has there been a change in selinux-policy? Is selinux enforcing? Could you provide the output of ls -lRZ /etc/pki/vdsm ? Does these paths show up in /var/log/audit.log?
Dan Kenigsberg wrote:
I'm only guessing here, but has there been a change in selinux-policy? Is selinux enforcing?
Could you provide the output of
ls -lRZ /etc/pki/vdsm ? Does these paths show up in /var/log/audit.log?
Attached both from working and non-working host and what the update did on the now non-working host. Joop Loaded plugins: langpacks, presto, refresh-packagekit, versionlock Transaction ID : 65 Begin time : Sun Sep 1 14:14:38 2013 Begin rpmdb : 2196:1f486883bd12ee2565809284bbed49516b04d9d0 End time : 14:17:08 2013 (150 seconds) End rpmdb : 2228:294fcdd4891492dc093b3cec497e6d1ce9d98126 User : beheer <beheer> Return-Code : Success Command Line : update Transaction performed with: Installed rpm-4.10.3.1-1.fc18.x86_64 @updates Installed yum-3.4.3-54.fc18.noarch @updates Installed yum-metadata-parser-1.1.4-7.fc18.x86_64 @anaconda Installed yum-plugin-versionlock-1.1.31-10.fc18.noarch @updates Installed yum-presto-0.9.0-1.fc18.noarch @anaconda Packages Altered: Updated NetworkManager-1:0.9.8.1-3.git20130514.fc18.x86_64 @updates Update 1:0.9.8.2-1.fc18.x86_64 @updates Updated NetworkManager-glib-1:0.9.8.1-3.git20130514.fc18.x86_64 @updates Update 1:0.9.8.2-1.fc18.x86_64 @updates Updated abrt-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-3.fc18.x86_64 @updates Updated abrt-addon-ccpp-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-3.fc18.x86_64 @updates Updated abrt-addon-kerneloops-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-3.fc18.x86_64 @updates Updated abrt-addon-python-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-3.fc18.x86_64 @updates Updated abrt-addon-uefioops-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-3.fc18.x86_64 @updates Updated abrt-addon-vmcore-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-3.fc18.x86_64 @updates Updated abrt-addon-xorg-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-3.fc18.x86_64 @updates Updated abrt-dbus-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-3.fc18.x86_64 @updates Updated abrt-desktop-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-3.fc18.x86_64 @updates Updated abrt-gui-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-3.fc18.x86_64 @updates Updated abrt-libs-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-3.fc18.x86_64 @updates Updated abrt-plugin-bodhi-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-3.fc18.x86_64 @updates Updated abrt-retrace-client-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-3.fc18.x86_64 @updates Updated akonadi-1.9.2-1.fc18.x86_64 @updates Update 1.10.2-1.fc18.x86_64 @updates Updated akonadi-mysql-1.9.2-1.fc18.x86_64 @updates Update 1.10.2-1.fc18.x86_64 @updates Updated apper-0.8.1-0.3.20130511.fc18.x86_64 @updates Update 0.8.1-1.fc18.x86_64 @updates Dep-Install audit-libs-2.3.1-2.fc18.i686 @updates Updated augeas-1.0.0-1.fc18.x86_64 @updates Update 1.1.0-1.fc18.x86_64 @updates Updated augeas-libs-1.0.0-1.fc18.x86_64 @updates Update 1.1.0-1.fc18.x86_64 @updates Updated binutils-2.23.51.0.1-6.fc18.x86_64 @updates Update 2.23.51.0.1-10.fc18.x86_64 @updates Updated boost-chrono-1.50.0-6.fc18.x86_64 @updates Update 1.50.0-7.fc18.x86_64 @updates Updated boost-date-time-1.50.0-6.fc18.x86_64 @updates Update 1.50.0-7.fc18.x86_64 @updates Updated boost-filesystem-1.50.0-6.fc18.x86_64 @updates Update 1.50.0-7.fc18.x86_64 @updates Updated boost-iostreams-1.50.0-6.fc18.x86_64 @updates Update 1.50.0-7.fc18.x86_64 @updates Updated boost-program-options-1.50.0-6.fc18.x86_64 @updates Update 1.50.0-7.fc18.x86_64 @updates Updated boost-regex-1.50.0-6.fc18.x86_64 @updates Update 1.50.0-7.fc18.x86_64 @updates Updated boost-signals-1.50.0-6.fc18.x86_64 @updates Update 1.50.0-7.fc18.x86_64 @updates Updated boost-system-1.50.0-6.fc18.x86_64 @updates Update 1.50.0-7.fc18.x86_64 @updates Updated boost-thread-1.50.0-6.fc18.x86_64 @updates Update 1.50.0-7.fc18.x86_64 @updates Updated chrony-1.28-1.fc18.x86_64 @updates Update 1.29-1.fc18.x86_64 @updates Updated corosync-2.3.1-1.fc18.x86_64 @updates Update 2.3.1-2.fc18.x86_64 @updates Updated corosynclib-2.3.1-1.fc18.x86_64 @updates Update 2.3.1-2.fc18.x86_64 @updates Dep-Install cracklib-2.8.22-2.fc18.i686 @fedora Updated cryptsetup-1.6.1-1.fc18.x86_64 @updates Update 1.6.2-1.fc18.x86_64 @updates Updated cryptsetup-libs-1.6.1-1.fc18.x86_64 @updates Update 1.6.2-1.fc18.x86_64 @updates Dep-Install dbus-libs-1:1.6.12-1.fc18.i686 @updates Updated firefox-22.0-1.fc18.x86_64 @updates Update 23.0-1.fc18.x86_64 @updates Dep-Install fros-1.0-1.fc18.noarch @updates Updated gdisk-0.8.5-1.fc18.x86_64 @anaconda Update 0.8.7-1.fc18.x86_64 @updates Dep-Install glibc-2.16-33.fc18.i686 @updates Updated glusterfs-3.4.0-3.fc18.x86_64 @updates Update 3.4.0-8.fc18.x86_64 @updates Updated glusterfs-fuse-3.4.0-3.fc18.x86_64 @updates Update 3.4.0-8.fc18.x86_64 @updates Dep-Install glusterfs-libs-3.4.0-8.fc18.x86_64 @updates Updated gnome-abrt-0.2.12-2.fc18.x86_64 @updates Update 0.3.0-2.fc18.x86_64 @updates Updated gnupg-1.4.13-2.fc18.x86_64 @fedora Update 1.4.14-1.fc18.x86_64 @updates Updated gstreamer1-1.0.8-1.fc18.x86_64 @updates Update 1.0.9-1.fc18.x86_64 @updates Updated gstreamer1-plugins-bad-free-1.0.8-1.fc18.x86_64 @updates Update 1.0.9-1.fc18.x86_64 @updates Updated gstreamer1-plugins-base-1.0.8-1.fc18.x86_64 @updates Update 1.0.9-1.fc18.x86_64 @updates Updated gstreamer1-plugins-good-1.0.8-1.fc18.x86_64 @updates Update 1.0.9-1.fc18.x86_64 @updates Updated hpijs-1:3.13.6-2.fc18.x86_64 @updates Update 1:3.13.7-1.fc18.x86_64 @updates Updated hplip-3.13.6-2.fc18.x86_64 @updates Update 3.13.7-1.fc18.x86_64 @updates Updated hplip-common-3.13.6-2.fc18.x86_64 @updates Update 3.13.7-1.fc18.x86_64 @updates Updated hplip-libs-3.13.6-2.fc18.x86_64 @updates Update 3.13.7-1.fc18.x86_64 @updates Updated httpd-2.4.4-3.fc18.x86_64 @updates Update 2.4.6-2.fc18.x86_64 @updates Updated httpd-tools-2.4.4-3.fc18.x86_64 @updates Update 2.4.6-2.fc18.x86_64 @updates Updated hunspell-1.3.2-10.fc18.x86_64 @updates Update 1.3.2-13.fc18.x86_64 @updates Updated ibus-1.5.2-4.fc18.x86_64 @updates Update 1.5.3-1.fc18.x86_64 @updates Updated ibus-gtk2-1.5.2-4.fc18.x86_64 @updates Update 1.5.3-1.fc18.x86_64 @updates Updated ibus-gtk3-1.5.2-4.fc18.x86_64 @updates Update 1.5.3-1.fc18.x86_64 @updates Updated ibus-libs-1.5.2-4.fc18.x86_64 @updates Update 1.5.3-1.fc18.x86_64 @updates Updated ibus-typing-booster-1.2.2-1.fc18.noarch @updates Update 1.2.3-2.fc18.noarch @updates Updated iperf-2.0.5-5.fc18.x86_64 @fedora Update 2.0.5-9.fc18.x86_64 @updates Updated java-1.7.0-openjdk-1:1.7.0.25-2.3.10.4.fc18.x86_64 @updates Update 1:1.7.0.25-2.3.12.3.fc18.x86_64 @updates Updated java-1.7.0-openjdk-devel-1:1.7.0.25-2.3.10.4.fc18.x86_64 @updates Update 1:1.7.0.25-2.3.12.3.fc18.x86_64 @updates Erase kernel-3.9.11-200.fc18.x86_64 @updates Install kernel-3.10.9-100.fc18.x86_64 @updates Erase kernel-devel-3.9.10-200.fc18.x86_64 @updates Install kernel-devel-3.10.9-100.fc18.x86_64 @updates Updated kernel-headers-3.10.4-100.fc18.x86_64 @updates Update 3.10.9-100.fc18.x86_64 @updates Erase kernel-modules-extra-3.9.11-200.fc18.x86_64 @updates Install kernel-modules-extra-3.10.9-100.fc18.x86_64 @updates Updated kernel-tools-3.10.4-100.fc18.x86_64 @updates Update 3.10.9-100.fc18.x86_64 @updates Updated kernel-tools-libs-3.10.4-100.fc18.x86_64 @updates Update 3.10.9-100.fc18.x86_64 @updates Obsoleted khrplatform-devel-9.2-0.7.20130528.fc18.noarch @updates Updated kipi-plugins-3.2.0-3.fc18.x86_64 @updates Update 3.3.0-1.fc18.x86_64 @updates Updated kipi-plugins-libs-3.2.0-3.fc18.x86_64 @updates Update 3.3.0-1.fc18.x86_64 @updates Dep-Install libX11-1.5.99.901-3.20130524gita3bdd2b09.fc18.i686 @updates Dep-Install libXau-1.0.6-4.fc18.i686 @fedora Dep-Install libattr-2.4.46-7.fc18.i686 @fedora Dep-Install libcap-2.22-5.fc18.i686 @updates Dep-Install libdb-5.3.21-3.fc18.i686 @fedora Dep-Install libdrm-2.4.45-1.fc18.i686 @updates Dep-Install libffi-3.0.10-3.fc18.i686 @fedora Dep-Install libgcc-4.7.2-8.fc18.i686 @fedora Dep-Install libgcrypt-1.5.3-1.fc18.i686 @updates Dep-Install libgpg-error-1.10-3.fc18.i686 @fedora Updated libkgeomap-3.2.0-3.fc18.x86_64 @updates Update 3.3.0-1.fc18.x86_64 @updates Updated libkvkontakte-3.2.0-3.fc18.x86_64 @updates Update 3.3.0-1.fc18.x86_64 @updates Updated libmediawiki-3.2.0-3.fc18.x86_64 @updates Update 3.3.0-1.fc18.x86_64 @updates Updated libnm-gtk-0.9.8.1-4.git20130514.fc18.x86_64 @updates Update 0.9.8.2-1.fc18.x86_64 @updates Dep-Install libpciaccess-0.13.1-2.fc18.i686 @fedora Updated libreport-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-2.fc18.x86_64 @updates Updated libreport-fedora-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-2.fc18.x86_64 @updates Updated libreport-filesystem-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-2.fc18.x86_64 @updates Updated libreport-gtk-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-2.fc18.x86_64 @updates Updated libreport-newt-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-2.fc18.x86_64 @updates Updated libreport-plugin-bugzilla-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-2.fc18.x86_64 @updates Updated libreport-plugin-kerneloops-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-2.fc18.x86_64 @updates Updated libreport-plugin-logger-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-2.fc18.x86_64 @updates Updated libreport-plugin-reportuploader-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-2.fc18.x86_64 @updates Updated libreport-plugin-ureport-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-2.fc18.x86_64 @updates Updated libreport-python-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-2.fc18.x86_64 @updates Updated libreport-web-2.1.5-1.fc18.x86_64 @updates Update 2.1.6-2.fc18.x86_64 @updates Dep-Install libselinux-2.1.12-7.3.fc18.i686 @updates Updated libsmbclient-2:4.0.7-2.fc18.x86_64 @updates Update 2:4.0.9-1.fc18.x86_64 @updates Dep-Install libstdc++-4.7.2-8.fc18.i686 @fedora Updated libtiff-4.0.3-6.fc18.x86_64 @updates Update 4.0.3-8.fc18.x86_64 @updates Updated libvirt-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-client-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-config-network-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-config-nwfilter-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-driver-interface-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-driver-libxl-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-driver-lxc-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-driver-network-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-driver-nodedev-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-driver-nwfilter-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-driver-qemu-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-driver-secret-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-driver-storage-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-driver-uml-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-driver-xen-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-kvm-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-daemon-qemu-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-devel-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-docs-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-lock-sanlock-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Updated libvirt-python-0.10.2.6-1.fc18.x86_64 @updates Update 0.10.2.7-1.fc18.x86_64 @updates Dep-Install libwayland-client-1.0.5-1.fc18.i686 @updates Dep-Install libwayland-server-1.0.5-1.fc18.i686 @updates Updated libwbclient-2:4.0.7-2.fc18.x86_64 @updates Update 2:4.0.9-1.fc18.x86_64 @updates Dep-Install libxcb-1.9-3.fc18.i686 @updates Updated make-1:3.82-14.fc18.x86_64 @updates Update 1:3.82-15.fc18.x86_64 @updates Updated mesa-dri-drivers-9.2-0.7.20130528.fc18.x86_64 @updates Update 9.2-0.12.20130610.fc18.x86_64 @updates Updated mesa-filesystem-9.2-0.7.20130528.fc18.x86_64 @updates Update 9.2-0.12.20130610.fc18.x86_64 @updates Updated mesa-libEGL-9.2-0.7.20130528.fc18.x86_64 @updates Dep-Install mesa-libEGL-9.2-0.12.20130610.fc18.i686 @updates Update mesa-libEGL-9.2-0.12.20130610.fc18.x86_64 @updates Updated mesa-libEGL-devel-9.2-0.7.20130528.fc18.x86_64 @updates Obsoleting mesa-libEGL-devel-9.2-0.12.20130610.fc18.i686 @updates Obsoleting mesa-libEGL-devel-9.2-0.12.20130610.fc18.x86_64 @updates Updated mesa-libGL-9.2-0.7.20130528.fc18.x86_64 @updates Update 9.2-0.12.20130610.fc18.x86_64 @updates Updated mesa-libGL-devel-9.2-0.7.20130528.fc18.x86_64 @updates Update 9.2-0.12.20130610.fc18.x86_64 @updates Updated mesa-libgbm-9.2-0.7.20130528.fc18.x86_64 @updates Dep-Install mesa-libgbm-9.2-0.12.20130610.fc18.i686 @updates Update mesa-libgbm-9.2-0.12.20130610.fc18.x86_64 @updates Updated mesa-libglapi-9.2-0.7.20130528.fc18.x86_64 @updates Dep-Install mesa-libglapi-9.2-0.12.20130610.fc18.i686 @updates Update mesa-libglapi-9.2-0.12.20130610.fc18.x86_64 @updates Updated mesa-libxatracker-9.2-0.7.20130528.fc18.x86_64 @updates Update 9.2-0.12.20130610.fc18.x86_64 @updates Updated mod_ssl-1:2.4.4-3.fc18.x86_64 @updates Update 1:2.4.6-2.fc18.x86_64 @updates Updated nm-connection-editor-0.9.8.1-4.git20130514.fc18.x86_64 @updates Update 0.9.8.2-1.fc18.x86_64 @updates Updated nmap-ncat-2:6.25-1.fc18.x86_64 @updates Update 2:6.40-1.fc18.x86_64 @updates Dep-Install nss-softokn-freebl-3.15.1-1.fc18.i686 @updates Dep-Install pam-1.1.6-4.fc18.i686 @updates Updated paps-0.6.8-23.fc18.x86_64 @anaconda Update 0.6.8-26.fc18.x86_64 @updates Updated paps-libs-0.6.8-23.fc18.x86_64 @anaconda Update 0.6.8-26.fc18.x86_64 @updates Dep-Install pcre-8.31-5.fc18.i686 @updates Updated samba-client-2:4.0.7-2.fc18.x86_64 @updates Update 2:4.0.9-1.fc18.x86_64 @updates Updated samba-common-2:4.0.7-2.fc18.x86_64 @updates Update 2:4.0.9-1.fc18.x86_64 @updates Updated samba-libs-2:4.0.7-2.fc18.x86_64 @updates Update 2:4.0.9-1.fc18.x86_64 @updates Dep-Install satyr-0.5-2.fc18.x86_64 @updates Updated selinux-policy-3.11.1-98.fc18.noarch @updates Update 3.11.1-100.fc18.noarch @updates Updated selinux-policy-devel-3.11.1-98.fc18.noarch @updates Update 3.11.1-100.fc18.noarch @updates Updated selinux-policy-doc-3.11.1-98.fc18.noarch @updates Update 3.11.1-100.fc18.noarch @updates Updated selinux-policy-targeted-3.11.1-98.fc18.noarch @updates Update 3.11.1-100.fc18.noarch @updates Updated spherical-cow-kde-theme-18.0.1-1.fc18.noarch @updates Update 18.0.3-1.fc18.noarch @updates Updated spice-server-0.12.2-3.fc18.x86_64 @updates Update 0.12.4-1.fc18.x86_64 @updates Updated stunnel-4.55-1.fc18.x86_64 @updates Update 4.56-1.fc18.x86_64 @updates Updated subversion-1.7.8-3.fc18.x86_64 @updates Update 1.7.11-1.fc18.1.x86_64 @updates Updated subversion-libs-1.7.8-3.fc18.x86_64 @updates Update 1.7.11-1.fc18.1.x86_64 @updates Updated system-config-keyboard-1.3.1-9.fc18.x86_64 @anaconda Update 1.3.1-14.fc18.x86_64 @updates Updated system-config-keyboard-base-1.3.1-9.fc18.x86_64 @anaconda Update 1.3.1-14.fc18.x86_64 @updates Dep-Install systemd-libs-201-2.fc18.7.i686 @updates Updated tomcat-el-2.2-api-7.0.40-1.fc18.noarch @updates Update 7.0.42-1.fc18.noarch @updates Updated tomcat-jsp-2.2-api-7.0.40-1.fc18.noarch @updates Update 7.0.42-1.fc18.noarch @updates Updated tomcat-lib-7.0.40-1.fc18.noarch @updates Update 7.0.42-1.fc18.noarch @updates Updated tomcat-servlet-3.0-api-7.0.40-1.fc18.noarch @updates Update 7.0.42-1.fc18.noarch @updates Updated xulrunner-22.0-4.fc18.x86_64 @updates Update 23.0-2.fc18.x86_64 @updates Dep-Install xz-libs-5.1.2-2alpha.fc18.i686 @fedora Dep-Install zlib-1.2.7-9.fc18.i686 @fedora history info [root@localhost ~]# ls -lRZ /etc/pki/vdsm/ /etc/pki/vdsm/: drwxr-xr-x. vdsm kvm system_u:object_r:cert_t:s0 certs drwxr-xr-x. vdsm kvm system_u:object_r:cert_t:s0 keys drwxr-xr-x. root root unconfined_u:object_r:cert_t:s0 libvirt-spice /etc/pki/vdsm/certs: -rw-r--r--. root root unconfined_u:object_r:cert_t:s0 cacert.pem -rw-------. vdsm kvm unconfined_u:object_r:cert_t:s0 cacert.pem.20130410164816 -rw-r--r--. root root unconfined_u:object_r:cert_t:s0 vdsmcert.pem -rw-------. vdsm kvm unconfined_u:object_r:cert_t:s0 vdsmcert.pem.20130410164816 -rw-r--r--. root root unconfined_u:object_r:cert_t:s0 vdsmcert.pem.20130410165759 /etc/pki/vdsm/keys: -rw-------. vdsm kvm system_u:object_r:cert_t:s0 libvirt_password -r--r-----. vdsm kvm unconfined_u:object_r:cert_t:s0 vdsmkey.pem -rw-------. vdsm kvm unconfined_u:object_r:cert_t:s0 vdsmkey.pem.20130410164816 -r--r-----. vdsm kvm unconfined_u:object_r:cert_t:s0 vdsmkey.pem.20130410165759 /etc/pki/vdsm/libvirt-spice: -rw-r--r--. root root unconfined_u:object_r:cert_t:s0 ca-cert.pem -rw-r--r--. root root unconfined_u:object_r:cert_t:s0 server-cert.pem -rw-r--r--. root root unconfined_u:object_r:cert_t:s0 server-cert.pem.20130410165759 -r--r-----. vdsm kvm unconfined_u:object_r:cert_t:s0 server-key.pem -r--r-----. vdsm kvm unconfined_u:object_r:cert_t:s0 server-key.pem.20130410165759 /etc/pki/vdsm: drwxr-xr-x. vdsm kvm system_u:object_r:cert_t:s0 certs drwxr-xr-x. vdsm kvm system_u:object_r:cert_t:s0 keys drwxr-xr-x. root root unconfined_u:object_r:cert_t:s0 libvirt-spice /etc/pki/vdsm/certs: -rw-r--r--. root root unconfined_u:object_r:cert_t:s0 cacert.pem -rw-r--r--. root root unconfined_u:object_r:cert_t:s0 vdsmcert.pem /etc/pki/vdsm/keys: -rw-------. vdsm kvm system_u:object_r:cert_t:s0 libvirt_password -r--r-----. vdsm kvm unconfined_u:object_r:cert_t:s0 vdsmkey.pem /etc/pki/vdsm/libvirt-spice: -rw-r--r--. root root unconfined_u:object_r:cert_t:s0 ca-cert.pem -rw-r--r--. root root unconfined_u:object_r:cert_t:s0 server-cert.pem -r--r-----. vdsm kvm unconfined_u:object_r:cert_t:s0 server-key.pem
Joop wrote:
Dan Kenigsberg wrote:
I'm only guessing here, but has there been a change in selinux-policy? Is selinux enforcing?
Could you provide the output of
ls -lRZ /etc/pki/vdsm ? Does these paths show up in /var/log/audit.log?
Attached both from working and non-working host and what the update did on the now non-working host.
No /etc/pki/vdsm in /var/log/audit/audit.log. Only relation is a failure notice for starting test06 by libvirt, but no why that I can find. Joop
On Tue, Sep 03, 2013 at 05:13:55PM +0200, Joop wrote:
Joop wrote:
Dan Kenigsberg wrote:
I'm only guessing here, but has there been a change in selinux-policy? Is selinux enforcing?
Could you provide the output of
ls -lRZ /etc/pki/vdsm ? Does these paths show up in /var/log/audit.log? Attached both from working and non-working host and what the update did on the now non-working host.
No /etc/pki/vdsm in /var/log/audit/audit.log. Only relation is a failure notice for starting test06 by libvirt, but no why that I can find.
those unconfined_* are fishy, but they exist on the working setup as well. If Dan Walsh were not listening I'd suggest to try it with setenforce 0, nonetheless. Excuse my continued guesswork, but how about $ chown vdsm.qemu /etc/pki/vdsm/keys/vdsmkey.pem we once had a libvirt bug were auxiliary group kvm was not set on the qemu process. Maybe history repeats itself.
On 3-9-2013 18:26, Dan Kenigsberg wrote:
those unconfined_* are fishy, but they exist on the working setup as well. If Dan Walsh were not listening I'd suggest to try it with setenforce 0, nonetheless.
Excuse my continued guesswork, but how about
$ chown vdsm.qemu /etc/pki/vdsm/keys/vdsmkey.pem
we once had a libvirt bug were auxiliary group kvm was not set on the qemu process. Maybe history repeats itself.
Tried both and no go :-( Currently backing up my F18 install and then will start experimenting and if needed wipe everything and try clean F18, which won't work, and then F19 Joop
On 4-9-2013 12:36, noc wrote:
On 3-9-2013 18:26, Dan Kenigsberg wrote:
those unconfined_* are fishy, but they exist on the working setup as well. If Dan Walsh were not listening I'd suggest to try it with setenforce 0, nonetheless.
Excuse my continued guesswork, but how about
$ chown vdsm.qemu /etc/pki/vdsm/keys/vdsmkey.pem
we once had a libvirt bug were auxiliary group kvm was not set on the qemu process. Maybe history repeats itself.
Tried both and no go :-(
Currently backing up my F18 install and then will start experimenting and if needed wipe everything and try clean F18, which won't work, and then F19
Joop
Backup finished and trying updates-testing didn't help (update of selinux-policy), updated with virt-preview repo enabled and now it works again. BUT, ofcourse much much newer versions of qemu and libvirt are installed now. If you need further testing I can go back to my backup and start updating trying different things. Joop PS: sorry about not mailing the list. Will watch what the TO is saying.
On Tue, Sep 03, 2013 at 05:26:30PM +0100, Dan Kenigsberg wrote:
On Tue, Sep 03, 2013 at 05:13:55PM +0200, Joop wrote:
Joop wrote:
Dan Kenigsberg wrote:
I'm only guessing here, but has there been a change in selinux-policy? Is selinux enforcing?
Could you provide the output of
ls -lRZ /etc/pki/vdsm ? Does these paths show up in /var/log/audit.log? Attached both from working and non-working host and what the update did on the now non-working host.
No /etc/pki/vdsm in /var/log/audit/audit.log. Only relation is a failure notice for starting test06 by libvirt, but no why that I can find.
those unconfined_* are fishy, but they exist on the working setup as well. If Dan Walsh were not listening I'd suggest to try it with setenforce 0, nonetheless.
Excuse my continued guesswork, but how about
$ chown vdsm.qemu /etc/pki/vdsm/keys/vdsmkey.pem
we once had a libvirt bug were auxiliary group kvm was not set on the qemu process. Maybe history repeats itself.
Joop, do you have any news for us? More and more people are crashing into this :-( Bug 1006394 - after update machines fail to up with spice client interface
On Tue, Sep 10, 2013 at 11:37 PM, Dan Kenigsberg wrote:
Joop, do you have any news for us? More and more people are crashing into this :-(
Bug 1006394 - after update machines fail to up with spice client interface
Hello, incurring into the same bug. I posted this into the bugzilla indicated by Dan: " 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 all-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 " I'm available to test proposed patches. My system is with selinux in permissive mode from the beginning of 3.2. Gianluca
On Sun, Sep 15, 2013 at 10:52:18AM +0200, Gianluca Cecchi wrote:
On Tue, Sep 10, 2013 at 11:37 PM, Dan Kenigsberg wrote:
Joop, do you have any news for us? More and more people are crashing into this :-(
Bug 1006394 - after update machines fail to up with spice client interface
Hello, incurring into the same bug. I posted this into the bugzilla indicated by Dan: " 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 all-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 "
I'm available to test proposed patches. My system is with selinux in permissive mode from the beginning of 3.2.
Would you be kind to try starting a VM from virsh, where the VM image is out of ovirt's repor? I am asking you to have a VM image somewhere on your local disk, chown it to vdsm:kvm mode 0660, create a libvirt domxml for it (something simple, no spice or encryption), and try to start it up. Would this fail to start with the same permission issue, and the issue is again solved by `chown vdsm:qemu` ? If so, please copy libvir-list with your reply. Dan.
On Sun, Sep 15, 2013 at 11:54 AM, Dan Kenigsberg wrote:
Would you be kind to try starting a VM from virsh, where the VM image is out of ovirt's repor?
I am asking you to have a VM image somewhere on your local disk, chown it to vdsm:kvm mode 0660, create a libvirt domxml for it (something simple, no spice or encryption), and try to start it up.
Would this fail to start with the same permission issue, and the issue is again solved by `chown vdsm:qemu` ? If so, please copy libvir-list with your reply.
Dan.
It seems it doesn't solve for me... see below [root@tekkaman ~]# saslpasswd2 -a libvirt virshuser [root@tekkaman ~]# qemu-img create -f qcow2 /var/lib/libvirt/images/testvm.img 4G Formatting '/var/lib/libvirt/images/testvm.img', fmt=qcow2 size=4294967296 encryption=off cluster_size=65536 lazy_refcounts=off [root@tekkaman ~]# chown vdsm.kvm /var/lib/libvirt/images/testvm.img [root@tekkaman ~]# chmod 0660 /var/lib/libvirt/images/testvm.img [root@tekkaman ~]# virsh define /tmp/testvm2.xml Please enter your authentication name: virshuser Please enter your password: Domain testvm2 defined from /tmp/testvm2.xml [root@tekkaman ~]# ll /etc/libvirt/qemu total 8 drwx------. 3 root root 4096 Aug 2 01:41 networks -rw-------. 1 root root 2367 Sep 15 12:48 testvm2.xml [root@tekkaman ~]# virsh start testvm2 Please enter your authentication name: virshuser Please enter your password: error: Failed to start domain testvm2 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/2 ((null):19320): Spice-Warning **: reds.c:3247:reds_init_ssl: Could not use private key file qemu-kvm: failed to initialize spice server [root@tekkaman ~]# ll /var/lib/libvirt/images/ total 136 -rw-rw----. 1 vdsm kvm 197120 Sep 15 12:24 testvm.img [root@tekkaman ~]# chgrp qemu /var/lib/libvirt/images/testvm.img [root@tekkaman ~]# ll /var/lib/libvirt/images/ total 136 -rw-rw----. 1 vdsm qemu 197120 Sep 15 12:24 testvm.img [root@tekkaman ~]# virsh start testvm2 Please enter your authentication name: virshuser Please enter your password: error: Failed to start domain testvm2 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/2 ((null):19434): Spice-Warning **: reds.c:3247:reds_init_ssl: Could not use private key file qemu-kvm: failed to initialize spice server [root@tekkaman ~]# virsh list --all Please enter your authentication name: virshuser Please enter your password: Id Name State ---------------------------------------------------- - testvm2 shut off In attach the generated testvm2.xml in /etc/libvirt/qemu. The diff between it and the one used to define domain here: [root@tekkaman ~]# diff /tmp/testvm2.xml /etc/libvirt/qemu/testvm2.xml 0a1,7
<!-- WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE OVERWRITTEN AND LOST. Changes to this xml configuration should be made using: virsh edit testvm2 or other application using the libvirt API. -->
3,5c10,13 < <memory>1048576</memory> < <currentMemory>1048576</currentMemory> < <vcpu>1</vcpu> ---
<uuid>91d6012b-043f-2ea0-fcf8-dfa4fcda5b62</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu placement='static'>1</vcpu> 32c40 < <address type='drive' controller='0' bus='1' unit='0'/>
<address type='drive' controller='0' bus='1' target='0' unit='0'/>
39a48,50
<controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller>
50a62,65
<video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video>
Gianluca
On Sun, Sep 15, 2013 at 12:57:13PM +0200, Gianluca Cecchi wrote:
On Sun, Sep 15, 2013 at 11:54 AM, Dan Kenigsberg wrote:
Would you be kind to try starting a VM from virsh, where the VM image is out of ovirt's repor?
I am asking you to have a VM image somewhere on your local disk, chown it to vdsm:kvm mode 0660, create a libvirt domxml for it (something simple, no spice or encryption), and try to start it up.
Would this fail to start with the same permission issue, and the issue is again solved by `chown vdsm:qemu` ? If so, please copy libvir-list with your reply.
Dan.
It seems it doesn't solve for me... see below
[root@tekkaman ~]# saslpasswd2 -a libvirt virshuser
[root@tekkaman ~]# qemu-img create -f qcow2 /var/lib/libvirt/images/testvm.img 4G Formatting '/var/lib/libvirt/images/testvm.img', fmt=qcow2 size=4294967296 encryption=off cluster_size=65536 lazy_refcounts=off
[root@tekkaman ~]# chown vdsm.kvm /var/lib/libvirt/images/testvm.img
[root@tekkaman ~]# chmod 0660 /var/lib/libvirt/images/testvm.img
[root@tekkaman ~]# virsh define /tmp/testvm2.xml Please enter your authentication name: virshuser Please enter your password: Domain testvm2 defined from /tmp/testvm2.xml
[root@tekkaman ~]# ll /etc/libvirt/qemu total 8 drwx------. 3 root root 4096 Aug 2 01:41 networks -rw-------. 1 root root 2367 Sep 15 12:48 testvm2.xml
[root@tekkaman ~]# virsh start testvm2 Please enter your authentication name: virshuser Please enter your password: error: Failed to start domain testvm2 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/2 ((null):19320): Spice-Warning **: reds.c:3247:reds_init_ssl: Could not use private key file
This means you still have spice in your xml. That's ok, but then, to test my theory you'd need to chgrp your spice private key as well. Could you do that?
qemu-kvm: failed to initialize spice server
[root@tekkaman ~]# ll /var/lib/libvirt/images/ total 136 -rw-rw----. 1 vdsm kvm 197120 Sep 15 12:24 testvm.img [root@tekkaman ~]# chgrp qemu /var/lib/libvirt/images/testvm.img [root@tekkaman ~]# ll /var/lib/libvirt/images/ total 136 -rw-rw----. 1 vdsm qemu 197120 Sep 15 12:24 testvm.img
[root@tekkaman ~]# virsh start testvm2 Please enter your authentication name: virshuser Please enter your password: error: Failed to start domain testvm2 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/2 ((null):19434): Spice-Warning **: reds.c:3247:reds_init_ssl: Could not use private key file qemu-kvm: failed to initialize spice server
[root@tekkaman ~]# virsh list --all Please enter your authentication name: virshuser Please enter your password: Id Name State ---------------------------------------------------- - testvm2 shut off
In attach the generated testvm2.xml in /etc/libvirt/qemu. The diff between it and the one used to define domain here:
[root@tekkaman ~]# diff /tmp/testvm2.xml /etc/libvirt/qemu/testvm2.xml 0a1,7
<!-- WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE OVERWRITTEN AND LOST. Changes to this xml configuration should be made using: virsh edit testvm2 or other application using the libvirt API. -->
3,5c10,13 < <memory>1048576</memory> < <currentMemory>1048576</currentMemory> < <vcpu>1</vcpu> ---
<uuid>91d6012b-043f-2ea0-fcf8-dfa4fcda5b62</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu placement='static'>1</vcpu> 32c40 < <address type='drive' controller='0' bus='1' unit='0'/>
<address type='drive' controller='0' bus='1' target='0' unit='0'/>
39a48,50
<controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller>
50a62,65
<video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video>
Gianluca
<!-- WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE OVERWRITTEN AND LOST. Changes to this xml configuration should be made using: virsh edit testvm2 or other application using the libvirt API. -->
<domain type='kvm'> <name>testvm2</name> <uuid>91d6012b-043f-2ea0-fcf8-dfa4fcda5b62</uuid> <memory unit='KiB'>1048576</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='x86_64' machine='pc-0.14'>hvm</type> <boot dev='cdrom'/> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images//testvm.img'/> <target dev='hda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdc' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <input type='mouse' bus='ps2'/> <graphics type='spice' autoport='yes'/> <sound model='ac97'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </sound> <video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain>
On Sun, Sep 15, 2013 at 1:37 PM, Dan Kenigsberg wrote:
This means you still have spice in your xml. That's ok, but then, to test my theory you'd need to chgrp your spice private key as well. Could you do that?
ah... I only deleted the spice channel... so now it works. [root@tekkaman ~]# virsh undefine testvm2 Please enter your authentication name: virshuser Please enter your password: Domain testvm2 has been undefined [root@tekkaman ~]# vi /tmp/testvm2.xml cancelled the spice graphics line
<graphics type='spice' autoport='yes'/>
[root@tekkaman ~]# virsh define /tmp/testvm2.xml Please enter your authentication name: virshuser Please enter your password: Domain testvm2 defined from /tmp/testvm2.xml [root@tekkaman ~]# virsh start testvm2 Please enter your authentication name: virshuser Please enter your password: Domain testvm2 started [root@tekkaman ~]# virsh list --all Please enter your authentication name: virshuser Please enter your password: Id Name State ---------------------------------------------------- 11 testvm2 running Gianluca
On Sun, Sep 15, 2013 at 1:50 PM, Gianluca Cecchi wrote: and [root@tekkaman ~]# chgrp kvm /var/lib/libvirt/images/testvm.img [root@tekkaman ~]# ll /var/lib/libvirt/images/testvm.img -rw-rw----. 1 vdsm kvm 197120 Sep 15 12:24 /var/lib/libvirt/images/testvm.img [root@tekkaman ~]# virsh undefine testvm2 Please enter your authentication name: virshuser Please enter your password: Domain testvm2 has been undefined [root@tekkaman ~]# virsh define /tmp/testvm2.xml Please enter your authentication name: virshuser Please enter your password: Domain testvm2 defined from /tmp/testvm2.xml [root@tekkaman ~]# virsh start testvm2 Please enter your authentication name: virshuser Please enter your password: error: Failed to start domain testvm2 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/2 qemu-kvm: -drive file=/var/lib/libvirt/images//testvm.img,if=none,id=drive-virtio-disk0,format=qcow2: could not open disk image /var/lib/libvirt/images//testvm.img: Permission denied
On Sun, Sep 15, 2013 at 01:59:29PM +0200, Gianluca Cecchi wrote:
On Sun, Sep 15, 2013 at 1:50 PM, Gianluca Cecchi wrote:
and
[root@tekkaman ~]# chgrp kvm /var/lib/libvirt/images/testvm.img [root@tekkaman ~]# ll /var/lib/libvirt/images/testvm.img -rw-rw----. 1 vdsm kvm 197120 Sep 15 12:24 /var/lib/libvirt/images/testvm.img
[root@tekkaman ~]# virsh undefine testvm2 Please enter your authentication name: virshuser Please enter your password: Domain testvm2 has been undefined
[root@tekkaman ~]# virsh define /tmp/testvm2.xml Please enter your authentication name: virshuser Please enter your password: Domain testvm2 defined from /tmp/testvm2.xml
[root@tekkaman ~]# virsh start testvm2 Please enter your authentication name: virshuser Please enter your password: error: Failed to start domain testvm2 error: internal error Process exited while reading console log output: char device redirected to /dev/pts/2 qemu-kvm: -drive file=/var/lib/libvirt/images//testvm.img,if=none,id=drive-virtio-disk0,format=qcow2: could not open disk image /var/lib/libvirt/images//testvm.img: Permission denied
Gianluca, due to all the twists of this thread, I no longer recall which libvirt version you are using. Would you remind us? All signs show that it starts up qemu without setting its auxiliary group properly (Assuming that your # groups qemu qemu : qemu kvm is just as mine) I've added libvir-list so the fine folks there could check why qemu cannot read/write files group-owned by kvm. Dan.
On Sun, Sep 15, 2013 at 2:42 PM, Dan Kenigsberg wrote:
On Sun, Sep 15, 2013 at 01:59:29PM +0200, Gianluca Cecchi wrote:
On Sun, Sep 15, 2013 at 1:50 PM, Gianluca Cecchi wrote:
Gianluca, due to all the twists of this thread, I no longer recall which libvirt version you are using. Would you remind us?
All signs show that it starts up qemu without setting its auxiliary group properly (Assuming that your # groups qemu qemu : qemu kvm is just as mine)
I've added libvir-list so the fine folks there could check why qemu cannot read/write files group-owned by kvm.
Dan.
I'm using what stock f18 repo gives today: [root@tekkaman ~]# rpm -q libvirt libvirt-0.10.2.7-1.fc18.x86_64 [root@tekkaman ~]# groups qemu qemu : qemu kvm [root@tekkaman ~]# grep libvirt-0 /var/log/yum.log Jan 07 00:12:13 Installed: libvirt-0.10.2.2-3.fc18.x86_64 Feb 09 17:17:30 Updated: libvirt-0.10.2.3-1.fc18.x86_64 Apr 18 19:44:58 Updated: libvirt-0.10.2.4-1.fc18.x86_64 May 29 20:45:26 Updated: libvirt-0.10.2.5-1.fc18.x86_64 Jun 27 20:05:24 Updated: libvirt-0.10.2.6-1.fc18.x86_64 Aug 18 19:09:52 Updated: libvirt-0.10.2.7-1.fc18.x86_64 I'm not using consistently this all-in-one system for ovirt. For sure in July it worked ok. Only today when I wanted to run one of its vms, I saw the error and I found this reference in the list. Gianluca
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --DrQQlJSa6cUmoodqLvkLe3EFgJB9NwrQI Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 09/15/2013 07:55 AM, Gianluca Cecchi wrote:
I'm using what stock f18 repo gives today: [root@tekkaman ~]# rpm -q libvirt libvirt-0.10.2.7-1.fc18.x86_64
Known bug: CVE-2013-4291. Downgrade to 0.10.2.6, or wait for 0.10.2.8 to be released. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --DrQQlJSa6cUmoodqLvkLe3EFgJB9NwrQI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJSNwqWAAoJEKeha0olJ0Nqt6sH/1YyOPpaIC82QwGtlProTo4n Lx5H9LHmPI4UB7XDmZm0H+AuMbflt40RVon29hsk0n2jh5Kzwn1cLxqzcZwBs/dV R4nA2qLVd2FRvnwkRBHlH94q/vSWCgTIOJ5eobNqnSQfRTgxL9KUqIrlYSd6Ue9v PQ2eI6gH/gd6an3mqtunmP4hV+ekdcOV+2shvp2QimBTRIqTWJXkP42ycRiLrV39 3yfGAXUvaqAQFhYd4Dxqt0zAsn6SKqU/32S047+7qSABA2ZvGhbT28ip4rsgQgX0 2f46mP/OCv/qLqx58xwssPy9xThtaie9JbZIi8ypRqU07nXn1iILL+SCnah7Plo= =66vG -----END PGP SIGNATURE----- --DrQQlJSa6cUmoodqLvkLe3EFgJB9NwrQI--
On Mon, Sep 16, 2013 at 3:41 PM, Eric Blake wrote:
On 09/15/2013 07:55 AM, Gianluca Cecchi wrote:
I'm using what stock f18 repo gives today: [root@tekkaman ~]# rpm -q libvirt libvirt-0.10.2.7-1.fc18.x86_64
Known bug: CVE-2013-4291. Downgrade to 0.10.2.6, or wait for 0.10.2.8 to be released.
-- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
thanks. Uhm, not so easy. It seems it wants to downgrade to 0.10.2.2-3 (why?) and not 0.10.2.6 and vdsm complains about that.... Where to eventually find intermediate updates? I only found latest ones (so the broken ones...) on mirrors? On my system [g.cecchi@tekkaman ~]$ sudo yum downgrade libvirt-daemon-driver-storage libvirt-daemon-driver-lxc libvirt-daemon-driver-qemu libvirt-daemon-kvm libvirt-daemon-driver-network libvirt-daemon-driver-uml libvirt-lock-sanlock libvirt libvirt-python libvirt-daemon-driver-nwfilter libvirt-daemon-driver-libxl libvirt-client libvirt-daemon-driver-secret libvirt-daemon-config-nwfilter libvirt-daemon-driver-nodedev libvirt-daemon-config-network libvirt-daemon libvirt-daemon-driver-interface libvirt-daemon-driver-xen Loaded plugins: fastestmirror, langpacks, presto, refresh-packagekit, versionlock Loading mirror speeds from cached hostfile * fedora: mirror.switch.ch * livna: ftp-stud.fht-esslingen.de * rpmfusion-free: mirror.switch.ch * rpmfusion-free-updates: mirror.switch.ch * rpmfusion-nonfree: mirror.switch.ch * rpmfusion-nonfree-updates: mirror.switch.ch * updates: mirror.switch.ch Resolving Dependencies --> Running transaction check ---> Package libvirt.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-client.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-client.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-daemon.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-daemon.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-daemon-config-network.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-daemon-config-network.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-daemon-config-nwfilter.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-daemon-config-nwfilter.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-daemon-driver-interface.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-daemon-driver-interface.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-daemon-driver-libxl.x86_64 0:0.10.2.7-1.fc18 will be obsoleted ---> Package libvirt-daemon-driver-lxc.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-daemon-driver-lxc.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-daemon-driver-network.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-daemon-driver-network.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-daemon-driver-nodedev.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-daemon-driver-nodedev.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-daemon-driver-nwfilter.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-daemon-driver-nwfilter.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-daemon-driver-qemu.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-daemon-driver-qemu.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-daemon-driver-secret.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-daemon-driver-secret.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-daemon-driver-storage.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-daemon-driver-storage.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-daemon-driver-uml.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-daemon-driver-uml.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-daemon-driver-xen.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-daemon-driver-xen.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-daemon-kvm.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-daemon-kvm.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-lock-sanlock.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-lock-sanlock.x86_64 0:0.10.2.7-1.fc18 will be erased ---> Package libvirt-python.x86_64 0:0.10.2.2-3.fc18 will be a downgrade ---> Package libvirt-python.x86_64 0:0.10.2.7-1.fc18 will be erased --> Finished Dependency Resolution Error: Package: vdsm-4.10.3-17.fc18.x86_64 (@ovirt-stable) Requires: libvirt >= 0.10.2.4-1 Removing: libvirt-0.10.2.7-1.fc18.x86_64 (@updates) libvirt = 0.10.2.7-1.fc18 Downgraded By: libvirt-0.10.2.2-3.fc18.x86_64 (fedora) libvirt = 0.10.2.2-3.fc18 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
On Mon, Sep 16, 2013 at 4:12 PM, Gianluca Cecchi wrote:
On Mon, Sep 16, 2013 at 3:41 PM, Eric Blake wrote:
On 09/15/2013 07:55 AM, Gianluca Cecchi wrote:
I'm using what stock f18 repo gives today: [root@tekkaman ~]# rpm -q libvirt libvirt-0.10.2.7-1.fc18.x86_64
Known bug: CVE-2013-4291. Downgrade to 0.10.2.6, or wait for 0.10.2.8 to be released.
-- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
thanks. Uhm, not so easy. It seems it wants to downgrade to 0.10.2.2-3 (why?) and not 0.10.2.6 and vdsm complains about that.... Where to eventually find intermediate updates? I only found latest ones (so the broken ones...) on mirrors?
Just to notice that what worked for me online, without need of reboot of my all-in one f18 system was take notice of packages to downgrade, just for reference: rpm -qa | grep libvirt|grep 0.10.2.7-1 mkdir libvirt_downgrade cd libvirt_downgrade LIST=$(rpm -qa | grep libvirt|grep 0.10.2.7-1 | sed "s/0.10.2.7-1/0.10.2.6-1/") SITE="http://kojipkgs.fedoraproject.org/packages/libvirt/0.10.2.6/1.fc18/x86_64/" (note that it is indeed a "/" in 0.10.2.6/1 and not a "-") for pack in $LIST do wget ${SITE}${pack}.rpm done sudo rpm -Uvh --force *rpm connect to webadmin and start one of my WinXP VMs --> ok Gianluca
On Thu, Sep 19, 2013 at 7:50 AM, Gianluca Cecchi wrote:
Just to notice that what worked for me online, without need of reboot of my all-in one f18 system was
take notice of packages to downgrade, just for reference: rpm -qa | grep libvirt|grep 0.10.2.7-1
mkdir libvirt_downgrade cd libvirt_downgrade
LIST=$(rpm -qa | grep libvirt|grep 0.10.2.7-1 | sed "s/0.10.2.7-1/0.10.2.6-1/") SITE="http://kojipkgs.fedoraproject.org/packages/libvirt/0.10.2.6/1.fc18/x86_64/" (note that it is indeed a "/" in 0.10.2.6/1 and not a "-")
for pack in $LIST do wget ${SITE}${pack}.rpm done
sudo rpm -Uvh --force *rpm
connect to webadmin and start one of my WinXP VMs --> ok
Gianluca
I've put a note on bugzilla too https://bugzilla.redhat.com/show_bug.cgi?id=1006394 I previously reverted to 0.10.2.6-1 and oVirt worked again. Now it works with 0.10.2.8-1 in updates-testing repo: [g.cecchi@tekkaman ~]$ 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
participants (6)
-
Dan Kenigsberg -
Eric Blake -
Gianluca Cecchi -
Joop -
noc -
Shaun Glass