Brian Wolfe
2004-Apr-03 21:53 UTC
[Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
First off, I''d like to say that Xen looks very promising. I have been trying to get xen to run on my machine for the last 4 days with only marginal sucess. I think I am having a hardware compatibility issue. I have tried the pre-compiled 1.2 tarball, and the nightly build tarball. Neither will work if I attempt to use more than 16MB of ram (dom0_mem=16384 works, dom0_mem=16385 crashes) I''m getting varying addresses for the xenolinux kernel oopses. Of course, this takes out the xen core kernel since dom0 is dying. If I boot with dom0_mem=16384, I can get a dom0 up and running. I can use it sucesfully with no errors, glitches, etc. I can compile on it (albeit painfully slowly due to swaping), so I know the core is stable. This is what I get if I try to launch a xen 1.2 dom1 instance. vhost1:~# xc_dom_create -Dip=10.10.10.162;vmid=1 Segmentation fault DOM0: Unable to handle kernel paging request at virtual address ecdc6944 DOM0: printing eip: DOM0: c000538e DOM0: *pde=00000000(00000000) DOM0: Oops: 0000 DOM0: CPU: 0 DOM0: EIP: 0819:[<c000538e>] Not tainted DOM0: EFLAGS: 00211297 DOM0: eax: ecdc6940 ebx: c1032348 ecx: fbff9000 edx: c036de3c DOM0: esi: ffffffff edi: c036de3c ebp: ecdc6940 esp: c036de28 DOM0: ds: 0821 es: 0821 ss: 0821 DOM0: Process python (pid: 238, stackpage=c036d000)<1> DOM0: Stack: c0019d48 c1032348 c036c000 c0019f8b c107e0a4 00000001 c036c000 ecdc6940 DOM0: 00000000 c1032348 0000007f 000000cd c107e0a4 c001a00a c1032348 c001b671 DOM0: c03778f4 0000007f c107e0a4 000000cd c0377840 c03778f4 c0454640 c0e31860 DOM0: Call Trace: [<c0019d48>] [<c0019f8b>] [<c001a00a>] [<c001b671>] [<c0016ea0>] DOM0: [<c0016cf8>] [<c00170fc>] [<c0074b48>] [<c00310d9>] [<c003ceca>] [<c0033df5>] DOM0: [<c003114d>] [<c006ea20>] DOM0: DOM0: <1>Unable to handle kernel paging request at virtual address ecdc6940 DOM0: printing eip: DOM0: c0019efc DOM0: *pde=00000000(00000000) DOM0: Oops: 0000 DOM0: CPU: 0 DOM0: EIP: 0819:[<c0019efc>] Not tainted DOM0: EFLAGS: 00211286 DOM0: eax: c1032348 ebx: c0112518 ecx: 00000020 edx: ffffffff DOM0: esi: ecdc6940 edi: 00001000 ebp: c0122e20 esp: c01eff4c DOM0: ds: 0821 es: 0821 ss: 0821 DOM0: Process rpciod (pid: 7, stackpage=c01ef000)<1> DOM0: Stack: c0123480 c1032348 c0058d3c c0377840 c0122ec4 c01fd518 c0bb5264 c0122f30 DOM0: 00000000 00000008 c0122e20 c01ee000 00000001 c00ea9ef c0122e20 00000000 DOM0: c01effbc 00000000 c036c000 00dcb000 00000008 c01367e8 c01ee000 00000001 DOM0: Call Trace: [<c0058d3c>] [<c00ea9ef>] [<c00eab8b>] [<c00eb181>] [<c00eb0d0>] DOM0: [<c006c94e>] [<c00eb0d0>] DOM0: 8-P This is what I am getting when I boot 1.3-nightly (as of 4-3-2004), It dies on the IDE chipset detection. (i''ll list the machine info at the end of this message.) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.4,XEN_VER=1.3'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Kernel image: 02800000->02995810 (XEN) Initrd image: 00000000->00000000 (XEN) Dom0 alloc.: 02c00000->03d94000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0000000->c01c97c4 (XEN) Init. ramdisk: c01ca000->c01ca000 (XEN) Phys-Mach map: c01ca000->c01ce650 (XEN) Page tables: c01cf000->c01d1000 (XEN) Start info: c01d1000->c01d2000 (XEN) Boot stack: c01d2000->c01d3000 (XEN) TOTAL: c0000000->c0400000 (XEN) ENTRY ADDRESS: c0000000 (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen). (XEN) Give DOM0 read access to all PCI devices Linux version 2.4.25-xen (xenod@labyrinth.cl.cam.ac.uk) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #2 Sat Apr 3 03:53:46 BST 2004 (XEN) spurious 8259A interrupt: IRQ7. On node 0 totalpages: 4500 zone(0): 4096 pages. zone(1): 404 pages. zone(2): 0 pages. Kernel command line: /xenolinux-1.3.gz root=/dev/nfs nfsroot=10.10.10.161:/xen/dom0 rw ip =10.10.10.160::10.10.10.1:255.255.255.0:vhost1:eth0:off console=xencons0 ignorebiostables noacpi Initializing CPU#0 Xen reported: 1852.117 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 18507.36 BogoMIPS Memory: 15916k/18000k available (1292k kernel code, 2084k reserved, 246k data, 60k init, 0k highmem) Dentry cache hash table entries: 4096 (order: 3, 32768 bytes) Inode cache hash table entries: 2048 (order: 2, 16384 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 8192 (order: 3, 32768 bytes) CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU: AMD Athlon(tm) XP 2500+ stepping 00 POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd Journalled Block Device driver loaded Installing knfsd (copyright (C) 1996 okir@monad.swb.de). Event-channel device installed. Xen virtual console successfully installed Successfully installed virtual firewall/router interface Starting Xen Balloon driver Detected PS/2 Mouse Port. pty: 256 Unix98 ptys configured Partition check: hda: hda1 hda2 hda3 Skipping partition check on cdrom /dev/hdb RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: loaded (max 8 devices) NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 512 bind 1024) IP-Config: Complete: device=eth0, addr=10.10.10.160, mask=255.255.255.0, gw=10.10.10.1, host=vhost1, domain=, nis-domain=(none), bootserver=255.255.255.255, rootserver=10.10.10.161, rootpathip_conntrack version 2.1 (125 buckets, 1000 max) - 292 bytes per conntrack ip_tables: (C) 2000-2002 Netfilter core team NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. Looking up port of RPC 100003/2 on 10.10.10.161 (XEN) *pde = 0027a063 (XEN) *pte = 00000000 (XEN) CPU: 0 (XEN) EIP: 0808:[<fc531b5b>] (XEN) EFLAGS: 00211217 (XEN) eax: fffa004e ebx: 0000d010 ecx: 0000000f edx: 0000d010 (XEN) esi: fc6ac120 edi: fffa0012 ebp: fc681140 esp: fc503ec0 (XEN) ds: 0810 es: 0810 fs: 0810 gs: 0810 ss: 0810 (XEN) Stack trace from ESP=fc503ec0: (XEN) 00000051 00000020 00201096 003e5562 0000d018 0000003c 0000d000 fc681000 (XEN) 00000000 0000e011 00000020 [fc531360] fc681000 fc62be40 00000001 00201016 (XEN) 00000011 00000001 00000000 00000000 0000d00e 0000d000 fc681140 fc67ca20 (XEN) 00000000 00000011 fc62f640 [fc5e2424] 00000011 fc681000 fc503f60 fc629cc0 (XEN) 1173b3af fc67ca20 00000000 fc629cc0 00000000 fc629cc0 00000000 [fc5df4e0] (XEN) fc629cc0 00000000 00001ffc 00000000 fc629cc0 00000000 00000000 00000810 (XEN) 00000810 00000810 00000810 ffffff11 [fc5e7f2c] 00000808 00201246 c0182000 (XEN) c0182000 [fc513385] fc503fb8 00000001 fc69c040 [fc5e7eb0] 00000001 d21bbb00 (XEN) 98e34b00 c0182000 c0182000 c0182000 00000008 00000821 00000821 00000821 (XEN) 00000821 00000008 c00abd25 00000819 00201246 c0183fd8 00000821 fc629cc0 **************************************** CPU0 FATAL PAGE FAULT [error_code=00000002] Faulting linear address might be fffa0012 Aieee! CPU0 is toast... **************************************** Reboot in five seconds... Now, this machine has been used for aprox 5 months now without any glitches or oopses. So i''m 99.9999% certain that the hardware is good. I''m using an NFS root since the ide is only in pio mode (and to eliminate it''s use toher than to boot the kernels). Any insights? If necessary for debuging, I can provide access to the hardware via serial console. :) Thanks for any help yall can give! ====== My standard CPU and system info from running stock bf24 kernel from Debian 3.0r2==== processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 10 model name : AMD Athlon(tm) XP 2500+ stepping : 0 cpu MHz : 1852.080 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow bogomips : 3696.23 vhost1:/proc# free total used free shared buffers cached Mem: 900080 34680 865400 0 2152 21544 -/+ buffers/cache: 10984 889096 Swap: 499960 0 499960 Disk /dev/hda: 60.0 GB, 60022480896 bytes 16 heads, 63 sectors/track, 116301 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System /dev/hda1 1 496 249952+ 83 Linux /dev/hda2 497 1488 499968 82 Linux swap /dev/hda3 1489 9425 4000248 83 Linux v vhost1:~# cat /proc/interrupts CPU0 0: 139522 IO-APIC-edge timer 1: 2 IO-APIC-edge keyboard 2: 0 XT-PIC cascade 4: 351 IO-APIC-edge serial 8: 4 IO-APIC-edge rtc 14: 53292 IO-APIC-edge ide0 17: 20 IO-APIC-level eth1 23: 11 IO-APIC-level eth0 NMI: 0 LOC: 139463 ERR: 0 MIS: 0 vhost1:~# cat /proc/ioports 0000-001f : dma1 0020-003f : pic1 0040-005f : timer 0060-006f : keyboard 0070-007f : rtc 0080-008f : dma page reg 00a0-00bf : pic2 00c0-00df : dma2 00f0-00ff : fpu 01f0-01f7 : ide0 03c0-03df : vga+ 03f6-03f6 : ide0 03f8-03ff : serial(set) 0cf8-0cff : PCI conf1 d000-d01f : 3Com Corporation 3c595 100BaseTX [Vortex] d000-d01f : 00:09.0 e000-e00f : VIA Technologies, Inc. Bus Master IDE e400-e4ff : VIA Technologies, Inc. Ethernet Controller e400-e4ff : via-rhine vhost1:/proc# cat iomem 00000000-0009f7ff : System RAM 0009f800-0009ffff : reserved 000a0000-000bffff : Video RAM area 000c0000-000c7fff : Video ROM 000f0000-000fffff : System ROM 00100000-3feeffff : System RAM 00100000-002bdc69 : Kernel code 002bdc6a-00347183 : Kernel data 3fef0000-3fef2fff : ACPI Non-volatile Storage 3fef3000-3fefffff : ACPI Tables d0000000-d7ffffff : PCI device 1106:3189 (VIA Technologies, Inc.) d8000000-d9ffffff : PCI Bus #01 d8000000-d9ffffff : nVidia Corporation Riva TnT2 [NV5] da000000-dbffffff : PCI Bus #01 da000000-daffffff : nVidia Corporation Riva TnT2 [NV5] dd001000-dd0010ff : VIA Technologies, Inc. Ethernet Controller dd001000-dd0010ff : via-rhine fec00000-fec00fff : reserved fee00000-fee00fff : reserved ffff0000-ffffffff : reserved vhost1:~# uname -a Linux vhost1 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 GNU/Linux Debian - Unstable. (updated 4-2-2004) --- dmesg from debian bootup for reference info.--- Linux version 2.4.18-bf2.4 (root@zombie) (gcc version 2.95.4 20011002 (Debian pr erelease)) #1 Son Apr 14 09:53:28 CEST 2002 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f800 (usable) BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000003fef0000 (usable) BIOS-e820: 000000003fef0000 - 000000003fef3000 (ACPI NVS) BIOS-e820: 000000003fef3000 - 000000003ff00000 (ACPI data) BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved) Warning only 896MB will be used. Use a HIGHMEM enabled kernel. found SMP MP-table at 000f60c0 hm, page 000f6000 reserved twice. hm, page 000f7000 reserved twice. hm, page 000f0000 reserved twice. hm, page 000f1000 reserved twice. On node 0 totalpages: 229376 zone(0): 4096 pages. zone(1): 225280 pages. zone(2): 0 pages. Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000 Processor #0 Pentium(tm) Pro APIC version 17 I/O APIC #2 Version 17 at 0xFEC00000. Processors: 1 Kernel command line: root=/dev/hda3 ro console=ttyS0,115200,8n1 Initializing CPU#0 Detected 1852.080 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 3696.23 BogoMIPS Memory: 899800k/917504k available (1783k kernel code, 17316k reserved, 549k data , 280k init, 0k highmem) Dentry-cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Mount-cache hash table entries: 16384 (order: 5, 131072 bytes) Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes) Page-cache hash table entries: 262144 (order: 8, 1048576 bytes) CPU: Before vendor init, caps: 0383fbff c1c3fbff 00000000, vendor = 2 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU: After vendor init, caps: 0383fbff c1c3fbff 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After generic, caps: 0383fbff c1c3fbff 00000000 00000000 CPU: Common caps: 0383fbff c1c3fbff 00000000 00000000 CPU: AMD Athlon(tm) XP 2500+ stepping 00 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking ''hlt'' instruction... OK. Checking for popad bug... OK. POSIX conformance testing by UNIFIX enabled ExtINT on CPU#0 ESR value before enabling vector: 00000000 ESR value after enabling vector: 00000000 ENABLING IO-APIC IRQs Setting 2 in the phys_id_present_map ...changing IO-APIC physical APIC ID to 2 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-10, 2-11, 2-16, 2-18, 2-19, 2-20, 2-21, 2-22 not co nnected. ..TIMER: vector=0x31 pin1=2 pin2=0 number of MP IRQ sources: 16. number of IO-APIC #2 registers: 24. testing the IO APIC....................... IO APIC #2...... .... register #00: 02000000 ....... : physical APIC id: 02 .... register #01: 00178003 ....... : max redirection entries: 0017 ....... : PRQ implemented: 1 ....... : IO APIC version: 0003 WARNING: unexpected IO-APIC, please mail to linux-smp@vger.kernel.org .... IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 1 0 0 0 0 0 0 00 01 001 01 0 0 0 0 0 1 1 39 02 001 01 0 0 0 0 0 1 1 31 03 001 01 0 0 0 0 0 1 1 41 04 001 01 0 0 0 0 0 1 1 49 05 001 01 0 0 0 0 0 1 1 51 06 001 01 0 0 0 0 0 1 1 59 07 001 01 0 0 0 0 0 1 1 61 08 001 01 0 0 0 0 0 1 1 69 09 001 01 0 0 0 0 0 1 1 71 0a 000 00 1 0 0 0 0 0 0 00 0b 000 00 1 0 0 0 0 0 0 00 0c 001 01 0 0 0 0 0 1 1 79 0d 001 01 0 0 0 0 0 1 1 81 0e 001 01 0 0 0 0 0 1 1 89 0f 001 01 0 0 0 0 0 1 1 91 10 000 00 1 0 0 0 0 0 0 00 11 001 01 1 1 0 1 0 1 1 99 12 000 00 1 0 0 0 0 0 0 00 13 000 00 1 0 0 0 0 0 0 00 14 000 00 1 0 0 0 0 0 0 00 15 000 00 1 0 0 0 0 0 0 00 16 000 00 1 0 0 0 0 0 0 00 17 001 01 1 1 0 1 0 1 1 A1 IRQ to pin mappings: IRQ0 -> 0:2 IRQ1 -> 0:1 IRQ3 -> 0:3 IRQ4 -> 0:4 IRQ5 -> 0:5 IRQ6 -> 0:6 IRQ7 -> 0:7 IRQ8 -> 0:8 IRQ9 -> 0:9 IRQ12 -> 0:12 IRQ13 -> 0:13 IRQ14 -> 0:14 IRQ15 -> 0:15 IRQ17 -> 0:17 IRQ23 -> 0:23 .................................... done. Using local APIC timer interrupts. calibrating APIC timer ... ..... CPU clock speed is 1851.9610 MHz. ..... host bus clock speed is 336.7201 MHz. cpu: 0, clocks: 3367201, slice: 1683600 CPU0<T0:3367200,T1:1683600,D:0,S:1683600,C:3367201> mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au) mtrr: detected mtrr type: Intel PCI: PCI BIOS revision 2.10 entry at 0xfb8d0, last bus=1 PCI: Using configuration type 1 PCI: Probing PCI hardware Unknown bridge resource 0: assuming transparent PCI: Using IRQ router VIA [1106/3177] at 00:11.0 PCI->APIC IRQ transform: (B0,I9,P0) -> 17 PCI->APIC IRQ transform: (B0,I18,P0) -> 23 Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd VFS: Diskquotas version dquot_6.4.0 initialized Journalled Block Device driver loaded vga16fb: initializing vga16fb: mapped to 0xc00a0000 Console: switching to colour frame buffer device 80x30 fb0: VGA16 VGA frame buffer device Detected PS/2 Mouse Port. pty: 256 Unix98 ptys configured Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI en abled ttyS00 at 0x03f8 (irq = 4) is a 16550A Real Time Clock Driver v1.10e block: 128 slots per queue, batch=32 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 89 PCI: No IRQ known for interrupt pin A of device 00:11.1. Probably buggy MP table . VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later VP_IDE: Unknown VIA SouthBridge, contact Vojtech Pavlik <vojtech@suse.cz> hda: ST360021A, ATA DISK drive hdb: TOSHIBA CD-ROM XM-5602B, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide0: probed IRQ 14 failed, using default. hda: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=7297/255/63 hdb: ATAPI 8X CD-ROM drive, 256kB Cache Uniform CD-ROM driver Revision: 3.12 ide-floppy driver 0.97.sv Partition check: hda: hda1 hda2 hda3 floppy0: no floppy controllers found Loading I2O Core - (c) Copyright 1999 Red Hat Software I2O configuration manager v 0.04. (C) Copyright 1999 Red Hat Software loop: loaded (max 8 devices) Compaq CISS Driver (v 2.4.5) HDLC support module revision 1.02 for Linux 2.4 Cronyx Ltd, Synchronous PPP and CISCO HDLC (c) 1994 Linux port (c) 1998 Building Number Three Ltd & Jan "Yenya" Kasprzak. ide-floppy driver 0.97.sv Promise Fasttrak(tm) Softwareraid driver 0.03beta: No raid array found Highpoint HPT370 Softwareraid driver for linux version 0.01 No raid array found SCSI subsystem driver Revision: 1.00 Red Hat/Adaptec aacraid driver, Apr 14 2002 DC390: 0 adapters found 3ware Storage Controller device driver for Linux v1.02.00.016. 3w-xxxx: No cards with valid units found. request_module[scsi_hostadapter]: Root fs not mounted request_module[scsi_hostadapter]: Root fs not mounted i2o_scsi.c: Version 0.0.1 chain_pool: 0 bytes @ c1e0ecc0 (512 byte buffers X 4 can_queue X 0 i2o controllers) NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 8192 buckets, 64Kbytes TCP: Hash tables configured (established 262144 bind 65536) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 280k freed Adding Swap: 499960k swap-space (priority -1) EXT3 FS 2.4-0.9.17, 10 Jan 2002 on ide0(3,3), internal journal via-rhine.c:v1.10-LK1.1.13 Nov-17-2001 Written by Donald Becker http://www.scyld.com/network/via-rhine.html eth0: VIA VT6102 Rhine-II at 0xe400, 00:50:8d:4f:33:d7, IRQ 23. eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1. 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html 00:09.0: 3Com PCI 3c595 Vortex 100baseTx at 0xd000. Vers LK1.1.16 00:09.0: Overriding PCI latency timer (CFLT) setting of 32, new value is 248. eth0: Setting full-duplex based on MII #1 link partner capability of 45e1. -- Brian Wolfe | Phone 1-(214)-764-1204 President, | Email brianw@terrabox.com TerraBox.com Inc. | pub 1024D/73C5A2DF 2003-03-18 Brian Wolfe <brianw@terrabox.com> Key fingerprint = 050E 5E3C CF65 4C1E A183 F48F E3E3 5B22 73C5 A2DF sub 1024g/BB87A3DD 2003-03-18 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Keir Fraser
2004-Apr-04 08:05 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
> Now, this machine has been used for aprox 5 months now without any > glitches or oopses. So i''m 99.9999% certain that the hardware is good. > > I''m using an NFS root since the ide is only in pio mode (and to eliminate > it''s use toher than to boot the kernels). > > Any insights? > > If necessary for debuging, I can provide access to the hardware via serial > console. :) > > Thanks for any help yall can give!The crashes look quite random -- I don''t think this is a bug in the core of Xen. The two most likely possibilities are that you have duff memory or that a misconfigured device is trashing memory. I definitely wouldn''t discount the former, even though native x86 Linux has been running okay -- crashes can be very sensitive to memory layout. It might be worth running a few rounds of memtest on the machine, or swapping the memory, or trying to boot Xen on another identical box. If that doesn''t cure it then try swapping out or disabling hardware. For example, boot off local disc and disable networking (''ifname=dummy''). Since the cause is most likely hardware-related, the best approach is to isolate the problem hardware. -- Keir PS. If you build your own Xen/Xenolinux then keep the build trees around (or at least, for Xenolinux, the ''vmlinux'' file). I can''t find suitable image files for the tarballs on the Xen website, and without them it is very difficult to determine anything from crash dumps. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Ian Pratt
2004-Apr-04 08:34 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
> First off, I''d like to say that Xen looks very promising. > > I have been trying to get xen to run on my machine for the last 4 days > with only marginal sucess. > > I think I am having a hardware compatibility issue. I have tried the > pre-compiled 1.2 tarball, and the nightly build tarball. Neither will work > if I attempt to use more than 16MB of ram (dom0_mem=16384 works, > dom0_mem=16385 crashes)I think its best to try and understand this before looking at the crashes when starting new domains. Running memtest is a good idea because your stock Debian boot isn''t actually exercising all of memory as its a non HIGHMEM kernel on a 1GB machine, hence the top 100MB or so never gets used. Also, it would be useful to see the full output of Xen/dom0 booting. The memory detection happens early on, and its just possible that the BIOS table parsing is failing (The Debian linux kernel grumbles about pages being reserved twice). Ian ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Brian Wolfe
2004-Apr-04 19:23 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
Bad memory is what I also thought the first time it failed to run. It certainly LOOKS like a case of bad ram. However the unknown ACPI boot message has given me memory faults on other mainboards in the past year or so when using Athlon XP 1900+ and 2000+ cpus. That and the hardware''s history of use makes me think that it is ok. I''ll go ahead and run memtest on it for a few hours to see if it finds anything and report back the results once I have completed the hardware testing. I will also try swapping out the memory in my new workstation and see if that affects it any. Workstation ram: 2 pcs. Micron pc2100 512MB, using it right now under 2.6.4 (Linux enigma 2.6.4-1-k7 #1 Sat Mar 13 22:44:25 EST 2004 i686 GNU/Linux) Debian unstable. Xen server: 1 pc. 512MB pc2100 Micron, 2 pcs. 256M Micron pc2100. I hope it is as simple as the system doesn''t liek the memory that is in it I have attempted boting from IDE and nfsroot with the IDE turned off. There is one item during the xen-1.2 bootup with the debian xen package that I did notice. Note the "unknown apic" line where it attempts to initialize the ACPI hardware. I don''t know if this can be a source fo the issue. This mesage has given me grief in other systems with similar effects as this until I custom compiled a newer 2.6 kernel that supported the APIC natively. The stock debian 2.4 kernel also seems to have issues with the io APIC. This is why I compiled custom 2.6 kernels which found the APIC and used it ok. This is also what was leading me to believe that the Via chipset may be behaving in a way that Xen isn''t expecting and that the Linux 2.4 and 2.6 kernels are avoiding triggering. Maybe Xen pokes around in different ways/areas than the linux kernel did and has found some bad ram and/or APIC flaw that I just never ran into with Linux by sheer chance. The following is a full dump of the system booting up under xen-1.2 with 18m for domain0 as compild by Adam (doogie) for Debian unstable. It loads grub, xen, and xenolinux from hda1. Root is loaded from the nfsroot fileserver. For some reason using 18000 works as well as using < 16384, but memory sizes between 16M and 18m fail, as does anything over 18m. BTW, just smack me if I provide too much and/or the wrong info that yall need. :) ------- bootup dump of Debian xen.deb, 1.2 version. ----- root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen.gz dom0_mem=18000 ser_baud=115200 noht watchdog [Multiboot-elf, <0x100000:0x11a138:0x0>, <0x21c000:0x1f4f8:0x29528>, shtab=0 x265280, entry=0x100000] module /xenolinux.gz root=/dev/nfs nfsroot=10.10.10.161:/xen/dom0 rw ip=10.10.1 0.160::10.10.10.1:255.255.255.0:vhost1:eth0:off console=xencons0 [Multiboot-module @ 0x286000, 0x12f8cc bytes] __ __ _ ____ \ \/ /___ _ __ / | |___ \ \ // _ \ ''_ \ | | __) | / \ __/ | | | | |_ / __/ /_/\_\___|_| |_| |_(_)_____| http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 1.2 (root@private.brainfood.com) (gcc version 3.3.3 (Debian)) Thu M ar 4 12:56:20 CST 2004 Initialised all memory on a 1022MB machine Reading BIOS drive-info tables at 0xf95f0 and 0xfe819 CPU0: Before vendor init, caps: 0383fbff c1c3fbff 00000000, vendor = 2 CPU caps: 0383fbff c1c3fbff 00000000 00000000 found SMP MP-table at 000f60c0 Memory Reservation 0xf60c0, 4096 bytes Memory Reservation 0xf0c00, 4096 bytes ACPI: Searched entire block, no RSDP was found. ACPI: RSDP located at physical address fc4f7ac0 RSD PTR v0 [KT600 ] __va_range(0x3fef3000, 0x68): idx=8 mapped at ffff6000 ACPI table found: RSDT v1 [KT600 AWRDACPI 16944.11825] __va_range(0x3fef3040, 0x24): idx=8 mapped at ffff6000 __va_range(0x3fef3040, 0x74): idx=8 mapped at ffff6000 ACPI table found: FACP v1 [KT600 AWRDACPI 16944.11825] __va_range(0x3fef7a00, 0x24): idx=8 mapped at ffff6000 __va_range(0x3fef7a00, 0x5a): idx=8 mapped at ffff6000 ACPI table found: APIC v1 [KT600 AWRDACPI 16944.11825] __va_range(0x3fef7a00, 0x5a): idx=8 mapped at ffff6000 LAPIC (acpi_id[0x0000] id[0x0] enabled[1]) CPU 0 (0x0000) enabledProcessor #0 Pentium(tm) Pro APIC version 16 IOAPIC (id[0x2] address[0xfec00000] global_irq_base[0x0]) INT_SRC_OVR (bus[0] irq[0x0] global_irq[0x2] polarity[0x0] trigger[0x0]) INT_SRC_OVR (bus[0] irq[0x9] global_irq[0x9] polarity[0x0] trigger[0x0]) LAPIC_NMI (acpi_id[0x0000] polarity[0x1] trigger[0x1] lint[0x1]) 1 CPUs total Local APIC address fee00000 Enabling the CPU''s according to the ACPI table Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000 Processor #0 Pentium(tm) Pro APIC version 17 I/O APIC #2 Version 17 at 0xFEC00000. Enabling APIC mode: Flat.Using 1 I/O APICs Processors: 2 Initialising domains Initialising schedulers Initializing CPU#0 Detected 1852.069 MHz processor. CPU0: Before vendor init, caps: 0383fbff c1c3fbff 00000000, vendor = 2 CPU caps: 0383fbff c1c3fbff 00000000 00000000 CPU0 booted enabled ExtINT on CPU#0 ESR value before enabling vector: 00000000 ESR value after enabling vector: 00000000 Error: only one processor found. ENABLING IO-APIC IRQs Setting 2 in the phys_id_present_map ...changing IO-APIC physical APIC ID to 2 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-10, 2-11, 2-16, 2-18, 2-19, 2-20, 2-21, 2-22 not co nnected. ..TIMER: vector=0x41 pin1=2 pin2=0 number of MP IRQ sources: 16. number of IO-APIC #2 registers: 24. testing the IO APIC....................... IO APIC #2...... .... register #00: 02000000 ....... : physical APIC id: 02 .... register #01: 00178003 ....... : max redirection entries: 0017 ....... : PRQ implemented: 1 ....... : IO APIC version: 0003 An unexpected IO-APIC was found. If this kernel release is less than three months old please report this to linux-smp@vger.kernel.org .... IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 1 0 0 0 0 0 0 00 01 0FF 0F 0 0 0 0 0 1 1 49 02 001 01 0 0 0 0 0 1 1 41 03 0FF 0F 0 0 0 0 0 1 1 51 04 0FF 0F 0 0 0 0 0 1 1 59 05 0FF 0F 0 0 0 0 0 1 1 61 06 0FF 0F 0 0 0 0 0 1 1 69 07 0FF 0F 0 0 0 0 0 1 1 71 08 0FF 0F 0 0 0 0 0 1 1 79 09 0FF 0F 0 0 0 0 0 1 1 81 0a 000 00 1 0 0 0 0 0 0 00 0b 000 00 1 0 0 0 0 0 0 00 0c 0FF 0F 0 0 0 0 0 1 1 89 0d 0FF 0F 0 0 0 0 0 1 1 91 0e 0FF 0F 0 0 0 0 0 1 1 99 0f 0FF 0F 0 0 0 0 0 1 1 A1 10 000 00 1 0 0 0 0 0 0 00 11 0FF 0F 1 1 0 1 0 1 1 A9 12 000 00 1 0 0 0 0 0 0 00 13 000 00 1 0 0 0 0 0 0 00 14 000 00 1 0 0 0 0 0 0 00 15 000 00 1 0 0 0 0 0 0 00 16 000 00 1 0 0 0 0 0 0 00 17 0FF 0F 1 1 0 1 0 1 1 B1 IRQ to pin mappings: IRQ0 -> 0:2 IRQ1 -> 0:1 IRQ3 -> 0:3 IRQ4 -> 0:4 IRQ5 -> 0:5 IRQ6 -> 0:6 IRQ7 -> 0:7 IRQ8 -> 0:8 IRQ9 -> 0:9 IRQ12 -> 0:12 IRQ13 -> 0:13 IRQ14 -> 0:14 IRQ15 -> 0:15 IRQ17 -> 0:17 IRQ23 -> 0:23 .................................... done. Using local APIC timer interrupts. Calibrating APIC timer for CPU0... ..... CPU speed is 1852.1073 MHz. ..... Bus speed is 336.7467 MHz. ..... bus_scale = 0x000158E5 ACT: Initialising Accurate timers Time init: .... System Time: 11615885ns .... cpu_freq: 00000000:6E645690 .... scale: 00000001:14728FC3 .... Wall Clock: 1081028483s 0us Start schedulers Testing NMI watchdog --- CPU#0 okay. PCI: PCI BIOS revision 2.10 entry at 0xfb8d0, last bus=1 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Using IRQ router VIA [1106/3177] at 00:11.0 PCI->APIC IRQ transform: (B0,I9,P0) -> 17 PCI->APIC IRQ transform: (B0,I18,P0) -> 23 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html 00:09.0: 3Com PCI 3c595 Vortex 100baseTx at 0xd000. Vers LK1.1.16 00:09.0: Overriding PCI latency timer (CFLT) setting of 32, new value is 248. Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 89 VP_IDE: detected chipset, but driver not compiled in! PCI: No IRQ known for interrupt pin A of device 00:11.1. Probably buggy MP table . VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:pio, hdd:pio hda: ST360021A, ATA DISK drive hdb: TOSHIBA CD-ROM XM-5602B, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hdb: ATAPI 8X CD-ROM drive, 256kB Cache Uniform CD-ROM driver Revision: 3.12 hda: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=7297/255/63 PIO (slow!) SCSI subsystem driver Revision: 1.00 Red Hat/Adaptec aacraid driver (1.1.2 Mar 4 2004 12:55:28) Device eth0 opened and ready for use. DOM0: Guest OS virtual load address is c0000000 DOM0: xen_console_init DOM0: Linux version 2.4.25-xeno-p2 (adam@gradall) (gcc version 3.3.3 (Debian)) # 1 Thu Mar 4 12:49:07 CST 2004 DOM0: On node 0 totalpages: 4500 DOM0: zone(0): 4096 pages. DOM0: zone(1): 404 pages. DOM0: zone(2): 0 pages. DOM0: Kernel command line: /xenolinux.gz root=/dev/nfs nfsroot=10.10.10.161:/xen /dom0 rw ip=10.10.10.160::10.10.10.1:255.255.255.0:vhost1:eth0:off console=xenco ns0 DOM0: Initializing CPU#0 DOM0: Xen reported: 1852.069 MHz processor. DOM0: Console: colour VGA+ 80x25 DOM0: Calibrating delay loop... 14837.35 BogoMIPS DOM0: Memory: 16348k/18000k available (978k kernel code, 1652k reserved, 166k da ta, 52k init, 0k highmem) DOM0: Dentry cache hash table entries: 4096 (order: 3, 32768 bytes) DOM0: Inode cache hash table entries: 2048 (order: 2, 16384 bytes) DOM0: Mount cache hash table entries: 512 (order: 0, 4096 bytes) DOM0: Buffer cache hash table entries: 1024 (order: 0, 4096 bytes) DOM0: Page-cache hash table entries: 8192 (order: 3, 32768 bytes) DOM0: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) DOM0: CPU: L2 Cache: 512K (64 bytes/line) DOM0: CPU: AMD Athlon(tm) XP 2500+ stepping 00 DOM0: POSIX conformance testing by UNIFIX DOM0: Linux NET4.0 for Linux 2.4 DOM0: Based upon Swansea University Computer Society NET3.039 DOM0: Initializing RT netlink socket DOM0: Starting kswapd DOM0: VFS: Disk quotas vdquot_6.5.1 DOM0: register_swap_method: method blkdev DOM0: register_swap_method: method blkdev file DOM0: register_swap_method: method nfs file DOM0: Xeno console successfully installed DOM0: Successfully installed virtual firewall/router interface DOM0: Starting Xeno Balloon driver DOM0: pty: 256 Unix98 ptys configured DOM0: Serial driver version 5.05c (2001-07-08) with no serial options enabled DOM0: ttyS00 at 0x03f8 (irq = 4) is a 16550A DOM0: Real Time Clock Driver v1.10f DOM0: Could not allocate block update interrupt DOM0: Initializing Cryptographic API DOM0: NET4: Linux TCP/IP 1.0 for NET4.0 DOM0: IP Protocols: ICMP, UDP, TCP, IGMP DOM0: IP: routing cache hash table of 512 buckets, 4Kbytes DOM0: TCP: Hash tables configured (established 1024 bind 2048) DOM0: IP-Config: Complete: DOM0: device=eth0, addr=10.10.10.160, mask=255.255.255.0, gw=10.10.10.1, DOM0: host=vhost1, domain=, nis-domain=(none), DOM0: bootserver=255.255.255.255, rootserver=10.10.10.161, rootpathDOM0: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. DOM0: Looking up port of RPC 100003/2 on 10.10.10.161 DOM0: Looking up port of RPC 100005/1 on 10.10.10.161 DOM0: VFS: Mounted root (nfs filesystem). DOM0: Freeing unused kernel memory: 52k freed DOM0: INIT: version 2.85 booting DOM0: Hello World! DOM0: mount: can''t find / in /etc/fstab or /etc/mtab DOM0: Hello World. DOM0: Loading /etc/console/boottime.kmap.gz DOM0: Activating swap. DOM0: Calculating module dependencies... done. DOM0: Loading modules: via-rhine modprobe: Can''t locate module via-rhine DOM0: 3c59x modprobe: Can''t locate module 3c59x DOM0: DOM0: Checking all file systems... DOM0: fsck 1.35 (28-Feb-2004) DOM0: Setting kernel variables.. DOM0: Mounting local filesystems... DOM0: /var/run /var/lock. DOM0: Running 0dns-down to make sure resolv.conf is ok...done. DOM0: Cleaning: /etc/network/ifstate. DOM0: Setting up IP spoofing protection: rp_filter. DOM0: Configuring network interfaces...SIOCADDRT: File exists DOM0: done. DOM0: /etc/rcS.d/S41hostname.dhcp: line 1: host: command not found DOM0: Starting portmap daemon: portmap. DOM0: Loading the saved-state of the serial devices... DOM0: /dev/ttyS0 at 0x03f8 (irq = 4) is a 16550A DOM0: Initializing random number generator...done. DOM0: Recovering nvi editor sessions... done. DOM0: /etc/init.d/rcS: line 54: /etc/rcS.d/S70xfree86-common: Permission denied DOM0: INIT: Entering runlevel: 2 DOM0: Starting system log daemon: syslogd. DOM0: Starting kernel log daemon: klogd. DOM0: Starting portmap daemon: portmap. DOM0: Starting MTA: 2004-04-03 15:41:35 Failed to open configuration file /etc/e xim/exim.conf DOM0: Starting internet superserver: inetd. DOM0: Starting OpenBSD Secure Shell server: sshd. DOM0: Starting NFS common utilities: statd. DOM0: Starting deferred execution scheduler: atd. DOM0: Starting periodic command scheduler: cron. DOM0: INIT: no more processes left in this runlevel DOM0: INIT: Switching to runlevel: 6 DOM0: Stopping periodic command scheduler: cron. DOM0: Stopping MTA: No /usr/lib/exim/exim3 found running; none killed. DOM0: exim. DOM0: Stopping internet superserver: inetd. DOM0: Stopping OpenBSD Secure Shell server: sshd. DOM0: Stopping NFS common utilities: statd. DOM0: Stopping deferred execution scheduler: atd. DOM0: Stopping kernel log daemon: klogd. DOM0: Stopping system log daemon: syslogd. DOM0: Sending all processes the TERM signal...done. DOM0: Sending all processes the KILL signal...done. DOM0: Saving random seed...done. DOM0: Unmounting remote and non-toplevel virtual filesystems...done. DOM0: NOT deconfiguring network interfaces: / is an NFS mount DOM0: Deactivating swap...done. DOM0: Unmounting local filesystems...done. DOM0: Rebooting... Restarting system. Domain 0 killed: rebooting machine! ---------------------- Here is some of the machine''s work history that will explain why i''m so confident that the hardware is ok. Prior to retasking this machine as a Xen server it was my workstation. I have run a variety of kernels on it in the pat and even pushed the system memory consumption quite hard (it used to have a triple head xinerama setup on it.) I''ve run 2.4.21, 22, 23 and 24, 2.6.0-test9, 0, 1, 2, 3 and 4 on it (all custom compiles, 2.6 compiles used highmem 2G) when it was my workstation. I have pushed the memory consumption to the point of causing heavy swapping (700M+ of swap used, < 100M cache used, <16M free memory). Prior to emailing the Xen list I swapped the ram sticks out with another server that has run flawlessly for the past 12 months as a production mail server (50,000 email accounts, 400+ simultaneous receiving sendmail processes). Wehn the mainboard, cpu, disk, and power supply were my workstation I did MANY intensive compiling sessions (best method to find bad ram besides badram and memtest), sometimes several compiles in parallel. -- Brian Wolfe | Phone 1-(214)-764-1204 President, | Email brianw@terrabox.com TerraBox.com Inc. | pub 1024D/73C5A2DF 2003-03-18 Brian Wolfe <brianw@terrabox.com> Key fingerprint = 050E 5E3C CF65 4C1E A183 F48F E3E3 5B22 73C5 A2DF sub 1024g/BB87A3DD 2003-03-18 Keir Fraser said:> >> Now, this machine has been used for aprox 5 months now without any >> glitches or oopses. So i''m 99.9999% certain that the hardware is good. >> >> I''m using an NFS root since the ide is only in pio mode (and to >> eliminate >> it''s use toher than to boot the kernels). >> >> Any insights? >> >> If necessary for debuging, I can provide access to the hardware via >> serial >> console. :) >> >> Thanks for any help yall can give! > > The crashes look quite random -- I don''t think this is a bug in the > core of Xen. The two most likely possibilities are that you have duff > memory or that a misconfigured device is trashing memory. I definitely > wouldn''t discount the former, even though native x86 Linux has been > running okay -- crashes can be very sensitive to memory layout. > > It might be worth running a few rounds of memtest on the machine, or > swapping the memory, or trying to boot Xen on another identical box. > > If that doesn''t cure it then try swapping out or disabling > hardware. For example, boot off local disc and disable networking > (''ifname=dummy''). Since the cause is most likely hardware-related, the > best approach is to isolate the problem hardware. > > -- Keir > > PS. If you build your own Xen/Xenolinux then keep the build trees > around (or at least, for Xenolinux, the ''vmlinux'' file). I can''t find > suitable image files for the tarballs on the Xen website, and without > them it is very difficult to determine anything from crash dumps. >------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Brian Wolfe
2004-Apr-04 21:09 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
Ok, I have done two things so far as recomended. #1 I compiled a custom 2.6.4 with HIGHMEN4G and booted it up. It works just fine on all 1GB of ram. I kicked off 3 parallel kernel compiles and compared the resulting bzImage files. All 3 are identical and boot just fine. This SHOULD have beat any bad memory usage out of the machine if it existed. Memory usage went to all but 4MB used for cache and apps. No swapping occurred. #2 The initial 4 memtest86+ 3.0 tests passed. I am installing a copy of memtest86+ 3.0 that I just finished building in order to allow an overnight run happen, and be able to capture the serial output of memtest86+ for review later. btw, I placed the memtest deb I created for this test at http://www.terrabox.com/debs/memtest86+serial_3.0-1_i386.deb if anyone wants a deb that uses serial console. It won''t overwrite the official memtest86+ deb files. At this point i''m still %99.999 certain that the hardware is good. What is the next step after I have run all of the memtest86+ tests on the system overnight? -- Brian Wolfe | Phone 1-(214)-764-1204 President, | Email brianw@terrabox.com TerraBox.com Inc. | pub 1024D/73C5A2DF 2003-03-18 Brian Wolfe <brianw@terrabox.com> Key fingerprint = 050E 5E3C CF65 4C1E A183 F48F E3E3 5B22 73C5 A2DF sub 1024g/BB87A3DD 2003-03-18 Keir Fraser said:> >> Now, this machine has been used for aprox 5 months now without any >> glitches or oopses. So i''m 99.9999% certain that the hardware is good. >> >> I''m using an NFS root since the ide is only in pio mode (and to >> eliminate >> it''s use toher than to boot the kernels). >> >> Any insights? >> >> If necessary for debuging, I can provide access to the hardware via >> serial >> console. :) >> >> Thanks for any help yall can give! > > The crashes look quite random -- I don''t think this is a bug in the > core of Xen. The two most likely possibilities are that you have duff > memory or that a misconfigured device is trashing memory. I definitely > wouldn''t discount the former, even though native x86 Linux has been > running okay -- crashes can be very sensitive to memory layout. > > It might be worth running a few rounds of memtest on the machine, or > swapping the memory, or trying to boot Xen on another identical box. > > If that doesn''t cure it then try swapping out or disabling > hardware. For example, boot off local disc and disable networking > (''ifname=dummy''). Since the cause is most likely hardware-related, the > best approach is to isolate the problem hardware. > > -- Keir > > PS. If you build your own Xen/Xenolinux then keep the build trees > around (or at least, for Xenolinux, the ''vmlinux'' file). I can''t find > suitable image files for the tarballs on the Xen website, and without > them it is very difficult to determine anything from crash dumps. > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel >------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Keir Fraser
2004-Apr-05 07:06 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
> Note the "unknown apic" line where it attempts to initialize the ACPI > hardware. I don''t know if this can be a source fo the issue. This mesage > has given me grief in other systems with similar effects as this until I > custom compiled a newer 2.6 kernel that supported the APIC natively. > > The stock debian 2.4 kernel also seems to have issues with the io APIC. > This is why I compiled custom 2.6 kernels which found the APIC and used it > ok. This is also what was leading me to believe that the Via chipset may > be behaving in a way that Xen isn''t expecting and that the Linux 2.4 and > 2.6 kernels are avoiding triggering. > > Maybe Xen pokes around in different ways/areas than the linux kernel did > and has found some bad ram and/or APIC flaw that I just never ran into > with Linux by sheer chance.Okay, I''ll take a look at what changes there have been to IO-APIC and ACPI code up to Linux 2.4.25 -- certainly the most recent 2.4 kernel matches your IO-APIC version and doesn''t print the ''unexpected IO-APIC'' message. Perhaps there is some ''quirk'' fix that we are missing -- VIA boards usually need a few of those (the general opinion of VIA boards among Linux kernel developers is pretty low, I think :-). -- Keir ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Keir Fraser
2004-Apr-05 13:21 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
> > Maybe Xen pokes around in different ways/areas than the linux kernel did > > and has found some bad ram and/or APIC flaw that I just never ran into > > with Linux by sheer chance. > > Okay, I''ll take a look at what changes there have been to IO-APIC and > ACPI code up to Linux 2.4.25 -- certainly the most recent 2.4 kernel > matches your IO-APIC version and doesn''t print the ''unexpected > IO-APIC'' message. > > Perhaps there is some ''quirk'' fix that we are missing -- VIA boards > usually need a few of those (the general opinion of VIA boards among > Linux kernel developers is pretty low, I think :-).I''ve pushed updates from latest Linux 2.4 into Xen. If you don''t want to download the source repository and build it yourself, suitable Xen and Xenolinux images are available here: http://www.cl.cam.ac.uk/~kaf24/xen.gz http://www.cl.cam.ac.uk/~kaf24/xenolinux.gz -- Keir ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Keir Fraser
2004-Apr-05 13:38 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
> > > Maybe Xen pokes around in different ways/areas than the linux kernel did > > > and has found some bad ram and/or APIC flaw that I just never ran into > > > with Linux by sheer chance. > > > > Okay, I''ll take a look at what changes there have been to IO-APIC and > > ACPI code up to Linux 2.4.25 -- certainly the most recent 2.4 kernel > > matches your IO-APIC version and doesn''t print the ''unexpected > > IO-APIC'' message. > > > > Perhaps there is some ''quirk'' fix that we are missing -- VIA boards > > usually need a few of those (the general opinion of VIA boards among > > Linux kernel developers is pretty low, I think :-). > > I''ve pushed updates from latest Linux 2.4 into Xen. If you don''t want > to download the source repository and build it yourself, suitable Xen > and Xenolinux images are available here: > http://www.cl.cam.ac.uk/~kaf24/xen.gz > http://www.cl.cam.ac.uk/~kaf24/xenolinux.gzAnother couple of things to try: 1. Specify ''noacpi'' and/or ''ignorebiostables'' on Xen''s command line. This will cause parsing of some configuration tables to be skipped -- which may help if the BIOS is buggy. 2. Let us know more hardware details (e.g. VIA chipset version). It would be useful to see the output of lspci (''lspci -vv''). -- Keir ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Brian Wolfe
2004-Apr-05 17:29 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
Heh, I know what you mean on the VIA boards. I almost always have an issue booting > 3 month old kernels on them. 8-P I spose I could look at via as a "enforced upgrade" system. ;) *nod* I''d tried the noacpi, ignorebiostables, etc. All of the usual tricks on the xenolinux.gz kernel image as well to no avail pror to harassing yall. :) I think my friend Adam was feeling a bit abused as a Xen suport route as well. *grin* Things are getting a LITTLE bit futher on the bootup. :) Any chance the IDE , USB, and/or ethernet interfaces are doign something funky? Here is the lspci -vv and Linux 2.6.4 compiled for K7 and HIGHMEM4G if you need the raw info. I disabled USB, firewire etc, basicly anything that wasn''t needed for a server setup. Striped scsi out as much as possible as well (i''m a minimalist on server kernels). I have attached a copy of the serial console log from booting with dom0_mem=1800 vs dom0_mem=1600 noacpi ignorebiostables for reference. I have also attached a log of lspci -vv and the kernel boot log for 2.6.4 +HIGHMEM4G and the screen from memtest86+ 3.0 If you need ANYTHING to help, please don''t hesitate to let me know directly. The hardware and my time are at you and other xen developers command. :) -- Brian Wolfe | Phone 1-(214)-764-1204 President, | Email brianw@terrabox.com TerraBox.com Inc. | pub 1024D/73C5A2DF 2003-03-18 Brian Wolfe <brianw@terrabox.com> Key fingerprint = 050E 5E3C CF65 4C1E A183 F48F E3E3 5B22 73C5 A2DF sub 1024g/BB87A3DD 2003-03-18 Keir Fraser said:>> > > Maybe Xen pokes around in different ways/areas than the linux kernel >> did >> > > and has found some bad ram and/or APIC flaw that I just never ran >> into >> > > with Linux by sheer chance. >> > >> > Okay, I''ll take a look at what changes there have been to IO-APIC and >> > ACPI code up to Linux 2.4.25 -- certainly the most recent 2.4 kernel >> > matches your IO-APIC version and doesn''t print the ''unexpected >> > IO-APIC'' message. >> > >> > Perhaps there is some ''quirk'' fix that we are missing -- VIA boards >> > usually need a few of those (the general opinion of VIA boards among >> > Linux kernel developers is pretty low, I think :-). >> >> I''ve pushed updates from latest Linux 2.4 into Xen. If you don''t want >> to download the source repository and build it yourself, suitable Xen >> and Xenolinux images are available here: >> http://www.cl.cam.ac.uk/~kaf24/xen.gz >> http://www.cl.cam.ac.uk/~kaf24/xenolinux.gz > > Another couple of things to try: > 1. Specify ''noacpi'' and/or ''ignorebiostables'' on Xen''s command line. > This will cause parsing of some configuration tables to be skipped > -- which may help if the BIOS is buggy. > 2. Let us know more hardware details (e.g. VIA chipset version). It > would be useful to see the output of lspci (''lspci -vv''). > > -- Keir >
Adam Heath
2004-Apr-05 17:37 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
On Mon, 5 Apr 2004, Keir Fraser wrote:> > > Maybe Xen pokes around in different ways/areas than the linux kernel did > > > and has found some bad ram and/or APIC flaw that I just never ran into > > > with Linux by sheer chance. > > > > Okay, I''ll take a look at what changes there have been to IO-APIC and > > ACPI code up to Linux 2.4.25 -- certainly the most recent 2.4 kernel > > matches your IO-APIC version and doesn''t print the ''unexpected > > IO-APIC'' message. > > > > Perhaps there is some ''quirk'' fix that we are missing -- VIA boards > > usually need a few of those (the general opinion of VIA boards among > > Linux kernel developers is pretty low, I think :-). > > I''ve pushed updates from latest Linux 2.4 into Xen. If you don''t want > to download the source repository and build it yourself, suitable Xen > and Xenolinux images are available here: > http://www.cl.cam.ac.uk/~kaf24/xen.gz > http://www.cl.cam.ac.uk/~kaf24/xenolinux.gzIf this does fix it for Brian(who I know in real life, he''s a local nut here in Dallas), then I''d like this as a regular patch. I can''t use bitkeeper, as I am interested in doing revision control software work(have done a little in the past, and want to do more in the future), and bk''s license keeps me from doing this. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Keir Fraser
2004-Apr-06 07:11 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
> Heh, I know what you mean on the VIA boards. I almost always have an issue > booting > 3 month old kernels on them. 8-P I spose I could look at via as > a "enforced upgrade" system. ;) > > *nod* I''d tried the noacpi, ignorebiostables, etc. All of the usual tricks > on the xenolinux.gz kernel image as well to no avail pror to harassing > yall. :) I think my friend Adam was feeling a bit abused as a Xen suport > route as well. *grin* > > Things are getting a LITTLE bit futher on the bootup. :) Any chance the > IDE , USB, and/or ethernet interfaces are doign something funky?Looks like the Ethernet interface might be doing bad things. Both crashes are at the same point in its interrupt handler. I''m not sure whether this is a cause or merely a symptom though. I''ll take a look. Meanwhile, can you put a different card in that machine? For example, we know that 3com 3c905''s are good. 3c595 is a relic. :-) -- Keir ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Keir Fraser
2004-Apr-06 09:56 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
> > > Heh, I know what you mean on the VIA boards. I almost always have an issue > > booting > 3 month old kernels on them. 8-P I spose I could look at via as > > a "enforced upgrade" system. ;) > > > > *nod* I''d tried the noacpi, ignorebiostables, etc. All of the usual tricks > > on the xenolinux.gz kernel image as well to no avail pror to harassing > > yall. :) I think my friend Adam was feeling a bit abused as a Xen suport > > route as well. *grin* > > > > Things are getting a LITTLE bit futher on the bootup. :) Any chance the > > IDE , USB, and/or ethernet interfaces are doign something funky? > > Looks like the Ethernet interface might be doing bad things. Both > crashes are at the same point in its interrupt handler. I''m not sure > whether this is a cause or merely a symptom though. > > I''ll take a look. Meanwhile, can you put a different card in that > machine? For example, we know that 3com 3c905''s are good. 3c595 is a > relic. :-)Okay, I think I''ve found and fixed the problem. I''ve made pre-built images available at: http://www.cl.cam.ac.uk/~kaf24/xen.gz http://www.cl.cam.ac.uk/~kaf24/xenolinux.gz The problem is that the 3c595 is not using DMA, but is instead using PIO (polled I/O). This is doubly bad in Xen: 1. The main CPU is responsibel for transferring all data to/from slow on-card memory. 2. Xen needs to temporarily map the buffer into its address space to execute the transfer. It was the latter which was not being done -- Xen has a one-to-one mapping of onyl the first 40MB of physical memory. If the buffer location is any higher than that then we ended up copying received packets to a random location! So, if you''re looking for decent performance then you want to get yourself a good network card -- eg. 3c905. I''ve checked the probable fix into both 1.2 and 1.3 trees. -- Keir ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Keir Fraser
2004-Apr-06 09:57 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
> If this does fix it for Brian(who I know in real life, he''s a local nut here > in Dallas), then I''d like this as a regular patch. I can''t use bitkeeper, as > I am interested in doing revision control software work(have done a little in > the past, and want to do more in the future), and bk''s license keeps me from > doing this.If the fix is confirmed to work then you can pull and build the latest 1.2 repository, which now has the fix applied. I''d recommend doing this soon anyway --- a few nasty bugs have been fixed since you last packaged the tree for distribution. -- Keir ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Brian Wolfe
2004-Apr-06 14:37 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
Would a decchip tulip card be a good choice for xen? Digital Equipment Corporation DECchip 21140 [FasterNet] (rev 22). I also have a server class Intel ether card (not certain of the version, have to drop it in a system) that I can try on the server. btw, I just noticed that I misspelled your name on my files. ;-P Sorry bout that. :) Thank you for the amazingly fast response times to my issues. This is moving faster than suport that I have gotten from IBM for it''s AIX RS6000 servers! I do have a fairly large array of various low end network cards. I''ll set aside some time to test what I can on the spare parts that I have. If I can manage more spare time I cna try to learn what needs to be done with the network stuff to make other cards from linux 2.4 work with Xen. Looks like i Have a bit of learning to do... :) though it should be fun to try. -- Brian Wolfe | Phone 1-(214)-764-1204 President, | Email brianw@terrabox.com TerraBox.com Inc. | pub 1024D/73C5A2DF 2003-03-18 Brian Wolfe <brianw@terrabox.com> Key fingerprint = 050E 5E3C CF65 4C1E A183 F48F E3E3 5B22 73C5 A2DF sub 1024g/BB87A3DD 2003-03-18 Keir Fraser said:>> >> > Heh, I know what you mean on the VIA boards. I almost always have an >> issue >> > booting > 3 month old kernels on them. 8-P I spose I could look at via >> as >> > a "enforced upgrade" system. ;) >> > >> > *nod* I''d tried the noacpi, ignorebiostables, etc. All of the usual >> tricks >> > on the xenolinux.gz kernel image as well to no avail pror to harassing >> > yall. :) I think my friend Adam was feeling a bit abused as a Xen >> suport >> > route as well. *grin* >> > >> > Things are getting a LITTLE bit futher on the bootup. :) Any chance >> the >> > IDE , USB, and/or ethernet interfaces are doign something funky? >> >> Looks like the Ethernet interface might be doing bad things. Both >> crashes are at the same point in its interrupt handler. I''m not sure >> whether this is a cause or merely a symptom though. >> >> I''ll take a look. Meanwhile, can you put a different card in that >> machine? For example, we know that 3com 3c905''s are good. 3c595 is a >> relic. :-) > > Okay, I think I''ve found and fixed the problem. I''ve made pre-built > images available at: > http://www.cl.cam.ac.uk/~kaf24/xen.gz > http://www.cl.cam.ac.uk/~kaf24/xenolinux.gz > > The problem is that the 3c595 is not using DMA, but is instead using > PIO (polled I/O). This is doubly bad in Xen: > 1. The main CPU is responsibel for transferring all data to/from slow > on-card memory. > 2. Xen needs to temporarily map the buffer into its address space to > execute the transfer. > > It was the latter which was not being done -- Xen has a one-to-one > mapping of onyl the first 40MB of physical memory. If the buffer > location is any higher than that then we ended up copying received > packets to a random location! > > So, if you''re looking for decent performance then you want to get > yourself a good network card -- eg. 3c905. > > I''ve checked the probable fix into both 1.2 and 1.3 trees. > > -- Keir >------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Keir Fraser
2004-Apr-06 14:44 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
> Would a decchip tulip card be a good choice for xen? Digital Equipment > Corporation DECchip 21140 [FasterNet] (rev 22).Tulip is a good NIC design, and it can do full bus-mastering DMA. It''s not as well tested on Xen as some others, but should work just fine. For reference, the NICs that we use are Broadcom tg3, Intel e1000, and 3com 3c905. There are suspected issues with the tg3 driver though (the same issues exist on native Linux also - the driver just isn''t fully mature yet).> I also have a server class Intel ether card (not certain of the version, > have to drop it in a system) that I can try on the server.Intel e100 and e1000 should work just fine and give good performance.> I do have a fairly large array of various low end network cards. I''ll set > aside some time to test what I can on the spare parts that I have. If I > can manage more spare time I cna try to learn what needs to be done with > the network stuff to make other cards from linux 2.4 work with Xen.The new IO model will be unveiled in a short while. At that point we hope that all Linux network and block-device drivers will work with no modifications required. Fingers crossed. :-) -- Keir ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Brian Wolfe
2004-Apr-06 15:04 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
Sounds great! I''ll drop in the Intel then. The latest fixes that you posted are still showing memory corruption symptoms. Different point again, so the driver is probably just being really naughty in how it''s using things. 8-P Since you will have the new IO layer soon I think it may be a good idea for me to just dig out another card from my pile of parts (accumulation of 15 years of pc upgrades, repairs, etc on my own, and other people''s machines.) If I tried, I think I could probably make a good 7 or 8 working machines from the pile. Is that scary or what? *grin* Sounds like I''ll have plenty of testing to do once the new IO layer is released. Any information on the IDE subsystems in the new IO layer? I''d love to see the same "drop in" capability for IDE drivers. Course with me knowing very little about this level of things in driver land I may be asking for the sun. Adam mentioned that the 1.2 version does IDE in a very non-linux way. I feel bad for having you spend a couple days chasing the 3com driver around now. 8-/ Is there anything that I can provide that the xen team can use? I''d like to see if there are any other ways that I can conribute with my limited amount of available time. I''ll definitly be allocating some time to testing various cards and systems once the new IO layer is released. -- Brian Wolfe | Phone 1-(214)-764-1204 President, | Email brianw@terrabox.com TerraBox.com Inc. | pub 1024D/73C5A2DF 2003-03-18 Brian Wolfe <brianw@terrabox.com> Key fingerprint = 050E 5E3C CF65 4C1E A183 F48F E3E3 5B22 73C5 A2DF sub 1024g/BB87A3DD 2003-03-18 Keir Fraser said:> >> Would a decchip tulip card be a good choice for xen? Digital Equipment >> Corporation DECchip 21140 [FasterNet] (rev 22). > > Tulip is a good NIC design, and it can do full bus-mastering DMA. > > It''s not as well tested on Xen as some others, but should work just > fine. For reference, the NICs that we use are Broadcom tg3, Intel > e1000, and 3com 3c905. There are suspected issues with the tg3 driver > though (the same issues exist on native Linux also - the driver just > isn''t fully mature yet). > >> I also have a server class Intel ether card (not certain of the version, >> have to drop it in a system) that I can try on the server. > > Intel e100 and e1000 should work just fine and give good performance. > >> I do have a fairly large array of various low end network cards. I''ll >> set >> aside some time to test what I can on the spare parts that I have. If I >> can manage more spare time I cna try to learn what needs to be done with >> the network stuff to make other cards from linux 2.4 work with Xen. > > The new IO model will be unveiled in a short while. At that point > we hope that all Linux network and block-device drivers will work with > no modifications required. Fingers crossed. :-) > > -- Keir >------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Keir Fraser
2004-Apr-06 15:31 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
> Sounds great! I''ll drop in the Intel then. > > The latest fixes that you posted are still showing memory corruption > symptoms. Different point again, so the driver is probably just being > really naughty in how it''s using things. 8-PActually, I think that my fix was broken -- can you try: http://www.cl.cam.ac.uk/~kaf24/xen.gz (The same xenolinux.gz as before will work okay). Just for safety''s sake, the md5sum of the xen.gz file should be 32971f4737c8e1f853086a60dd0f92c2 If this still doesn''t work, but your Intel card does work, then I think that we''ll ignore this bug. :-) -- Keir ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Brian Wolfe
2004-Apr-06 16:10 UTC
Re: [Xen-devel] issues getting more than 16M ram to be used without oopsing. 1.2 and 1.3-unstable
That did it. :) 3c59x can be listed as "working, partially tested" Thank you VERY much. :) Now I have 3 more cards that I can use with Xen. -- Brian Wolfe | Phone 1-(214)-764-1204 President, | Email brianw@terrabox.com TerraBox.com Inc. | pub 1024D/73C5A2DF 2003-03-18 Brian Wolfe <brianw@terrabox.com> Key fingerprint = 050E 5E3C CF65 4C1E A183 F48F E3E3 5B22 73C5 A2DF sub 1024g/BB87A3DD 2003-03-18 Keir Fraser said:>> Sounds great! I''ll drop in the Intel then. >> >> The latest fixes that you posted are still showing memory corruption >> symptoms. Different point again, so the driver is probably just being >> really naughty in how it''s using things. 8-P > > Actually, I think that my fix was broken -- can you try: > http://www.cl.cam.ac.uk/~kaf24/xen.gz > (The same xenolinux.gz as before will work okay). > > Just for safety''s sake, the md5sum of the xen.gz file should be > 32971f4737c8e1f853086a60dd0f92c2 > > If this still doesn''t work, but your Intel card does work, then I > think that we''ll ignore this bug. :-) > > -- Keir >------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
I also downloadded the prebuilt images (xen.gz and xenolinux.gz). The underlying system is Fedora-core-1. I I boot the box from xen-1.2-CD and try xen_nat_enable xc_dom-create.py -D ip=169.254.1.2;mem=64 I can craete a new domain. Now with new binaries (I am still having problems with the one that I compile): - system boots - xen_nat_enable produces no error - xc_dom_create.py -D vmid=1;ip=169.254.1.2;mem-64 fails with a complaint about not finding a handle for interface 2.. Fedora-core-1 used /dev/hda1 for root /dev/hda2 for swap, so what is the right entries in /etc/xc/defaults for: . vbd_list = ?? (tried [ (''phy:hda1'',''hda1,''r'') ] but no luck) . cmdline_ip = ?? (did not change the original) . cmdline_root = ?? (tried ''root=/dev/hda1 ro" bu did not work) Any pointers? -ishwar ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
The exact error message when parsing /etc/xc/defaults fiel: .. VM cmdline : "ip=169.254.1.2:162.254.1.0:169.254.1.0:255.255.0.0::etho:off \ root=/dev/hda1 r 4 LOCALIP=169.254.1.2" ERROR: couldn''t obtain handle on privilged mode command interface (2 = No such\ file or directory) Traceback (most recent call last): FIle "/usr/bin/xc_dom_create.py", line 197, in ?? xc = Xc.new() SystemError: error return without exception set .. -ishwar On Tue, 6 Apr 2004, I RATTAN wrote:> > I also downloadded the prebuilt images (xen.gz and xenolinux.gz). > The underlying system is Fedora-core-1. > > I I boot the box from xen-1.2-CD and try > xen_nat_enable > xc_dom-create.py -D ip=169.254.1.2;mem=64 > > I can craete a new domain. > > Now with new binaries (I am still having problems with the one that I > compile): > > - system boots > - xen_nat_enable produces no error > - xc_dom_create.py -D vmid=1;ip=169.254.1.2;mem-64 fails with > a complaint about not finding a handle for interface 2.. > > Fedora-core-1 used /dev/hda1 for root /dev/hda2 for swap, so > what is the right entries in /etc/xc/defaults for: > > . vbd_list = ?? (tried [ (''phy:hda1'',''hda1,''r'') ] but no luck) > . cmdline_ip = ?? (did not change the original) > . cmdline_root = ?? (tried ''root=/dev/hda1 ro" bu did not work) > > Any pointers? > > -ishwar > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel >------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
which version of the tools are you using? Which version of Xen/Xenolinux are you using? the versions of the tools and XenoLinux/Xen need to match. I suspect you use the 1.2 tools with a newer XenoLinux/Xen. Also, the format/content of the /etc/xc/defaults file might have changed. Rolf On Tue, 2004-04-06 at 18:46, I RATTAN wrote:> The exact error message when parsing /etc/xc/defaults fiel: > .. > VM cmdline : "ip=169.254.1.2:162.254.1.0:169.254.1.0:255.255.0.0::etho:off \ > root=/dev/hda1 r 4 LOCALIP=169.254.1.2" > ERROR: couldn''t obtain handle on privilged mode command interface (2 = No such\ > file or directory) > Traceback (most recent call last): > FIle "/usr/bin/xc_dom_create.py", line 197, in ?? > xc = Xc.new() > SystemError: error return without exception set > .. > > -ishwar > > On Tue, 6 Apr 2004, I RATTAN wrote: > > > > > I also downloadded the prebuilt images (xen.gz and xenolinux.gz). > > The underlying system is Fedora-core-1. > > > > I I boot the box from xen-1.2-CD and try > > xen_nat_enable > > xc_dom-create.py -D ip=169.254.1.2;mem=64 > > > > I can craete a new domain. > > > > Now with new binaries (I am still having problems with the one that I > > compile): > > > > - system boots > > - xen_nat_enable produces no error > > - xc_dom_create.py -D vmid=1;ip=169.254.1.2;mem-64 fails with > > a complaint about not finding a handle for interface 2.. > > > > Fedora-core-1 used /dev/hda1 for root /dev/hda2 for swap, so > > what is the right entries in /etc/xc/defaults for: > > > > . vbd_list = ?? (tried [ (''phy:hda1'',''hda1,''r'') ] but no luck) > > . cmdline_ip = ?? (did not change the original) > > . cmdline_root = ?? (tried ''root=/dev/hda1 ro" bu did not work) > > > > Any pointers? > > > > -ishwar > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > GenToo technologies. Learn everything from fundamentals to system > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/xen-devel > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
xen.gz and xenolinux.gz from keir''s URL xc/defaults and xc_* tools from xeno-1.2-CD I understand they have to match but how to make them match/work is what I asked.. -ishwar On Tue, 6 Apr 2004, Rolf Neugebauer wrote:> which version of the tools are you using? Which version of Xen/Xenolinux > are you using? > > the versions of the tools and XenoLinux/Xen need to match. > > I suspect you use the 1.2 tools with a newer XenoLinux/Xen. > > Also, the format/content of the /etc/xc/defaults file might have > changed. > > Rolf > > On Tue, 2004-04-06 at 18:46, I RATTAN wrote: > > The exact error message when parsing /etc/xc/defaults fiel: > > .. > > VM cmdline : "ip=169.254.1.2:162.254.1.0:169.254.1.0:255.255.0.0::etho:off \ > > root=/dev/hda1 r 4 LOCALIP=169.254.1.2" > > ERROR: couldn''t obtain handle on privilged mode command interface (2 = No such\ > > file or directory) > > Traceback (most recent call last): > > FIle "/usr/bin/xc_dom_create.py", line 197, in ?? > > xc = Xc.new() > > SystemError: error return without exception set > > .. > > > > -ishwar > > > > On Tue, 6 Apr 2004, I RATTAN wrote: > > > > > > > > I also downloadded the prebuilt images (xen.gz and xenolinux.gz). > > > The underlying system is Fedora-core-1. > > > > > > I I boot the box from xen-1.2-CD and try > > > xen_nat_enable > > > xc_dom-create.py -D ip=169.254.1.2;mem=64 > > > > > > I can craete a new domain. > > > > > > Now with new binaries (I am still having problems with the one that I > > > compile): > > > > > > - system boots > > > - xen_nat_enable produces no error > > > - xc_dom_create.py -D vmid=1;ip=169.254.1.2;mem-64 fails with > > > a complaint about not finding a handle for interface 2.. > > > > > > Fedora-core-1 used /dev/hda1 for root /dev/hda2 for swap, so > > > what is the right entries in /etc/xc/defaults for: > > > > > > . vbd_list = ?? (tried [ (''phy:hda1'',''hda1,''r'') ] but no luck) > > > . cmdline_ip = ?? (did not change the original) > > > . cmdline_root = ?? (tried ''root=/dev/hda1 ro" bu did not work) > > > > > > Any pointers? > > > > > > -ishwar > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: IBM Linux Tutorials > > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > > GenToo technologies. Learn everything from fundamentals to system > > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/xen-devel > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > GenToo technologies. Learn everything from fundamentals to system > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/xen-devel >------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Tue, 2004-04-06 at 19:11, I RATTAN wrote:> xen.gz and xenolinux.gz from keir''s URL > xc/defaults and xc_* tools from xeno-1.2-CD > > I understand they have to match but how to make them match/work > is what I asked..can you download them and from bkbits or the tar-ball and then install the tools from there, i.e., make install from the tools directory? Rolf> -ishwar > > On Tue, 6 Apr 2004, Rolf Neugebauer wrote: > > > which version of the tools are you using? Which version of Xen/Xenolinux > > are you using? > > > > the versions of the tools and XenoLinux/Xen need to match. > > > > I suspect you use the 1.2 tools with a newer XenoLinux/Xen. > > > > Also, the format/content of the /etc/xc/defaults file might have > > changed. > > > > Rolf > > > > On Tue, 2004-04-06 at 18:46, I RATTAN wrote: > > > The exact error message when parsing /etc/xc/defaults fiel: > > > .. > > > VM cmdline : "ip=169.254.1.2:162.254.1.0:169.254.1.0:255.255.0.0::etho:off \ > > > root=/dev/hda1 r 4 LOCALIP=169.254.1.2" > > > ERROR: couldn''t obtain handle on privilged mode command interface (2 = No such\ > > > file or directory) > > > Traceback (most recent call last): > > > FIle "/usr/bin/xc_dom_create.py", line 197, in ?? > > > xc = Xc.new() > > > SystemError: error return without exception set > > > .. > > > > > > -ishwar > > > > > > On Tue, 6 Apr 2004, I RATTAN wrote: > > > > > > > > > > > I also downloadded the prebuilt images (xen.gz and xenolinux.gz). > > > > The underlying system is Fedora-core-1. > > > > > > > > I I boot the box from xen-1.2-CD and try > > > > xen_nat_enable > > > > xc_dom-create.py -D ip=169.254.1.2;mem=64 > > > > > > > > I can craete a new domain. > > > > > > > > Now with new binaries (I am still having problems with the one that I > > > > compile): > > > > > > > > - system boots > > > > - xen_nat_enable produces no error > > > > - xc_dom_create.py -D vmid=1;ip=169.254.1.2;mem-64 fails with > > > > a complaint about not finding a handle for interface 2.. > > > > > > > > Fedora-core-1 used /dev/hda1 for root /dev/hda2 for swap, so > > > > what is the right entries in /etc/xc/defaults for: > > > > > > > > . vbd_list = ?? (tried [ (''phy:hda1'',''hda1,''r'') ] but no luck) > > > > . cmdline_ip = ?? (did not change the original) > > > > . cmdline_root = ?? (tried ''root=/dev/hda1 ro" bu did not work) > > > > > > > > Any pointers? > > > > > > > > -ishwar > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > This SF.Net email is sponsored by: IBM Linux Tutorials > > > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > > > GenToo technologies. Learn everything from fundamentals to system > > > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > > > _______________________________________________ > > > > Xen-devel mailing list > > > > Xen-devel@lists.sourceforge.net > > > > https://lists.sourceforge.net/lists/listinfo/xen-devel > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: IBM Linux Tutorials > > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > > GenToo technologies. Learn everything from fundamentals to system > > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/xen-devel > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> xen.gz and xenolinux.gz from keir''s URL > xc/defaults and xc_* tools from xeno-1.2-CD > > I understand they have to match but how to make them match/work > is what I asked.. > > -ishwarYou obtain a matching set by building and installing your own Xen, Xenolinux, and tools from the source repository on xen.bkbits.net. Alternatively a pre-built tarball is available from our web pages. This is all documented in the ''Downloads'' section of http://xen.sf.net -- Keir ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
I am looking at xeno-1.2-install.tgz from download URL. The tar file wrt to ./install, so do I copy the files to respective dirs in the underlying system? Also, the same defaults file problem is visible: (I have / on /dev/hda1 and swap /dev/hda2): vbd_list = [ (''phy:sda%d''%(7+vnid),''sda1'',''w''), (''phy:sda6'',''sda6'',''r'') ] ... cmdline_root = "root=/dev/sda1 ro" ... cmdline_extra = "4 VMID=%d usr=/dev/sda6"%vmid ... /dev/sda sounds like SCSI, so how to replace it by IDE. Is there some other trick to create other domains?? -ishwar On Tue, 6 Apr 2004, Keir Fraser wrote:> > xen.gz and xenolinux.gz from keir''s URL > > xc/defaults and xc_* tools from xeno-1.2-CD > > > > I understand they have to match but how to make them match/work > > is what I asked.. > > > > -ishwar > > You obtain a matching set by building and installing your own Xen, > Xenolinux, and tools from the source repository on > xen.bkbits.net. Alternatively a pre-built tarball is available from > our web pages. This is all documented in the ''Downloads'' section of > http://xen.sf.net > > -- Keir >------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> I am looking at xeno-1.2-install.tgz from download URL. > > The tar file wrt to ./install, so > do I copy the files to respective dirs in the underlying system?Yes. The only possible problem is that the Python modules may not end up in the right place to get found by your Python installation. In which case you may need to set the PYTHONPATH environment variable, or manually work out teh correct place to put the modules (it''ll be somthing like /usr/lib/python-2.2/site-packages).> Also, the same defaults file problem is visible: (I have / on /dev/hda1 > and swap /dev/hda2): > > vbd_list = [ (''phy:sda%d''%(7+vnid),''sda1'',''w''), (''phy:sda6'',''sda6'',''r'') ] > ... > cmdline_root = "root=/dev/sda1 ro" > ... > cmdline_extra = "4 VMID=%d usr=/dev/sda6"%vmid > ... > > /dev/sda sounds like SCSI, so how to replace it by IDE. Is there > some other trick to create other domains??It doesn''t matter -- it''s not /really/ SCSI. It''s just the name the teh virtual device appears as in the other guest. What you do need to change is: vbd_list = [ (''phy:sda%d''%(7+vnid),''sda1'',''w''), (''phy:sda6'',''sda6'',''r'') ] ^^^^^^^^^^^^^^^ ^^^^ The former binds the name ''sda1'' in the guest to real physical device sda(7+vmid), and ''sda6'' to realy physical device sda6. These need to be changed to appropriate partitions on hda. -- Keir ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Tue, 6 Apr 2004, Keir Fraser wrote:> It doesn''t matter -- it''s not /really/ SCSI. It''s just the name the > teh virtual device appears as in the other guest. What you do need to > change is: > vbd_list = [ (''phy:sda%d''%(7+vnid),''sda1'',''w''), (''phy:sda6'',''sda6'',''r'') ] > ^^^^^^^^^^^^^^^ ^^^^ > > The former binds the name ''sda1'' in the guest to real physical device > sda(7+vmid), and ''sda6'' to realy physical device sda6. These need to > be changed to appropriate partitions on hda.So vbd_list = [ (''phy:hda1'',''sda1'',''w''), (''phy:hda1'',''sda6'',''r'') ] might be an appropriate entry as I have one IDE disk (hda) with root-fs on /dev/hda1 ? -ishwar ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> vbd_list = [ (''phy:hda1'',''sda1'',''w''), (''phy:hda1'',''sda6'',''r'') ] > > might be an appropriate entry as I have one IDE disk (hda) with root-fs > on /dev/hda1 > ?I don''t know enough about your setup to know what you should have, but this is almost certainly wrong: you''re trying to make real physcial partition hda1 visible to the domain as both sda1 and sda6. Are you trying to have a a separate writeable root and read-only /usr partion? You do realise that the writeable partition must not be the same partition that you''re using for domain0''s root? You need to make a copy. Ian ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
The vbd_list contains a list of mappings of the form: (''real device name [as seen by dom0]'', ''target device name [what the new domain sees the device as]'', ''permissions''). The ''w'' (writeable) permission implicitly also allows read access. The real device name is specified as ''phy:devname'' for a physical disk or partition, or as ''vd:identifier'' for a Xen ''virtual disk''. As you know, you can use this list of mappings to selectively grant a new domain access to certain disk resources. You should never allow two domains to simultaneously have write access to any disk area - normal disk filesystems aren''t designed to cope with multiple-writer access, so it will cause severe corruption. Linux also gets confused if a filesystem that''s read-only by one domain is written to by another, so single writer, multiple reader should also be avoided (although it won''t cause corruption). It is perfectly safe to have two domains have read-only access to a filesystem, however - this can be useful to avoid duplicating data). Here''s a concrete example of VBDs, where I''m configuring my system so I can start a second domain: Suppose my machine has the following real partitions (as viewed from dom0, or booting with a normal Linux kernel): /dev/hda1 : DOM0''s / filesystem (the one you boot off) /dev/hda2 : DOM0''s /usr filesystem /dev/hda3 : DOM0''s swap partition /dev/hda5 : a secondary / filesystem for use by a second domain /dev/hda6 : a swap partition for the second domain to use The new domain I''m going to start must have a separate / partition since it will have different information in it. It will want write access to this partition. It will also need a different swap partition to DOM0 because the two domains will be swapping out different data. I might, however, want to share the contents of /usr, since they''ll be the same for both domains. This would have to be read-only for both DOM0 and my second domain, otherwise Linux will get confused. * DOM0''s fstab should specify /usr as read only. For this example, I want the second domain to think its / filesystem is on /dev/sda1, its swap is on /dev/sda2 and its /usr is on /dev/sda3. * vbd_list = [(''phy:hda5'',''sda1'',''w''), (''phy:hda6'',''sda2'',''w''), (''phy:hda2'',''sda3'',''r'')] This setups up the appropriate disk translations so that the second domain will get this view of the disks. * the other domain''s fstab should match these details, i.e. / on /dev/sda1, swap on /dev/sda2, /usr read only on /dev/sda3 The standard xc_dom_create.py does some sanity checking to try to avoid dangerous sharing. If you get a VBD sharing error, then you should check that, for instance, none of the second domain''s filesystems are mounted in DOM0 and that the VBD mappings do not allow incorrect sharing. This should get you going. There''s a more detailed discussion of this (and some more advanced stuff about Virtual Disks) in the VBD-HOWTO.txt document, which you should take a look at). You could alternatively use NFS-root to boot the second domain. HTH, Mark ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel