Re: [Xen-users] DomU boot problem in Xen 3.2 (Important)

[weiming <zephyr.zhao@xxxxxxxxx>]

1.  I can' remember exactly. Basically, I do
make prep-kernels KERNELS="linux-2.6-xen"
cd <build-linux-2.6.18-xen-...>
make menuconfig
make all 

In menuconfig, I just disable some unnecessary device drivers etc. No special tweaking.

2.
I use both xenU (more lightweight) and xen (works for both dom0 and domU). Both are ok.

3. I use separate partitions.

4. attached

Hope it helps!
Good Luck

Weiming

On Wed, Mar 5, 2008 at 10:34 AM, Dushmant Mohapatra <d_mpatra@xxxxxxxxx> wrote:

Hi,

Thanks for the reply. So could you pls provide me with a few details so that I can compare the steps:

1. What command did you use to compile the dom0 kernel? did u do the "make world and make install" or did you do
some configuration changes. If you did some  configuration changes can you list some  of the more important ones?

2. What kernel do you use to boot a domU? is it the same dom0  kernel or you prepared a separate one?

3. What file system and swap image do you use?  Any pointers  to the steps you followed for creating this?

4. Finally could you send me a copy of your xend config and domU config files for comparison?

Thanks
Dushmanta

 

----- Original Message ----
From: weiming <zephyr.zhao@xxxxxxxxx>
To: Dushmant Mohapatra <d_mpatra@xxxxxxxxx>
Sent: Wednesday, March 5, 2008 1:00:20 AM
Subject: Re: [Xen-users] DomU boot problem in Xen 3.2 (Important)

I installed on FC8  x86_64. Xen is built from source. No problem to boot domu.
try to set "extra=1" to see if it goes well.

On Wed, Mar 5, 2008 at 12:46 AM, Dushmant Mohapatra <d_mpatra@xxxxxxxxx> wrote:

Hello,

I am facing some problem in booting up a DomU in Xen 3.2 (Installed on top of a FC8-64bit).

I installed FC8 without virtualization and on top of that installed Xen 3.2 (compiled from source). I used "make world" and "make install" for my compilation.

After this my Dom0 boots up fine. But when I try to boot a domU using the same (dom 0)kernel (with the file system and swap image being Fedora 64 images obtained from Jailtime.org), the boot process continues for some time and then stops. I am including below the entire boot messages obtained on the console.
(The same file system and swap image worked properly with a Xen 3.1 Dom0 kernel).


So can any one tell me whats going wrong? Is some thing wrong with my compiled kernel? Did I miss some configuration due to "make world"?

Please reply. If some other information is needed I can provide that. But this is a bit urgent and I will really appreciate any help.

If any one was able to install a domU properly on a FC8 + Xen 3.2 configuration (without any external tools like virt-manager/virt-install) please let me know the procedure.

Regards
Dushmanta

<<<<<<<<<<<<<<
[root@dmcomp xen-domU]# xm create -c fedora.fc8.64.xen3.cfg
Using config file "./fedora.fc8.64.xen3.cfg".
Started domain fedora.fc8.64
                            Bootdata ok (command line is root=/dev/sda1 fastboot)
Linux version 2.6.18.8-xen (root@dmcomp) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Fri Feb 22 20:24:57 EST 2008
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000010800000 (usable)
No mptable found.
Built 1 zonelists.  Total pages: 66660
Kernel command line: root=/dev/sda1 fastboot
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 16384 bytes)
Xen reported: 1729.515 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB disabled
Memory: 242932k/270336k available (2015k kernel code, 19184k reserved, 882k data, 176k init)
Calibrating delay using timer specific routine.. 3460.36 BogoMIPS (lpj=17301823)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
SMP alternatives: switching to UP code
Freeing SMP alternatives: 24k freed
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 9684k freed
NET: Registered protocol family 16
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
PCI: System does not support PCI
PCI: System does not support PCI
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
IA-32 Microcode Update Driver: v1.14a-xen <tigran@xxxxxxxxxxx>
audit: initializing netlink socket (disabled)
audit(1204694388.919:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
Xen virtual console successfully installed as xvc0
Event-channel device installed.
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 idebus=xx
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 1
NET: Registered protocol family 17
xen-vbd: registered block device major 8
blkfront: sda1: barriers enabled
blkfront: sda2: barriers enabled
XENBUS: Device with no driver: device/console/0
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
Freeing unused kernel memory: 176k freed
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v3.0
SCSI subsystem initialized
register_blkdev: cannot get major 8 for sd
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@xxxxxxxxxx
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.

>>>>>>>>>>>>>>>>>

The config file I am using for booting domU is:

kernel = "/boot/vmlinuz-2.6.18.8-xen"
ramdisk = "/boot/initrd-2.6.18.8-xen.img"
memory = 256
name = "fedora.fc8.64"
vif = [ '' ]
#dhcp= "dhcp"
#disk = ['file:/xen/fedora/fedora.fc8.64.img,sda1,w', 'file:/xen/fedora/fedora.swap,sda2,w']
disk = ['file:/home/dmpatra/Xen_Downloads/xen-domU/fedora.fc8.64.img,sda1,w', 'file:/home/dmpatra/Xen_Downloads/xen-domU/fedora.swap,sda2,w']
root = "/dev/sda1"
extra = "fastboot"

---

Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

---

Looking for last minute shopping deals? Find them fast with Yahoo! Search.

xm1
Description: Binary data

xend-config.sxp
Description: Binary data

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users