Re: [Xen-users] Problem restarting Guests

[David F Barrera <dfbp@xxxxxxxxxx>]

Ben,

I reported that problem a couple of days ago. There is a bugzilla defect
on it, http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=176


On Wed, 2005-08-24 at 17:31 +0530, benjamin wrote:
> 
> 
> On 8/24/05, Michael McCabe <mccabemt@xxxxxxxxx> wrote:
>         Hello
>         I'm running yesterday's unstable installation tarball on top
>         of FC4 and
>         I'm running into a problem when I reboot a guest.  When the
>         guest tries
>         to come back up it's unable to find sda1. Here's the
>         configuration file 
>         
>         kernel="/boot/vmlinuz-2.6-xenU"
>         memory="128"
>         name="web"
>         nics=1
>         disk=['phy:mapper/XenVolume-lvol3,sda1,w',
>         'phy:mapper/XenVolume-lvol4,sda2,w']
>         root="/dev/sda1 ro" 
>         
>         And here's the output from the console.
>         
>         Linux version 2.6.12-xenU (xenod@xxxxxxxxxxxxxxxxxxxxx) (gcc
>         version
>         3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 SMP Tue Aug 23
>         04:49:46 BST 
>         2005
>         BIOS-provided physical RAM map:
>         Xen: 0000000000000000 - 0000000008000000 (usable)
>         0MB HIGHMEM available.
>         128MB LOWMEM available.
>         DMI not present.
>         IRQ lockup detection disabled
>         Allocating PCI resources starting at 08000000 (gap:
>         08000000:f8000000) 
>         Built 1 zonelists
>         Kernel command line:  root=/dev/sda1 ro 3
>         Initializing CPU#0
>         PID hash table entries: 1024 (order: 10, 16384 bytes)
>         Xen reported: 1793.202 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 (1744k kernel code, 4484k
>         reserved,
>         555k 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: L1 I Cache: 64K (64 bytes/line), D cache 64K (64
>         bytes/line)
>         CPU: L2 Cache: 64K (64 bytes/line) 
>         Enabling fast FPU save and restore... done.
>         Enabling unmasked SIMD FPU exception support... done.
>         Checking 'hlt' instruction... disabled
>         CPU0: AMD Duron(tm) processor stepping 01
>         Total of 1 processors activated ( 3578.26 BogoMIPS).
>         Brought up 1 CPUs
>         NET: Registered protocol family 16
>         store_evtchn = 2
>         XENBUS xs_read_watch: 0
>         XENBUS xs_read_watch: 0
>         XENBUS xs_read_watch: 0
>         xen_mem: Initialising balloon driver.
>         XENBUS xs_read_watch: 0
>         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_blk: Timeout connecting to device! 
>         Netdev frontend (TX) is using grant tables.
>         Netdev frontend (RX) is using grant tables.
>         xen_net: Initialising virtual ethernet driver.
>         \uffff\uffff\uffff\uffff\uffff\uffffNET: 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
>         Root-NFS: No NFS server available, giving up.
>         VFS: Unable to mount root fs via NFS, trying floppy.
>         VFS: Cannot open root device "sda1" or unknown-block(2,0) 
>         Please append a correct "root=" boot option
>         Kernel panic - not syncing: VFS: Unable to mount root fs on
>         unknown-block(2,0)
>         
>         Thanks,
>         Mike
>         
>         
>         _______________________________________________ 
>         Xen-users mailing list
>         Xen-users@xxxxxxxxxxxxxxxxxxx
>         http://lists.xensource.com/xen-users
> 
> disk=['phy:mapper/XenVolume 
> -lvol3,sda1,w',
> 'phy:mapper/XenVolume-lvol4,sda2,w']
> 
> Try giving full path to the  disk file.
> 
> -- 
> benjamin rualthanzauva
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides


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