2:40 p.m.
This is a multi-part message in MIME format.
--------------000404000508050906030709
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 11/25/2013 06:49 PM, Blaster wrote:
So this has happened twice now....Running Windows 7/64 in a VM.
I git cloned the ovirt windows agent and installed the 3 Python
applications as instructed in the README.
When I run the win-guest-agent-build-exe.bat file to create the exe,
it gets to the line of:
adding python27.dll as a resource to virtguestservices.exe.
Then the cmd.exe window just hangs. It can not be killed, nor can any
other window.
The system will not shutdown, either from the Windows side or the VM
side. I had to power off from the GUI.
The first time this happened, the VM hung and became non-responsive.
When I tried to reboot the physical machine, the physical machine
would not reboot either. Had to hit the reset button to get it back.
The second time this happened, ovirt was able to power off
successfully, I decided to reboot the physical machine again, and
again the physical machine hung shutting down and had to physically reset.
Both times when I tried to start the Windows 7 VM again, ovirt refused
to start it. I get the message
Failed to run VM Win7-01 (User: admin@internal).
So off to restore the VM for a second time....
Any explanation how Python is able to destroy a VM like that?
Honestly this does
not sound like an issue to me which is caused by
Python or the build of the guest agent
I would start looking into the logs for the Host.
Please check the logs in /var/log/libvirt/qemu for the corresponding VM
log (Win7-01)
Also check your logs if you find any hints in /var/log/vdsm/libvirtd.log
and /var/log/vdsm/vdsm.log
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--
Regards,
Vinzenz Feenstra | Senior Software Engineer
RedHat Engineering Virtualization R & D
Phone: +420 532 294 625
IRC: vfeenstr or evilissimo
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
--------------000404000508050906030709
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/25/2013 06:49 PM, Blaster
wrote:<br>
</div>
<blockquote cite="mid:52938DC2.20900@556nato.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
So this has happened twice now....Running Windows 7/64 in a VM.<br>
<br>
I git cloned the ovirt windows agent and installed the 3 Python
applications as instructed in the README.<br>
<br>
When I run the win-guest-agent-build-exe.bat file to create the
exe, it gets to the line of:<br>
adding python27.dll as a resource to virtguestservices.exe.<br>
<br>
Then the cmd.exe window just hangs. It can not be killed, nor can
any other window.<br>
<br>
The system will not shutdown, either from the Windows side or the
VM side. I had to power off from the GUI.<br>
<br>
The first time this happened, the VM hung and became
non-responsive. When I tried to reboot the physical machine, the
physical machine would not reboot either. Had to hit the reset
button to get it back.<br>
<br>
The second time this happened, ovirt was able to power off
successfully, I decided to reboot the physical machine again, and
again the physical machine hung shutting down and had to
physically reset.<br>
<br>
Both times when I tried to start the Windows 7 VM again, ovirt
refused to start it. I get the message<br>
<div title="" tabindex="0" style="outline-style:
none;"
__gwt_cell="cell-gwt-uid-33835">
<div id="gwt-uid-3368_col2_row0">Failed to run VM Win7-01 (User:
admin(a)internal).<br>
<br>
So off to restore the VM for a second time....<br>
<br>
Any explanation how Python is able to destroy a VM like that?<br>
</div>
</div>
</blockquote>
Honestly this does not sound like an issue to me which is caused by
Python or the build of the guest agent<br>
I would start looking into the logs for the Host. <br>
<br>
Please check the logs in /var/log/libvirt/qemu for the corresponding
VM log (Win7-01)<br>
Also check your logs if you find any hints in
/var/log/vdsm/libvirtd.log<br>
and /var/log/vdsm/vdsm.log<br>
<br>
<blockquote cite="mid:52938DC2.20900@556nato.com"
type="cite">
<div title="" tabindex="0" style="outline-style:
none;"
__gwt_cell="cell-gwt-uid-33835">
<div id="gwt-uid-3368_col2_row0"> <br>
</div>
</div>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Regards,
Vinzenz Feenstra | Senior Software Engineer
RedHat Engineering Virtualization R & D
Phone: +420 532 294 625
IRC: vfeenstr or evilissimo
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com</pre>
</body>
</html>
--------------000404000508050906030709--