Bug 450990 - virt-install ks-based guest creation errors during disk initialization part
virt-install ks-based guest creation errors during disk initialization part
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: python-virtinst (Show other bugs)
5.2
x86_64 Linux
low Severity low
: rc
: ---
Assigned To: Daniel Berrange
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-12 01:09 EDT by erik tapang
Modified: 2009-12-14 16:16 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-06-12 06:58:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
anacdump and virt-install log (48.61 KB, text/plain)
2008-06-12 01:09 EDT, erik tapang
no flags Details
kickstart file (2.87 KB, text/plain)
2008-06-12 01:11 EDT, erik tapang
no flags Details

  None (edit)
Description erik tapang 2008-06-12 01:09:52 EDT
Description of problem:
trying to create a guest system using virt-install. ks install start out but
during the disk init part, a prompt appers with the message:

 Operation not permitted during write on /dev/xvdb

[Retry  Ignore ...

pressed Ignore and goes to an anaconda trace window.

Version-Release number of selected component (if applicable):

python-virtinst-0.300.2-8.el5

How reproducible:
always 



Steps to Reproduce:
1. virt-install -p -n node01 -r 1000 -f /dev/Virtual00VG/lvNODE01  -m
00:16:3e:21:c5:c1 -w network:public1  --os-type=linux --os-variant=rhel5
--arch=x86_64   -l /var/ftp/pub/rhel5u2/rhel-5-server-x86_64-dvd.iso  -x
ks=http://192.168.222.1/rhel5u2/node01_ks.cfg ksdevice=eth0  --vnc --debug
2. check the vnc session a prompt appears
3. press ignore and trace dump appears and then prompts to reboot
  
Actual results:
guest creation is unsuccessful

Expected results:
disk initialization should be ok

Additional info:
anaconda trace and virt-install log (combined) attached.
Comment 1 erik tapang 2008-06-12 01:09:52 EDT
Created attachment 309026 [details]
anacdump and virt-install log
Comment 2 erik tapang 2008-06-12 01:11:34 EDT
Created attachment 309027 [details]
kickstart file
Comment 3 erik tapang 2008-06-12 03:02:39 EDT
i've recreated the LV:

lvcreate -L 30G  -n lvNODE01 Virtual00VG

and re-installed using the same virt-install syntax, and it got through the
whole process.

previously, lvNODE01 used in guest system is created using this syntax:

lvcreate -L 30G -i 2 -n lvNODE01 Virtual00VG

# Virtual00VG has 2 x 100G HP EVA8K LUN

so does my problem has something to do with the striped LV?
Comment 4 Daniel Berrange 2008-06-12 06:58:42 EDT
Your  virt-install command line only specifies a single disk (ie f
/dev/Virtual00VG/lvNODE01) which will become xvda.  Your kickstart file
specifies two disks xvda and xvdb. Since xvdb does not exit (you didn't ask
virt-install for 2 disks) it will obvious fail to install.

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