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

[Xen-users] Error: ramdisk

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: [Xen-users] Error: ramdisk
From: ccmail111 <ccmail111@xxxxxxxxx>
Date: Sat, 20 Mar 2010 09:06:22 -0700 (PDT)
Cc: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 20 Mar 2010 09:08:30 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1269101182; bh=m2sJ0aXTzN7OIRKSmuEGwYGQH6mxzN1Gui8T+CKJzdY=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=WWRjhjLuMKVRgT2Imj+pqPZiSv4PijqxEC3GKXkB0EnLFdbjXqU2IzZSda6WXjb/M84UrfLqHCBmb6Xo73KWLAZygrMgicM5K60gkVNvmiQC/XnYH14LkouFDC32sFe7yrP5dygB+ryP+tUZjnQtofYHT2Q5ukLR/X4+whAURRI=
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:MIME-Version:Content-Type; b=Ueo/w19qL8vOivZjTTn7F3BwcZf9bYZ9ZPWhFk7TN6fVYo0GTDga3/x99oiB1SmHaIsyt0ELnOYfvS+CyIiQkbJXMXRnsAGwHn18MdEgJJlButLXnfFvcyMxYZ0kn4NXy85H7BGmMcdG0OU5BuTvv0i7acUUR4Ouh3JCeB94OgA=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
 
Sure. Thanks again for the prompt help - very appreciated.
As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.
 

Now error below Xen dom 0 is trying to bring up Linux:

 

<..clipped..>

md: ... autorun DONE.

RAMDISK: ext2 filesystem found at block 0

RAMDISK: image too big! (524288KiB/4096KiB)

 

<...clipped: Details below...>

 

 

 
The grub is:
 
title SPIRIT OS: Dom0 Xen 3.4 XenLinux 2.6
       kernel /boot/xen.gz noreboot dom0_mem=8024M loglvl=all  console=com1 com1=115200,8n1
       module /boot/vmlinuz.vm  root=dev/ram0 ro console=ttyS0, 115200
       module /boot/ramdisk.gz
 
 
RAMDISK:
 

# ls -l ./ramdisk.gz

-rwxr-xr-x 1 root root 44512403 Mar 20 00:15 ./ramdisk.gz

 

RAMDISK uncompressed: 

# ls -l ./ramdisk

-rwxr-xr-x 1 root root 1051721728 Mar 20 01:22 ./ramdisk

 
CONSOLE LOG DETAILS:
 
(XEN) PCI add device 00:09.0
PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
NET: Registered protocol family 2
IP route cache hash table entries: 262144 (order: 9, 2097152 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
IA-32 Microcode Update Driver: v1.14a-xen <tigran@xxxxxxxxxxx>
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Limiting direct PCI/PCI transfers.
PCI: PIIX3: Enabling Passive Release on 0000:00:01.0
Activating ISA DMA hang workarounds.
floppy0: Unable to grab DMA2 for the floppy driver
FDC 0 is a S82078B
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
HP CISS Driver (v 3.6.10)
Intel(R) PRO/1000 Network Driver - version 7.1.9-k4
Copyright (c) 1999-2006 Intel Corporation.
(XEN) PCI add device 00:03.0
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKC] -> GSI 11 (level, high) -> IRQ 11
e1000: 0000:00:03.0: e1000_probe: (PCI:33MHz:32-bit) 52:46:03:00:04:01
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
pcnet32.c:v1.32 18.Mar.2006 tsbogend@xxxxxxxxxxxxxxxx
e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
(XEN) PCI add device 00:08.0
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LNKD] -> GSI 10 (level, high) -> IRQ 10
e100: eth1: e100_probe: addr 0xf6001000, irq 10, MAC addr 52:54:00:12:34:5A
(XEN) PCI add device 00:09.0
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LNKA] -> GSI 10 (level, high) -> IRQ 10
e100: eth2: e100_probe: addr 0xf6040000, irq 10, MAC addr 52:54:00:12:34:5B
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@xxxxxxxxxxxx>
Xen virtual console successfully installed as xvc0
Event-channel device installed.
blktap_device_init: blktap device major 254
blktap_ring_init: blktap ring major: 253
netfront: Initialising virtual ethernet driver.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX3: IDE controller at PCI slot 0000:00:01.1
PIIX3: chipset revision 0
PIIX3: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio
hda: QEMU HARDDISK, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: QEMU DVD-ROM, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
(XEN) PCI add device 00:01.1
hda: max request size: 512KiB
hda: 204800 sectors (104 MB) w/256KiB Cache, CHS=203/255/63, (U)DMA
hda: cache flushes supported
 hda: unknown partition table
