RE: [Xen-users] Problem booting Xen DomU images under Ubuntu Jaun ty (Dom0 working nicely)

[Guido Hecken <guido.hecken@xxxxxxxxxxxxx>]

Try changing disk statements from sda to hda.
I couldn't get any hvm to work with sda.

Here is an example of a working installation (hvm):
disk = [ 'phy:/dev/virt_vm_vg/centos_5_3_ast,hda,w' ]

Regards,

Guido


> -----Ursprüngliche Nachricht-----
> Von: Nicholas W [mailto:4407@xxxxxxxx] 
> Gesendet: Donnerstag, 14. Mai 2009 15:37
> An: Xen-users@xxxxxxxxxxxxxxxxxxx
> Betreff: [Xen-users] Problem booting Xen DomU images under 
> Ubuntu Jaunty (Dom0 working nicely)
> 
> Dear All,
>  I now have my Dom0 working nicely running Ubuntu Jaunty. I am now
> trying to boot Images I had been using without problem under my
> previous Xen installation (Gentoo). For the Dom0 host kernel I am
> using the debian package
> linux-image-2.6.26-2-xen-686_2.6.26-15_i386.deb. The DomU kernel is
> one I compiled myself a while ago (sometime last year and has always
> worked on Gentoo and I think even Centos)
> 
> 
> Unfortunately, there seems to be a problem with the DomU not
> recognizing the virtual disk image.
> 
> /etc/xen/ubuntu looks like this:
> 
> kernel = "/workarea/xen/kernels/vmlinuz"
> memory = 1024
> name = "ubuntu"
> vif = [ '' ]
> dhcp = "dhcp"
> disk = ['tap:aio:/workarea/xen/images/ubuntu.img,sda1,w',
>         'tap:aio:/workarea/xen/images/swapubuntu.img,sda2,w']
> root = "/dev/sda1 ro"
> 
> and the console output of the failed boot is like this:
> 
> Using config file "./ubuntu".
> Started domain ubuntu
>                      Linux version 2.6.21-xen (root@localhost) (gcc
> version 4.1.2 (Gentoo 4.1.2 p1.1)) #3 Mon Oct 13 16:05:59 CEST 2008
> BIOS-provided physical RAM map:
> sanitize start
> sanitize bail 0
> copy_e820_map() start: 0000000000000000 size: 0000000040800000 end:
> 0000000040800000 type: 1
>  Xen: 0000000000000000 - 0000000040800000 (usable)
> 304MB HIGHMEM available.
> 727MB LOWMEM available.
> NX (Execute Disable) protection: active
> Zone PFN ranges:
>   DMA             0 ->   186366
>   Normal     186366 ->   186366
>   HighMem    186366 ->   264192
> early_node_map[1] active PFN ranges
>     0:        0 ->   264192
> Detected 2992.570 MHz processor.
> Built 1 zonelists.  Total pages: 262129
> Kernel command line: root=/dev/sda1 ro ip=:127.0.255.255::::eth0:dhcp
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Initializing CPU#0
> PID hash table entries: 4096 (order: 12, 16384 bytes)
> Xen reported: 2992.576 MHz processor.
> Console: colour dummy device 80x25
> 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: ee000000-f53fe000, maxmem 2d7fe000
> Memory: 1032872k/1056768k available (2310k kernel code, 15028k
> reserved, 708k data, 168k init, 311304k highmem)
> virtual kernel memory layout:
>     fixmap  : 0xf56ed000 - 0xf57fe000   (1092 kB)
>     pkmap   : 0xf5400000 - 0xf5600000   (2048 kB)
>     vmalloc : 0xee000000 - 0xf53fe000   ( 115 MB)
>     lowmem  : 0xc0000000 - 0xed7fe000   ( 727 MB)
>       .init : 0xc03f6000 - 0xc0420000   ( 168 kB)
>       .data : 0xc0341b2d - 0xc03f2e98   ( 708 kB)
>       .text : 0xc0100000 - 0xc0341b2d   (2310 kB)
> Checking if this processor honours the WP bit even in 
> supervisor mode... Ok.
> Calibrating delay using timer specific routine.. 6026.31 
> BogoMIPS (lpj=3013157)
> Security Framework v1.0.0 initialized
> Mount-cache hash table entries: 512
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 2048K
> CPU: Intel Pentium 4 (Foster) stepping 03
> Checking 'hlt' instruction... OK.
> NET: Registered protocol family 16
> PCI: Fatal: No config space access function found
> PCI: setting up Xen PCI frontend stub
> Setting up standard PCI resources
> xen_mem: Initialising balloon driver.
> SCSI subsystem initialized
> PCI: System does not support PCI
> PCI: System does not support PCI
> 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: 6, 262144 bytes)
> TCP: Hash tables configured (established 131072 bind 65536)
> TCP reno registered
> highmem bounce pool size: 64 pages
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> SGI XFS with ACLs, security attributes, realtime, large block numbers,
> no debug enabled
> SGI XFS Quota Management subsystem
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> io scheduler deadline registered
> io scheduler cfq registered
> rtc: IRQ 8 is not free.
> Non-volatile memory driver v1.2
> Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is 
> unknown type 15 (usb?)
> Failed to obtain physical IRQ 6
> floppy0: no floppy controllers found
> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
> loop: loaded (max 8 devices)
> Xen virtual console successfully installed as tty1
> 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
> netfront: device eth0 has copying receive path.
> st: Version 20070203, fixed bufsize 32768, s/g segs 256
> i8042.c: No controller found.
> mice: PS/2 mouse device common for all mice
> md: linear personality registered for level -1
> md: raid0 personality registered for level 0
> md: raid1 personality registered for level 1
> md: raid10 personality registered for level 10
> md: multipath personality registered for level -4
> IPv4 over IPv4 tunneling driver
> TCP cubic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> NET: Registered protocol family 15
> Using IPI Shortcut mode
> XENBUS: Timeout connecting to device: device/vbd/2049 (state 3)
> XENBUS: Timeout connecting to device: device/vbd/2050 (state 3)
> XENBUS: Device with no driver: device/console/0
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> VFS: Cannot open root device "sda1" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on 
> unknown-block(0,0)
> 
> 
> Could anyone please give me some clues as to what might be happening.
> 
> Thanks so much for your help,
> Regards,
> Nicholas
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 

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