<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>Hi</div><div><br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Wolfgang Bucher" <wolfgang.bucher@netland-mn.de><br><b>To: </b>users@ovirt.org<br><b>Sent: </b>Sunday, May 3, 2015 1:53:35 PM<br><b>Subject: </b>[ovirt-users] ovirt 3.5.2 cannot start windows vms<br><div><br></div><title>ovirt 3.5.2 cannot start windows vms</title><p style="margin-top: 0px; margin-bottom: 0px; color: #000000; font-family: Arial, Verdana, sans-serif;"><span id="_mce_caret"><span style="font-size: 12pt; font-family: tahoma,arial,helvetica,sans-serif;">Hello,<br></span></span></p><p style="margin-top: 0px; margin-bottom: 0px; color: #000000; font-family: Arial, Verdana, sans-serif;"><span style="font-size: 12pt; font-family: tahoma,arial,helvetica,sans-serif;"><br></span></p><p style="margin-top: 0px; margin-bottom: 0px; color: #000000; font-family: Arial, Verdana, sans-serif;"><span style="font-size: 12pt; font-family: tahoma,arial,helvetica,sans-serif;">i have a new and one updated ovirt 3.5.2 and cannot start windows vms.<br></span></p><p style="margin-top: 0px; margin-bottom: 0px; color: #000000; font-family: Arial, Verdana, sans-serif;"><span style="font-size: 12pt; font-family: tahoma,arial,helvetica,sans-serif;"><br></span></p><p style="margin-top: 0px; margin-bottom: 0px; color: #000000; font-family: Arial, Verdana, sans-serif;"><span style="font-size: 12pt; font-family: tahoma,arial,helvetica,sans-serif;">here is the vdsm.log part<br></span></p><p style="margin-top: 0px; margin-bottom: 0px; color: #000000; font-family: Arial, Verdana, sans-serif;"><span id="_mce_caret"><span style="font-size: 12pt; font-family: tahoma,arial,helvetica,sans-serif;"><br></span><span id="_mce_caret"><span style="font-family: tahoma,arial,helvetica,sans-serif; font-size: 12pt;">Thread-137::DEBUG::2015-05-03 13:46:22,725::libvirtconnection::143::root::(wrapper) Unknown libvirterror: ecode: 1 edom: 10 level: 2 message: Interner Fehler: Prozess während der Verbindungsaufnahme zum Monitor beendet :2015-05-03T11:46:22.396113Z qemu-kvm: -drive file=/var/run/vdsm/payload/8801126b-6fc8-4d6f-af48-b0be9fdd2c83.0a41ac3e81bce0429e32b725fbf3ba5d.img,if=none,id=drive-fdc0-0-0,format=raw,serial=: could not open disk image /var/run/vdsm/payload/8801126b-6fc8-4d6f-af48-b0be9fdd2c83.0a41ac3e81bce0429e32b725fbf3ba5d.img: Could not open file: Permission denied<br></span></span></span></p><p style="margin-top: 0px; margin-bottom: 0px; color: #000000; font-family: Arial, Verdana, sans-serif;"><span style="font-family: tahoma,arial,helvetica,sans-serif; font-size: 12pt;"><br></span></p><p style="margin-top: 0px; margin-bottom: 0px; color: #000000; font-family: Arial, Verdana, sans-serif;"><span style="font-family: tahoma,arial,helvetica,sans-serif; font-size: 12pt;"><br></span></p><p style="margin-top: 0px; margin-bottom: 0px; color: #000000; font-family: Arial, Verdana, sans-serif;"><span id="_mce_caret"><span id="_mce_caret"><span style="font-family: tahoma,arial,helvetica,sans-serif; font-size: 12pt;">with runonce and sysprep floppy attached the vms are starting. It seems ovirt now tries to attach a floppy always.<br></span></span></span></p></blockquote><div>Maybe this BZ is related:<br></div><div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1213410">https://bugzilla.redhat.com/show_bug.cgi?id=1213410</a></div><div><br></div><div>can you share the hypervisor configuration? Is it running on oVirt Node maybe? Or CentOS anything else?<br></div><div>Can you follow the steps outlined in <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1213410#c2">https://bugzilla.redhat.com/show_bug.cgi?id=1213410#c2</a> and <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1213410#c5">https://bugzilla.redhat.com/show_bug.cgi?id=1213410#c5</a><br></div><div>?<br></div><div><br></div><div>To troubleshoot this issue, we need more context from vdsm.log and from supervdsm.log.<br></div><div><br></div><div>Thanks,<br></div><div><br></div><div>-- <br></div><div><span name="x"></span>Francesco Romani<br>RedHat Engineering Virtualization R & D<br>Phone: 8261328<br>IRC: fromani<span name="x"></span><br></div></div></body></html>