Hello,
here are the logfiles from libvirt
May 4 19:08:22 ovirt kernel: ovirtmgmt: port 2(vnet0) entered forwarding state
May 4 19:08:22 ovirt kernel: ovirtmgmt: port 2(vnet0) entered forwarding state
May 4 19:08:23 ovirt sanlock[638]: 2015-05-04 19:08:23+0200 5077 [638]: cmd 9
target pid 10182 not found
May 4 19:08:23 ovirt systemd: Starting Virtual Machine qemu-testwin.
May 4 19:08:23 ovirt systemd-machined: New machine qemu-testwin.
May 4 19:08:23 ovirt systemd: Started Virtual Machine qemu-testwin.
May 4 19:08:23 ovirt kvm: 1 guest now active
May 4 19:08:23 ovirt kernel: ovirtmgmt: port 2(vnet0) entered disabled state
May 4 19:08:23 ovirt kernel: device vnet0 left promiscuous mode
May 4 19:08:23 ovirt kernel: ovirtmgmt: port 2(vnet0) entered disabled state
May 4 19:08:23 ovirt kvm: 0 guests now active
May 4 19:08:23 ovirt systemd-machined: Machine qemu-testwin terminated.
May 4 19:08:23 ovirt libvirtd: 9183: error : qemuMonitorOpenUnix:309 :
Verbindung mit Monitor-Socket gescheitert: Kein passender Prozess gefunden
May 4 19:08:23 ovirt libvirtd: 9183: error : qemuProcessWaitForMonitor:2131 :
Interner Fehler: Prozess während der Verbindungsaufnahme zum Monitor beendet
:2015-05-04T17:08:23.274206Z qemu-kvm: -drive
file=/var/run/vdsm/payload/c07772b8-6369-44cf-b554-b8dcb0e0e09b.0a41ac3e81bce0429e32b725fbf3ba5d.img,if=none,id=drive-fdc0-0-0,format=raw,serial=:
could not open disk image
/var/run/vdsm/payload/c07772b8-6369-44cf-b554-b8dcb0e0e09b.0a41ac3e81bce0429e32b725fbf3ba5d.img:
Could not open file: Permission denied
May 4 19:08:23 ovirt libvirtd: 9183: warning :
virSecuritySELinuxRestoreSecurityFileLabel:1034 : cannot lookup default selinux
label for
/rhev/data-center/d5e8a32f-35ed-4dec-bf9d-3c818c2780a4/66f8876c-0898-4ff2-9325-a14835f2a872/images/b329d34e-78b3-46a5-9df8-00b83c2c982a/c79a596b-5701-4afd-a5b5-d37cf412095c
May 4 19:08:23 ovirt journal: vdsm vm.Vm ERROR
vmId=`c07772b8-6369-44cf-b554-b8dcb0e0e09b`::The vm start process failed
Traceback (most recent call last):
File "/usr/share/vdsm/virt/vm.py", line 2271, in _startUnderlyingVm
self._run()
File "/usr/share/vdsm/virt/vm.py", line 3335, in _run
self._connection.createXML(domxml, flags),
File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 111,
in wrapper
ret = f(*args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3427, in createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
libvirtError: Interner Fehler: Prozess w��hrend der Verbindungsaufnahme zum
Monitor beendet :2015-05-04T17:08:23.274206Z qemu-kvm: -drive
file=/var/run/vdsm/payload/c07772b8-6369-44cf-b554-b8dcb0e0e09b.0a41ac3e81bce0429e32b725fbf3ba5d.img,if=none,id=drive-fdc0-0-0,format=raw,serial=:
could not open disk image
/var/run/vdsm/payload/c07772b8-6369-44cf-b554-b8dcb0e0e09b.0a41ac3e81bce0429e32b725fbf3ba5d.img:
Could not open file: Permission denied
May 4 19:08:24 ovirt journal: vdsm vm.Vm WARNING
vmId=`c07772b8-6369-44cf-b554-b8dcb0e0e09b`::trying to set state to Powering
down when already Down
May 4 19:08:24 ovirt journal: vdsm root WARNING File:
/var/lib/libvirt/qemu/channels/c07772b8-6369-44cf-b554-b8dcb0e0e09b.com.redhat.rhevm.vdsm
already removed
May 4 19:08:24 ovirt journal: vdsm root WARNING File:
/var/lib/libvirt/qemu/channels/c07772b8-6369-44cf-b554-b8dcb0e0e09b.org.qemu.guest_agent.0
already removed
and qemu
2015-05-04 17:08:23.237+0000: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name testwin -S -machine
rhel6.5.0,accel=kvm,usb=off -cpu Opteron_G3,hv_relaxed -m 1024 -realtime
mlock=off -smp 1,maxcpus=16,sockets=16,cores=1,threads=1 -uuid
c07772b8-6369-44cf-b554-b8dcb0e0e09b -smbios
type=1,manufacturer=oVirt,product=oVirt
Node,version=7-1.1503.el7.centos.2.8,serial=804BE279-8EFE-D511-B2A7-5404A6B49297,uuid=c07772b8-6369-44cf-b554-b8dcb0e0e09b
-no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/testwin.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc
base=2015-05-04T18:08:22,clock=vm,driftfix=slew -global
kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device
virtio-serial-pci,id=virtio-serial0,max_ports=16,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=/var/run/vdsm/payload/c07772b8-6369-44cf-b554-b8dcb0e0e09b.0a41ac3e81bce0429e32b725fbf3ba5d.img,if=none,id=drive-fdc0-0-0,format=raw,serial=
-global isa-fdc.driveA=drive-fdc0-0-0 -drive
file=/rhev/data-center/d5e8a32f-35ed-4dec-bf9d-3c818c2780a4/66f8876c-0898-4ff2-9325-a14835f2a872/images/b329d34e-78b3-46a5-9df8-00b83c2c982a/c79a596b-5701-4afd-a5b5-d37cf412095c,if=none,id=drive-virtio-disk0,format=raw,serial=b329d34e-78b3-46a5-9df8-00b83c2c982a,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,bootindex=1
-netdev tap,fd=25,id=hostnet0,vhost=on,vhostfd=26 -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:fe:54:00,bus=pci.0,addr=0x3
-chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/c07772b8-6369-44cf-b554-b8dcb0e0e09b.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/c07772b8-6369-44cf-b554-b8dcb0e0e09b.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
-device usb-tablet,id=input0 -vnc 10.21.100.5:0,password -k en-us -vga cirrus
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on
2015-05-04T17:08:23.274206Z qemu-kvm: -drive
file=/var/run/vdsm/payload/c07772b8-6369-44cf-b554-b8dcb0e0e09b.0a41ac3e81bce0429e32b725fbf3ba5d.img,if=none,id=drive-fdc0-0-0,format=raw,serial=:
could not open disk image
/var/run/vdsm/payload/c07772b8-6369-44cf-b554-b8dcb0e0e09b.0a41ac3e81bce0429e32b725fbf3ba5d.img:
Could not open file: Permission denied
2015-05-04 17:08:23.454+0000: shutting down
Thanks
-----Ursprüngliche Nachricht-----
Von: Michal Skrivanek <[email protected]>
Gesendet: Mon 4 Mai 2015 17:44
An: Wolfgang Bucher <[email protected]>
CC: [email protected] ([email protected]) <[email protected]>
Betreff: Re: [ovirt-users] ovirt 3.5.2 cannot start windows vms
On 4 May 2015, at 16:56, Wolfgang Bucher wrote:
Hello
sorry but i sent the wrong logs.
this one should be ok.
Again it affects only windows vm's since 3.5.2
it might really be because of the bug that we always attach sysprep even when
not requested.
Still, the failure is weird.
Ideally enable libvirt debug logs and attach those. perhaps also qemu.log
Thanks,
michal
Thanks
Wolfgang
-----Ursprüngliche Nachricht-----
Von: Wolfgang Bucher <[email protected]
<mailto:[email protected]> >
Gesendet: Mon 4 Mai 2015 16:22
An: Michal Skrivanek <[email protected] <mailto:[email protected]> >
CC: [email protected] <mailto:[email protected]> ([email protected]
<mailto:[email protected]> ) <[email protected] <mailto:[email protected]> >
Betreff: Re: [ovirt-users] ovirt 3.5.2 cannot start windows vms
Hello
I have no sysprep in VM properties.
attached vdsm.log and supervdsm.log
Thanks
Wolfgang
-----Ursprüngliche Nachricht-----
Von: Michal Skrivanek <[email protected] <mailto:[email protected]> >
Gesendet: Mon 4 Mai 2015 16:02
An: Wolfgang Bucher <[email protected]
<mailto:[email protected]> >
CC: Francesco Romani <[email protected] <mailto:[email protected]> >;
[email protected] <mailto:[email protected]> ([email protected]
<mailto:[email protected]> ) <[email protected] <mailto:[email protected]> >; Shahar
Havivi <[email protected] <mailto:[email protected]> >
Betreff: Re: [ovirt-users] ovirt 3.5.2 cannot start windows vms
On 4 May 2015, at 15:32, Wolfgang Bucher <[email protected]
<mailto:[email protected]> > wrote:
Hello
i think it's not related to Bug 1213410. I can only start the vm's if i attach
sysprep floppy.
I tested a new host with iscsi storage all centos 7.1 and i got the same
results. Starting linux vm's works without problems.
Do you have any sysprep config in VM properties?
Might be related to the bug Shahe is working on about always attaching sysprep
It shouldn't fail though. Vdsm logs would help
Thanks,
michal
Thanks
Wolfgang
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.ovirt.org/mailman/listinfo/users
<http://lists.ovirt.org/mailman/listinfo/users>
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.ovirt.org/mailman/listinfo/users
<http://lists.ovirt.org/mailman/listinfo/users>
<vdsm.tar.gz>
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users
