I just tried the proposed fix. My results are as follows:
1) I can confirm that with 0.5.3-0ubuntu9, both the CD option and the
use harddrive partition option were grayed-out when run as a normal user
and when run as root (i.e., changing to root did not help in my case).
2) When using the proposed fix 0.5.3-ubuntu10, the CD option was
available. Hard drive option was not, but I have not tried to run as
root.
3) I can confirm that the CD (in my case, "VISTA_64_BUSINESS") appears
twice in the menu, but as stated, this appears to be cosmetic and is
possibly related to the fact that /media/cdrom and /media/cdrom0 both
point to the CD.
4) When I selected to use the CD, the install began as normal by
creating the disk image, but this ended with a mysterious error that did
not occur with 0.5.3-ubuntu9 (i.e., this would seem to somehow be
related to the update):
Unable to complete install '<class 'libvirt.libvirtError'>
virDomainCreateLinux() failed Timed out while reading monitor startup output
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/create.py", line 620, in do_install
dom = guest.start_install(False, meter = meter)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 820, in
start_install
return self._do_install(consolecb, meter)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 841, in
_do_install
self.domain = self.conn.createLinux(install_xml, 0)
File "/usr/lib/python2.5/site-packages/libvirt.py", line 585, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed',
conn=self)
libvirtError: virDomainCreateLinux() failed Timed out while reading monitor
startup output
'
5) This error does not appear to block continuing installation, but my
personal results after this point have all failed to finish the install.
Once, it failed because my processor was not set to 64bit, so I changed
the processor from i686 to x86_64 (I am running a core 2 duo processor,
which supports x86_64, but the Ubuntu I am running is i686). Next, it
failed on some unknown windows error before starting the actual windows
install, though the windows welcome screen did appear (meaning it was
accessing the CD). After this time, I upped the number of CPU available
to the virtual machine to 2. In this case, it wouldn't boot at all -
instead it would indicate that the CD had been detected, but would do no
more, though virt-manager indicated it was using CPU. This happened
regardless of whether I deleted and recreated the virtual machine. At
this point, I am out of options to try. As virt-manager appears to be
failing at multiple point, I am not sure whether these problems have
anything to do with the fix committed. I would be happy to report any
or all of this in a separate bug, but I am not sure what is actually
failing. Suggestions?
--
vm cannot access cd-rom unless run as root
https://bugs.launchpad.net/bugs/196850
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
