hi all, first this is actually in reply to some other mails. i provide the output of lspci -xxx, but also a part from X.0.log: it shows the 0xffffffff that Ronald G. Minnich told about. if you want more info, let me know. (xen-2.0-testing tarball from 03/01/2005, 2.4.28, on slc3) X.0.log (final part): (**) I810(0): Depth 24, (--) framebuffer bpp 32 (==) I810(0): RGB weight 888 (==) I810(0): Default visual is TrueColor (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a (II) I810(0): initializing int10 (WW) I810(0): Bad V_BIOS checksum (II) I810(0): Primary V_BIOS segment is: 0xc000 (WW) System lacks support for changing MTRRs (EE) I810(0): unknown type(0xffffffff)=0xff (II) I810(0): EAX=0x00004f00, EBX=0x00000000, ECX=0x00000000, EDX=0x00000000 (II) I810(0): ESP=0x00000ffa, EBP=0x00000000, ESI=0x00000000, EDI=0x00002000 (II) I810(0): CS=0xc000, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, GS=0x0000 (II) I810(0): EIP=0x00000014, EFLAGS=0x00003200 (II) I810(0): code at 0x000c0014: e9 0d 14 27 40 00 b0 0a 30 30 49 42 4d 20 56 47 41 20 43 6f 6d 70 61 74 69 62 6c 65 20 42 49 4f (II) stack at 0x00001ffa: 00 06 00 00 00 32 (II) I810(0): VESA BIOS not detected (EE) I810(0): VBE initialization failed. (II) UnloadModule: "i810" (II) UnloadModule: "int10" (II) UnloadModule: "vgahw" (II) Unloading /usr/X11R6/lib/modules/libvgahw.a (II) UnloadModule: "vbe" (II) Unloading /usr/X11R6/lib/modules/libvbe.a (II) UnloadModule: "int10" (II) Unloading /usr/X11R6/lib/modules/linux/libint10.a (EE) Screen(s) found, but none have a usable configuration. --------------------------------------------------------- output from lspci -xxx: 00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) 00: 86 80 70 25 06 01 90 20 02 00 00 06 00 00 00 00 10: 08 00 00 f8 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 70 25 30: 00 00 00 00 e4 00 00 00 00 00 00 00 00 00 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 44 00 40 80 1c 00 00 00 00 00 00 00 00 00 60: 08 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 10 11 01 00 00 33 33 00 00 00 00 00 00 1a 38 00 a0: 02 00 30 00 17 42 00 1f 00 00 00 00 00 00 00 00 b0: 00 00 00 00 30 00 00 00 00 00 00 00 10 10 00 00 c0: 00 00 00 00 00 3f 0e 28 00 01 00 00 00 00 00 00 d0: 02 28 04 0e 0b 0d 00 00 00 00 00 00 00 00 40 41 e0: 00 00 00 00 09 00 06 01 00 02 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 68 0f 03 00 00 00 00 00 00:02.0 VGA compatible controller: Intel Corp. 82865G Integrated Graphics Device (rev 02) 00: 86 80 72 25 07 00 90 00 02 00 00 03 00 00 00 00 10: 08 00 00 f0 00 00 a8 ff 01 ec 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 43 4c 30: 00 00 00 00 d0 00 00 00 00 00 00 00 0b 01 00 00 40: 00 00 00 00 0f 47 8c 23 00 00 00 00 00 00 00 00 50: 00 00 44 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 01 02 ff 00 00 00 71 02 50 20 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 24 08 00 00 24 08 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 3f 0e 28 00 00 00 00 00 00 00 00 d0: 01 00 21 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 2a 00 00 00 09 00 06 01 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 68 0f 03 00 00 00 00 00 00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02)00: 86 80 d2 24 05 00 80 02 02 00 03 0c 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 c8 00 00 00 00 00 00 00 00 00 00 86 80 43 4c 30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 2f 00 00 03 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 66 0f 05 00 00 00 00 00 00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02)00: 86 80 d4 24 05 00 80 02 02 00 03 0c 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 cc 00 00 00 00 00 00 00 00 00 00 86 80 43 4c 30: 00 00 00 00 00 00 00 00 00 00 00 00 05 02 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 2f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 66 0f 05 00 00 00 00 00 00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02)00: 86 80 d7 24 05 00 80 02 02 00 03 0c 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 d0 00 00 00 00 00 00 00 00 00 00 86 80 43 4c 30: 00 00 00 00 00 00 00 00 00 00 00 00 0a 03 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 2f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 66 0f 05 00 00 00 00 00 00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 (rev 02)00: 86 80 de 24 05 00 80 02 02 00 03 0c 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 d4 00 00 00 00 00 00 00 00 00 00 86 80 43 4c 30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 2f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 66 0f 05 00 00 00 00 00 00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) 00: 86 80 dd 24 06 01 90 02 02 20 03 0c 00 00 00 00 10: 00 fc a7 ff 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 43 4c 30: 00 00 00 00 50 00 00 00 00 00 00 00 09 04 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 01 58 c2 c9 00 00 00 00 0a 00 a0 20 00 00 00 00 60: 20 20 ff 01 00 00 00 00 01 00 00 00 00 00 08 c0 70: 00 00 c5 3f 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 80 00 00 88 83 40 00 66 0f 05 00 06 14 00 00 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev c2) 00: 86 80 4e 24 07 01 80 00 c2 00 04 06 00 00 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 20 b0 b0 80 22 20: 80 ff 80 ff f0 ff 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 02 40: 02 28 30 76 00 00 00 00 00 00 00 00 00 00 00 00 50: 02 64 73 00 00 00 00 00 50 01 34 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 01 00 02 00 00 00 c0 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 66 0f 05 00 00 00 4d 37 00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02) 00: 86 80 d0 24 0f 01 80 02 02 00 01 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 01 04 00 00 10 00 00 00 00 00 00 00 00 00 02 00 50: 00 00 00 00 00 00 00 00 01 05 00 00 10 00 00 00 60: 0b 03 0a 05 d0 00 00 00 09 80 80 09 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: ff fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 20 02 00 00 30 00 00 00 0d 00 00 00 00 03 01 00 b0: 00 00 00 00 00 00 00 00 00 00 00 08 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 86 21 00 00 00 0f 00 00 04 00 00 00 00 00 00 00 e0: 10 00 00 80 81 06 0f 14 33 22 11 00 00 00 67 45 f0: 00 00 40 00 04 00 00 00 66 0f 05 3e 00 00 00 02 00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02) 00: 86 80 db 24 07 00 88 02 02 8a 01 01 00 00 00 00 10: 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00 20: a1 ff 00 00 00 00 00 3f 00 00 00 00 86 80 43 4c 30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 01 00 00 40: 07 a3 07 a3 00 00 00 00 05 00 01 02 00 00 00 00 50: 00 00 00 00 11 10 00 00 00 00 00 00 00 00 00 00 60: 08 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 66 0f 05 00 00 00 00 00 00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage Controller (rev 02) 00: 86 80 d1 24 05 00 a0 02 02 8f 01 01 00 00 00 00 10: 01 e8 00 00 01 e4 00 00 01 e0 00 00 01 dc 00 00 20: 01 d8 00 00 00 00 00 00 00 00 00 00 86 80 43 4c 30: 00 00 00 00 00 00 00 00 00 00 00 00 0a 01 00 00 40: 00 80 00 80 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 01 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 05 70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 03 00 00 20 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 66 0f 05 00 00 00 00 00 00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) 00: 86 80 d3 24 01 00 80 02 02 00 05 0c 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 c4 00 00 00 00 00 00 00 00 00 00 86 80 43 4c 30: 00 00 00 00 00 00 00 00 00 00 00 00 03 02 00 00 40: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 66 0f 05 00 00 00 00 00 00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC''97 Audio Controller (rev 02) 00: 86 80 d5 24 06 00 90 02 02 00 01 04 00 00 00 00 10: 00 00 00 00 00 00 00 00 00 f8 a7 ff 00 f4 a7 ff 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 02 e0 30: 00 00 00 00 50 00 00 00 00 00 00 00 03 02 00 00 40: 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 01 00 c2 c9 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 66 0f 05 00 00 00 00 00 01:08.0 Ethernet controller: Intel Corp. 82562EZ 10/100 Ethernet Controller (rev 01) 00: 86 80 50 10 17 01 90 02 01 00 00 02 10 20 00 00 10: 00 f0 8f ff 01 bc 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 3a 30 30: 00 00 00 00 dc 00 00 00 00 00 00 00 09 01 08 38 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 01 00 22 fe e0: 00 40 00 3a 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 66 0f 05 00 00 00 00 00 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Tue, 4 Jan 2005, Stijn De Weirdt wrote:> hi all, > > first this is actually in reply to some other mails. > i provide the output of lspci -xxx, but also a part from X.0.log: it > shows the 0xffffffff that Ronald G. Minnich told about. if you want > more info, let me know. > (xen-2.0-testing tarball from 03/01/2005, 2.4.28, on slc3) > > X.0.log (final part): > > (**) I810(0): Depth 24, (--) framebuffer bpp 32 > (==) I810(0): RGB weight 888 > (==) I810(0): Default visual is TrueColor > (II) Loading sub module "int10" > (II) LoadModule: "int10" > (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a > (II) I810(0): initializing int10 > (WW) I810(0): Bad V_BIOS checksumthis is bad. It''s a warning but it should not be happening. It means the vga bios checksum was wrong. Do you get this if you boot without xen, i.e. standard linux?> (II) I810(0): Primary V_BIOS segment is: 0xc000 > (WW) System lacks support for changing MTRRs > (EE) I810(0): unknown type(0xffffffff)=0xffI forget where this EE comes from, but:> (II) I810(0): EAX=0x00004f00, EBX=0x00000000, ECX=0x00000000, EDX=0x00000000 > (II) I810(0): ESP=0x00000ffa, EBP=0x00000000, ESI=0x00000000, EDI=0x00002000 > (II) I810(0): CS=0xc000, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, GS=0x0000 > (II) I810(0): EIP=0x00000014, EFLAGS=0x00003200 > (II) I810(0): code at 0x000c0014: > e9 0d 14 27 40 00 b0 0a 30 30 49 42 4d 20 56 47 > 41 20 43 6f 6d 70 61 74 69 62 6c 65 20 42 49 4f > (II) stack at 0x00001ffa: > 00 06 00 00 00 32 > (II) I810(0): VESA BIOS not detectedAs I read this, the module loader tried to run the vga bios and failed, as it could not get to the actual BIOS code? That''s how it looks to me anyway. I have no idea: has anyone seen option rom access working under Xen? I have not, but I have not tried this recently. The VGA bios ROM is not accessible on my laptop, however. Does Xen currently allow a guest to set enable the option rom access and set the register (0x30 I think) for the option ram base address?> (EE) I810(0): VBE initialization failed.So you get this error, and ...> (II) UnloadModule: "i810" > (II) UnloadModule: "int10" > (II) UnloadModule: "vgahw" > (II) Unloading /usr/X11R6/lib/modules/libvgahw.a > (II) UnloadModule: "vbe" > (II) Unloading /usr/X11R6/lib/modules/libvbe.a > (II) UnloadModule: "int10" > (II) Unloading /usr/X11R6/lib/modules/linux/libint10.a > (EE) Screen(s) found, but none have a usable configuration.it unloads the modules since it can''t run the vga bios. ron ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Tue, 4 Jan 2005 08:34:19 -0700 (MST), Ronald G. Minnich <rminnich@lanl.gov> wrote:> > (WW) I810(0): Bad V_BIOS checksum > > this is bad. It''s a warning but it should not be happening. It means the > vga bios checksum was wrong. Do you get this if you boot without xen, i.e. > standard linux?yes, it''s actaully not that unfrequent.> > > (II) I810(0): Primary V_BIOS segment is: 0xc000 > > (WW) System lacks support for changing MTRRs > > (EE) I810(0): unknown type(0xffffffff)=0xff >i think this is much worse :)> I forget where this EE comes from, but: > > (II) I810(0): EAX=0x00004f00, EBX=0x00000000, ECX=0x00000000, EDX=0x00000000 > > (II) I810(0): ESP=0x00000ffa, EBP=0x00000000, ESI=0x00000000, EDI=0x00002000 > > (II) I810(0): CS=0xc000, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, GS=0x0000 > > (II) I810(0): EIP=0x00000014, EFLAGS=0x00003200 > > (II) I810(0): code at 0x000c0014: > > e9 0d 14 27 40 00 b0 0a 30 30 49 42 4d 20 56 47 > > 41 20 43 6f 6d 70 61 74 69 62 6c 65 20 42 49 4f > > (II) stack at 0x00001ffa: > > 00 06 00 00 00 32 > > (II) I810(0): VESA BIOS not detected > > As I read this, the module loader tried to run the vga bios and failed, as > it could not get to the actual BIOS code? That''s how it looks to me > anyway. > > I have no idea: has anyone seen option rom access working under Xen? I > have not, but I have not tried this recently. The VGA bios ROM is not > accessible on my laptop, however. > > Does Xen currently allow a guest to set enable the option rom access and > set the register (0x30 I think) for the option ram base address? > > > > (EE) I810(0): VBE initialization failed. > > So you get this error, and ... > > > (II) UnloadModule: "i810" > > (II) UnloadModule: "int10" > > (II) UnloadModule: "vgahw" > > (II) Unloading /usr/X11R6/lib/modules/libvgahw.a > > (II) UnloadModule: "vbe" > > (II) Unloading /usr/X11R6/lib/modules/libvbe.a > > (II) UnloadModule: "int10" > > (II) Unloading /usr/X11R6/lib/modules/linux/libint10.a > > (EE) Screen(s) found, but none have a usable configuration. > > it unloads the modules since it can''t run the vga bios. > > ron >i''ve attached a working X.0.log hopefully this gets resolved soon. stijn ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
attachment added On Tue, 4 Jan 2005 18:01:30 +0100, Stijn De Weirdt <stijn.deweirdt@gmail.com> wrote:> On Tue, 4 Jan 2005 08:34:19 -0700 (MST), Ronald G. Minnich > <rminnich@lanl.gov> wrote: > > > (WW) I810(0): Bad V_BIOS checksum > > > > this is bad. It''s a warning but it should not be happening. It means the > > vga bios checksum was wrong. Do you get this if you boot without xen, i.e. > > standard linux? > yes, it''s actaully not that unfrequent. > > > > > (II) I810(0): Primary V_BIOS segment is: 0xc000 > > > (WW) System lacks support for changing MTRRs > > > (EE) I810(0): unknown type(0xffffffff)=0xff > > > i think this is much worse :) > > > I forget where this EE comes from, but: > > > (II) I810(0): EAX=0x00004f00, EBX=0x00000000, ECX=0x00000000, EDX=0x00000000 > > > (II) I810(0): ESP=0x00000ffa, EBP=0x00000000, ESI=0x00000000, EDI=0x00002000 > > > (II) I810(0): CS=0xc000, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, GS=0x0000 > > > (II) I810(0): EIP=0x00000014, EFLAGS=0x00003200 > > > (II) I810(0): code at 0x000c0014: > > > e9 0d 14 27 40 00 b0 0a 30 30 49 42 4d 20 56 47 > > > 41 20 43 6f 6d 70 61 74 69 62 6c 65 20 42 49 4f > > > (II) stack at 0x00001ffa: > > > 00 06 00 00 00 32 > > > (II) I810(0): VESA BIOS not detected > > > > As I read this, the module loader tried to run the vga bios and failed, as > > it could not get to the actual BIOS code? That''s how it looks to me > > anyway. > > > > I have no idea: has anyone seen option rom access working under Xen? I > > have not, but I have not tried this recently. The VGA bios ROM is not > > accessible on my laptop, however. > > > > Does Xen currently allow a guest to set enable the option rom access and > > set the register (0x30 I think) for the option ram base address? > > > > > > > (EE) I810(0): VBE initialization failed. > > > > So you get this error, and ... > > > > > (II) UnloadModule: "i810" > > > (II) UnloadModule: "int10" > > > (II) UnloadModule: "vgahw" > > > (II) Unloading /usr/X11R6/lib/modules/libvgahw.a > > > (II) UnloadModule: "vbe" > > > (II) Unloading /usr/X11R6/lib/modules/libvbe.a > > > (II) UnloadModule: "int10" > > > (II) Unloading /usr/X11R6/lib/modules/linux/libint10.a > > > (EE) Screen(s) found, but none have a usable configuration. > > > > it unloads the modules since it can''t run the vga bios. > > > > ron > > > i''ve attached a working X.0.log > > hopefully this gets resolved soon. > > stijn >
no attachment? ron ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
the unzipped waits moderator approval stijn On Tue, 4 Jan 2005 10:08:29 -0700 (MST), Ronald G. Minnich <rminnich@lanl.gov> wrote:> no attachment? > > ron > >
On Tue, 4 Jan 2005, Stijn De Weirdt wrote:> On Tue, 4 Jan 2005 08:34:19 -0700 (MST), Ronald G. Minnich > <rminnich@lanl.gov> wrote: > > > (WW) I810(0): Bad V_BIOS checksum > > > > this is bad. It''s a warning but it should not be happening. It means the > > vga bios checksum was wrong. Do you get this if you boot without xen, i.e. > > standard linux? > yes, it''s actaully not that unfrequent. > > > > > (II) I810(0): Primary V_BIOS segment is: 0xc000 > > > (WW) System lacks support for changing MTRRs > > > (EE) I810(0): unknown type(0xffffffff)=0xff > > > i think this is much worse :) > > > I forget where this EE comes from, but: > > > (II) I810(0): EAX=0x00004f00, EBX=0x00000000, ECX=0x00000000, EDX=0x00000000 > > > (II) I810(0): ESP=0x00000ffa, EBP=0x00000000, ESI=0x00000000, EDI=0x00002000 > > > (II) I810(0): CS=0xc000, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, GS=0x0000 > > > (II) I810(0): EIP=0x00000014, EFLAGS=0x00003200 > > > (II) I810(0): code at 0x000c0014: > > > e9 0d 14 27 40 00 b0 0a 30 30 49 42 4d 20 56 47 > > > 41 20 43 6f 6d 70 61 74 69 62 6c 65 20 42 49 4f > > > (II) stack at 0x00001ffa: > > > 00 06 00 00 00 32 > > > (II) I810(0): VESA BIOS not detected > >This is the good one: (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a (II) I810(0): initializing int10 (WW) I810(0): Bad V_BIOS checksum (II) I810(0): Primary V_BIOS segment is: 0xc000 (II) I810(0): VESA BIOS detected (II) I810(0): VESA VBE Version 3.0 (II) I810(0): VESA VBE Total Mem: 16192 kB (II) I810(0): VESA VBE OEM: Intel(r)865G Graphics Chip Accelerated VGA BIOS (II) I810(0): VESA VBE OEM Software Rev: 1.0 (II) I810(0): VESA VBE OEM Vendor: Intel Corporation (II) I810(0): VESA VBE OEM Product: Intel(r)865G Graphics Controller (II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0 (II) I810(0): Integrated Graphics Chipset: Intel(R) 865G (--) I810(0): Chipset: "865G" So the checksum is wrong. But ... note that the VESA BIOS detected is not happening. I am pretty sure that what is going on is that the option rom is not getting mapped to 0xc0000 as required. I don''t see how the MTRR failure should really matter in this case. One thing that might matter: Linux (without Xen) probably does not enable BIOS shadowing for the 0xc0000 region, and probably does not even now use it as RAM. But under Xen, is that 0xc0000 set up as RAM or ... I have no idea, I have not looked at this part of the linux modes -- a disadvantage to mainly having done Plan 9 work so far. I also vaguely remember you can try to invoke X and tell it to NOT try to run the vga bios, have you tried that? there is no real need to run it. Sorry, I''m doing too much guessing here, I hope this helps. ron ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > I am pretty sure that what is going on is that the option rom is not > getting mapped to 0xc0000 as required. I don''t see how the MTRR failure > should really matter in this case. One thing that might matter: Linux > (without Xen) probably does not enable BIOS shadowing for the 0xc0000 > region, and probably does not even now use it as RAM. But under Xen, is > that 0xc0000 set up as RAM or ... I have no idea, I have not looked at > this part of the linux modes -- a disadvantage to mainly having done Plan > 9 work so far.is this what you are talking about? (taken from http://portolano.cs.washington.edu/projects/hydra/info/tech.html) More About the Kernel>From Power-On to Shell promptWhen the power is turned on, the CPU can recognizes only first 8K of ROM and RAM and the on-chip RAM are not defined. The address of the 8K of ROM starts from 0x0. First, the reset vector is taken at address 0x04 and the CPU starts executing instructions from that address specified by reset vector. The bootup routine(arch/m68knommu/kernel/head.S) initializes the on-chip RAM and copies the instructions that initialize RAM and ROM to the onchip RAM and branches to the onchip RAM. After finishing setting up RAM and ROM, it jumps back to the ROM(now, ROM''s starting address is changed to 0xc00000). Memory blocks are configured as in the table. is there a way i can do this myself (eg copy data from working system to file, start xen in runlevel 3, copy data to correct place, run startx)> > I also vaguely remember you can try to invoke X and tell it to NOT try to > run the vga bios, have you tried that? there is no real need to run it.from man i810 on my system: The driver makes use of the video BIOS to program video modes for the 830M and later. This limits the video modes that can be used to those provided by the video BIOS, and to those that will fit into the amount of video memory that the video BIOS is aware of. (mine is the 865G)> > Sorry, I''m doing too much guessing here, I hope this helps. >all small bits help> ron >stijn ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> I am pretty sure that what is going on is that the option rom is not > getting mapped to 0xc0000 as required. I don''t see how the MTRR failure > should really matter in this case. One thing that might matter: Linux > (without Xen) probably does not enable BIOS shadowing for the 0xc0000 > region, and probably does not even now use it as RAM.If the driver is accessing the BIOS region via /dev/mem, it should be working as expected. What version of Xen are you using? 2.0.2 has a number of improvements as regards X support. Ian ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
how can i find out if the driver uses /dev/mem? xen version is a testing version from 03/01/05 with 2.4.28 kernel i''ll try 2.0.2 now stijn On Wed, 05 Jan 2005 11:57:57 +0000, Ian Pratt <Ian.Pratt@cl.cam.ac.uk> wrote:> > I am pretty sure that what is going on is that the option rom is not > > getting mapped to 0xc0000 as required. I don''t see how the MTRR failure > > should really matter in this case. One thing that might matter: Linux > > (without Xen) probably does not enable BIOS shadowing for the 0xc0000 > > region, and probably does not even now use it as RAM. > > If the driver is accessing the BIOS region via /dev/mem, it > should be working as expected. > > What version of Xen are you using? 2.0.2 has a number of > improvements as regards X support. > > Ian >------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
just tried 2.0.2 binary, same errors stijn On Wed, 5 Jan 2005 14:53:04 +0100, Stijn De Weirdt <stijn.deweirdt@gmail.com> wrote:> how can i find out if the driver uses /dev/mem? > > xen version is a testing version from 03/01/05 with 2.4.28 kernel > i''ll try 2.0.2 now > > stijn > > > On Wed, 05 Jan 2005 11:57:57 +0000, Ian Pratt <Ian.Pratt@cl.cam.ac.uk> wrote: > > > I am pretty sure that what is going on is that the option rom is not > > > getting mapped to 0xc0000 as required. I don''t see how the MTRR failure > > > should really matter in this case. One thing that might matter: Linux > > > (without Xen) probably does not enable BIOS shadowing for the 0xc0000 > > > region, and probably does not even now use it as RAM. > > > > If the driver is accessing the BIOS region via /dev/mem, it > > should be working as expected. > > > > What version of Xen are you using? 2.0.2 has a number of > > improvements as regards X support. > > > > Ian > > >------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Wed, 5 Jan 2005, Stijn De Weirdt wrote:> More About the Kernel From Power-On to Shell prompt When the power is > turned on, the CPU can recognizes only first 8K of ROM and RAM and the > on-chip RAM are not defined. The address of the 8K of ROM starts from > 0x0. First, the reset vector is taken at address 0x04 and the CPU starts > executing instructions from that address specified by reset vector. The > bootup routine(arch/m68knommu/kernel/head.S) initializes the on-chip RAM > and copies the instructions that initialize RAM and ROM to the onchip > RAM and branches to the onchip RAM. After finishing setting up RAM and > ROM, it jumps back to the ROM(now, ROM''s starting address is changed to > 0xc00000). Memory blocks are configured as in the table.this is just 68k, i386 is utterly different.> > I also vaguely remember you can try to invoke X and tell it to NOT try to > > run the vga bios, have you tried that? there is no real need to run it. > from man i810 on my system: > The driver makes use of the video BIOS to program video modes for the> 830M and later. This limits the video modes that can be used to those > provided by the video BIOS, and to those that will fit into the amount > of video memory that the video BIOS is aware of. > (mine is the 865G)yes, but bios has done that. I have started X on several cards and told it not to run the vga bios and it works on some, not on others. ron ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Wed, 5 Jan 2005, Ian Pratt wrote:> If the driver is accessing the BIOS region via /dev/mem, it > should be working as expected.there is a very easy way to test. dd if=/dev/mem bs=65536 skip=12 count=1 of=somefile hexdump the first 16 bytes of somefile and send it to me, there should be a bios signature in there. If not, that''s an issue. Here''s what I get on my two machines: 0000000 aa55 eb40 217b 0076 0000 0000 0000 0000 0000000 aa55 eb74 374b 3034 e930 194c cc77 4956 on my xen laptop I get this: 0000000 aa55 e960 04c7 0000 0000 0000 0000 0000 which is encouraging. What happens on your i810 machine? ron ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Wed, 5 Jan 2005, Stijn De Weirdt wrote:> how can i find out if the driver uses /dev/mem?it''s not really a "driver" as such. Use strace to see what it''s doing. ron ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
what we might want to try is the testbios program from linuxbios, which is able to run the vga bios and will give pretty good debugging output. ron ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
on working machine 0000000 aa55 e951 987b 3030 3030 3030 3030 3030 on xen 0000000 0000 0000 0000 0000 0000 0000 0000 0000 stijn On Wed, 5 Jan 2005 09:38:15 -0700 (MST), Ronald G. Minnich <rminnich@lanl.gov> wrote:> what we might want to try is the testbios program from linuxbios, which is > able to run the vga bios and will give pretty good debugging output. > ron > >------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Wed, 5 Jan 2005, Stijn De Weirdt wrote:> on working machine > 0000000 aa55 e951 987b 3030 3030 3030 3030 3030 > > on xen > 0000000 0000 0000 0000 0000 0000 0000 0000 0000 > > stijnwell you just found your problem. Now the question becomes, why do I have a vga bios image and you don''t. I forget -- is this a laptop or a desktop? ron ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> on working machine > 0000000 aa55 e951 987b 3030 3030 3030 3030 3030 > > on xen > 0000000 0000 0000 0000 0000 0000 0000 0000 0000Bizarre. It''s hard to see why this doesn''t work. You are doing this within dom 0, right? Has you machine got a very strange e820 map or something? You might want to try 2.0-testing to see if that helps (there''s new e820 Xen support). Ian ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
the machine is a desktop, motherboard is a intel d865glc, 1GB ram, p4 just tried the latest xen-testing and xen-unstable and both give the same problem. for more sysinfo, i''ve added dmesg from xen0 and from my working kernel. if the problem is that /dev/mem doesn''t has the correct info after booting xen0, maybe i can copy the info from my working system to some file, and then load this file in the memory of xen0. how big is the bios file (and what are the correct dd commands ;) ? stijn On Wed, 05 Jan 2005 19:24:36 +0000, Ian Pratt <Ian.Pratt@cl.cam.ac.uk> wrote:> > on working machine > > 0000000 aa55 e951 987b 3030 3030 3030 3030 3030 > > > > on xen > > 0000000 0000 0000 0000 0000 0000 0000 0000 0000 > > Bizarre. > > It''s hard to see why this doesn''t work. You are doing this within > dom 0, right? > > Has you machine got a very strange e820 map or something? You > might want to try 2.0-testing to see if that helps (there''s new > e820 Xen support). > > Ian > >
On Thu, 6 Jan 2005, Stijn De Weirdt wrote:> if the problem is that /dev/mem doesn''t has the correct info after > booting xen0, maybe i can copy the info from my working system to some > file, and then load this file in the memory of xen0. how big is the > bios file (and what are the correct dd commands ;) ?you can possibly even hand the file to X11 and tell it to use that file as the bios image, not /dev/mem. not sure if X11 will let you do this; we do it with our bios emulator. ron ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> On Thu, 6 Jan 2005, Stijn De Weirdt wrote: > > > if the problem is that /dev/mem doesn''t has the correct info after > > booting xen0, maybe i can copy the info from my working > system to some > > file, and then load this file in the memory of xen0. how big is the > > bios file (and what are the correct dd commands ;) ? > > you can possibly even hand the file to X11 and tell it to use > that file as > the bios image, not /dev/mem. > > not sure if X11 will let you do this; we do it with our bios emulator.This might get you a stage further, but it will fail as soon as the driver tries to access the frame bufffer via /dev/mem. We really need to get to the bottom of whis this is failing on your system. Please can you post the output of ''xm dmesg''. Does the system otherwise work? Can you start other VMs OK? What''s he *oldest* version of Xen you''ve tried this with? (i.e. have you ever tried 2.0.1 or 2.0.0 ?) Thanks, Ian ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Thu, 6 Jan 2005, Ian Pratt wrote:> This might get you a stage further, but it will fail as soon as the > driver tries to access the frame bufffer via /dev/mem. We really need to > get to the bottom of whis this is failing on your system. Please can you > post the output of ''xm dmesg''.I should be clearer. What we do here is get vgabios into a file, and then tell our emulator to use the file as the ''C segment'' but to use /dev/mem for everything else. In that way we init the physical hardware. X11 ought to do this but I do not know if they support the option it at this point. It''s easy: our code is just mods to the X11 emulator. Is there any easy way to dump the mfn''s for a guest -- that would tell us right away what is going on -- we should see pfn 0xc0 map to mfn 0xc0, i.e. dom 0 physical c0000 maps to vga bios at machine 0xc0000. This is where having /proc/sys/xen/dom/#/{mem,mfn,etc} would be VERY handy :-) ron ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
no output from xm dmesg. so something else must be wrong (and probably my fault ;) output from xm dmesg after xend start (111, ''Connection refused'') Error: Error connecting to xend, is xend running? no so good /var/log/xend.log [2005-01-06 17:00:50 xend] INFO (SrvDaemon:607) Xend Daemon started /var/log/xend-debug.log xu_notifier_new() error connecting to xcs(ctrl)! (111) Traceback (most recent call last): File "/usr/sbin/xend", line 121, in ? sys.exit(main()) File "/usr/sbin/xend", line 107, in main return daemon.start() File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", line 522, in start self.run() File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", line 610, in run self.listenNotifier() File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", line 629, in listenNotifier p.startListening() File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", line 90, in startListening self._connectToProtocol() File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", line 108, in _connectToProtocol self.startReading() File "/usr/lib/python2.2/site-packages/twisted/internet/abstract.py", line 205 , in startReading self.reactor.addReader(self) File "/usr/lib/python2.2/site-packages/twisted/internet/pollreactor.py", line 89, in addReader self._updateRegistration(fd) File "/usr/lib/python2.2/site-packages/twisted/internet/pollreactor.py", line 52, in _updateRegistration poller.unregister(fd) ValueError: file descriptor cannot be a negative integer (-1) (i tried the writing to /dev/mem, and as ian guessed, it doesn''t solve it) stijn On Thu, 6 Jan 2005 08:51:00 -0700 (MST), Ronald G. Minnich <rminnich@lanl.gov> wrote:> > > On Thu, 6 Jan 2005, Ian Pratt wrote: > > > This might get you a stage further, but it will fail as soon as the > > driver tries to access the frame bufffer via /dev/mem. We really need to > > get to the bottom of whis this is failing on your system. Please can you > > post the output of ''xm dmesg''. > > I should be clearer. What we do here is get vgabios into a file, and then > tell our emulator to use the file as the ''C segment'' but to use /dev/mem > for everything else. In that way we init the physical hardware. X11 ought > to do this but I do not know if they support the option it at this point. > It''s easy: our code is just mods to the X11 emulator. > > Is there any easy way to dump the mfn''s for a guest -- that would tell us > right away what is going on -- we should see pfn 0xc0 map to mfn > 0xc0, i.e. dom 0 physical c0000 maps to vga bios at machine 0xc0000. > > This is where having /proc/sys/xen/dom/#/{mem,mfn,etc} would be VERY handy > :-) > > ron >------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> no output from xm dmesg. so something else must be wrong (and probably > my fault ;) > output from xm dmesg after xend startAs you guessed, this is a totally different problem. Where did you get your python and twisted install from? What versions are they? It looks like some kind of internal error. I''d like to get this problem fixed and see the ouput of ''xm dmesg'' and check that you''re able to start domains before dwelling on the X problem. Ian> (111, ''Connection refused'') > Error: Error connecting to xend, is xend running? > > no so good > > /var/log/xend.log > [2005-01-06 17:00:50 xend] INFO (SrvDaemon:607) Xend Daemon started > > /var/log/xend-debug.log > xu_notifier_new() > error connecting to xcs(ctrl)! (111) > Traceback (most recent call last): > File "/usr/sbin/xend", line 121, in ? > sys.exit(main()) > File "/usr/sbin/xend", line 107, in main > return daemon.start() > File > "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > line 522, in start > self.run() > File > "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > line 610, in run > self.listenNotifier() > File > "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > line 629, in listenNotifier > p.startListening() > File > "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > line 90, in startListening > self._connectToProtocol() > File > "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > line 108, in _connectToProtocol > self.startReading() > File > "/usr/lib/python2.2/site-packages/twisted/internet/abstract.py > ", line 205 > , in startReading > self.reactor.addReader(self) > File > "/usr/lib/python2.2/site-packages/twisted/internet/pollreactor > .py", line > 89, in addReader > self._updateRegistration(fd) > File > "/usr/lib/python2.2/site-packages/twisted/internet/pollreactor > .py", line > 52, in _updateRegistration > poller.unregister(fd) > ValueError: file descriptor cannot be a negative integer (-1)------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
If you are working out of the unstable tree you will need to reinstall the tools if you haven''t done so since the end of last week. We''ve added a switch for control messages below xend, and the error looks a bit like it isn''t running. a. On Thu, 6 Jan 2005 17:36:30 +0100, Stijn De Weirdt <stijn.deweirdt@gmail.com> wrote:> no output from xm dmesg. so something else must be wrong (and probably > my fault ;) > output from xm dmesg after xend start > > (111, ''Connection refused'') > Error: Error connecting to xend, is xend running? > > no so good > > /var/log/xend.log > [2005-01-06 17:00:50 xend] INFO (SrvDaemon:607) Xend Daemon started > > /var/log/xend-debug.log > xu_notifier_new() > error connecting to xcs(ctrl)! (111) > Traceback (most recent call last): > File "/usr/sbin/xend", line 121, in ? > sys.exit(main()) > File "/usr/sbin/xend", line 107, in main > return daemon.start() > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > line 522, in start > self.run() > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > line 610, in run > self.listenNotifier() > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > line 629, in listenNotifier > p.startListening() > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > line 90, in startListening > self._connectToProtocol() > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > line 108, in _connectToProtocol > self.startReading() > File "/usr/lib/python2.2/site-packages/twisted/internet/abstract.py", line 205 > , in startReading > self.reactor.addReader(self) > File "/usr/lib/python2.2/site-packages/twisted/internet/pollreactor.py", line > 89, in addReader > self._updateRegistration(fd) > File "/usr/lib/python2.2/site-packages/twisted/internet/pollreactor.py", line > 52, in _updateRegistration > poller.unregister(fd) > ValueError: file descriptor cannot be a negative integer (-1) > > (i tried the writing to /dev/mem, and as ian guessed, it doesn''t solve it) > > stijn > > On Thu, 6 Jan 2005 08:51:00 -0700 (MST), Ronald G. Minnich > <rminnich@lanl.gov> wrote: > > > > > > On Thu, 6 Jan 2005, Ian Pratt wrote: > > > > > This might get you a stage further, but it will fail as soon as the > > > driver tries to access the frame bufffer via /dev/mem. We really need to > > > get to the bottom of whis this is failing on your system. Please can you > > > post the output of ''xm dmesg''. > > > > I should be clearer. What we do here is get vgabios into a file, and then > > tell our emulator to use the file as the ''C segment'' but to use /dev/mem > > for everything else. In that way we init the physical hardware. X11 ought > > to do this but I do not know if they support the option it at this point. > > It''s easy: our code is just mods to the X11 emulator. > > > > Is there any easy way to dump the mfn''s for a guest -- that would tell us > > right away what is going on -- we should see pfn 0xc0 map to mfn > > 0xc0, i.e. dom 0 physical c0000 maps to vga bios at machine 0xc0000. > > > > This is where having /proc/sys/xen/dom/#/{mem,mfn,etc} would be VERY handy > > :-) > > > > ron > > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel >------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
i reinstalled the tools, this is from xm dmesg (the 2 cpu thing is very probably hyperthreading. i''ll turn it off in bios if it is needed) stijn __ __ ____ ___ \ \/ /___ _ __ |___ \ / _ \ \ // _ \ ''_ \ __) || | | | / \ __/ | | | / __/ | |_| | /_/\_\___|_| |_| |_____(_)___/ http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 2.0 (root@iihe.ac.be) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-42)) Thu Jan 6 14:28:31 CET 2005 Latest ChangeSet: information unavailable (XEN) Physical RAM map: (XEN) 0000000000000000 - 000000000009fc00 (usable) (XEN) 000000000009fc00 - 00000000000a0000 (reserved) (XEN) 00000000000e6000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000003ef2fc00 (usable) (XEN) 000000003ef2fc00 - 000000003ef30000 (ACPI NVS) (XEN) 000000003ef30000 - 000000003ef40000 (ACPI data) (XEN) 000000003ef40000 - 000000003eff0000 (ACPI NVS) (XEN) 000000003eff0000 - 000000003f000000 (reserved) (XEN) 00000000fecf0000 - 00000000fecf1000 (reserved) (XEN) 00000000fed20000 - 00000000feda0000 (reserved) (XEN) System RAM: 1006MB (1030968kB) (XEN) Xen heap: 10MB (10756kB) (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0 (XEN) CPU#0: Physical ID: 0, Logical ID: 0 (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 (XEN) found SMP MP-table at 000ff780 (XEN) ACPI: RSDP (v000 ACPIAM ) @ 0x000f61b0 (XEN) ACPI: RSDT (v001 INTEL D865GLC 0x20040622 MSFT 0x00000097) @ 0x3ef30000 (XEN) ACPI: FADT (v002 INTEL D865GLC 0x20040622 MSFT 0x00000097) @ 0x3ef30200 (XEN) ACPI: MADT (v001 INTEL D865GLC 0x20040622 MSFT 0x00000097) @ 0x3ef30300 (XEN) ACPI: ASF! (v016 LEGEND I865PASF 0x00000001 MSFT 0x0100000d) @ 0x3ef345b0 (XEN) ACPI: TCPA (v001 INTEL TBLOEMID 0x00000001 MSFT 0x00000097) @ 0x3ef34649 (XEN) ACPI: WDDT (v001 INTEL OEMWDDT 0x00000001 MSFT 0x0100000d) @ 0x3ef3467d (XEN) ACPI: DSDT (v001 INTEL D865GLC 0x00000001 MSFT 0x0100000d) @ 0x00000000 (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) Processor #0 Unknown CPU [15:3] APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) (XEN) Processor #1 Unknown CPU [15:3] APIC version 20 (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) (XEN) Using ACPI for processor (LAPIC) configuration information (XEN) Intel MultiProcessor Specification v1.4 (XEN) Virtual Wire compatibility mode. (XEN) OEM ID: Product ID: Springdale-G APIC at: 0xFEE00000 (XEN) I/O APIC #2 Version 32 at 0xFEC00000. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Processors: 2 (XEN) Using scheduler: Borrowed Virtual Time (bvt) (XEN) Initializing CPU#0 (XEN) Detected 2992.634 MHz processor. (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0 (XEN) CPU#0: Physical ID: 0, Logical ID: 0 (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 (XEN) CPU0 booted (XEN) enabled ExtINT on CPU#0 (XEN) ESR value before enabling vector: 00000000 (XEN) ESR value after enabling vector: 00000000 (XEN) Booting processor 1/1 eip 90000 (XEN) Initializing CPU#1 (XEN) masked ExtINT on CPU#1 (XEN) ESR value before enabling vector: 00000000 (XEN) ESR value after enabling vector: 00000000 (XEN) CPU1: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0 (XEN) CPU#1: Physical ID: 0, Logical ID: 1 (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 (XEN) CPU1 has booted. (XEN) Total of 2 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) Setting 2 in the phys_id_present_map (XEN) ...changing IO-APIC physical APIC ID to 2 ... ok. (XEN) init IO_APIC IRQs (XEN) ..TIMER: vector=0x41 pin1=2 pin2=0 (XEN) Using local APIC timer interrupts. (XEN) Calibrating APIC timer for CPU0... (XEN) ..... CPU speed is 2992.5762 MHz. (XEN) ..... Bus speed is 199.5050 MHz. (XEN) ..... bus_scale = 0x0000CC4F (XEN) checking TSC synchronization across CPUs: passed. (XEN) Time init: (XEN) .... System Time: 10701084ns (XEN) .... cpu_freq: 00000000:B25FF8F4 (XEN) .... scale: 00000001:562C68A6 (XEN) .... Wall Clock: 1105035408s 120000us (XEN) PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1 (XEN) PCI: Using configuration type 1 (XEN) PCI: Probing PCI hardware (XEN) PCI: Probing PCI hardware (bus 00) (XEN) PCI: Ignoring BAR0-3 of IDE controller 00:1f.1 (XEN) Transparent bridge - PCI device 8086:244e (XEN) PCI: Using IRQ router PIIX/ICH [8086/24d0] at 00:1f.0 (XEN) PCI->APIC IRQ transform: (B0,I2,P0) -> 16 (XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16 (XEN) PCI->APIC IRQ transform: (B0,I29,P1) -> 19 (XEN) PCI->APIC IRQ transform: (B0,I29,P2) -> 18 (XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16 (XEN) PCI->APIC IRQ transform: (B0,I29,P3) -> 23 (XEN) PCI->APIC IRQ transform: (B0,I31,P0) -> 18 (XEN) PCI->APIC IRQ transform: (B0,I31,P0) -> 18 (XEN) PCI->APIC IRQ transform: (B0,I31,P1) -> 17 (XEN) PCI->APIC IRQ transform: (B1,I8,P0) -> 20 (XEN) mtrr: v2.0 (20020519) (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.4,XEN_VER=2.0,VIRT_BASE=0xC0000000'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Kernel image: 00c00000->00f0991c (XEN) Initrd image: 00f0a000->016da000 (XEN) Dom0 alloc.: 01800000->21800000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c04528d4 (XEN) Init. ramdisk: c0453000->c0c23000 (XEN) Phys-Mach map: c0c23000->c0ca3000 (XEN) Page tables: c0ca3000->c0ca8000 (XEN) Start info: c0ca8000->c0ca9000 (XEN) Boot stack: c0ca9000->c0caa000 (XEN) TOTAL: c0000000->c1000000 (XEN) ENTRY ADDRESS: c0100000 (XEN) Scrubbing DOM0 RAM: ......done. (XEN) Initrd len 0x7d0000, start at 0xc0453000 (XEN) Scrubbing Free RAM: ...........done. (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen). On Thu, 6 Jan 2005 16:45:52 +0000, Andrew Warfield <andrew.warfield@gmail.com> wrote:> If you are working out of the unstable tree you will need to reinstall > the tools if you haven''t done so since the end of last week. We''ve > added a switch for control messages below xend, and the error looks a > bit like it isn''t running. > > a. > > On Thu, 6 Jan 2005 17:36:30 +0100, Stijn De Weirdt > <stijn.deweirdt@gmail.com> wrote: > > no output from xm dmesg. so something else must be wrong (and probably > > my fault ;) > > output from xm dmesg after xend start > > > > (111, ''Connection refused'') > > Error: Error connecting to xend, is xend running? > > > > no so good > > > > /var/log/xend.log > > [2005-01-06 17:00:50 xend] INFO (SrvDaemon:607) Xend Daemon started > > > > /var/log/xend-debug.log > > xu_notifier_new() > > error connecting to xcs(ctrl)! (111) > > Traceback (most recent call last): > > File "/usr/sbin/xend", line 121, in ? > > sys.exit(main()) > > File "/usr/sbin/xend", line 107, in main > > return daemon.start() > > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > > line 522, in start > > self.run() > > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > > line 610, in run > > self.listenNotifier() > > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > > line 629, in listenNotifier > > p.startListening() > > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > > line 90, in startListening > > self._connectToProtocol() > > File "/usr/lib/python2.2/site-packages/xen/xend/server/SrvDaemon.py", > > line 108, in _connectToProtocol > > self.startReading() > > File "/usr/lib/python2.2/site-packages/twisted/internet/abstract.py", line 205 > > , in startReading > > self.reactor.addReader(self) > > File "/usr/lib/python2.2/site-packages/twisted/internet/pollreactor.py", line > > 89, in addReader > > self._updateRegistration(fd) > > File "/usr/lib/python2.2/site-packages/twisted/internet/pollreactor.py", line > > 52, in _updateRegistration > > poller.unregister(fd) > > ValueError: file descriptor cannot be a negative integer (-1) > > > > (i tried the writing to /dev/mem, and as ian guessed, it doesn''t solve it) > > > > stijn > > > > On Thu, 6 Jan 2005 08:51:00 -0700 (MST), Ronald G. Minnich > > <rminnich@lanl.gov> wrote: > > > > > > > > > On Thu, 6 Jan 2005, Ian Pratt wrote: > > > > > > > This might get you a stage further, but it will fail as soon as the > > > > driver tries to access the frame bufffer via /dev/mem. We really need to > > > > get to the bottom of whis this is failing on your system. Please can you > > > > post the output of ''xm dmesg''. > > > > > > I should be clearer. What we do here is get vgabios into a file, and then > > > tell our emulator to use the file as the ''C segment'' but to use /dev/mem > > > for everything else. In that way we init the physical hardware. X11 ought > > > to do this but I do not know if they support the option it at this point. > > > It''s easy: our code is just mods to the X11 emulator. > > > > > > Is there any easy way to dump the mfn''s for a guest -- that would tell us > > > right away what is going on -- we should see pfn 0xc0 map to mfn > > > 0xc0, i.e. dom 0 physical c0000 maps to vga bios at machine 0xc0000. > > > > > > This is where having /proc/sys/xen/dom/#/{mem,mfn,etc} would be VERY handy > > > :-) > > > > > > ron > > > > > > > ------------------------------------------------------- > > The SF.Net email is sponsored by: Beat the post-holiday blues > > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > > It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/xen-devel > > >------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Thu, Jan 06, 2005 at 08:51:00AM -0700, Ronald G. Minnich wrote:> Is there any easy way to dump the mfn''s for a guest -- that would tell us > right away what is going on -- we should see pfn 0xc0 map to mfn > 0xc0, i.e. dom 0 physical c0000 maps to vga bios at machine 0xc0000.You could extend the guest''s debug handler to print entries from the mfn<->pfn translation tables. christian ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Thu, 6 Jan 2005, Christian Limpach wrote:> You could extend the guest''s debug handler to print entries from the > mfn<->pfn translation tables.good idea, I need to work more with linux guests anyway, I will try to look at that. ron ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
The python bug you sent is independent of the video problems -- the control switch doesn''t seem to be running. I''m looking at python dump that you sent:> error connecting to xcs(ctrl)! (111)do you see a process called xcs running in dom0? if not, can you run /usr/bin/xcs and send me any resulting errors? a. ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It''s fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel