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-devel

Re: [Xen-devel] domU guest for xcp 0.1.1

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] domU guest for xcp 0.1.1
From: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Date: Tue, 16 Mar 2010 16:25:17 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Delivery-date: Tue, 16 Mar 2010 16:27:43 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=IU2BbPsojVG3HIevo6HcNTRicMHfuScyvKx9DtoRj4w=; b=xBhXT9RwYL/NJmEZgrAlHf20GOsihgoT7BjVjFQUhxUR0wBclM/UCwV8voTXP6ZX52 1kJQKtuivmUh9F69AZ2yDrjcTaGCGYya0ZvEJ072/r31gOHK/mwELLCsxwYIS9wPCoPl 7uO2HkNSOltPfmQFmrRKhd1xJOfCxFfYISAxk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=U3F5FGVFXDwUu3F25S4Wuy+gpXawIsCN6c9UnmX6PL0tlwWh2v9o4zaxLsTGWn36Ak 6e4QCm8JzLfhLsuuqn3JZoLTczO6fzab9dTqSrLzYiYdLfyRJaJv6Ewz+JFSgw0YC+t/ 8lhfEYkhNTvK4GpsbYpcYVDunF0Y6Ndtcf5ko=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100316152259.GO1878@xxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <29b32d341003141329v3c6a73c0y8030cf3c6736634c@xxxxxxxxxxxxxx> <29b32d341003141840x5a55e74sfb2eda56005e4f84@xxxxxxxxxxxxxx> <29b32d341003142030p1fe511d2ke30b8483ff8cc368@xxxxxxxxxxxxxx> <1268642688.8652.2792.camel@xxxxxxxxxxxxxxxxxxxxx> <29b32d341003150642o4e2620edsf154b19d78aa7f42@xxxxxxxxxxxxxx> <1268660645.10129.25070.camel@xxxxxxxxxxxxxxxxxxxxxx> <29b32d341003150646o4d215dfel1c2a2bc6d287edc@xxxxxxxxxxxxxx> <29b32d341003151904m2a992be5s74697d6047b864c6@xxxxxxxxxxxxxx> <1268725069.8652.4179.camel@xxxxxxxxxxxxxxxxxxxxx> <20100316152259.GO1878@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thanks Pasi. Back to pci passthrough debugging.

I enabled nic interface via ifconfig and it doesn't receive any interrupts. Driver in domU experiences tx timeout  and if I try to write to a disk in domU(i.e cat /proc/interrupts > /root/debugs) system never recovers. From dom0 cannot execute reboot/shutdown... have to use magic way to reboot the system. I looked into xen-devel forum for any possible soln(patch mentioned in the forum are all present in xen code I have). Inputs appreciated.

1. when dom0 is booted, device has irq 11 assigned

lspci -v on dom0

 Ethernet controller: Unknown device dead:face
        Subsystem: Unknown device dead:face
        Flags: bus master, medium devsel, latency 32, IRQ 11
        Memory at d0000000 (32-bit, non-prefetchable) [size=128M]

2. After domU boots up, irq is reassigned to 17 and it shares with usb/ide disk and other devices
lspci -v on dom0

 Ethernet controller: Unknown device dead:face
        Subsystem: Unknown device dead:face
        Flags: bus master, medium devsel, latency 32, IRQ 17
        Memory at d0000000 (32-bit, non-prefetchable) [size=128M]

lspci -v on domU

00:00.0 Ethernet controller: Device dead:face
        Subsystem: Device dead:face
        Flags: bus master, medium devsel, latency 32, IRQ 17
        Memory at d0000000 (32-bit, non-prefetchable) [size=128M]
        Kernel driver in use: ncr2f
        Kernel modules: ncr2f

cat /proc/interrupts from domU

# cat /proc/interrupts
           CPU0      
 17:          0  xen-pirq-pcifront  ncr2f0
502:       6336   xen-dyn-event     eth0
503:       2951   xen-dyn-event     blkif
504:        105   xen-dyn-event     hvc_console
505:         52   xen-dyn-event     pcifront
506:        351   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:       5949   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:          0   Machine check polls
ERR:          0
MIS:          0

After around 50 secs...

# cat /proc/interrupts
           CPU0      
 17:          0  xen-pirq-pcifront  ncr2f0
502:       7283   xen-dyn-event     eth0
503:       2951   xen-dyn-event     blkif
504:        121   xen-dyn-event     hvc_console
505:         52   xen-dyn-event     pcifront
506:        351   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:       6237   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:          0   Machine check polls
ERR:          0
MIS:          0

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