6:09 a.m.
Hi,
I am also experiencing this problem but disabling selinux makes no difference for me. I
can only run the VM if I "Run once" and add a floppy image. Does anyone else
have a more elegant work around for this?
Best regards,
Ian Fraser
-----Original Message-----
From: users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] On Behalf Of Francesco
Romani
Sent: 05 May 2015 16:08
To: Michal Skrivanek
Cc: users(a)ovirt.org (users(a)ovirt.org)
Subject: Re: [ovirt-users] ovirt 3.5.2 cannot start windows vms
----- Original Message -----
From: "Michal Skrivanek" <mskrivan(a)redhat.com>
To: "Francesco Romani" <fromani(a)redhat.com>
Cc: "Wolfgang Bucher" <wolfgang.bucher(a)netland-mn.de>,
"users(a)ovirt.org (users(a)ovirt.org)" <users(a)ovirt.org>
Sent: Tuesday, May 5, 2015 9:33:03 AM
Subject: Re: [ovirt-users] ovirt 3.5.2 cannot start windows vms
>> 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
>
> This is the translation of the well-known 'internal error: monitor
> disconbected'
> QEMU error (not literal transaltion)! which is in turn caused by...
>
>> :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
>
> ... this error, and so the root cause seems indeed very much the
> same of
> https://bugzilla.redhat.com/show_bug.cgi?id=1213410#c7
>
> because of this:
>
>> 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-089
>> 8-4ff2-9325-a14835f2a872/images/b329d34e-78b3-46a5-9df8-00b83c2c982
>> a/c79a596b-5701-4afd-a5b5-d37cf412095c
>
> From the data gathered so far, it seems a selinux issue.
This is from Wolfgang's issue or the bug 1213410 or is it the same thing?
From Wolfgang's issue, this thread
In the bug the floppy creation failed
In logs attached earlier to this thread it seems the floppy was
created but libvirt access failed
I believe is the same root cause for bz1213410, it was just more hidden
Bests,
--
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
________________________________
The information in this message and any attachment is intended for the addressee and is
confidential. If you are not that addressee, no action should be taken in reliance on the
information and you should please reply to this message immediately to inform us of
incorrect receipt and destroy this message and any attachments.
For the purposes of internet level email security incoming and outgoing emails may be read
by personnel other than the named recipient or sender.
Whilst all reasonable efforts are made, ASM (UK) Ltd cannot guarantee that emails and
attachments are virus free or compatible with your systems. You should make your own
checks and ASM (UK) Ltd does not accept liability in respect of viruses or computer
problems experienced.
Registered address: Agency Sector Management (UK) Ltd. Ashford House, 41-45 Church Road,
Ashford, Middlesex, TW15 2TQ
Registered in England No.2053849
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________