RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result

[You, Yongkang]

Hi Akio,

Sorry for response late. It is very detailed instructions. :)
I found my initrd doesn't preload xenblk.ko. Then it failed to create root device.
Now I can create xenU too with your guide. Thank you so much. 
But did you notice xenU booting is a little slow?

Best Regards,
Yongkang (Kangkang) 永康
> -----Original Message-----
> From: Akio Takebe [mailto:[e-mail]]
> Sent: 2006年9月22日 13:06
> To: You, Yongkang; Yang, Fred; [e-mail];
> [e-mail]
> Cc: [e-mail]; Akio Takebe
> Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result
>
> Hi, Yongkang and all
>
> I can boot up domU by using my special initrd without vif.
> I think mkinitrd of fc6 make initrd by using dom0 infomation.
> (for example dom0's /etc/fstab, dom0's pci infomaition. )
> So when xm boot domU, domU kernel don't use bootparmeter of domU.
>
> The below is a recipe of making my special inird
> copy initrd
>
> # mkdir tmp
> # cp /boot/efi/efi/redhat/initrd-2.6.18-1.2679.fc6xenU.img tmp/
> expand inird
>
> # cd tmp
> # gzip -cd ../initrd-2.6.18-1.2679.fc6xenU.img |cpio -id
> modify init in initrd
>
> # vi init
>    insmod /lib/ohci-hcd.ko
>    echo "Loading ehci-hcd.ko module"
>    insmod /lib/ehci-hcd.ko
>    mount -t usbfs /proc/bus/usb /proc/bus/usb
>    echo "Loading jbd.ko module"
>    insmod /lib/jbd.ko
>    echo "Loading ext3.ko module"
>    insmod /lib/ext3.ko
>    #echo "Loading scsi_mod.ko module"           <<<<<< comment out
>    #insmod /lib/scsi_mod.ko                     <<<<<< comment out
>    #echo "Loading sd_mod.ko module"             <<<<<< comment out
>    #insmod /lib/sd_mod.ko                       <<<<<< comment out
>    #echo "Loading scsi_transport_spi.ko module" <<<<<< comment out
>    #insmod /lib/scsi_transport_spi.ko           <<<<<< comment out
>    #echo "Loading mptbase.ko module"            <<<<<< comment out
>    #insmod /lib/mptbase.ko                      <<<<<< comment out
>    #echo "Loading mptscsih.ko module"           <<<<<< comment out
>    #insmod /lib/mptscsih.ko                     <<<<<< comment out
>    #echo "Loading mptspi.ko module"             <<<<<< comment out
>    #insmod /lib/mptspi.ko                       <<<<<< comment out
>    echo "Loading xenblk.ko module"
>    insmod /lib/xenblk.ko
>    mkblkdevs
>    #resume LABEL=SWAP-sda3                      <<<<<< comment
> out
>    echo Creating root device.
>    mkrootdev -t ext3 -o defaults,ro sda1 <<<<change device to sda1
>    echo Mounting root filesystem.
>    mount /sysroot
>    echo Setting up other filesystems.
>    setuproot
>    echo Switching to new root and running init.
>    switchroot
> 4. make new initrd
> # find . -print | cpio --quiet -c -o | gzip -9 >../initrd-new.img
> my domU configuration
>
> kernel = "/boot/efi/efi/redhat/vmlinuz-2.6.18-1.2679.fc6xen"
> ramdisk = "/xen/initrd-new.img"
> memory = 1024
> name = "fc6.DomU"
> #vif = [ '' ]
> disk = [ 'file:/xen/image/fc6.root.img,sda1,w' ]
> root = "/dev/sda1 ro"
> extra = "4 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe selinux=0
> rhgb"
> etc
>
> 6.1. copy modlues into domU image file
>        # mount -o loop domU.img /mnt
>        # cp -a /lib/modules/2.6.18-1.2679.fc6xen/ /mnt/lib/modules/
>   6.2. disable selinux
>        # vi /etc/sysconfig/selinux
>        SELINUX=disabled <<<< change enforcing to disabled
>   6.3. modify /etc/fstab in domU.img
>    /dev/sda1     /         ext3    defaults        1 1
>    devpts        /dev/pts  devpts  gid=5,mode=620  0 0
>    tmpfs         /dev/shm  tmpfs   defaults        0 0
>    proc          /proc     proc    defaults        0 0
>    sysfs         /sys      sysfs   defaults        0 0
>
> But I cannot use network on domU.
> I'll check the src.rpm of kernel-xen.
>
> Best Regards,
>
> Akio Takebe
> > Hi Akio,
> >
> > Sorry for response late. I just tried with the config you provide (I
> > changed xenU modprobe.conf and fstab). But unfortunately it still couldn't
> > work. XenU booting still report can not find filesystem /dev/root/ and
> > kernel panic.
> >
> > Well, after add "ide0=noprobe" etc. xenU won't complain to check hda, hdb
> > etc. again. Thanks for this information.
> >
> > Best Regards,
> > Yongkang (Kangkang) モタソオ
> > > -----Original Message-----
> > > From: Akio Takebe [mailto:[e-mail]]
> > > Sent: 2006ト・ヤツ21ネユ 10:18
> > > To: Akio Takebe; You, Yongkang; Yang, Fred; [e-mail];
> > > [e-mail]
> > > Cc: [e-mail]
> > > Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result
> > >
> > > Hi, Yongkang
> > >
> > > I have a small mistake.
> > >
> > > Please try the following configuration.
> > >    kernel = "vmlinuz-2.6.17-1.2630.fc6xen"
> > >    ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img"
> > >    memory = 512
> > >    name = "domU"
> > >    vif = [ '' ]
> > >    disk = [ 'file:/xen/image/fc6.root.img,sda1,w' ] <----this
> > >    root = "/dev/sda1 ro" <--------this
> > >    extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe"
>
> <---
> > > -this
> > >
> > > Best Regards,
> > >
> > > Akio Takebe
> > > > Hi, Yongkang
> > > >
> > > > I think this issue is configuration mistakes.
> > > > Can you try the following configuration?
> > > > I cannot try it because I meet another issue...
> > > > /etc/modprobe.conf for initrd of domU
> > > >
> > > > The following configuration would solve the issue of booting domU.
> > > >    [root@tiger156 xen]# cat /etc/modprobe.conf
> > > >    #alias eth0 e1000
> > > >    #alias scsi_hostadapter mptbase
> > > >    #alias scsi_hostadapter1 mptspi
> > > >    alias eth0 xennet  <----this
> > > >    alias scsi_hostadapter xenblk <----and this
> > > > domU.conf
> > > >
> > > > The following configuration would solve the issue of probing ide disk.
> > > >    kernel = "vmlinuz-2.6.17-1.2630.fc6xen"
> > > >    ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img"
> > > >    memory = 512
> > > >    name = "domU"
> > > >    vif = [ '' ]
> > > >    disk = [ 'file:/xen/image/fc6.root.img,hda1,w' ]
> > > >    root = "/dev/hda1 ro"
> > > >    extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe"
> > >
> > > <----this
> > > > Best Regards,
> > > >
> > > > Akio Takebe
> > > > > Hi,
> > > > >
> > > > > I have reported 2 bugs to redhat bugzilla:
> > > > > [Bug 207227] New: Xen0 reboot command can not reboot Tiger4
>
> machine.
> > > > > [Bug 207241] New: XenU domain can not be created successfully.
> > > > > New xenU created failure serial log has been pasted to the bug.
> > > > >
> > > > > I also notice FC6-test3 Xen0 operation is a little slower, compared with
> > > > > RHEL4u3. I assign 2 vcpus to Xen0. When I destroy domains or do some
> > >
> > > heavy
> > > > > IO operations, Xen0 operations will be blocked for a while. I didn't track
> > > > > this to bugzilla.
> > > > >
> > > > > There are also a lot of unaligned accessing from some applications. They
> > > > > should be common FC6-test3 issues.
> > > > >
> > > > > Sometime Xen0 monitor will print "Bug: soft lockup detected on
>
> CPU#0(or
> > > #1)"
> > > > > Best Regards,
> > > > > Yongkang (Kangkang) ・筵ソ・ス・ェ
> > > > > > -----Original Message-----
> > > > > > From: [e-mail]
> > > > > > [mailto:[e-mail]] On Behalf Of
>
> You,
> > > > > > Yongkang
> > > > > > Sent: 2006・ネs・茹ト20・ヘ・・10:07
> > > > > > To: Yang, Fred; [e-mail]; [e-mail]
> > > > > > Cc: [e-mail]
> > > > > > Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test
> > > > > > result
> > > > > >
> > > > > > Hi Fred & Yoshi,
> > > > > >
> > > > > > The former XenU creating failure issue seemed to be the config issue.
> > >
> > > Now I
> > > > > > can create XenU. But XenU booting process met an old bug. It will cost
>
> a
> > > > > > long
> > > > > > time to check hard disk IRQ response from hda to hdh.
> > > > > >
> > > > > > After that, xenU met the problem of mounting root partition to start
> > > > > > services,
> > > > > > and then XenU booting failed (Kill init). I am not sure if it is because
> > > > > > initrd issue.
> > > > > > I will continue to check it.
> > > > > >
> > > > > > Best Regards,
> > > > > > Yongkang (Kangkang) ・筵ソ・ス・ェ
> > > > > >
> > > > > > >-----Original Message-----
> > > > > > >From: [e-mail]
> > > > > > >[mailto:[e-mail]] On Behalf Of
> > >
> > > Yang,
> > > > > > >Fred
> > > > > > >Sent: 2006・ネs・茹ト20・ヘ・・8:26
> > > > > > >To: [e-mail]; [e-mail]
> > > > > > >Cc: [e-mail]
> > > > > > >Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test
> > >
> > > result
> > > > > > >
> > > > > > >Here it comes!
> > > > > > >-Fred
> > > > > > >
> > > > > > >>-----Original Message-----
> > > > > > >>From: [e-mail] [mailto:[e-mail]]
> > > > > > >>Sent: Tuesday, September 19, 2006 4:23 PM
> > > > > > >>To: Yang, Fred; [e-mail]
> > > > > > >>Cc: [e-mail]
> > > > > > >>Subject: Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test
> > > > > > >>result
> > > > > > >>
> > > > > > >>Fred, Yongkang,
> > > > > > >>
> > > > > > >>> Other issues:
> > > > > > >>> 1) Xen0 operation is a little slower than RHEL4u3.
> > > > > > >>> 2) XenU creating failure, please see attachment for the serial
> > > > > > >>> output.
> > > > > > >>
> > > > > > >>I can't find the attachment.
> > > > > > >>Could you repost the serial log?
> > > > > > >>
> > > > > > >>Thanks,
> > > > > > >>Yoshi Oguchi
> > > > > > >>
> > > > > > >>"Yang, Fred"  wrote。ケ・ウ
> > > > > > >>> Following is the quick Xen test result with FC6 Test3.  We will file
> > > > > > >>BZ for the issues tonight; the early data is to get community to fix
> > > > > > >>Xen
> > > > > > >>issues ASAP
> > > > > > >>> Thanks,
> > > > > > >>> -Fred
> > > > > > >>>
> > > > > > >>> ====
> > > > > > >>> I have followed Redhat instructions (FC6-test3 can not be installed
> > > > > > >>from CDs) to install FC6-Test3 and do some testing.  Both Xen0 and
> > >
> > > VTI
> > > > > > >>can all boot up, but XenU couldn't be created successfully.
> > > > > > >>>
> > > > > > >>> Detailed Items:
> > > > > > >>> 1.  Using yum to upgrade FC6 Test2 to FC6 Test3    [almost
>
> Pass]
> > > > > > need
> > > > > > >>manually reinstall kernel-xen rpm package.
> > > > > > >>> 2.  Boot Native Linux of FC6 Test3   [Pass]
> > > > > > >>> 3.  Boot Xen of FC6 Test3   [Pass]
> > > > > > >>> 4.  xend and xm commands are working.    [Pass]
> > > > > > >>> 5.  XenU Domain creating failed.     [__FAIL__]
> > > > > > >>> 6.  Missing VTI guest firmware
>
> (/usr/lib/xen/boot/guest_firmware.bin)
> > > > > > >>    [__FAIL__ (expected)]
> > > > > > >>> 7.  After manually copy VTI guest firmware, creating VTI domain
> > > > > > >>[Pass]
> > > > > > >>> 8.    VTI domain with network supported     [Pass]
> > > > > > >>> 9.    2 VTI domains coexisting testing      [Pass]
> > > > > > >>> 10.   Linux Kernel build in VTI domain          [Pass]
> > > > > > >>> 11.   LTP testing in VTI domain          [Pass]
> > > > > > >>> 12.   SMP VTI domain          [Pass]
> > > > > > >>> 13.   SMP Xen0       [Pass]
> > > > > > >>> 14.   1 VTI Windows 2k3       [Pass] a little slower.
> > > > > > >>> 15.   1 VTI Linux + 1 VTI Windows    [__FAIL__ VTI Windows
>
> blue
> > > > > > >screen]
> > > > > > >>> 16.  Reboot machine failed with Xen FC6-test3. [__FAIL__]
> > > > > > >>>
> > > > > > >>> Other issues:
> > > > > > >>> 1) Xen0 operation is a little slower than RHEL4u3.
> > > > > > >>> 2) XenU creating failure, please see attachment for the serial
> > > > > > >>> output.
> > > > > > >>>
> > > > > > >>> Best Regards,
> > > > > > >>> Yongkang (Kangkang) ・筵ソ・ス・ェ
> > > > > > >>>
> > > > > > >>> _______________________________________________
> > > > > > >>> Xen-ia64-devel mailing list
> > > > > > >>> [e-mail]
> > > > > > >>> http://lists.xensource.com/xen-ia64-devel
> > > > > >
> > > > > > Xen-ia64-devel mailing list
> > > > > > [e-mail]
> > > > > > http://lists.xensource.com/xen-ia64-devel
> > > > >
> > > > > Xen-ia64-devel mailing list
> > > > > [e-mail]
> > > > > http://lists.xensource.com/xen-ia64-devel
> > > >
> > > > Xen-ia64-devel mailing list
> > > > [e-mail]
> > > > http://lists.xensource.com/xen-ia64-devel

[Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result

[Akio Takebe]

Hi, Yongkang
> Hi Akio,
>
> Sorry for response late. It is very detailed instructions. :)
> I found my initrd doesn't preload xenblk.ko. Then it failed to create root 
> device.
> Now I can create xenU too with your guide. Thank you so much. 
> But did you notice xenU booting is a little slow?

Yes, starting sendmail is very slow.
I also suspected dom0/domU hanged up. :-)

Best Regards,

Akio Takebe