Red Hat Bugzilla – Bug 249427
unclear message in installer, improper failure with existing disk image present
Last modified: 2009-12-14 16:17:35 EST
Two matters, one of wording, and one of a missing state inventory and recovery.
[root@amd64 ~]# virt-install
Would you like a fully virtualized guest (yes or no)? This will allow you to
run unmodified operating systems. yes
What is the name of your virtual machine? russ1
How much RAM should be allocated (in megabytes)? 1000
What would you like to use as the disk (path)? /var/zen
BUG 1 *** This setup wizard message implies that a path is an acceptable answer
here ... I understand that a FQ path and file name is required here, but this is
not what it states.
ERROR: Must provide a file, not a directory for the disk
What would you like to use as the disk (path)? /var/zen/russ-disk
Would you like to enable graphics support? (yes or no) no
What would you like to use for the virtual CD image?
BUG 2 *** as indicated by the 'ls -l' below, the file exists -- I knew it
existed, and clearly the intsller can test for an existing file, and ask about
an over-write. Instead it crashes. This path should be caught and handles.
libvir: Xen Daemon error : POST operation failed: (xend.err 'Error creating
domain: Disk image does not exist: /var/zen/russ-disk')
Failed to create domain russ1
Traceback (most recent call last):
File "/usr/sbin/virt-install", line 447, in ?
File "/usr/sbin/virt-install", line 411, in main
dom = guest.start_install(conscb)
File "/usr/lib/python2.4/site-packages/virtinst/XenGuest.py", line 367, in
self.domain = self.conn.createLinux(cxml, 0)
File "/usr/lib64/python2.4/site-packages/libvirt.py", line 249, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed')
libvirt.libvirtError: virDomainCreateLinux() failed
[root@amd64 ~]# ls -al /var/zen/russ-disk
-rwxr-xr-x 1 root root 5368709121 Jul 24 07:42 /var/zen/russ-disk
I just changed the clarity of the virt-instal question upstream:
The question does not actually require I fully qualified path though. As far as
the file being present, this seems to work fine in 5.0. My guess is you have
selinux enabled and it is preventing you from accessing the file. Can you
confirm if this is the case?
Since I can't reproduce, no one has reported a similar issue, and it's been in
NEEDINFO for 3 months, I'm closing this bug. Please reopen if you are still
seeing this issue. Thanks!