Bug 243647 - Consistent error when creating virtual machine
Summary: Consistent error when creating virtual machine
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 7
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Daniel Berrangé
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-11 08:29 UTC by John Lagrue
Modified: 2008-01-11 04:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-11 04:10:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description John Lagrue 2007-06-11 08:29:49 UTC
Description of problem:

After creating a VM disk as a single file I get this error:
Unable to complete install '<class 'libvirt.libvirtError'>
virDomainCreateLinux() failed internal error Timed out while reading monitor
startup output
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 681, in do_install
    dom = guest.start_install(False, meter = meter)
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 649, in
start_install
    return self._do_install(consolecb, meter)
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 666, in
_do_install
    self.domain = self.conn.createLinux(install_xml, 0)
  File "/usr/lib64/python2.5/site-packages/libvirt.py", line 480, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: virDomainCreateLinux() failed internal error Timed out while
reading monitor startup output


Version-Release number of selected component (if applicable):
Current version with f7

How reproducible:
Every time I create a new VM

Steps to Reproduce:
1.Follow wizard
2.Guest OS type does not make any difference
3.
  
Actual results:
Machine is created, if the error is ignred.

Expected results:


Additional info:

Comment 1 Daniel Berrangé 2007-06-11 21:25:10 UTC
A new libvirt release 0.2.3-1.fc7 will shortly be available in Fedora 7
Updates-testing yum repository. Please upgrade to this version when available,
run 'service libvirtd restart' and then try to create the virtual machine again.
This should give you improved error reporting in the UI, and failing that also
create a log file in /var/log/libvirt/ with full info.


Comment 2 Michal Klich 2007-07-12 06:34:50 UTC
I am having same error with libvirt-0.3.0-1.fc7. I tried to create virtual
machine out of Kde4Live and then Win Xp Home Sp2. Both gave me same error. I
dont have log file, directory you provided is empty.

Error message:

Unable to complete install '<class 'libvirt.libvirtError'>
virDomainCreateLinux() failed operacja POST nie powiodła się: (xend.err 'Device
768 (vbd) could not be connected.
/home/InIrudeBwoy/Publiczne/WinXP_Home_SP2_ENG/VMWinXPHomeSP2 does not exist.')
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 681, in do_install
    dom = guest.start_install(False, meter = meter)
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 649, in
start_install
    return self._do_install(consolecb, meter)
  File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 666, in
_do_install
    self.domain = self.conn.createLinux(install_xml, 0)
  File "/usr/lib64/python2.5/site-packages/libvirt.py", line 521, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: virDomainCreateLinux() failed operacja POST nie powiodła się:
(xend.err 'Device 768 (vbd) could not be connected.
/home/InIrudeBwoy/Publiczne/WinXP_Home_SP2_ENG/VMWinXPHomeSP2 does not exist.')

Comment 3 Daniel Veillard 2007-07-12 07:47:23 UTC
Error from #2 seems completely unrelated to this bug. As the log shows
the /home/InIrudeBwoy/Publiczne/WinXP_Home_SP2_ENG/VMWinXPHomeSP2 path
specified for the install is not found by Xen when starting the domain.

Can the author of the bug report check with package libvirt-0.3.0-1.fc7
available in Testing ? Make sure to stop libvirtd service before the
upgrade and restart it after, or simply reboot the machine after the
upgrade to make sure the new daemon is in use.

Daniel

Comment 4 Red Hat Bugzilla 2007-07-25 02:13:12 UTC
change QA contact

Comment 5 Daniel Berrangé 2008-01-11 04:10:51 UTC
Most likely blocked by SELinux since the file was under /home instead of
/var/lib/xen/images. Please re-open if this wasn't the problem & you have the
info reuqest from comment #3.


Note You need to log in before you can comment on or make changes to this bug.