Fedora xen - Nov 2006 - fc6: xennet module issue with kickstart

Hello,

I found one more little issue to stumble over :)

I tried (among others) the following kernel:
 kernel-xen-2.6.18-1.2798.fc6.i686.rpm and the initrd from a (freshly
rsynced) images/xen/ directory.

When the domU is created it comes up properly, and automatically preloads
the xenvbd module,
but not xennet. I extracted the initrd and found the xennet module there,
but it seems not possible
to load it from the network driver dialog (it''s not listed).
I''m confused as
I also tried an fc5 kernel + initrd, and also
a rhel5 beta kernel+initrd. I think the issue is somewhere with the initrd,
but don''t really found a hook to
change anything, maybe short of rebuilding the initrd using --preload xennet

If You''re successfully installing FC6 domU''s from within xen,
please speak
up!

the following are the relevant settings from the domU configfile
kernel = "/mnt/xendistro_temp//vmlinuz"
ramdisk = "/mnt/xendistro_temp/initrd.img"
extra = "ks=http://192.168.199.4/ks_fc6.cfg"
ip = "192.168.199.5"
netmask = "255.255.255.0"
gateway = "192.168.199.1"
# single line :)
disk = [ ''phy:/dev/evms/ll-kickme_root,hda,w'',
''phy:/dev/evms/ll-kickme_rootmir,hdb,w'',
''phy:/dev/evms/ll-kickme_swap,hdc,w'',
''phy:/dev/evms/ll-kickme_home,hdd,w'' ]
vif = [ ''type=ioemu, bridge=xenbr1'' ]

Florian

-- 
''Sie brauchen sich um Ihre Zukunft keine Gedanken zu machen''

On Fri, Nov 10, 2006 at 01:41:02AM +0100, Florian Heigl
wrote:
> Hello,
> 
> I found one more little issue to stumble over :)
> 
> I tried (among others) the following kernel:
> kernel-xen-2.6.18-1.2798.fc6.i686.rpm and the initrd from a (freshly
> rsynced) images/xen/ directory.
> 
> When the domU is created it comes up properly, and automatically preloads
> the xenvbd module,
> but not xennet. I extracted the initrd and found the xennet module there,
> but it seems not possible
> to load it from the network driver dialog (it''s not listed).
I''m confused as
> I also tried an fc5 kernel + initrd, and also
> a rhel5 beta kernel+initrd. I think the issue is somewhere with the initrd,
> but don''t really found a hook to
> change anything, maybe short of rebuilding the initrd using --preload
xennet
The error message about not finding a network driver is actually a little
misleading in the Xen case. What it actually means is that the Dom0 host
failed to create the backend interface for the virtual NIC - so there was
nothing for the xennet driver to talk to.
> If You''re successfully installing FC6 domU''s from within
xen, please speak
> up!
> 
> the following are the relevant settings from the domU configfile
> kernel = "/mnt/xendistro_temp//vmlinuz"
> ramdisk = "/mnt/xendistro_temp/initrd.img"
> extra = "ks=http://192.168.199.4/ks_fc6.cfg"
> ip = "192.168.199.5"
> netmask = "255.255.255.0"
> gateway = "192.168.199.1"
> # single line :)
> disk = [ ''phy:/dev/evms/ll-kickme_root,hda,w'',
> ''phy:/dev/evms/ll-kickme_rootmir,hdb,w'',
> ''phy:/dev/evms/ll-kickme_swap,hdc,w'',
> ''phy:/dev/evms/ll-kickme_home,hdd,w'' ]
> vif = [ ''type=ioemu, bridge=xenbr1'' ]
This is your problem - ''type=ioemu'' is only relevant for
fully-virt
guests, but you''re trying to do parav-irt install - just remove the
type param & it will probably work.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|

Hi Daniel,

2006/11/10, Daniel P. Berrange
<berrange@redhat.com>:
>
> On Fri, Nov 10, 2006 at 01:41:02AM +0100, Florian Heigl wrote:
> > Hello,
> >
> > I found one more little issue to stumble over :)
> >
> > I tried (among others) the following kernel:
> > kernel-xen-2.6.18-1.2798.fc6.i686.rpm and the initrd from a (freshly
> > rsynced) images/xen/ directory.
> >
> > When the domU is created it comes up properly, and automatically
> preloads
> > the xenvbd module,
> > but not xennet. I extracted the initrd and found the xennet module
> there,

[...] snipped myself out
> ''phy:/dev/evms/ll-kickme_home,hdd,w'' ]
> > vif = [ ''type=ioemu, bridge=xenbr1'' ]
>
> This is your problem - ''type=ioemu'' is only relevant for
fully-virt
> guests, but you''re trying to do parav-irt install - just remove
the
> type param & it will probably work.

Thank You _again_, You pointed me at the right thing.
I am currently trying to figure out why I added it in the first place, my
template
doesn''t have it. I think it was about the type=ioemu vif being cleared
from
the bridge more reliable than the standard vif.
i.e. just now
root@xen-host3 /etc/xen/configs/linlab# xm create -c ll-kickme
Using config file "ll-kickme".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
this happened after a successful boot, so my spirit is up anyway)

I feel a bit stupid, having wasted a few hours on this.
on the other had it still fed google. :)

-- 
''Sie brauchen sich um Ihre Zukunft keine Gedanken zu machen''