WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

AW: AW: [Xen-users] Did anyone succeeded in installing xen 4.0.0 on Debi

To: Carsten Schiers <carsten@xxxxxxxxxx>
Subject: AW: AW: [Xen-users] Did anyone succeeded in installing xen 4.0.0 on Debian Lenny?
From: Meister Schieber <meisterschieber@xxxxxxxxx>
Date: Thu, 9 Sep 2010 11:03:40 +0000 (GMT)
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 09 Sep 2010 04:06:18 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s1024; t=1284030223; bh=BoOjoK9skGWPUjzDVlgQOEMlH6oWsnAryYvH23nQnoA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=FlNSjHuq5qGYAlDc7vUTqqUstZxDJdjDh7qvtQFWuYQNF1dMfyf1yUAoeu63h4FIt7V8AXkl9yZR/sBrB6RhrLZGDVpsDTslh83TqE6DpvuwtLaRzRpC9C5oouCVHXuHt8u4dBxsHn+0AYTGHdEeJE4BrkFqHiBcUsgxEATj1zo=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=ymail.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=wYqGQfFArwaM9qMUbM4ghjF93tb/eIqfRbRxlUQSoLwpIGyL7q+XI5ltbkepKfBQsotW8j/eXcD612NuY/lMY0Yf65WVdrXZSCmssJoiwt7saywl9syy92fh6n+V7OXb7t0YXlb1Pp/DjrE6bg6s/kNUP8hbngM2M8RcVP0Ntcg=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <13076439.301283948625001.JavaMail.root@uhura>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <13076439.301283948625001.JavaMail.root@uhura>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
From: Carsten Schiers <carsten@xxxxxxxxxx>
>
> 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@xxxxxxxxxxxxxxxxxxx
Betreff: 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users