WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] boot Xen 4.0

To: yingbin wang <yingbin.wangyb@xxxxxxxxx>
Subject: Re: [Xen-devel] boot Xen 4.0
From: ccmail111 <ccmail111@xxxxxxxxx>
Date: Mon, 17 May 2010 13:17:37 -0700 (PDT)
Cc: deshantm@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 17 May 2010 13:18:49 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1274127457; bh=qShCR4bepeT2pkHa0gl/pboe2FLIvLM9N/jMsFP4/Yk=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=DNewBMvHfDVUY3hq7rmofv5/rf2PcTC4Q5oAkilU0Gt6fh0qvOF4D3qyOmueR8gHa8VJfVGJAbWR9ht8hrqi966ip1W/qRpeWP5Eg5chxdZ4WGqwUeHtPk2xAt5uEhQmRzidlrMvPxMHFgw/RZX4rHxC+wsu/kppH0ZrecIJWq0=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=LteMHbDe6Jpogb+DXbSgGf9KHRwrPlwF/QmdKTeTdUZ/tkbcIDAIJbKQwO8w/4nzvjMgbpIc27mzrL+k05Sa/ErniRfjN4dZUmhPpcJ7oNioJ8C+zFuTpjeVnXwCLneI7T5Dkg5ZHmd1STi2c/ctoF8KWcbKzGcslga6UVUPEzo=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTik0kQ-aV5TnxaE_bOHw1Ur8Ju2MRLaE0udO8cFV@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Hi Yingbin,

Thanks, I tried but no progress.

I see during boot kernel stuck at:
usb usb6: Manufacturer: Linux 2.6.31.13 uhci_hcd
usb usb6: SerialNumber: 0000:00:1d.0
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
xen: registering gsi 16 triggering 0 polarity 1
xen_allocate_pirq: returning irq 16 for gsi 16
xen: --> irq=16
xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic 0 pin 16 triggering 1 polarity 1
(XEN) io_apic.c:2290:
(XEN) ioapic_guest_write: apic=0, pin=16, irq=16
(XEN) ioapic_guest_write: new_entry=0001a998
(XEN) ioapic_guest_write: old_entry=0000a998 pirq=16
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
uhci_hcd 0000:00:1d.1: PCI INT D -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.1: irq 16, io base 0x00004040
usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb7: Product: UHCI Host Controller
usb usb7: Manufacturer: Linux 2.6.31.13 uhci_hcd
usb usb7: SerialNumber: 0000:00:1d.1
usb usb7: configuration #1 chosen from 1 choice
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
xen: registering gsi 16 triggering 0 polarity 1
xen_allocate_pirq: returning irq 16 for gsi 16
xen: --> irq=16
xen_set_ioapic_routing: irq 16 gsi 16 vector 16 ioapic 0 pin 16 triggering 1 polarity 1
(XEN) io_apic.c:2290:
(XEN) ioapic_guest_write: apic=0, pin=16, irq=16
(XEN) ioapic_guest_write: new_entry=0001a998
(XEN) ioapic_guest_write: old_entry=0000a998 pirq=16
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
uhci_hcd 0000:00:1d.2: PCI INT D -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
uhci_hcd 0000:00:1d.2: irq 16, io base 0x00004020
usb usb8: New USB device found, idVendor=1d6b, idProduct=0001
usb usb8: New USB device strings: Mfr=3, Product=2, Serial
    <<<< stuck here...


grub conf is:

title Xen 4.0 debug  XenLinux 2.6
        root (hd0,0)
       kernel /xen-4.0.0.gz console=com1, com1=115200,8n1 noreboot loglvl=all  vv
ga=text-80x50,keep iommu=off apic=debug guest_loglvl=all
       module /vmlinuz-2.6.31.13  ro root=/dev/ram0 console=hvc0  earlyprintk=xee
n nomodeset initcall_debug debug loglevel=10
       module /initrd.img-2.6.31.13



Any suggestions ?

CM

--- On Sat, 5/15/10, yingbin wang <yingbin.wangyb@xxxxxxxxx> wrote:

From: yingbin wang <yingbin.wangyb@xxxxxxxxx>
Subject: Re: [Xen-devel] boot Xen 4.0
To: "ccmail111" <ccmail111@xxxxxxxxx>
Cc: "Pasi Kärkkäinen" <pasik@xxxxxx>, deshantm@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Saturday, May 15, 2010, 12:34 PM

