On 06/24/2011 05:15 AM, Chris Lalancette wrote:
On 06/23/11 - 09:44:30PM, Steven Dake wrote:
> Chris,
>
> I have had oz fail perhaps two times in the last few weeks I have been
> using it. It looks to me to be a libvirtd problem. I have also had
> libvirtd crash once. It always seems to be around the time that the vm
> is finished installing - then oz-install blocks. I am not entirely sure
> what the issue is, but I'd speculate the doman is killed and then the
> block device stats are read, which results in badness (rather then a
> raise). I don't know for sure though, and don't have a clear reproduer.
>
>
> callback such as it is:
> Waiting for F15-x86_64-jeos to finish installing, 49630/50000
> Waiting for F15-x86_64-jeos to finish installing, 49620/50000
> ^CLibvirt Domain Info Failed:
> code is 38
> domain is 13
> message is poll on socket failed: Interrupted system call
> level is 2
> str1 is %s
> str2 is poll on socket failed: Interrupted system call
> str3 is None
> int1 is -1
> int2 is -1
> Cleaning up guest named F15-x86_64-jeos
> Cleaning up after install
> Removing modified ISO
> Traceback (most recent call last):
> File "/usr/bin/oz-install", line 139, in <module>
> libvirt_xml = guest.install(timeout, force_download)
> File "/usr/lib/python2.7/site-packages/oz/Guest.py", line 1156, in
install
> return self.do_install(timeout, force, 0)
> File "/usr/lib/python2.7/site-packages/oz/Guest.py", line 1141, in
> do_install
> self.wait_for_install_finish(dom, timeout)
> File "/usr/lib/python2.7/site-packages/oz/Guest.py", line 432, in
> wait_for_install_finish
> rd_req, rd_bytes, wr_req, wr_bytes, errs =
> libvirt_dom.blockStats(diskdev)
> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 760, in
> blockStats
> if ret is None: raise libvirtError ('virDomainBlockStats() failed',
> dom=self)
> libvirt.libvirtError: poll on socket failed: Interrupted system call
Hm, yeah, that does seem like you say. In the past I have had libvirtd hang
up/crash on me due to various libvirt bugs, but they have mostly gone away
with the latest update in Fedora-14 (0.8.3-9). I've never seen this particular
problem. Out of curiousity, what is the version of libvirt you are using
(and on what platform)?
libvirt 0.8.3-9.fc14.x86_64