From: Ritu kaur <ritu.kaur.us@gmail.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: domU guest for xcp 0.1.1
Date: Tue, 16 Mar 2010 16:25:17 -0700 [thread overview]
Message-ID: <29b32d341003161625w2969f2daib3408561920793d3@mail.gmail.com> (raw)
In-Reply-To: <20100316152259.GO1878@reaktio.net>
[-- Attachment #1.1: Type: text/plain, Size: 3599 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 3911 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-03-16 23:25 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 17:10 domU guest for xcp 0.1.1 Ritu kaur
2010-03-12 17:51 ` Pasi Kärkkäinen
2010-03-13 1:51 ` Ritu kaur
2010-03-13 11:18 ` Pasi Kärkkäinen
2010-03-13 16:09 ` Ritu kaur
2010-03-13 16:41 ` Pasi Kärkkäinen
2010-03-14 1:43 ` Ritu kaur
2010-03-14 9:04 ` pvops xen/master and xen/stable domU kernel compilation errors Pasi Kärkkäinen
2010-03-14 11:15 ` domU guest for xcp 0.1.1 Sander Eikelenboom
2010-03-14 20:29 ` Ritu kaur
2010-03-14 20:52 ` Sander Eikelenboom
2010-03-15 1:40 ` Ritu kaur
2010-03-15 3:30 ` Ritu kaur
2010-03-15 8:44 ` Ian Campbell
2010-03-15 13:42 ` Ritu kaur
2010-03-15 13:44 ` Ian Campbell
2010-03-15 13:46 ` Ritu kaur
2010-03-16 2:04 ` Ritu kaur
2010-03-16 7:37 ` Ian Campbell
2010-03-16 15:23 ` Pasi Kärkkäinen
2010-03-16 23:25 ` Ritu kaur [this message]
2010-03-17 18:44 ` Ritu kaur
2010-03-18 9:17 ` Ian Campbell
2010-03-18 13:43 ` Ritu kaur
2010-03-18 14:11 ` Ian Campbell
2010-03-18 14:23 ` Ritu kaur
2010-03-18 14:27 ` Ian Campbell
2010-03-18 14:32 ` Ian Campbell
2010-03-18 14:39 ` Konrad Rzeszutek Wilk
2010-03-18 15:28 ` Ritu kaur
2010-03-18 16:26 ` Konrad Rzeszutek Wilk
2010-03-19 15:27 ` Ritu kaur
2010-03-21 1:50 ` Ritu kaur
2010-03-21 17:22 ` Ritu kaur
2010-03-21 18:41 ` Pasi Kärkkäinen
2010-03-21 21:21 ` Ritu kaur
2010-03-22 8:58 ` Pasi Kärkkäinen
2010-03-22 21:02 ` Ritu kaur
2010-03-22 21:09 ` Pasi Kärkkäinen
2010-03-23 20:21 ` Ritu kaur
2010-03-26 19:11 ` Ritu kaur
2010-03-27 18:28 ` Ritu kaur
2010-03-27 18:43 ` Pasi Kärkkäinen
2010-03-28 1:32 ` Ritu kaur
2010-03-28 3:21 ` Ritu kaur
2010-03-28 11:34 ` Pasi Kärkkäinen
2010-03-28 11:55 ` Pasi Kärkkäinen
2010-03-31 0:28 ` Ritu kaur
2010-03-31 1:07 ` Ritu kaur
2010-03-31 6:30 ` Pasi Kärkkäinen
2010-03-31 13:15 ` Ritu kaur
2010-03-31 13:42 ` Konrad Rzeszutek Wilk
2010-03-31 13:55 ` Ritu kaur
2010-03-31 14:39 ` Pasi Kärkkäinen
2010-03-31 21:10 ` Ritu kaur
2010-04-01 12:48 ` Ritu kaur
2010-04-05 14:10 ` Ritu kaur
2010-04-05 17:00 ` Konrad Rzeszutek Wilk
2010-04-06 4:00 ` Ritu kaur
2010-04-06 6:03 ` Pasi Kärkkäinen
2010-04-06 13:31 ` Ritu kaur
2010-04-09 15:53 ` Ritu kaur
2010-04-11 17:11 ` Ritu kaur
2010-04-12 14:04 ` Konrad Rzeszutek Wilk
2010-04-12 22:14 ` Ritu kaur
2010-04-13 8:34 ` Ian Campbell
2010-04-13 22:06 ` Ritu kaur
2010-04-14 8:48 ` Ian Campbell
2010-03-28 11:33 ` Pasi Kärkkäinen
2010-03-31 23:23 ` Ritu kaur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29b32d341003161625w2969f2daib3408561920793d3@mail.gmail.com \
--to=ritu.kaur.us@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.