> 
> Also: have you put pci=nomsi in your DomU kernel line? 
I tried, did not change anything:
domU login: [   71.986115] e1000: eth1: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
[   72.801768] e1000: eth1: e1000_watchdog: NIC Link is Down
[   74.421975] e1000: eth1: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
[   75.232677] e1000: eth1:
 e1000_watchdog: NIC Link is Down
[   76.945332] e1000: eth1: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
[   77.749471] e1000: eth1: e1000_watchdog: NIC Link is Down
[   79.581691] e1000: eth1: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
> Or check with cat /proc/interrupts, whether you use 
> GSI or MSI interrupts...
The output of cat /proc/interrupts does not have any entries about "msi" or "gsi":
root@domU:~# cat /proc/interrupts | grep -ie gsi -ie msi
root@domU:~#
root@saturn:~# cat /proc/interrupts
           CPU0
  1:          2  xen-pirq-ioapic-edge  i8042
  8:          0  xen-pirq-ioapic-edge  rtc0
 
 9:          0  xen-pirq-ioapic-edge  acpi
 12:          4  xen-pirq-ioapic-edge  i8042
 14:         90  xen-pirq-ioapic-edge  pata_sis
 15:          0  xen-pirq-ioapic-edge  pata_sis
 17:       5311  xen-pirq-ioapic-level  sata_sis
 18:        201  xen-pirq-ioapic-level
 19:       2622  xen-pirq-ioapic-level  peth0
 20:         28  xen-pirq-ioapic-level  ohci_hcd:usb2
 21:          0  xen-pirq-ioapic-level 
 ohci_hcd:usb3
 22:          0  xen-pirq-ioapic-level  ohci_hcd:usb4
 23:          2  xen-pirq-ioapic-level  ehci_hcd:usb1
499:         14   xen-dyn-event     evtchn:xenstored
500:       5877   xen-dyn-event     evtchn:xenstored
502:          0   xen-dyn-virq      mce
505:          0   xen-dyn-virq      pcpu
506:      10874   xen-dyn-event     xenbus
507:          0   xen-dyn-ipi      
 callfuncsingle0
508:          0   xen-dyn-virq      debug0
509:          0   xen-dyn-ipi       callfunc0
510:          0   xen-dyn-ipi       resched0
511:      18433   xen-dyn-virq      timer0
NMI:          0   Non-maskable interrupts
LOC:          0   Local timer interrupts
SPU:          0   Spurious interrupts
PMI:          0   Performance monitoring
 interrupts
PND:          0   Performance pending work
RES:          0   Rescheduling interrupts
CAL:          0   Function call interrupts
TLB:          0   TLB shootdowns
TRM:          0   Thermal event interrupts
THR:          0   Threshold APIC interrupts
MCE:          0   Machine check exceptions
MCP:          3   Machine check polls
ERR:          0
MIS:          0
----- Originalnachricht
 -----
Von: Meister Schieber <
meisterschieber@xxxxxxxxx>
Gesendet: Mit, 8.9.2010 13:34
An: Pasi Kärkkäinen <
pasik@xxxxxx>
Cc: 
xen-users@xxxxxxxxxxxxxxxxxxxBetreff: AW: [Xen-users] Did anyone succeeded in installing xen 4.0.0 on Debian Lenny?
From: Pasi Kärkkäinen <
pasik@xxxxxx>
>How much memory does your domU have? If more than 3 GB, try with 2GB or less.
Dom0 has 2 GB total, domU has 128 MB reserved and "ballooning" is activated.
 > What's the mode you're using for xen pci backend driver in dom0 kernel? 
 To be honest, I do not really understand your question. I just
 installed and used the kernel which comes with the xen-system  (2.6.32-5). I was told it supports pcihide out of the box. I just added the line
 xen-pciback.hide=(09:00.0) to the grub-config.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxxhttp://lists.xensource.com/xen-users