I get the following error on the bootup sequence. Any clues? I can see
it picking up the serial ports, the kernel found the serial port for
it''s bootup. Maybe I"m beign stupid. 8-P
Kernel panic: Couldn''t register Xen virtual console driver as ttyS
Yeah, I noticed the double logging of the XenLinux messages. I''m
assumign that the XenLinux kernel is sending messages to both ttyS0 AND
the xenconsole. why, i''m not certain.
hardware: tyan dual P-III mainboard w/ 1 celeron 333A slot-1 cpu. 128MB
ram ide disk.
p.s. I''m nearly done with the debs of xen and XenLinux-builder scripts.
--------xen console log.
root (hd0,0)
Filesystem type is reiserfs, partition type 0x83
kernel /boot/xen.gz dom0_mem=65535 noht watchdog com1=115200,8n1
[Multiboot-elf, <0x100000:0x5d36c:0x34df4>, shtab=0x193078,
entry=0x100000]
module /boot/vmlinuz-2.6.7-dev-Xen0 root=/dev/hda1
console=ttyS0,115200,8n1
[Multiboot-module @ 0x194000, 0x252974 bytes]
boot
__ __ _ _____ _ _
\ \/ /___ _ __ / | |___ / __| | _____ _____| |
\ // _ \ ''_ \ | | |_ \ __ / _` |/ _ \ \ / / _ \ |
/ \ __/ | | | | |_ ___) |__| (_| | __/\ V / __/ |
/_/\_\___|_| |_| |_(_)____/ \__,_|\___| \_/ \___|_|
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 1.3-devel (root@office.terrabox.com) (gcc version 3.3.4
(Debian 1:3.3.4-9)) Fri Aug 20 12:56:10 CDT 2004
(XEN) Initialised 255MB memory (65520 pages) on a 255MB machine
(XEN) Xen heap size is 10668KB
(XEN) CPU0: Before vendor init, caps: 0183fbff 00000000 00000000, vendor
= 0
(XEN) CPU caps: 0183fbff 00000000 00000000 00000000
(XEN) found SMP MP-table at 000fb570
(XEN) Memory Reservation 0xfb570, 4096 bytes
(XEN) Memory Reservation 0xf6840, 4096 bytes
(XEN) Intel MultiProcessor Specification v1.1
(XEN) Virtual Wire compatibility mode.
(XEN) OEM ID: INTEL Product ID: 440GX APIC at: 0xFEE00000
(XEN) Processor #0 Pentium(tm) Pro APIC version 17
(XEN) I/O APIC #2 Version 17 at 0xFEC00000.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Processors: 1
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 334.101 MHz processor.
(XEN) CPU0: Before vendor init, caps: 0183fbff 00000000 00000000, vendor
= 0
(XEN) CPU caps: 0183fbff 00000000 00000000 00000000
(XEN) CPU0 booted
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 00000004
(XEN) ESR value after enabling vector: 00000000
(XEN) Error: only one processor found.
(XEN) ENABLING IO-APIC IRQs
(XEN) Setting 2 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 2 ... ok.
(XEN) init IO_APIC IRQs
(XEN) ..TIMER: vector=0x41 pin1=2 pin2=0
(XEN) Using local APIC timer interrupts.
(XEN) Calibrating APIC timer for CPU0...
(XEN) ..... CPU speed is 334.0925 MHz.
(XEN) ..... Bus speed is 66.8183 MHz.
(XEN) ..... bus_scale = 0x0000446D
(XEN) Time init:
(XEN) .... System Time: 20000945ns
(XEN) .... cpu_freq: 00000000:13E9FABC
(XEN) .... scale: 00000002:FE3C257F
(XEN) .... Wall Clock: 1093033463s 150000us
(XEN) Testing NMI watchdog --- CPU#0 okay.
(XEN) PCI: PCI BIOS revision 2.10 entry at 0xfdb81, last bus=1
(XEN) PCI: Using configuration type 1
(XEN) PCI: Probing PCI hardware
(XEN) PCI: Probing PCI hardware (bus 00)
(XEN) Limiting direct PCI/PCI transfers.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=1.3''
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Kernel image: 02800000->02a52974
(XEN) Initrd image: 00000000->00000000
(XEN) Dom0 alloc.: 02c00000->06c00000
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c038565c
(XEN) Init. ramdisk: c0386000->c0386000
(XEN) Phys-Mach map: c0386000->c0396000
(XEN) Page tables: c0396000->c0399000
(XEN) Start info: c0399000->c039a000
(XEN) Boot stack: c039a000->c039b000
(XEN) TOTAL: c0100000->c0800000
(XEN) ENTRY ADDRESS: c0100000
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch
input to Xen).
Linux version 2.6.7-dev-Xen0 (root@enigma) (gcc version 3.3.4 (Debian
1:3.3.4-9)) #2 Fri Aug 20 14:31:34 CDT 2004
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000004000000 (usable)
64MB LOWMEM available.
On node 0 totalpages: 16384
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 12288 pages, LIFO batch:3
HighMem zone: 0 pages, LIFO batch:1
DMI not present.
Built 1 zonelists
Kernel command line: /boot/vmlinuz-2.6.7-dev-Xen0 root=/dev/hda1
console=ttyS0,115200,8n1
Unknown boot option `/boot/vmlinuz-2.6.7-dev-Xen0'': ignoring
Initializing CPU#0
PID hash table entries: 512 (order 9: 4096 bytes)
Xen reported: 334.101 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Linux version 2.6.7-dev-Xen0 (root@enigma) (gcc version 3.3.4 (Debian
1:3.3.4-9)) #2 Fri Aug 20 14:31:34 CDT 2004
Linux version 2.6.7-dev-Xen0 (root@enigma) (gcc version 3.3.4 (Debian
1:3.3.4-9)) #2 Fri Aug 20 14:31:34 CDT 2004
BIOS-provided physical RAM map:
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000004000000 (usable)
Xen: 0000000000000000 - 0000000004000000 (usable)
64MB LOWMEM available.
64MB LOWMEM available.
On node 0 totalpages: 16384
On node 0 totalpages: 16384
DMA zone: 4096 pages, LIFO batch:1
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 12288 pages, LIFO batch:3
Normal zone: 12288 pages, LIFO batch:3
HighMem zone: 0 pages, LIFO batch:1
HighMem zone: 0 pages, LIFO batch:1
DMI not present.
DMI not present.
Built 1 zonelists
Built 1 zonelists
Kernel command line: /boot/vmlinuz-2.6.7-dev-Xen0 root=/dev/hda1
console=ttyS0,115200,8n1
Kernel command line: /boot/vmlinuz-2.6.7-dev-Xen0 root=/dev/hda1
console=ttyS0,115200,8n1
Unknown boot option `/boot/vmlinuz-2.6.7-dev-Xen0'': ignoring
Unknown boot option `/boot/vmlinuz-2.6.7-dev-Xen0'': ignoring
Initializing CPU#0
Initializing CPU#0
PID hash table entries: 512 (order 9: 4096 bytes)
PID hash table entries: 512 (order 9: 4096 bytes)
Xen reported: 334.101 MHz processor.
Xen reported: 334.101 MHz processor.
Using tsc for high-res timesource
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Console: colour VGA+ 80x25
Memory: 62156k/65536k available (1567k kernel code, 3284k reserved, 671k data,
108k init, 0k highmem)
Memory: 62156k/65536k available (1567k kernel code, 3284k reserved, 671k data,
108k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Checking if this processor honours the WP bit e
ven in supervisor mode... Ok.
Ok.
Calibrating delay loop... Calibrating delay loop... 666.82 BogoMIPS
666.82 BogoMIPS
Security Scaffold v1.0.0 initialized
Security Scaffold v1.0.0 initialized
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: L1 I cache: 16KCPU: L1 I cache: 16K, L1 D cache: 16K
, L1 D cache: 16K
CPU: L2 cache: 128K
CPU: L2 cache: 128K
CPU: CPU: Intel Intel Celeron (Mendocino)Celeron (Mendocino) stepping 00
stepping 00
Enabling fast FPU save and restore... Enabling fast FPU save and restore...
done.
done.
Checking ''hlt'' instruction... Checking ''hlt''
instruction... disabled
disabled
NET: Registered protocol family 16
NET: Registered protocol family 16
PCI: Using configuration type Xen
PCI: Using configuration type Xen
PCI: System does not support PCI
PCI: System does not support PCI
PCI: System does not support PCI
PCI: System does not support PCI
VFS: Disk quotas dquot_6.5.1
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
devfs: boot_options: 0x0
Initializing Cryptographic API
Initializing Cryptographic API
Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
ttyS0ttyS0 at at I/O 0x3f8I/O 0x3f8 (irq = 4) is a 16550A
(irq = 4) is a 16550A
ttyS1ttyS1 at at I/O 0x2f8I/O 0x2f8 (irq = 3) is a NS16550A
(irq = 3) is a NS16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
hda: IBM-DTLA-305040, hda: IBM-DTLA-305040, ATA DISK drive
ATA DISK drive
Using anticipatory io scheduler
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 128KiB
hda: max request size: 128KiB
hda: 80418240 sectors (41174 MB)hda: 80418240 sectors (41174 MB) w/380KiB Cache
w/380KiB Cache, CHS=65535/15/63, CHS=655
35/15/63
/dev/ide/host0/bus0/target0/lun0: /dev/ide/host0/bus0/target0/lun0: p1 p1 p2 p2
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
input: AT Translated Set 2 keyboard on isa0060/serio0
Kernel panic: Couldn''t register Xen virtual console driver as ttyS
Kernel panic: Couldn''t register Xen virtual console driver as ttyS
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brian Wolfe wrote:> I get the following error on the bootup sequence. Any clues? I can see > it picking up the serial ports, the kernel found the serial port for > it''s bootup. Maybe I"m beign stupid. 8-P > > Kernel panic: Couldn''t register Xen virtual console driver as ttyS > > > Yeah, I noticed the double logging of the XenLinux messages. I''m > assumign that the XenLinux kernel is sending messages to both ttyS0 AND > the xenconsole. why, i''m not certain. > > hardware: tyan dual P-III mainboard w/ 1 celeron 333A slot-1 cpu. 128MB > ram ide disk. > > p.s. I''m nearly done with the debs of xen and XenLinux-builder scripts. >> Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled > Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabledYou currently have to keep the 8250 driver disabled. Unfortunate, as it means you can''t get to real serial ports afaict, and it means that drivers like mwave just won''t work. - -- Mike Waychison Sun Microsystems, Inc. 1 (650) 352-5299 voice 1 (416) 202-8336 voice http://www.sun.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NOTICE: The opinions expressed in this email are held by me, and may not represent the views of Sun Microsystems, Inc. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBJmpfdQs4kOxk3/MRAoIeAJwJzoCOk5Qk+CkUUZc/9RjdWSQpYACbBSQV 0aBM7KKVNMQlCijv4Ks282I=gsCX -----END PGP SIGNATURE----- ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled > > Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled > > You currently have to keep the 8250 driver disabled. Unfortunate, as it > means you can''t get to real serial ports afaict, and it means that > drivers like mwave just won''t work.You''ve pointed out Brian''s problem, but the situation isn''t as bad as you think. If you want to have the domain access the serial port directly rather than going via Xen then: 1) *don''t* have a com1= entry on the Xen command line 2) Have "xencons=off" on the linux command line You can then configure the serial port however you like (though I haven''t tested it under 2.6). For most users, I think it makes more sense to have Xen own the serial port and for dom0 to send its output via the xencons driver registered on ttyS0. That way you get the ouput from both dom0 and Xen. Best, Ian ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Interesting. So if I use the serial port driver as a module, then I *should* be able to get to com2 while com1 is in use by xen as a serial console? On Fri, 2004-08-20 at 17:14, Ian Pratt wrote:> > > Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled > > > Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled > > > > You currently have to keep the 8250 driver disabled. Unfortunate, as it > > means you can''t get to real serial ports afaict, and it means that > > drivers like mwave just won''t work. > > You''ve pointed out Brian''s problem, but the situation isn''t as > bad as you think. > > If you want to have the domain access the serial port directly > rather than going via Xen then: > 1) *don''t* have a com1= entry on the Xen command line > 2) Have "xencons=off" on the linux command line > > You can then configure the serial port however you like (though I > haven''t tested it under 2.6). > > For most users, I think it makes more sense to have Xen own the > serial port and for dom0 to send its output via the xencons > driver registered on ttyS0. That way you get the ouput from both > dom0 and Xen. > > Best, > Ian > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> Interesting. So if I use the serial port driver as a module, then I > *should* be able to get to com2 while com1 is in use by xen as a serial > console?If you have xencons=off (or xencons=tty) then the xencons driver will not grab the ttyS major and the uart driver will be able to get it. However, Linux''s uart driver will likely poke around the hardware for both uarts even if only one device is actually ever being opened. I expect you''ll get away with this as Xen will just plough on using it regardless. The only problem could be if the uart driver barfs because it can''t grant the interrupt line for the port that Xen is using. Give it a go and let us know. Ian ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
I''m using the version pulled as of Aug 19th. When I switched the serial driver to module, it no longer gives me ANY indication of the bootup sequence of XenLinux, not with any console= setting. I think I have something farked in my config, so i''m going to re-copy the default config provided with xen instead of the merged debian config i''m using and see how it behaves. I''ll let you know once I get it working again. :) Thanks for the serial info. Brian On Sat, 2004-08-21 at 01:49, Ian Pratt wrote:> > Interesting. So if I use the serial port driver as a module, then I > > *should* be able to get to com2 while com1 is in use by xen as a serial > > console? > > If you have xencons=off (or xencons=tty) then the xencons driver > will not grab the ttyS major and the uart driver will be able to > get it. > > However, Linux''s uart driver will likely poke around the hardware > for both uarts even if only one device is actually ever being > opened. I expect you''ll get away with this as Xen will just > plough on using it regardless. The only problem could be if the > uart driver barfs because it can''t grant the interrupt line for > the port that Xen is using. > > Give it a go and let us know. > > Ian > > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
An update on my kernel config issues.... I copied the xen distro 2.6.7 Xen0 default config over and started enabling all of the options that come set in the debian kernel in order to acheive a complete port of the standard debian kernel config to xen. So far I have not run into the config option that caused the console issues. I''m fairly certain that with a bit of testing I can track down what triggered the console disapearance issues. And for the info on the debification of Xen and XenLinux kernels... I''m cleaning up the Makefile for XenLinux-Build script set for a release soon. The intent of this script set is make it easier to create tarball and/or deb (if you want RH, someone will have to port it to support rpms) packages of the resulting XenLinux kernels. Right now it only creates tarballs, alows you to specify config files to build from, applies the debified kernel patch of xen-sparse, and allows for easy configuration of a XenLinux kernel from multiple config targets, and creates tarballs of the kernel and modules. I anticipate having the last few glitches in the debian Xen packages cleaned out in 48 to 72 hours. If anyone wants bleeding edge, please let me know and i"ll send you the URL to the deb files. If you aren''t familiar with debian packaging, xen dependancies, etc, don''t bother asking for them. As I said, they are highly unstable. 8-P Anyways, back to getting this packaging system cleaned up better. :) On Sat, 2004-08-21 at 01:49, Ian Pratt wrote:> > Interesting. So if I use the serial port driver as a module, then I > > *should* be able to get to com2 while com1 is in use by xen as a serial > > console? > > If you have xencons=off (or xencons=tty) then the xencons driver > will not grab the ttyS major and the uart driver will be able to > get it. > > However, Linux''s uart driver will likely poke around the hardware > for both uarts even if only one device is actually ever being > opened. I expect you''ll get away with this as Xen will just > plough on using it regardless. The only problem could be if the > uart driver barfs because it can''t grant the interrupt line for > the port that Xen is using. > > Give it a go and let us know. > > Ian > > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel