Hi, I''m trying to boot my domU based on rhel4 and i have build a custom initrd for it with the xenblk and xennet, but with partial sucess. I can boot and the following errors appear and i cannot get network. If i do ifconfig -a only lo iface appears. If there is a need for more information let me know.. Thanks for the help ----- XM INFO--------------------- xen_major : 3 xen_minor : 1 xen_extra : .3 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20070925 (Red Hat 4.1.2-33) -------ERRORS------------------- XENBUS: Device with no driver: device/console/0 XENBUS: Device with no driver: device/vbd/51713 XENBUS: Device with no driver: device/vbd/51714 XENBUS: Device with no driver: device/vif/0 ----------CFG------------------------- name = "sometest" kernel = "/boot/vmlinuz-2.6.21.7-3.fc8xen" ramdisk = "/boot/initrd-2.6.21.7-3.fc8xen.1.img" memory = "256" disk [''phy:/dev/vg1/xen-root-sometest,xvda1,w'',''phy:/dev/vg1/xen-swap-sometest,xvda2,w''] root = "/dev/xvda1 ro" vif = [ '''' ] on_reboot = ''restart'' on_crash = ''restart'' on_poweroff = ''restart'' #bootloader = ''/usr/bin/pygrub'' -------INITRD------------ mkinitrd -f --preload=xenblk --with=xenblk --with=xennet --with=ext3 --with=jbd --with=ata_piix --with=libata --with=e1000 --with=i2c_i801 --with=i2c_core --with=bridge --with=netloop --with=ipv6 --with=ip_tables --with=iptable_filter --with=loop --omit-scsi-modules --omit-raid-modules --omit-lvm-modules initrd-2.6.21.7-3.fc8xen.1.img 2.6.21.7-3.fc8xen ---------BOOTING LOG-------------- NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 3, 32768 bytes) TCP established hash table entries: 16384 (order: 6, 393216 bytes) TCP bind hash table entries: 16384 (order: 6, 262144 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 8888k freed audit: initializing netlink socket (disabled) audit(1212878640.386:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (order 0, 4096 bytes) ksign: Installing public key data Loading keyring io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.102 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize input: Macintosh mouse button emulation as /class/input/input0 Xen virtual console successfully installed as xvc0 Event-channel device installed. usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/console/0 XENBUS: Device with no driver: device/vbd/51713 XENBUS: Device with no driver: device/vbd/51714 XENBUS: Device with no driver: device/vif/0 drivers/rtc/hctosys.c: unable to open rtc device (rtc0) Freeing unused kernel memory: 200k freed Write protecting the kernel read-only data: 981k Red Hat nash version 6.0.19 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading xenblk.ko module xen-vbd: registered block device major 202 blkfront: xvda1: barriers enabled blkfront: xvda2: barriers enabled Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading mbcache.ko module Loading jbd.ko module Loading ext3.ko module Loading scsi_mod.ko module SCSI subsystem initialized Loading libata.ko module Loading ahci.ko module Waiting for driver initialization. Loading ata_piix.ko module Waiting for driver initialization. Loading e1000.ko module Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI Copyright (c) 1999-2006 Intel Corporation. Loading i2c-core.ko module Loading i2c-i801.ko module Loading bridge.ko module Bridge firewalling registered Loading netloop.ko module Loading ipv6.ko module NET: Registered protocol family 10 lo: Disabled Privacy Extensions Mobile IPv6 Loading x_tables.ko module Loading ip_tables.ko module ip_tables: (C) 2000-2006 Netfilter Core Team Loading iptable_filter.ko module Loading loop.ko module loop: loaded (max 8 devices) Creating root device. Mounting root filesystem. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Setting up other filesystems. Setting up new root fs no fstab.sys, mounting internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys SELinux: Disabled at runtime. audit(1212878650.213:2): selinux=0 auid=4294967295 INIT: version 2.85 booting Setting default font (): [ OK ] <xen-users@lists.xensource.com> _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Saturday June 07 2008 07:31:11 pm odin odin wrote:> I''m trying to boot my domU based on rhel4 and i have build a custom initrd > for it with the xenblk and xennet, but with partial sucess. I can boot and > the following errors appear and i cannot get network. If i do ifconfig -a > only lo iface appears.From your config''s kernel= and ramdisk= lines, you seem to using F8 as a dom0. Once you get your network back up in your domu, just yum install the kernel-xen package, which does a good job of calculating what modules your domu needs, and then you can use pygrub.> XENBUS: Device with no driver: device/console/0 > XENBUS: Device with no driver: device/vbd/51713 > XENBUS: Device with no driver: device/vbd/51714 > XENBUS: Device with no driver: device/vif/0AFAIK, this are just initialization messages that indicate xen needs to find drivers later in the boot process.> vif = [ '''' ]It''s a good idea to include a MAC parm in your vif= statement, rather than let xen randomly use one on each boot. Do an ''xm list -l sometest'' to find out what it is using now, and hardcode it into your config.> -------INITRD------------ > mkinitrd -f --preload=xenblk --with=xenblk --with=xennet --with=ext3 > --with=jbd --with=ata_piix --with=libata --with=e1000 --with=i2c_i801 > --with=i2c_core --with=bridge --with=netloop --with=ipv6 --with=ip_tables > --with=iptable_filter --with=loop --omit-scsi-modules --omit-raid-modules > --omit-lvm-modules initrd-2.6.21.7-3.fc8xen.1.img 2.6.21.7-3.fc8xenThis is probably your problem: you are loading xennet and e1000. Since I don''t see any pci passthrough messages in your dmesg, remove the e1000 part, and let xennet grab the virtual interface.> Creating root device. > Mounting root filesystem. > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > Setting up other filesystems. > Setting up new root fs > no fstab.sys, mounting internal defaults > Switching to new root and running init. > unmounting old /dev > unmounting old /proc > unmounting old /sys > SELinux: Disabled at runtime. > audit(1212878650.213:2): selinux=0 auid=4294967295 > INIT: version 2.85 booting > Setting default font (): [ OK ]This is a normal end of boot message, with EXT3-fs mounted. If you need to login with ''xm create sometest -c'' on the xen console (as opposed to a vnc window), make sure you have a getty in your domu''s /etc/inittab file in the getty section: co:2345:respawn:/sbin/agetty ttyS0 9600 vt100-nav and you have the xvc0 device listed in your /etc/securetty file. Or else just use vnc. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Saturday June 07 2008 08:19:20 pm you wrote:> On Saturday June 07 2008 07:31:11 pm odin odin wrote: > > I''m trying to boot my domU based on rhel4 and i have build a custom > > initrd for it with the xenblk and xennet, but with partial sucess. I can > > boot and the following errors appear and i cannot get network. If i do > > ifconfig -a only lo iface appears. > > From your config''s kernel= and ramdisk= lines, you seem to using F8 as a > dom0. Once you get your network back up in your domu, just yum install the > kernel-xen package, which does a good job of calculating what modules your > domu needs, and then you can use pygrub.Well, since your domu is based on rhel4, you will probably need to download the kernel-xen-2.6.21.7-3.fc8.i686.rpm separately from the F8 repos, and then ''rpm -ihv'' it. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Removing the e1000 module did the trick. I will rebuild the initrd again and configure the network parameters.> Well, since your domu is based on rhel4, you will probably need to download > the kernel-xen-2.6.21.7-3.fc8.i686.rpm separately from the F8 repos, and > then ''rpm -ihv'' it. >I will do that Thank you for helping> > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users