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/
Home Products Support Community News


Re: [Xen-users] Is RAMDISK required for domU boot?

To: "You, Yongkang" <yongkang.you@xxxxxxxxx>
Subject: Re: [Xen-users] Is RAMDISK required for domU boot?
From: "Itamar Reis Peixoto" <itamar@xxxxxxxxxxxxxxxx>
Date: Mon, 11 Sep 2006 23:20:50 -0300
Cc: multisyncfe991@xxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 11 Sep 2006 19:21:52 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <094BCE01AFBE9646AF220B0B3F367AAB588F4B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
the best solution for this problem is mount the domU disk on /mnt and do
this command.

for i in console null zero ; do MAKEDEV -d /mnt/dev -x $i ; done

if you're running a new distro, remember to install udev on domU


Itamar Reis Peixoto

e-mail: itamar@xxxxxxxxxxxxxxxx
msn: itamarjp@xxxxxxxxxxxxx
skype: itamarjp
icq: 81053601
+55 34 3238 3845
+55 11 4063 5033

Subject: RE: [Xen-users] Is RAMDISK required for domU boot?

From the log, the real reason is because:
Warning: unable to open an initial console.

An solution is to mount your domU harddisk firstly, then copy your
Xen0:/dev/* to domU:/dev/

After above 2 steps, that domU should be created without Ramdisk option.
Well, Ramdisk is harmless. :)

I found one weird thing: I heard RAMDISK is not required for domU, but it
seems I have to add RAMDISK to my domU config file, otherwiese the domU
will hang up when it is booting. Please see the message below, the domU
booting hangs up after "Continuing..."

Does anyone have any clue for this issue? BTW, xen-friendly glibc is



---Begin of  domU boot message---------------------------------
xen]# xm create domain1.xm -c
Using config file "domain1.xm".
Started domain domain1
Linux version 2.6.16-xen (root@xxxxxxxxxxxxxxxxxxxxx) (gcc version 3.4.6
20060404 (Red Hat 3.4.6-3)) #1 SMP Fri Sep 8 18:40:45 MST 2006
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000020000000 (usable)
0MB HIGHMEM available.
520MB LOWMEM available.
ACPI in unprivileged domain disabled
IRQ lockup detection disabled
Built 1 zonelists
Kernel command line:  ip=: root=/dev/sda1 ro 3
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Xen reported: 2666.662 MHz processor.
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Software IO TLB disabled
vmalloc area: e1000000-fb7fe000, maxmem 33ffe000
Memory: 514048k/532480k available (2250k kernel code, 9780k reserved,
data, 172k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Calibrating delay using timer specific routine.. 5334.98 BogoMIPS
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: L3 cache: 4096K
Checking 'hlt' instruction... OK.
Brought up 1 CPUs
Grant table initialized
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Subsystem revision 20060127
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
IA-32 Microcode Update Driver: v1.14-xen <tigran@xxxxxxxxxxx>
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
blkif_init: reqs=64, pages=704, mmap_vstart=0xdf800000
netfront: Initialising virtual ethernet driver.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with
Registering block device major 8
ide-floppy driver 0.99.newide
usbmon: debugfs is not available
usbcore: registered new driver libusual
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
Using IPI No-Shortcut mode
EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 172k freed
Warning: unable to open an initial console.

 ** WARNING: Currently emulating unsupported memory accesses  **
 **          in /lib/tls glibc libraries. The emulation is    **
 **          slow. To ensure full performance you should      **
 **          install a 'xen-friendly' (nosegneg) version of   **
 **          the library, or disable tls support by executing **
 **          the following as root:                           **
 **          mv /lib/tls /lib/tls.disabled                    **
 ** Offending process: init (pid=1)                           **


--End of domU boot message----------------------------------------

---Begin of my domU config file--------------------
kernel = "/boot/vmlinuz-2.6-xenU"
ramdisk = "/boot/initrd-2.6-xen.img"
memory = 512
name = "domain1"
extra = "3"
vif = [ 'bridge=xenbr0' ]
dhcp = "dhcp"
disk = ['phy:/dev/VG_Dom6_Linux/LogVol00,sda1,w' ]
root = "/dev/sda1 ro"

---End of my domU config file--------------------

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>