WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] Problem with 3.0.3 tap:aio from xensource kernel image

To: "Gary W. Smith" <gary@xxxxxxxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Problem with 3.0.3 tap:aio from xensource kernel image
From: "Gary W. Smith" <gary@xxxxxxxxxxxxxxx>
Date: Mon, 15 Jan 2007 19:27:17 -0800
Delivery-date: Mon, 15 Jan 2007 19:27:20 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <57F9959B46E0FA4D8BA88AEDFBE5829024EF9D@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <57F9959B46E0FA4D8BA88AEDFBE5829024EF84@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <57F9959B46E0FA4D8BA88AEDFBE5829024EF9D@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acc0jWM9M9qIDgdWQWuclTIUGlnZGgEX5CAwAAwxcZA=
Thread-topic: [Xen-users] Problem with 3.0.3 tap:aio from xensource kernel image
I managed to get xvdN devices working.  Not sure what I did but they are
working.  But when I switch file from file: to tap:aio it still failes.

I get this error:

2007-01-15 19:12:20 xend 4975] DEBUG (blkif:24) exception looking up
device number for xvda1: [Errno 2] No such file or directory:
'/dev/xvda1'

Here is the config (note this is fedora 6 instance 4):

name           = 'fedora4'
memory         = '256'
disk           = [ 'file:/xen-build/fedora4/xen-D0.img,xvda1,w' ,
'file:/xen-build/fedora4/xen-swap.img,xvda2,w' ]
#disk           = [
'tap:aio:/xen/fedora4/xen-D0.img,sda1,w','tap:aio:/xen/fedora4/xen-swap.
img,sda2,w' ]
root           = '/dev/xvda1 ro'
vif            = [ 'mac=00:16:e6:CD:49:5B' ]
kernel         = '/xen/xen-3.0.4/boot/vmlinuz-2.6-xen'
#kernel         = '/boot/vmlinuz-2.6.18-1.2869.fc6xen'
on_reboot      = 'restart'
on_crash       = 'restart'
extras         = 'console=xvc0'

Any ideas?

Also, when I use the FC6 kernel the DomU just simply kernel panics.  But
if I use the xen provided 32bit PAE then it works, just not real well.


> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Gary W. Smith
> Sent: Monday, January 15, 2007 1:36 PM
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] Problem with 3.0.3 tap:aio from xensource
kernel
> image
> 
> Anyone have any ideas on this?
> 
> If I use the xensource kernel for DomU's (3.0.3 or 3.0.4) I can't use
> file tap:aio nor can I use xvdN drivers.
> 
> Gary Wayne Smith
> 
> > -----Original Message-----
> > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-
> > bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Gary W. Smith
> > Sent: Wednesday, January 10, 2007 12:00 AM
> > To: xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: [Xen-users] Problem with 3.0.3 tap:aio from xensource
kernel
> > image
> >
> > Hello,
> >
> > I've been playing around with the kernel image downloaded directly
> from
> > xensource.com.  It's
> > the 32bit PAE.  I can use 'file:/' in the config but if I use
> > 'tap:aio:/' in the config it gets a kernel panic.  I have also tried
> to
> > use the xvda instead of sda1 (with 'file:/') and I also get a kernel
> > panic.  It's the same as below but the last 3 lines contain this
> instead
> > of the long listing.
> >
> > Shouldn't the xensource kernel 3.0.3 support both tap:aio and xvda?
> >
> > 'file:/' and type xvda
> >
> > VFS: Cannot open root device "xdva" 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)
> >
> > 'tap:aio:/' and any type (sda1, xvda, etc).
> >
> >
> > Linux version 2.6.16.29-xen (shand@endor) (gcc version 3.4.4
20050314
> > (prerelease) (Debian 3.4.3-13)) #4 SMP Sun Oct 15 13:20:46 BST 2006
> > BIOS-provided physical RAM map:
> >  Xen: 0000000000000000 - 0000000010800000 (usable)
> > 0MB HIGHMEM available.
> > 264MB LOWMEM available.
> > NX (Execute Disable) protection: active
> > ACPI in unprivileged domain disabled
> > Built 1 zonelists
> > Kernel command line:  root=/dev/sda1 ro
> > Enabling fast FPU save and restore... done.
> > Enabling unmasked SIMD FPU exception support... done.
> > Initializing CPU#0
> > PID hash table entries: 2048 (order: 11, 32768 bytes)
> > Xen reported: 2211.328 MHz processor.
> > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
> > Software IO TLB disabled
> > vmalloc area: d1000000-f51fe000, maxmem 2d7fe000
> > Memory: 253824k/270336k available (1976k kernel code, 7988k
reserved,
> > 754k data, 192k init, 0k highmem)
> > Checking if this processor honours the WP bit even in supervisor
> mode...
> > Ok.
> > Calibrating delay using timer specific routine.. 4424.20 BogoMIPS
> > (lpj=22121005)
> > Security Framework v1.0.0 initialized
> > Capability LSM initialized
> > Mount-cache hash table entries: 512
> > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> > CPU: L2 Cache: 512K (64 bytes/line)
> > Checking 'hlt' instruction... OK.
> > Brought up 1 CPUs
> > migration_cost=0
> > Grant table initialized
> > NET: Registered protocol family 16
> > Brought up 1 CPUs
> > PCI: setting up Xen PCI frontend stub
> > ACPI: Subsystem revision 20060127
> > 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
> > IA-32 Microcode Update Driver: v1.14-xen <tigran@xxxxxxxxxxx>
> > audit: initializing netlink socket (disabled)
> > audit(1168415636.163:1): initialized
> > VFS: Disk quotas dquot_6.5.1
> > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> > Initializing Cryptographic API
> > io scheduler noop registered
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered (default)
> > PNP: No PS/2 controller found. Probing ports directly.
> > i8042.c: No controller found.
> > 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 16384K 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
> > 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 2
> > netfront: device eth0 has flipping receive path.
> > Registering block device major 8
> > IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
> > TCP established hash table entries: 16384 (order: 5, 131072 bytes)
> > TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
> > TCP: Hash tables configured (established 16384 bind 16384)
> > TCP reno registered
> > NET: Registered protocol family 1
> > NET: Registered protocol family 17
> > Using IPI No-Shortcut mode
> > md: Autodetecting RAID arrays.
> > md: autorun ...
> > md: ... autorun DONE.
> > WARNING: g.e. still in use!
> > WARNING: leaking g.e. and page still in use!
> > end_request: I/O error, dev sda1, sector 2
> > EXT2-fs: unable to read superblock
> > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(8,1)
> >
> >
> > _______________________________________________
> > 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

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

<Prev in Thread] Current Thread [Next in Thread>