Hi,
I am trying to install a C6 VM on C6 using the text installer using:
# virt-install -n C6_1 -r 3072 --os-variant=rhel6 -l \ ftp://ftp.nluug.nl/site/centos.org/CentOS/6.3/os/x86_64/ --disk \ path=/dev/VG1/vm_c6_1 -w network:default --nographics \ -x "console=ttyS0" --autostart
/dev/VG1/vm_c6_1 has been successfully created. The installation starts but once I get to the disk partitioning no disk is listed and I cannot continue the installation.
Even worse, if I press space on the empty list CPU usage goes up to 100% for the qemu-kvm process.
ps shows root 26769 0.0 0.1 305120 22108 pts/2 S+ 16:34 0:00 /usr/bin/python -tt /usr/sbin/virt-install -n C6_1 -r 3072 --os-variant=rhel6 -l ftp://ftp.nluug.nl/site/centos.org/CentOS/6.3/os/x86_64/ --disk path=/dev/VG1/vm_c6_1 -w network:default --nographics -x console=ttyS0 --autostart qemu 26801 1.0 3.4 3490408 564540 ? Sl 16:34 0:09 /usr/libexec/qemu-kvm -S -M rhel6.3.0 -enable-kvm -m 3072 -smp 1,sockets=1,cores=1,threads=1 -name C6_1 -uuid b166f5ef-11dc-9e1b-eb9a-56e71365f72a -nographic -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/C6_1.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -no-shutdown -kernel /var/lib/libvirt/boot/virtinst-vmlinuz.GZ53UY -initrd /var/lib/libvirt/boot/virtinst-initrd.img.5OlWhn -append method=ftp://ftp.nluug.nl/site/centos.org/CentOS/6.3/os/x86_64/ console=ttyS0 -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/VG1/vm_c6_1,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=21,id=hostnet0,vhost=on,vhostfd=22 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:c0:fb:dd,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
Any ideas why anaconda isn't picking up the LV? Could this be a CentOS specific patch to anaconda or is that unlikely?
Thanks for any input, Leonard.