Changing to xvda or sda doesn't fix anything, nor does only using one
block device.
Maybe I have some leftover cruft from a previous install or previous
debian package install... any suggestions as to the best place to start
looking?
Thanks
James
> -----Original Message-----
> From: Ian Pratt [mailto:m+Ian.Pratt@xxxxxxxxxxxx]
> Sent: Thursday, 1 December 2005 13:20
> To: James Harper; Xen-devel@xxxxxxxxxxxxxxxxxxx
> Cc: ian.pratt@xxxxxxxxxxxx; ian.pratt@xxxxxxxxxxxx
> Subject: RE: [Xen-devel] domU won't recognise my block devices
>
> > No initrd. AoE is only used by dom0. Boot messages follow:
>
> It works for me... Are you sure you haven't borked your config?
>
> Using 'sdX' or 'hdX' as the device to import a virtual disk as is
rather
> bad form these days anyhow. The preferred device is "xvdX". e.g.
> "xvda1"
>
> Please can you try this (rememmer to update you root= and guest
> /etc/fstab as well as the disk= stanza).
>
> [You could try sda1 instead of hda1 too. If that still doesn't work,
> have you tried importing a single device rather than two?]
>
> Ian
>
> > Using config file "mail2".
> > Started domain mail2
> > Linux version 2.6.12.6-xen (root@xxxxxxxxxxxxxxxxxxxx) (gcc version
> > 4.0.2 (Debian 4.0.2-2)) #1 SMP Wed Nov 30 19:24:27 EST 2005
> > BIOS-provided physical RAM map:
> > Xen: 0000000000000000 - 0000000008000000 (usable) 0MB
> > HIGHMEM available.
> > 136MB LOWMEM available.
> > ACPI in unprivileged domain disabled
> > IRQ lockup detection disabled
> > Built 1 zonelists
> > Kernel command line: root=/dev/hda1 ro 4 VMID=2
> > Initializing CPU#0 PID hash table entries: 1024 (order: 10,
> > 16384 bytes) Xen reported: 498.679 MHz processor.
> > Dentry cache hash table entries: 32768 (order: 5, 131072
> > bytes) Inode-cache hash table entries: 16384 (order: 4, 65536
> > bytes) Software IO TLB disabled vmalloc area:
> > c9000000-fb7fe000, maxmem 34000000
> > Memory: 125244k/139264k available (2228k kernel code, 5472k
> > reserved, 891k data, 192k init, 0k highmem) Checking if this
> > processor honours the WP bit even in supervisor mode...
> > Ok.
> > Security Framework v1.0.0 initialized
> > SELinux: Disabled at boot.
> > Capability LSM initialized
> > Mount-cache hash table entries: 512
> > CPU: L1 I cache: 16K, L1 D cache: 16K
> > CPU: L2 cache: 512K
> > Enabling fast FPU save and restore... done.
> > Enabling unmasked SIMD FPU exception support... done.
> > Checking 'hlt' instruction... disabled
> > Brought up 1 CPUs
> > NET: Registered protocol family 16
> > Enabling SMP...
> > Initializing CPU#1
> > Brought up 2 CPUs
> > ACPI: Subsystem revision 20050309
> > 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: Using ACPI for IRQ routing
> > PCI: If a device doesn't work, try "pci=routeirq". If it
> > helps, post a report
> > PCI: System does not support PCI
> > PCI: System does not support PCI
> > Grant table initialized
> > 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)
> > devfs: 2004-01-31 Richard Gooch (rgooch@xxxxxxxxxxxxx)
> > devfs: boot_options: 0x0
> > Initializing Cryptographic API
> > isapnp: Scanning for PnP cards...
> > isapnp: No Plug & Play device found
> > PNP: No PS/2 controller found. Probing ports directly.
> > i8042.c: No controller found.
> > io scheduler noop registered
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered
> > RAMDISK driver initialized: 16 RAM disks of 8192K size 1024
> > blocksize Xen virtual console successfully installed as tty1
> > Event-channel device installed.
> > netfront: Initialising virtual ethernet driver.
> > Registering block device major 3
> > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> > ide: Assuming 50MHz system bus speed for PIO modes; override
> > with idebus=xx ide-floppy driver 0.99.newide
> > mice: PS/2 mouse device common for all mice
> > NET: Registered protocol family 2
> > IP: routing cache hash table of 1024 buckets, 8Kbytes TCP
> > established hash table entries: 8192 (order: 4, 65536 bytes)
> > TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
> > TCP: Hash tables configured (established 8192 bind 8192)
> > NET: Registered protocol family 8
> > NET: Registered protocol family 20
> > VFS: Cannot open root device "hda1" or unknown-block(3,1)
> > Please append a correct "root=" boot option Kernel panic -
> > not syncing: VFS: Unable to mount root fs on
> > unknown-block(3,1)
> >
> >
> > > -----Original Message-----
> > > From: Ian Pratt [mailto:m+Ian.Pratt@xxxxxxxxxxxx]
> > > Sent: Thursday, 1 December 2005 12:35
> > > To: James Harper; Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > Cc: ian.pratt@xxxxxxxxxxxx
> > > Subject: RE: [Xen-devel] domU won't recognise my block devices
> > >
> > > > With the following in my config file:
> > > >
> > > > disk = [ 'phy:vg00/mail2-root,hda1,w',
> > 'phy:vg00/mail2-swap,hda2,w'
> > ]
> > > >
> > > > root = "/dev/hda1 ro"
> > > >
> > > > My domU says:
> > > >
> > > > VFS: Cannot open root device "hda1" or unknown-block(3,1)
> > > >
> > > > I am using a -xen kernel (not xen0 or xenU) with the as-shipped
> > > > config with the exception that I have AoE compiled as a module.
> > > >
> > > > Any suggestions?
> > >
> > > Please can you post the full boot messages from the domU.
> > Is the AoE
> > > module loaded (e.g. by an initrd?)
> > >
> > > Ian
> >
> >
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home