hdc: ATAPI 4X CD-ROM drive, 512kB Cache, (U)DMA
Uniform CD-ROM driver Revision: 3.20
Adaptec aacraid driver (1.1-5[2409]-mh2)
3ware Storage Controller device driver for Linux v1.26.02.001.
Fusion MPT base driver 3.04.01
Copyright (c) 1999-2005 LSI Logic Corporation
Fusion MPT SPI Host driver 3.04.01
usbmon: debugfs is not available
USB Universal Host Controller Interface driver v3.0
(XEN) PCI add device 00:01.2
ACPI: PCI Interrupt 0000:00:01.2[D] -> Link [LNKD] -> GSI 10 (level, high) -> IRQ 10
uhci_hcd 0000:00:01.2: UHCI Host Controller
uhci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:01.2: irq 10, io base 0x0000c020
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usbcore: registered new driver usbhid
/ws/stevyang-sjc/hpv/hypervisor/contrib/linux-2.6.18-xen-3.4.2/contents/drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@xxxxxxxxxx
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
input: AT Translated Set 2 keyboard as /class/input/input0
input: ImExPS/2 Generic Explorer Mouse as /class/input/input1
Bridge firewalling registered
PCI IO multiplexer device installed.
ACPI: (supports S3 S4 S5)
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: ext2 filesystem found at block 0
RAMDISK: image too big! (524288KiB/4096KiB)
Root-NFS: No NFS server available, giving up.

VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Insert root floppy and press ENTER


 

Thanks !

 

SV


--- On Sat, 3/20/10, Pasi Kärkkäinen <pasik@xxxxxx> wrote:


From: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] Fw: not syncing
To: "ccmail111" <ccmail111@xxxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx>
Date: Saturday, March 20, 2010, 4:30 AM

On Sat, Mar 20, 2010 at 12:44:25AM -0700, ccmail111 wrote:
> Hi Pasi/Dan,
>
> 1) The error below is:
>
> > Kernel panic - not syncing: Out of memory
>

Please paste your grub.conf and the full boot log of the hypervisor.

-- Pasi