I met similar problems and solved it.

if your grub.conf is OK, you can try to edit a option of  your .config.
CONFIG_SYSFS_DEPRECATED_V2=y

2010/5/14 ccmail111 <ccmail111@xxxxxxxxx>
>
> Thanks Pasi/Todd,
>
> I did:
> # mkinitrd -v -f --builtin=ehci-hcd --builtin=ohci-hcd --builtin=uhci-hcd --builtin=ahci --builtin=aacraid --builtin=aacraid --builtin=sd_mod --builtin=scsi_mod /boot/initrd.img-2.6.31.13 2.6.31.13
>
>
> Now
> I see during boot: kernel panic:
>
> Mounting root filesystem.
> mount: could not find filesystem '/dev/root'
> setting up other filesystems
> setting up new root fs
> setuproot: moving /dev failed No such file or directory
> setuproot: error mounting /proc: No such file or directory
> setuproot: error mounting /sys: No such file or directory
> switchroot: mount failed: No such file or directory
>   kernel panic - not syncing : Attempted to kill init !
>
>
>
>
> --- On Thu, 5/13/10, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
>
> From: Pasi Kärkkäinen <pasik@xxxxxx>
> Subject: Re: [Xen-devel] initrd Xen 4.0
> To: "ccmail111" <ccmail111@xxxxxxxxx>
> Cc: deshantm@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
> Date: Thursday, May 13, 2010, 4:27 PM
>
> On Thu, May 13, 2010 at 01:08:36PM -0700, ccmail111 wrote:
> >    The #5 of README is not clear in details.
> >    which directory to run depmod and mkinitrd from ?
> >
>
> It doesn't matter.
>
> >    I see:
> >
> >    # depmod xen-4.0.0
> >    WARNING: Couldn't find symtab and strtab in module xen-4.0.0
> >
>
> Wrong. You need to run depmod for the *kernel*, not for xen.
>
> So like this:
> depmod -a 2.6.32.12
>
> Or whatever is your kernel version.
>
> -- Pasi
>
> >    # ls -l
> >    total 1356
> >    -rw-r--r-- 1 root root 1380620 May 13 13:05 xen-4.0.0
> >
> >    Any suggestions ?
> >
> >    --- On Wed, 5/12/10, Todd Deshane <deshantm@xxxxxxxxx> wrote:
> >
> >      From: Todd Deshane <deshantm@xxxxxxxxx>
> >      Subject: Re: [Xen-devel] initrd Xen 4.0
> >      To: "ccmail111" <ccmail111@xxxxxxxxx>
> >      Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> >      Date: Wednesday, May 12, 2010, 9:46 PM
> >
> >      Hi,
> >
> >      See inline.
> >
> >      On Wed, May 12, 2010 at 12:25 PM, ccmail111 <[1]ccmail111@xxxxxxxxx>
> >      wrote:
> >      >
> >      > Hi,
> >      >
> >      > I downloaded Xen 4.0 and did:
> >      > make install
> >      > I donot see initrd (ramdisk) being created at all.
> >      >
> >      > Any suggestions ?
> >      >
> >
> >      Step 5 of the README
> >         Depending on your config, you may need to use 'mkinitrd' to create
> >         an initial ram disk, just like a native system e.g.
> >          # depmod 2.6.18-xen
> >          # mkinitrd -v -f --with=aacraid --with=sd_mod --with=scsi_mod
> >      initrd-2.6.18-xen.img 2.6.18-xen
> >         Other systems may requires the use of 'mkinitramfs' to create the
> >         ram disk.
> >          # depmod 2.6.18-xen
> >          # mkinitramfs -o initrd-2.6.18-xen.img 2.6.18-xen
> >
> >      You may need to change the kernel version based on what you built.
> >      Also some distros use different commands to build initrd files.
> >
> >      I actually forgot about this step for a second too.
> >
> >      Thanks,
> >      Todd
> >
> >      --
> >      Todd Deshane
> >      [2]http://todddeshane.net
> >      [3]http://runningxen.com
> >
> > References
> >
> >    Visible links
> >    1. file:///mc/compose?to=ccmail111@xxxxxxxxx
> >    2. http://todddeshane.net/
> >    3. http://runningxen.com/
>
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>