LinuxQuestions.org - virt-install: kickstarting F17 from local ftp

The following command worked with Fedora 16 to install a virtual machine:

Code:

#/usr/bin/virt-install --vnc --noautoconsole --name=vserver.example.com

--ram=768 --arch=i386 --vcpus=1 --os-type=linux --os-variant=rhel6 --hvm

--accelerate --disk=/dev/vgsystem/vserver.example.com -m

52:54:00:42:2C:C4 -w bridge=virbr0

--location=ftp://192.168.122.1/pub/fedora/linux/releases/16/Fedora/i386/os/

--extra-args='ks=ftp://192.168.122.1/pub/kickstart/vserver.cfg

ip=192.168.122.100 netmask=255.255.255.0 gateway=192.168.122.1

dns=208.67.222.222 noipv6 s=100'

With Fedora 17 this fails. Maybe anaconda or the now dracut based initramfs does not handle the kernel parameters correctly that virt-install creates from the selected options.

I receive the following error message and a kernel panic just after the virtual machine booted:

Code:

FATAL: Please supply bootdev argument for multiple ip= lines

I also tried the 'ip=<ip>::<gw>:<nm>[:<dev>]' method to configure the
network interface the dracut way:

Code:

# /usr/bin/virt-install --vnc --noautoconsole --name=vserver.example.com

--ram=1024 --arch=i386 --vcpus=1 --os-type=linux --os-variant=rhel6

--hvm --accelerate --disk=/dev/vgsystem/vserver.example.com -m

52:54:00:42:89:08 -w bridge=virbr0

--location=ftp://192.168.122.1/pub/fedora/linux/releases/17/Fedora/i386/os

'--extra-args=ks=ftp://192.168.122.1/pub/kickstart/vserver.cfg

ip=192.168.122.100::192.168.122.1:255.255.255.0

nameserver=208.67.222.222 noipv6 s=100'

With this command the virtual machine boots and drops to a dracut debug
shell. However no network interface gets configured and I receive the
following messages:

Code:

dracut Warning: Unable to process initqueue

dracut Warning: /dev/root does not exist

Could someone please enlighten me, how I may automatically kickstart my
test box with Fedora 17?

I've already asked the same question on the Fedora Users mailinglist but did not receive any hints. I've searched the Bugzilla but mostly found unrelated issues...