Description of problem: Attempting to install from a windows cd in virt-manager
with kvm, after windows shuts down in the middle of the install, the cd image
vanishes and the user must locate a xml file in /etc/libvirt/qemu/ and manually
add the cd image back before the install can be continued and completed.
Probably virt manager should not try to be so smart, leave the cd mounted and
users can remove it themselves after the install completes successfully.
Version-Release number of selected component (if applicable):
I was about to submit this bug as well, but I will just add a "me too" instead.
Had the same problem trying to install a RHL 7.3 (don't ask, I needed something
from that system), after the installer finishes with CD1 and asks for CD2, there
is no way I can insert the new CD and RHL 7.3's anaconda to recognize it. Had to
do a minimum-minimum install to use only 1 CD.
btw, vfiend, can you please post the lines you had to add to the XML file? Thanks!
I can't remember exactly what I added, I created a new virtual machine with the
same settings, then looked at the new file and saw the section it automatically
created for the disc. I then copy-pasted the section from the new file into the
old file and deleted the new virtual machine, after you install you can then
remove the cd image/drive from the GUI.
Note: I think the services for qemu/virt manager need to be restarted after this
or possibly stopped before you do it, I'm not sure. This is just a quick dirty
work around I stumbled through with trial and error.
I think the patch to this bug was applied 5 days ago.
I am not sure. Maybe the developer have more information about it. If it's the
correct one I guess probably some more time before it comes to fedora7-updates.
Using changeset 205 65ea24a40b29 from
http://hg.et.redhat.com/virt/applications/virtinst--devel allowed me to install
Win XP from a iso file.
$ hg clone http://hg.et.redhat.com/virt/applications/virtinst--devel
$ cd virtinst--devel/
$ sudo ./virt-install
... (answer questions)
So this does appear to be solved with with the current version of virtinst. The
patch that Deependra mentions (change 202) will not easily apply to the version
103 that is in redhat since it depends on other changes made since 103 was
We will be updating to the new upstream version of python-virtinst in the near
future, since as you note, backporting this is not easy.....
Upstream virt-manager now also has the ability to add & remove CDROM devices
which will make Windows installs easier. This will appear in next Fedora update.
change QA contact
virt-manager-0.5.3-1.fc7, gtk-vnc-0.3.2-1.fc7, python-virtinst-0.300.2-1.fc7, virt-viewer-0.0.2-1.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update virt-manager gtk-vnc python-virtinst virt-viewer'
virt-manager-0.5.3-1.fc7, gtk-vnc-0.3.2-1.fc7, python-virtinst-0.300.2-1.fc7, virt-viewer-0.0.2-1.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.
I think this persists. I have these versions installed below. During the
install I am asked for D:\i386\asms which is right there on the CD where the
install done from, but it just keeps asking for it, so I assume this is the same
virt-manager.i386 0.5.3-1.fc7 installed
virt-viewer.i386 0.0.2-1.fc7 installed
gtk-vnc.i386 0.3.2-1.fc7 installed
python-virtinst.noarch 0.300.2-2.fc7 installed