> 2) The printk options below seem to be ok.
> But if that not recommended, for Xen 3.4.2/linux-2.6.18-xen  how to enable serial then ?
>
> Any thoughts ?
>
> --- On Sat, 3/20/10, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
>
>   From: Pasi Kärkkäinen <pasik@xxxxxx>
>   Subject: Re: [Xen-devel] Fw: not syncing
>   To: "ccmail111" <ccmail111@xxxxxxxxx>
>   Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx>
>   Date: Saturday, March 20, 2010, 3:14 AM
>
>   On Sat, Mar 20, 2010 at 12:00:40AM -0700, ccmail111 wrote:
>   >
>   > Attaching error I see on serial:
>   >
>   >
>   > (XEN) Dom0 has maximum 1 VCPUs
>   >
>   > (XEN) Scrubbing Free RAM:
>   > ....................................................................done.
>   >
>   > (XEN) Xen trace buffers: disabled
>   >
>   > (XEN) Std. Loglevel: All
>   >
>   > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
>   >
>   > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
>   >
>   > (XEN) Freed 128kB init memory.
>   >
>   > Bootdata ok (command line is root=dev/ram0 ro console=hvc0 earlyprintk=xen
>   > nomodeset)
>   >
>
>   "console=hvc0 earlyprintk=xen" are options for a pvops dom0 kernel,
>   I don't think linux-2.6.18-xen can use them.
>
>   -- Pasi
>
>   > Linux version 2.6.18.8-xen (stevyang@wilma) (gcc version 4.1.2 20080704 (Red Hat
>   > 4.1.2-44)) #1 SMP Mon Mar 15 23:23:21 PDT 2010
>   >
>   > BIOS-provided physical RAM map:
>   >
>   >  Xen: 0000000000000000 - 0000000040800000 (usable)
>   >
>   > kernel direct mapping tables up to 40800000 @ 3f736000-3f93d000
>   >
>   > DMI 2.4 present.
>   >
>   > bootmem alloc of 14794752 bytes failed!
>   >
>   > Kernel panic - not syncing: Out of memory
>   >
>   >  (XEN) Domain 0 crashed: 'noreboot' set - not rebooting.
>   >
>   > Any thoughts/suggestions, appreciated !
>   >
>   > Thanks,
>   > SV
>   >
>   > --- On Sat, 3/20/10, ccmail111 <[1]ccmail111@xxxxxxxxx> wrote:
>   >
>   >   From: ccmail111 <[2]ccmail111@xxxxxxxxx>
>   >   Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation
>   >   To: [3]xen-devel@xxxxxxxxxxxxxxxxxxx, "Dan Magenheimer"
>   <[4]dan.magenheimer@xxxxxxxxxx>
>   >   Date: Saturday, March 20, 2010, 2:37 AM
>   >
>   >   Thanks Dan.
>   >   I am past that and see different error now:
>   >
>   >   "Xen: Scrubbing Free RAM ............"
>   >   Then the xterm(screen) goes blank..
>   >
>   >   Any thoughts ?
>   >
>   >   SV
>   >   --- On Fri, 3/19/10, Dan Magenheimer <[5]dan.magenheimer@xxxxxxxxxx> wrote:
>   >
>   >     From: Dan Magenheimer <[6]dan.magenheimer@xxxxxxxxxx>
>   >     Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation
>   >     To: "ccmail111" <[7]ccmail111@xxxxxxxxx>, [8]xen-devel@xxxxxxxxxxxxxxxxxxx
>   >     Date: Friday, March 19, 2010, 9:16 PM
>   >
>   >     Your kernel and initrd are compressed and still exceed 512MB?  That is very
>   >     unusual.  Are you building everything in your dom0 kernel? (e.g. answering yes
>   >     to all drivers, and everything when configuring your kernel?)  If so, thatâ**s
>   >     not a good idea and is likely contributing to your problem.
>   >
>   >
>   >
>   >     You didnâ**t say how much memory is in your machine.  If you have enough, you
>   >     can try dom0_mem=768M or dom0_mem=1GB and so on.
>   >
>   >
>   >
>   >     If those suggestions donâ**t work, sorry, maybe someone else can answer but this
>   >     is probably a xen-users list question than a xen-devel question.
>   >
>   >
>   >
>   >     From: ccmail111 [mailto:[9]ccmail111@xxxxxxxxx]
>   >     Sent: Friday, March 19, 2010 5:47 PM
>   >     To: [10]xen-devel@xxxxxxxxxxxxxxxxxxx; Dan Magenheimer
>   >     Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation
>   >
>   >
>   >
>   >     Hi Dan,
>   >
>   >     Thanks for response.
>   >
>   >
>   >
>   >     I just tried (with dom0_mem=512M) and see error:
>   >
>   >     "Domain 0 allocation is too small for kernel image"
>   >
>   >
>   >
>   >     But if I dont use the parameter I see error as in subject line which is
>   >     different.
>   >
>   >     Question is: does subject line error printed by kernel ? Any kernel parameter
>   >     that I need to change during build ?
>   >
>   >
>   >
>   >     Any suggestions ?
>   >
>   >     Is there anyway I can specifiy the max for kernel and xen ?
>   >
>   >
>   >
>   >     Thanks,
>   >
>   >
>   >
>   >     SV
>   >
>   >
>   >
>   >     --- On Fri, 3/19/10, Dan Magenheimer <[11]dan.magenheimer@xxxxxxxxxx> wrote:
>   >
>   >       From: Dan Magenheimer <[12]dan.magenheimer@xxxxxxxxxx>
>   >       Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation
>   >       To: "ccmail111" <[13]ccmail111@xxxxxxxxx>, [14]xen-devel@xxxxxxxxxxxxxxxxxxx
>   >       Date: Friday, March 19, 2010, 6:10 PM
>   >
>   >       You should be able to get around this problem by specifying dom0_mem= on the
>   >       Xen boot line, e.g.:
>   >
>   >
>   >
>   >       kernel /boot/xen.gz noreboot loglvl=all dom0_mem=256M
>   >
>   >
>   >
>   >     From: ccmail111 [mailto:[15]ccmail111@xxxxxxxxx]
>   >     Sent: Friday, March 19, 2010 3:43 PM
>   >     To: [16]xen-devel@xxxxxxxxxxxxxxxxxxx
>   >     Subject: [Xen-devel] Fw: Not enough RAM for domain 0 allocation
>   >
>   >
>   >
>   >     --- On Fri, 3/19/10, ccmail111 <[17]ccmail111@xxxxxxxxx> wrote:
>   >
>   >     From: ccmail111 <[18]ccmail111@xxxxxxxxx>
>   >     Subject: Not enough RAM for domain 0 allocation
>   >     To: "Fajar A. Nugraha" <[19]fajar@xxxxxxxxx>
>   >     Cc: [20]xen-users@xxxxxxxxxxxxxxxxxxx
>   >     Date: Friday, March 19, 2010, 5:38 PM
>   >
>   >
>   >
>   >     Hi,
>   >
>   >
>   >
>   >     I see above error when xen tries to boot up.
>   >
>   >
>   >
>   >     The grub.conf is:
>   >
>   >
>   >
>   >     title Dom0 Xen 3.4.2  XenLinux 2.6
>   >            kernel /boot/xen.gz noreboot loglvl=all
>   >            module /boot/vmlinuz.vm  root=dev/ram0 ro
>   >            module /boot/ramdisk.gz
>   >
>   >     Looking through archives I found couple of pointers but no solution.
>   >
>   >     The closest I see:
>   >
>   >
>      [1][21]http://www.mailinglistarchive.com/xen-devel@xxxxxxxxxxxxxxxxxxx/msg56592.html
>   >
>   >     by Keir:
>   >
>   >
>   >
>   >     " Either this restriction of the domain builder needs
>   >     to be lifted (a bit of a pain and not really on anyone's todo list), ..."
>   >
>   >
>   >
>   >     Any solutions/suggestions is appreciated !
>   >
>   >
>   >
>   >     Thanks !
>   >
>   >
>   >
>   >     SV
>   >
>   >
>   >
>   >
>   >
>   >
>   >
>   >
>   >
>   > References
>   >
>   >    Visible links
>   >    1.
>   [22]http://www.mailinglistarchive.com/xen-devel@xxxxxxxxxxxxxxxxxxx/msg56592.html
>
>   > _______________________________________________
>   > Xen-devel mailing list
>   > [23]Xen-devel@xxxxxxxxxxxxxxxxxxx
>   > [24]http://lists.xensource.com/xen-devel
>
> References
>
>    Visible links
>    1. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
>    2. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
>    3. http://us.mc342.mail.yahoo.com/mc/compose?to=xen-devel@xxxxxxxxxxxxxxxxxxx
>    4. http://us.mc342.mail.yahoo.com/mc/compose?to=dan.magenheimer@xxxxxxxxxx
>    5. http://us.mc342.mail.yahoo.com/mc/compose?to=dan.magenheimer@xxxxxxxxxx
>    6. http://us.mc342.mail.yahoo.com/mc/compose?to=dan.magenheimer@xxxxxxxxxx
>    7. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
>    8. http://us.mc342.mail.yahoo.com/mc/compose?to=xen-devel@xxxxxxxxxxxxxxxxxxx
>    9. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
>   10. http://us.mc342.mail.yahoo.com/mc/compose?to=xen-devel@xxxxxxxxxxxxxxxxxxx
>   11. http://us.mc342.mail.yahoo.com/mc/compose?to=dan.magenheimer@xxxxxxxxxx
>   12. http://us.mc342.mail.yahoo.com/mc/compose?to=dan.magenheimer@xxxxxxxxxx
>   13. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
>   14. http://us.mc342.mail.yahoo.com/mc/compose?to=xen-devel@xxxxxxxxxxxxxxxxxxx
>   15. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
>   16. http://us.mc342.mail.yahoo.com/mc/compose?to=xen-devel@xxxxxxxxxxxxxxxxxxx
>   17. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
>   18. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
>   19. http://us.mc342.mail.yahoo.com/mc/compose?to=fajar@xxxxxxxxx
>   20. http://us.mc342.mail.yahoo.com/mc/compose?to=xen-users@xxxxxxxxxxxxxxxxxxx
>   21. http://www.mailinglistarchive.com/xen-devel@xxxxxxxxxxxxxxxxxxx/msg56592.html
>   22. http://www.mailinglistarchive.com/xen-devel@xxxxxxxxxxxxxxxxxxx/msg56592.html
>   23. http://us.mc342.mail.yahoo.com/mc/compose?to=Xen-devel@xxxxxxxxxxxxxxxxxxx
>   24. http://lists.xensource.com/xen-devel

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