Red Hat Bugzilla – Bug 249936
Cannot create VM, domain error
Last modified: 2008-06-16 21:59:44 EDT
Description of problem:
Failed to create virtual machine. I try to create Vm out of Win Xp Home SP2 and
after, i guess, registering domain error pops up. I attached output error below.
It also happend on previous version of libvirt. Please contact me if you need
any info. Thanks
Version-Release number of selected component (if applicable):
Any time i create VM it happens.
Nie można zakończyć instalacji: "virDomainCreateLinux() failed operacja POST nie
powiodła się: (xend.err 'Device 768 (vbd) could not be connected.
/home/InIrudeBwoy/Publiczne/winXPhomeVM does not exist.')"
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/winXPhomeVM does
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 710, in
return self._do_install(consolecb, meter)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 727, in
self.domain = self.conn.createLinux(install_xml, 0)
File "/usr/lib64/python2.5/site-packages/libvirt.py", line 525, 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/winXPhomeVM does not exist.')
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008.
Fedora 7 is no longer maintained, which means that it will not
receive any further security or bug fix updates. As a result we
are closing this bug.
If you can reproduce this bug against a currently maintained version
of Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.