Re: [Xen-devel] More on domU not starting -- HELP

[Rob Gardner <rob.gardner@xxxxxx>]

Ryan Grimm wrote:

> I don't know what the desired behavior should be, but good point about 
> the two disk statements...i am able to now get the desired behavior by 
> using one like you suggested.
> mine now looks like:
>
> disk = [ 'phy:sda3,hda1,w', 'file:/path/to/image,hda1,w' ]
>
> so i dont need the /dev in front of sda3 after all...but i think that 
> if you export hda6 as hda6, you need to specify hda6 instead of sda1.  
> so i think your disk and root statements should be:
> disk = [ 'phy:hda6,hda6,w',
>          'file:/xen/disk-images/dom1.fs,hda6,w']
> root = "/dev/hda6 ro"

If you want to export a file to a domain, I don't think you need to also 
export the underlying raw disk to the domain. At least you never had to 
do that before.
Anyway, I tried this, and  it still does not fix my problem. No matter 
what I do, the domain does not see any virtual block device and so 
cannot boot. This must be due to some new behavior of some component. 
I've got an older installation of xen-unstable from Sep. 21 and it works 
fine with the identical config file.
Can anyone suggest a clue to this problem?????  Boot messages attached 
below.
Rob


[root@localhost xen]# xm create -f /xen/dom1-3.0 vmid=1 -c
Using config file "/xen/dom1-3.0".
Started domain Rob-VM1
Linux version 2.6.12-xenU (rdg@cordoba) (gcc version 3.2.2 20030222 (Red 
Hat Linux 3.2.2-5)) #1 SMP Wed Oct 12 09:37:41 MDT 2005
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000008000000 (usable)
0MB HIGHMEM available.
128MB LOWMEM available.
IRQ lockup detection disabled
Built 1 zonelists
Kernel command line:  
ip=15.6.247.101:1.2.3.4:15.6.247.1:255.255.255.0:vm1:eth0:off 
root=/dev/sda1 ro 4 VMID=1
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 16384 bytes)
Xen reported: 2660.168 MHz processor.
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
vmalloc area: c8800000-fb7fe000, maxmem 34000000
Memory: 126336k/131072k available (1771k kernel code, 4476k reserved, 
584k data, 140k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
CPU0: Intel(R) Pentium(R) 4 CPU 2.66GHz stepping 09
Total of 1 processors activated (5308.41 BogoMIPS).
Brought up 1 CPUs
NET: Registered protocol family 16
xen_mem: Initialising balloon driver.
Grant table initialized
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
xen_blk: Initialising virtual block device driver
xen_net: Initialising virtual ethernet driver.
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 8Kbytes
TCP established hash table entries: 8192 (order: 5, 131072 bytes)
TCP bind hash table entries: 8192 (order: 4, 98304 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
IP-Config: Complete:
     device=eth0, addr=15.6.247.101, mask=255.255.255.0, gw=15.6.247.1,
    host=vm1, domain=, nis-domain=(none),
    bootserver=1.2.3.4, rootserver=1.2.3.4, rootpath=
Looking up port of RPC 100003/2 on 1.2.3.4



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