Frank Fricke
2004-Oct-06 09:26 UTC
[Xen-devel] No network-interface to the outside world in domain 0
Hi there!
First of all: Xen is great work! Thank you for that.
I''m maybe just getting somtething wrong here but the docs
don''t lead me further.
My domain-0 does not have a eth0 or similar. I am using a NIC wich requires the
"natsemi"
driver.
The driver is compiled as a module and states its usual messages when loaded
but no interface shows up. Also /proc/pci is completely empty. I also have tried
other
types of NICs - same effect: the module loads without any complains but
that''s all.
What do I do wrong? Does it only work with the epro100 cards?
...Frank
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel
Keir Fraser
2004-Oct-06 09:36 UTC
Re: [Xen-devel] No network-interface to the outside world in domain 0
Are you booting the right kernel? If you run ''uname -a'' your shoudl be running a kernel with suffix -xen0, not -xenU. -- Keir> Hi there! > > First of all: Xen is great work! Thank you for that. > > I''m maybe just getting somtething wrong here but the docs don''t lead me further. > > My domain-0 does not have a eth0 or similar. I am using a NIC wich requires the "natsemi" > driver. > The driver is compiled as a module and states its usual messages when loaded > but no interface shows up. Also /proc/pci is completely empty. I also have tried other > types of NICs - same effect: the module loads without any complains but that''s all. > > What do I do wrong? Does it only work with the epro100 cards? > > ...Frank > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Frank Fricke
2004-Oct-06 10:50 UTC
Re: [Xen-devel] No network-interface to the outside world in domain 0
Keir Fraser wrote:> Are you booting the right kernel? If you run ''uname -a'' your shoudl be > running a kernel with suffix -xen0, not -xenU.is it actually possible to boot right into xenU from grub? it''s definitely the xen0 wich i''m sitting on. btw i''m using the xen 2.0-"rc1" with linux-2.6.8.1 and i heavily changed the kernelconfig. in xen0, everything about hardware accessand stuff is enabled. maybe i enabled too much? i just noticed that i enabled CONFIG_XEN_NETDEV_FRONTEND _and_ CONFIG_XEN_NETDEV_BACKEND - could that be the problem? i''ll attach my config-xen0 here. ...Frank
Keir Fraser
2004-Oct-06 11:00 UTC
Re: [Xen-devel] No network-interface to the outside world in domain 0
> Keir Fraser wrote: > > Are you booting the right kernel? If you run ''uname -a'' your shoudl be > > running a kernel with suffix -xen0, not -xenU. > > is it actually possible to boot right into xenU from grub? it''s definitely > the xen0 wich i''m sitting on. > > btw i''m using the xen 2.0-"rc1" with linux-2.6.8.1 and i heavily changed the kernelconfig. > in xen0, everything about hardware accessand stuff is enabled. maybe i enabled too much? > i just noticed that i enabled CONFIG_XEN_NETDEV_FRONTEND _and_ > CONFIG_XEN_NETDEV_BACKEND - could that be the problem? i''ll attach my config-xen0 here.Unlikely. Hmm.. does a native 2.4 kernel boot okay on your machine? -- Keir ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Ian Pratt
2004-Oct-06 11:29 UTC
Re: [Xen-devel] No network-interface to the outside world in domain 0
> btw i''m using the xen 2.0-"rc1" with linux-2.6.8.1 and i heavily changed the kernelconfig. > in xen0, everything about hardware accessand stuff is > enabled. maybe i enabled too much?Just to recap, you''ve got a natsemi ethernet card which isn''t working as a module in domain 0, right? It''s possible the natsemi driver is technically buggy, and is making assumptions it oughtn''t but gets away with on plain x86. Have you another Ethernet card you can try? Alternatively, what happens if you compile the driver into the kernel rather than a module? [ I''d like to be able to ignore all bug reports on Ethernet cards which cost less than $10 ;-) ]> i just noticed that i enabled CONFIG_XEN_NETDEV_FRONTEND _and_ > CONFIG_XEN_NETDEV_BACKEND - could that be the problem? i''ll attach my config-xen0 here.This should be no problem at all. Ian ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
James Harper
2004-Oct-06 12:36 UTC
RE: [Xen-devel] No network-interface to the outside world in domain 0
> It''s possible the natsemi driver is technically buggy, and is > making assumptions it oughtn''t but gets away with on plain x86. > Have you another Ethernet card you can try? Alternatively, what > happens if you compile the driver into the kernel rather than a > module?FWIW, I use natsemi as a module on two different (but mostly identical) servers. I have seen a few odd problems which I think are related to pci problems with the onboard ethernet (tlan) driver but they otherwise work well. James ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Frank Fricke
2004-Oct-07 11:55 UTC
Re: [Xen-devel] No network-interface to the outside world in domain 0
Ian Pratt wrote:> Just to recap, you''ve got a natsemi ethernet card which isn''t > working as a module in domain 0, right?exactly. the driver initialisation-message shows up but the ''ethX: .....'' message does not.> It''s possible the natsemi driver is technically buggy, and is > making assumptions it oughtn''t but gets away with on plain x86. > Have you another Ethernet card you can try? Alternatively, what > happens if you compile the driver into the kernel rather than a > module? > > [ I''d like to be able to ignore all bug reports on Ethernet cards > which cost less than $10 ;-) ]The natsemi-card is an Netgear FA311 Rev A2. While it now is nearly as cheap as $10 it was not cheap as it was new some years ago. (I remember to have bought one in ''99 for $50 in an radioshaq(?)-shop in phoenix, az :-) I''ll attach dmesgs and /proc/pci from native 2.4, 2.6 and my 2.6-xen0. Sadly i have no really expensive NIC to test ;-) , but i''ll now try a FA311 Rev C1, a D-Link DFE-530TX and maybe one of that really cheap Realteks. And i''ll try to compile in the drivers.>>i just noticed that i enabled CONFIG_XEN_NETDEV_FRONTEND _and_ >>CONFIG_XEN_NETDEV_BACKEND - could that be the problem? i''ll attach my config-xen0 here. > > This should be no problem at all.yes. (below) Keir Fraser wrote:>>i just noticed that i enabled CONFIG_XEN_NETDEV_FRONTEND _and_ >>CONFIG_XEN_NETDEV_BACKEND - could that be the problem? i''ll attach my config-xen0 here. > > Unlikely. Hmm.. does a native 2.4 kernel boot okay on your machine?right - with only FRONTEND enabled nothing changes. 2.4.25 dmesg & /proc/pci is attached Thanks so far for caring - i''ll be back with success or more debug output :) Could you need some other output, too? ...Frank ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Frank Fricke
2004-Oct-07 13:32 UTC
Re: [Xen-devel] No network-interface to the outside world in domain 0
*argl* now with attachments even attached :)
...Frank
Keir Fraser
2004-Oct-07 13:56 UTC
Re: [Xen-devel] No network-interface to the outside world in domain 0
> xen-0 dmesg: > ... > PCI: Using configuration type Xen > Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: the driver ''system'' has been registered > PCI: System does not support PCI > PCI: System does not support PCI > ...There is your problem. For some reason the kernel is deciding that your machine is not PCI-capable. Rather unhelpfully, the kernel can print that message in three different places. The files concerned are: linux-2.6.8.1-xen0/arch/xen/i386/pci/irq.c linux-2.6.8.1-xen0/arch/xen/i386/pci/legacy.c linux-2.6.8.1-xen0/arch/xen/i386/pci/common.c You may want to edit the print statements to distinguish them, so that we can see which one(s) are actually being triggered. It looks like maybe raw_pci_ops == NULL, even though that should be impossible! At the same time the kernel prints ''Using configuration type Xen'' it should set raw_pci_ops to a non-NULL value. -- Keir ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Frank Fricke
2004-Oct-08 13:54 UTC
Re: [Xen-devel] No network-interface to the outside world in domain 0
Keir Fraser wrote:>> xen-0 dmesg: ... PCI: Using configuration type Xen Linux Plug and Play Support v0.97 (c) Adam Belay pnp: the driver >> ''system'' has been registered PCI: System does not support PCI PCI: System does not support PCI ... > > > There is your problem. For some reason the kernel is deciding that your machine is not PCI-capable.*grmbl* i really did not notice that %-}> Rather unhelpfully, the kernel can print that message in three different places. The files concerned are: > linux-2.6.8.1-xen0/arch/xen/i386/pci/irq.c linux-2.6.8.1-xen0/arch/xen/i386/pci/legacy.c > linux-2.6.8.1-xen0/arch/xen/i386/pci/common.c > > You may want to edit the print statements to distinguish them, so that we can see which one(s) are actually being > triggered. > > It looks like maybe raw_pci_ops == NULL, even though that should be impossible! At the same time the kernel prints > ''Using configuration type Xen'' it should set raw_pci_ops to a non-NULL value.here we go: --- linux-2.6.8.1-xen-sparse/arch/xen/i386/pci/direct.c.orig 2004-10-08 15:38:04.170446555 +0200 +++ linux-2.6.8.1-xen-sparse/arch/xen/i386/pci/direct.c 2004-10-07 18:18:03.000000000 +0200 @@ -75,7 +75,7 @@ static int __init pci_direct_init(void) { - printk(KERN_INFO "PCI: Using configuration type Xen\n"); + printk(KERN_INFO "PCI: Using configuration type Xen - raw_pci_ops = &pci_direct_xen is ''%p''\n",&pci_direct_xen); raw_pci_ops = &pci_direct_xen; return 0; } says: PCI: Using configuration type Xen - raw_pci_ops = &pci_direct_xen is ''c0349b40'' ---------------------------------------------------------------------------------------------------- --- arch/i386/pci/pcbios.c.orig 2004-10-08 15:34:01.782322532 +0200 +++ arch/i386/pci/pcbios.c 2004-10-08 14:36:49.918527521 +0200 @@ -478,7 +478,10 @@ && ((raw_pci_ops = pci_find_bios()))) { pci_probe |= PCI_BIOS_SORT; pci_bios_present = 1; + printk(KERN_INFO "XR: (pcbios.c::pci_pcbios_init) pci bios ''present'' here! raw_pci_ops: %p pci_probe %x\n", + raw_pci_ops,pci_probe); } else { + printk(KERN_INFO "XR: (pcbios.c::pci_pcbios_init) pci bios ''ABSENT'' here!"); } return 0; } says : XR: (pcbios.c::pci_pcbios_init) pci bios ''ABSENT'' here! ---------------------------------------------------------------------------------------------------- finally: XR: PCI: System does not support PCI (from legacy.c) XR: PCI: System does not support PCI (from common.c) ---------------------------------------------------------------------------------------------------- the full output is attached again. this time it was on a different machine with /lib/tls still in place but normally i ran it with thread local storage disabled. i''d like to debug this further for/with you if needed but i can not get back to you before october 19th. happy hacking.... :) ...Frank
Keir Fraser
2004-Oct-08 14:09 UTC
Re: [Xen-devel] No network-interface to the outside world in domain 0
Simple -- you should select ''Direct'' PCI access in your kernel config, not ''BIOS'' access. :-) I''ve checked in a fix to the configuration scripts so that a choice of PCI-access methods is no longer presented. -- Keir> Keir Fraser wrote: > >> xen-0 dmesg: ... PCI: Using configuration type Xen Linux Plug and Play Support v0.97 (c) Adam Belay pnp: the driver > >> ''system'' has been registered PCI: System does not support PCI PCI: System does not support PCI ... > > > > > > There is your problem. For some reason the kernel is deciding that your machine is not PCI-capable. > > *grmbl* i really did not notice that %-} > > > > Rather unhelpfully, the kernel can print that message in three different places. The files concerned are: > > linux-2.6.8.1-xen0/arch/xen/i386/pci/irq.c linux-2.6.8.1-xen0/arch/xen/i386/pci/legacy.c > > linux-2.6.8.1-xen0/arch/xen/i386/pci/common.c > > > > You may want to edit the print statements to distinguish them, so that we can see which one(s) are actually being > > triggered. > > > > It looks like maybe raw_pci_ops == NULL, even though that should be impossible! At the same time the kernel prints > > ''Using configuration type Xen'' it should set raw_pci_ops to a non-NULL value. > > here we go: > > --- linux-2.6.8.1-xen-sparse/arch/xen/i386/pci/direct.c.orig 2004-10-08 15:38:04.170446555 +0200 > +++ linux-2.6.8.1-xen-sparse/arch/xen/i386/pci/direct.c 2004-10-07 18:18:03.000000000 +0200 > @@ -75,7 +75,7 @@ > static int __init pci_direct_init(void) > { > > - printk(KERN_INFO "PCI: Using configuration type Xen\n"); > + printk(KERN_INFO "PCI: Using configuration type Xen - raw_pci_ops = &pci_direct_xen is ''%p''\n",&pci_direct_xen); > raw_pci_ops = &pci_direct_xen; > return 0; > } > > says: PCI: Using configuration type Xen - raw_pci_ops = &pci_direct_xen is ''c0349b40'' > ---------------------------------------------------------------------------------------------------- > > --- arch/i386/pci/pcbios.c.orig 2004-10-08 15:34:01.782322532 +0200 > +++ arch/i386/pci/pcbios.c 2004-10-08 14:36:49.918527521 +0200 > @@ -478,7 +478,10 @@ > && ((raw_pci_ops = pci_find_bios()))) { > pci_probe |= PCI_BIOS_SORT; > pci_bios_present = 1; > + printk(KERN_INFO "XR: (pcbios.c::pci_pcbios_init) pci bios ''present'' here! raw_pci_ops: %p pci_probe %x\n", > + raw_pci_ops,pci_probe); > } else { > + printk(KERN_INFO "XR: (pcbios.c::pci_pcbios_init) pci bios ''ABSENT'' here!"); > } > return 0; > } > > says : XR: (pcbios.c::pci_pcbios_init) pci bios ''ABSENT'' here! > ---------------------------------------------------------------------------------------------------- > > finally: > XR: PCI: System does not support PCI (from legacy.c) > XR: PCI: System does not support PCI (from common.c) > ---------------------------------------------------------------------------------------------------- > > > the full output is attached again. this time it was on a different machine with /lib/tls still in place > but normally i ran it with thread local storage disabled. i''d like to debug this further for/with you > if needed but i can not get back to you before october 19th. > happy hacking.... :) > > ...Frank > > > __ __ ____ ___ _ _ > \ \/ /___ _ __ |___ \ / _ \ | |__ ___| |_ __ _ > \ // _ \ ''_ \ __) || | | |__| ''_ \ / _ \ __/ _` | > / \ __/ | | | / __/ | |_| |__| |_) | __/ || (_| | > /_/\_\___|_| |_| |_____(_)___/ |_.__/ \___|\__\__,_| > > http://www.cl.cam.ac.uk/netos/xen > University of Cambridge Computer Laboratory > > Xen version 2.0-beta (root@emt.iis.fhg.de) (gcc version 3.4.1 (Mandrakelinux (Alpha 3.4.1-3mdk)) Thu Oct 7 16:34:10 CEST 2004 > > (XEN) Initialised 502MB memory (128752 pages) on a 502MB machine > (XEN) Xen heap size is 10784KB > (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) ACPI: RSDP (v000 PTLTD ) @ 0x000f7c50 > (XEN) ACPI: RSDT (v001 PTLTD RSDT 0x06040001 LTP 0x00000000) @ 0x1f6f757c > (XEN) ACPI: FADT (v001 FSC D156x 0x06040001 0x000f4240) @ 0x1f6f75ac > (XEN) ACPI: MADT (v001 FSC APIC 0x06040001 CSF 0x00000000) @ 0x1f6faf76 > (XEN) ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x06040001 LTP 0x00000001) @ 0x1f6fafd8 > (XEN) ACPI: DSDT (v001 FSC D156x 0x06040001 MSFT 0x0100000e) @ 0x00000000 > (XEN) ACPI: Local APIC address 0xfee00000 > (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) > (XEN) Processor #0 Pentium 4(tm) XEON(tm) APIC version 20 > (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) > (XEN) Processor #1 Pentium 4(tm) XEON(tm) APIC version 20 > (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) > (XEN) Using scheduler: Borrowed Virtual Time (bvt) > (XEN) Initializing CPU#0 > (XEN) Detected 2394.075 MHz processor. > (XEN) Found and enabled local APIC! > (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) SMP motherboard not detected. > (XEN) enabled ExtINT on CPU#0 > (XEN) ESR value before enabling vector: 00000000 > (XEN) ESR value after enabling vector: 00000000 > (XEN) Using local APIC timer interrupts. > (XEN) Calibrating APIC timer for CPU0... > (XEN) ..... CPU speed is 2394.0204 MHz. > (XEN) ..... Bus speed is 199.5015 MHz. > (XEN) ..... bus_scale = 0x0000CC4F > (XEN) Time init: > (XEN) .... System Time: 12132865ns > (XEN) .... cpu_freq: 00000000:8EB2AFA0 > (XEN) .... scale: 00000001:ABB8FC4B > (XEN) .... Wall Clock: 1097248978s 30000us > (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfd987, last bus=3 > (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: Discovered primary peer bus 01 [IRQ] > (XEN) PCI: Using IRQ router PIIX/ICH [8086/24d0] at 00:1f.0 > (XEN) PCI: Found IRQ 10 for device 00:1f.1 > (XEN) PCI: Sharing IRQ 10 with 00:1d.2 > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen-ELF header found: ''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=2.0,VIRT_BASE=0xC0000000,LOADER=generic,PT_MODE_WRITABLE'' > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Kernel image: 02800000->02aa4e84 > (XEN) Initrd image: 00000000->00000000 > (XEN) Dom0 alloc.: 02c00000->0ac00000 > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: c0100000->c03d33dc > (XEN) Init. ramdisk: c03d4000->c03d4000 > (XEN) Phys-Mach map: c03d4000->c03f4000 > (XEN) Page tables: c03f4000->c03f7000 > (XEN) Start info: c03f7000->c03f8000 > (XEN) Boot stack: c03f8000->c03f9000 > (XEN) TOTAL: c0000000->c0800000 > (XEN) ENTRY ADDRESS: c0100000 > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen). > > Linux version 2.6.8.1-xen0 (root@il108) (gcc version 3.4.1 (Mandrakelinux (Alpha 3.4.1-3mdk)) #2 Fri Oct 8 14:42:46 CEST 2004 > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 0000000008000000 (usable) > 0MB HIGHMEM available. > 128MB LOWMEM available. > On node 0 totalpages: 32768 > DMA zone: 4096 pages, LIFO batch:1 > Normal zone: 28672 pages, LIFO batch:7 > HighMem zone: 0 pages, LIFO batch:1 > DMI not present. > Built 1 zonelists > Kernel command line: root=/dev/hda7 ro console=tty0 vga=ask > Initializing CPU#0 > PID hash table entries: 1024 (order 10: 8192 bytes) > Xen reported: 2394.075 MHz processor. > Using tsc for high-res timesource > Console: colour VGA+ 80x25 > Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) > Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) > Memory: 126448k/131072k available (1839k kernel code, 4436k reserved, 715k data, 112k init, 0k highmem) > Checking if this processor honours the WP bit even in supervisor mode... Ok. > Calibrating delay loop... 4771.02 BogoMIPS > Security Scaffold v1.0.0 initialized > Mount-cache hash table entries: 512 (order: 0, 4096 bytes) > CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 > CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000 > CPU: Trace cache: 12K uops, L1 D cache: 8K > CPU: L2 cache: 512K > CPU: After all inits, caps: beebcbf1 00000000 00000000 00000080 > CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09 > Enabling unmasked SIMD FPU exception support... done. > Checking ''hlt'' instruction... disabled > NET: Registered protocol family 16 > PCI: Using configuration type Xen - raw_pci_ops = &pci_direct_xen is ''c0349b40'' > XR: (pcbios.c::pci_pcbios_init) pci bios ''ABSENT'' here!<6>Linux Plug and Play Support v0.97 (c) Adam Belay > pnp: the driver ''system'' has been registered > XR: PCI: System does not support PCI (from legacy.c) > XR: PCI: System does not support PCI (from common.c) > audit: initializing netlink socket (disabled) > audit(1097248978.540:0): initialized > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) > Initializing Cryptographic API > Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky > Xen virtual console successfully installed as ttyS > Event-channel device installed. > Initialising Xen netif backend > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx > pnp: the driver ''ide'' has been registered > hda: SAMSUNG SP0411N, ATA DISK drive > hdc: HL-DT-STDVD-ROM GDR8162B, ATAPI CD/DVD-ROM drive > Using anticipatory io scheduler > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > ide1 at 0x170-0x177,0x376 on irq 15 > hda: max request size: 1024KiB > hda: 78242976 sectors (40060 MB) w/2048KiB Cache, CHS=16383/255/63 > hda: hda1 hda4 < hda5 hda6 hda7 > > hdc: ATAPI 24X DVD-ROM drive, 256kB Cache > Uniform CD-ROM driver Revision: 3.20 > mice: PS/2 mouse device common for all mice > input: PC Speaker > serio: i8042 AUX port at 0x60,0x64 irq 12 > serio: i8042 KBD port at 0x60,0x64 irq 1 > input: AT Translated Set 2 keyboard on isa0060/serio0 > NET: Registered protocol family 2 > IP: routing cache hash table of 1024 buckets, 8Kbytes > TCP: Hash tables configured (established 8192 bind 16384) > NET: Registered protocol family 1 > NET: Registered protocol family 17 > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > VFS: Mounted root (ext3 filesystem) readonly. > Freeing unused kernel memory: 112k freed > > *************************************************************** > *************************************************************** > ** WARNING: Currently emulating unsupported memory accesses ** > ** in /lib/tls libraries. The emulation is very ** > ** slow, and may not work correctly with all ** > ** programs (e.g., some may ''Segmentation fault''). ** > ** TO ENSURE FULL PERFORMANCE AND CORRECT FUNCTION, ** > ** YOU MUST EXECUTE THE FOLLOWING AS ROOT: ** > ** mv /lib/tls /lib/tls.disabled ** > *************************************************************** > *************************************************************** > > Pausing... 5Pausing... 4Pausing... 3Pausing... 2Pausing... 1Continuing... > > Generic RTC Driver v1.07 > usbcore: registered new driver usbfs > usbcore: registered new driver hub > USB Universal Host Controller Interface driver v2.2 > EXT3 FS on hda7, internal journal > Adding 2104504k swap on /dev/hda1. Priority:-1 extents:1 > md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 > kjournald starting. Commit interval 5 seconds > EXT3 FS on hda5, internal journal > EXT3-fs: mounted filesystem with ordered data mode. > kjournald starting. Commit interval 5 seconds > EXT3 FS on hda6, internal journal > EXT3-fs: mounted filesystem with ordered data mode. > e100: Intel(R) PRO/100 Network Driver, 3.0.18 > e100: Copyright(c) 1999-2004 Intel Corporation > SCSI subsystem initialized > NET: Registered protocol family 10 > IPv6 over IPv4 tunneling driver > ioperm not fully supported - set iopl to 3 > ioperm not fully supported - ignore resource release > ioperm not fully supported - ignore resource release > ioperm not fully supported - set iopl to 3 > ioperm not fully supported - ignore resource release > ioperm not fully supported - ignore resource release > ioperm not fully supported - set iopl to 3 > ioperm not fully supported - ignore resource release > ioperm not fully supported - ignore resource release-=- MIME -=- This is a multi-part message in MIME format. --------------090902010109020707070802 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Keir Fraser wrote:>> xen-0 dmesg: ... PCI: Using configuration type Xen Linux Plug and Play Support v0.97 (c) Adam Belay pnp: the driver >> ''system'' has been registered PCI: System does not support PCI PCI: System does not support PCI ... > > > There is your problem. For some reason the kernel is deciding that your machine is not PCI-capable.*grmbl* i really did not notice that %-}> Rather unhelpfully, the kernel can print that message in three different places. The files concerned are: > linux-2.6.8.1-xen0/arch/xen/i386/pci/irq.c linux-2.6.8.1-xen0/arch/xen/i386/pci/legacy.c > linux-2.6.8.1-xen0/arch/xen/i386/pci/common.c > > You may want to edit the print statements to distinguish them, so that we can see which one(s) are actually being > triggered. > > It looks like maybe raw_pci_ops == NULL, even though that should be impossible! At the same time the kernel prints > ''Using configuration type Xen'' it should set raw_pci_ops to a non-NULL value.here we go: --- linux-2.6.8.1-xen-sparse/arch/xen/i386/pci/direct.c.orig 2004-10-08 15:38:04.170446555 +0200 +++ linux-2.6.8.1-xen-sparse/arch/xen/i386/pci/direct.c 2004-10-07 18:18:03.000000000 +0200 @@ -75,7 +75,7 @@ static int __init pci_direct_init(void) { - printk(KERN_INFO "PCI: Using configuration type Xen\n"); + printk(KERN_INFO "PCI: Using configuration type Xen - raw_pci_ops = &pci_direct_xen is ''%p''\n",&pci_direct_xen); raw_pci_ops = &pci_direct_xen; return 0; } says: PCI: Using configuration type Xen - raw_pci_ops = &pci_direct_xen is ''c0349b40'' ---------------------------------------------------------------------------------------------------- --- arch/i386/pci/pcbios.c.orig 2004-10-08 15:34:01.782322532 +0200 +++ arch/i386/pci/pcbios.c 2004-10-08 14:36:49.918527521 +0200 @@ -478,7 +478,10 @@ && ((raw_pci_ops = pci_find_bios()))) { pci_probe |= PCI_BIOS_SORT; pci_bios_present = 1; + printk(KERN_INFO "XR: (pcbios.c::pci_pcbios_init) pci bios ''present'' here! raw_pci_ops: %p pci_probe %x\n", + raw_pci_ops,pci_probe); } else { + printk(KERN_INFO "XR: (pcbios.c::pci_pcbios_init) pci bios ''ABSENT'' here!"); } return 0; } says : XR: (pcbios.c::pci_pcbios_init) pci bios ''ABSENT'' here! ---------------------------------------------------------------------------------------------------- finally: XR: PCI: System does not support PCI (from legacy.c) XR: PCI: System does not support PCI (from common.c) ---------------------------------------------------------------------------------------------------- the full output is attached again. this time it was on a different machine with /lib/tls still in place but normally i ran it with thread local storage disabled. i''d like to debug this further for/with you if needed but i can not get back to you before october 19th. happy hacking.... :) ...Frank --------------090902010109020707070802 Content-Type: text/plain; name="dbg_xen0_pci" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline; filename="dbg_xen0_pci" __ __ ____ ___ _ _ =20 \ \/ /___ _ __ |___ \ / _ \ | |__ ___| |_ __ _=20 \ // _ \ ''_ \ __) || | | |__| ''_ \ / _ \ __/ _` | / \ __/ | | | / __/ | |_| |__| |_) | __/ || (_| | /_/\_\___|_| |_| |_____(_)___/ |_.__/ \___|\__\__,_| =20 http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 2.0-beta (root@emt.iis.fhg.de) (gcc version 3.4.1 (Mandrakelinux (Alpha 3.4.1-3mdk)) Thu Oct 7 16:34:10 CEST 2004 (XEN) Initialised 502MB memory (128752 pages) on a 502MB machine (XEN) Xen heap size is 10784KB (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor =3D 0 (XEN) CPU#0: Physical ID: 0, Logical ID: 0 (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 (XEN) ACPI: RSDP (v000 PTLTD ) @ 0x000f7c50 (XEN) ACPI: RSDT (v001 PTLTD RSDT 0x06040001 LTP 0x00000000) @ 0x1f6f757c (XEN) ACPI: FADT (v001 FSC D156x 0x06040001 0x000f4240) @ 0x1f6f75ac (XEN) ACPI: MADT (v001 FSC APIC 0x06040001 CSF 0x00000000) @ 0x1f6faf76 (XEN) ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x06040001 LTP 0x00000001) @ 0x1f6fafd8 (XEN) ACPI: DSDT (v001 FSC D156x 0x06040001 MSFT 0x0100000e) @ 0x00000000 (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) Processor #0 Pentium 4(tm) XEON(tm) APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) (XEN) Processor #1 Pentium 4(tm) XEON(tm) APIC version 20 (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1]) (XEN) Using scheduler: Borrowed Virtual Time (bvt) (XEN) Initializing CPU#0 (XEN) Detected 2394.075 MHz processor. (XEN) Found and enabled local APIC! (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor =3D 0 (XEN) CPU#0: Physical ID: 0, Logical ID: 0 (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 (XEN) CPU0 booted (XEN) SMP motherboard not detected. (XEN) enabled ExtINT on CPU#0 (XEN) ESR value before enabling vector: 00000000 (XEN) ESR value after enabling vector: 00000000 (XEN) Using local APIC timer interrupts. (XEN) Calibrating APIC timer for CPU0... (XEN) ..... CPU speed is 2394.0204 MHz. (XEN) ..... Bus speed is 199.5015 MHz. (XEN) ..... bus_scale =3D 0x0000CC4F (XEN) Time init: (XEN) .... System Time: 12132865ns (XEN) .... cpu_freq: 00000000:8EB2AFA0 (XEN) .... scale: 00000001:ABB8FC4B (XEN) .... Wall Clock: 1097248978s 30000us (XEN) PCI: PCI BIOS revision 2.10 entry at 0xfd987, last bus=3D3 (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: Discovered primary peer bus 01 [IRQ] (XEN) PCI: Using IRQ router PIIX/ICH [8086/24d0] at 00:1f.0 (XEN) PCI: Found IRQ 10 for device 00:1f.1 (XEN) PCI: Sharing IRQ 10 with 00:1d.2 (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen-ELF header found: ''GUEST_OS=3Dlinux,GUEST_VER=3D2.6,XEN_VER=3D2=2E0,VIRT_BASE=3D0xC0000000,LOADER=3Dgeneric,PT_MODE_WRITABLE'' (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Kernel image: 02800000->02aa4e84 (XEN) Initrd image: 00000000->00000000 (XEN) Dom0 alloc.: 02c00000->0ac00000 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: c0100000->c03d33dc (XEN) Init. ramdisk: c03d4000->c03d4000 (XEN) Phys-Mach map: c03d4000->c03f4000 (XEN) Page tables: c03f4000->c03f7000 (XEN) Start info: c03f7000->c03f8000 (XEN) Boot stack: c03f8000->c03f9000 (XEN) TOTAL: c0000000->c0800000 (XEN) ENTRY ADDRESS: c0100000 (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen). Linux version 2.6.8.1-xen0 (root@il108) (gcc version 3.4.1 (Mandrakelinux (Alpha 3.4.1-3mdk)) #2 Fri Oct 8 14:42:46 CEST 2004 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000008000000 (usable) 0MB HIGHMEM available. 128MB LOWMEM available. On node 0 totalpages: 32768 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 28672 pages, LIFO batch:7 HighMem zone: 0 pages, LIFO batch:1 DMI not present. Built 1 zonelists Kernel command line: root=3D/dev/hda7 ro console=3Dtty0 vga=3Dask Initializing CPU#0 PID hash table entries: 1024 (order 10: 8192 bytes) Xen reported: 2394.075 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 126448k/131072k available (1839k kernel code, 4436k reserved, 715k data, 112k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 4771.02 BogoMIPS Security Scaffold v1.0.0 initialized Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: After all inits, caps: beebcbf1 00000000 00000000 00000080 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09 Enabling unmasked SIMD FPU exception support... done. Checking ''hlt'' instruction... disabled NET: Registered protocol family 16 PCI: Using configuration type Xen - raw_pci_ops =3D &pci_direct_xen is ''c0349b40'' XR: (pcbios.c::pci_pcbios_init) pci bios ''ABSENT'' here!<6>Linux Plug and Play Support v0.97 (c) Adam Belay pnp: the driver ''system'' has been registered XR: PCI: System does not support PCI (from legacy.c) XR: PCI: System does not support PCI (from common.c) audit: initializing netlink socket (disabled) audit(1097248978.540:0): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky Xen virtual console successfully installed as ttyS Event-channel device installed. Initialising Xen netif backend Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=3Dxx pnp: the driver ''ide'' has been registered hda: SAMSUNG SP0411N, ATA DISK drive hdc: HL-DT-STDVD-ROM GDR8162B, ATAPI CD/DVD-ROM drive Using anticipatory io scheduler ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 1024KiB hda: 78242976 sectors (40060 MB) w/2048KiB Cache, CHS=3D16383/255/63 hda: hda1 hda4 < hda5 hda6 hda7 > hdc: ATAPI 24X DVD-ROM drive, 256kB Cache Uniform CD-ROM driver Revision: 3.20 mice: PS/2 mouse device common for all mice input: PC Speaker serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 input: AT Translated Set 2 keyboard on isa0060/serio0 NET: Registered protocol family 2 IP: routing cache hash table of 1024 buckets, 8Kbytes TCP: Hash tables configured (established 8192 bind 16384) NET: Registered protocol family 1 NET: Registered protocol family 17 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 112k freed =20 *************************************************************** *************************************************************** ** WARNING: Currently emulating unsupported memory accesses ** ** in /lib/tls libraries. The emulation is very ** ** slow, and may not work correctly with all ** ** programs (e.g., some may ''Segmentation fault''). ** ** TO ENSURE FULL PERFORMANCE AND CORRECT FUNCTION, ** ** YOU MUST EXECUTE THE FOLLOWING AS ROOT: ** ** mv /lib/tls /lib/tls.disabled ** *************************************************************** *************************************************************** =20 Pausing... 5=08=08=08=08=08=08=08=08=08=08=08=08Pausing... 4=08=08=08=08=08=08=08=08=08=08=08=08Pausing... 3=08=08=08=08=08=08=08=08=08=08=08=08Pausing... 2=08=08=08=08=08=08=08=08=08=08=08=08Pausing... 1=08=08=08=08=08=08=08=08=08=08=08=08Continuing... Generic RTC Driver v1.07 usbcore: registered new driver usbfs usbcore: registered new driver hub USB Universal Host Controller Interface driver v2.2 EXT3 FS on hda7, internal journal Adding 2104504k swap on /dev/hda1. Priority:-1 extents:1 md: md driver 0.90.0 MAX_MD_DEVS=3D256, MD_SB_DISKS=3D27 kjournald starting. Commit interval 5 seconds EXT3 FS on hda5, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on hda6, internal journal EXT3-fs: mounted filesystem with ordered data mode. e100: Intel(R) PRO/100 Network Driver, 3.0.18 e100: Copyright(c) 1999-2004 Intel Corporation SCSI subsystem initialized NET: Registered protocol family 10 IPv6 over IPv4 tunneling driver ioperm not fully supported - set iopl to 3 ioperm not fully supported - ignore resource release ioperm not fully supported - ignore resource release ioperm not fully supported - set iopl to 3 ioperm not fully supported - ignore resource release ioperm not fully supported - ignore resource release ioperm not fully supported - set iopl to 3 ioperm not fully supported - ignore resource release ioperm not fully supported - ignore resource release --------------090902010109020707070802-- ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel