From: Hirofumi Tsujimura <tsujimura.hirof@jp.fujitsu.com>
To: xen-devel@lists.xensource.com
Subject: a domain VTx with the VNIF does hang.
Date: Tue, 03 Oct 2006 17:19:23 +0900 [thread overview]
Message-ID: <45221D0B.9040406@jp.fujitsu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2604 bytes --]
Hi all, my name is Hirofumi Tsujimura.
We are porting and testing a PV-on-HVM in the IPF.
This is a first time to send mail.
I probably found the problem when I tested the VNIF.
My operation for the test is following.
1. create a domain VTx and attach the VNIF in it.
2. create a domain U.
3. send a packet to the domain VTx from the domain U with ping
command.
Then, the domain VTx does hang.
And, it outputs as follows.
The domain U and a domain 0 doesn't do hang.
EAX: c03c7000 EBX: 00000286 ECX: 00000286 EDX: da676000
ESI: 000004e2 EDI: 0000000a EBP: c03c7fb8 DS: 007b ES: 007b
CR0: 8005003b CR2: b7ee2044 CR3: 1a6af000 CR4: 000006d0
[<c0118f92>] __printk_ratelimit+0x8f/0x95
[<e08a6316>] xennet_get_responses+0xca/0x31c [xen_vnif]
[<c0103dc2>] do_IRQ+0x70/0x7a
[<e08a6851>] netif_poll+0x1c/0x60v [xen_vnif]
[<c0103dc2>] net_rx_action+0x35/0x7d
[<c011c47d>] __do_softirq+0x38/0x3f
[<c0103e94>] do_softirq+0x38/0x3f
=======================
[<c0103dc2>] do_IRQ+0x70/0x7a
[<c0102c1a>] common_interrupt+0x27/0x2b
[<c014b5d8>] kmem_cache_free+0x27/0x2b
[<c013dac4>] free_pgtables+0x31/0x63
[<c01421ab>] exit_mmap+0x6a/0xb6
[<c0115f53>] mmput+0x1f/0x76
[<c011a58d>] do_exit+0x173/0x32b
[<c011a7f7>] sys_exit_group+0x0/0xd
[<c01029f3>] sysenter_past_esp+0x54/0x75
printk: 64425470 messages suppressed.
netfront: rx->offset: 0, size: 4294967295
printk: 64601036 messages suppressed.
netfront: rx->offset: 0, size: 4294967295
*** Please look at screenshots about the detail of the log. ***
The test environment is as follows.
- Architecture : x86
- Xen change set: 11683
- Domain 0 : kernel2.6.16.29-xen
- Domain U : kernel2.6.16.29-xen
- Domain VTx : kernel2.6.16
Probably, a domain VTx with the VNIF does Hang when it recieves a packet
from some domain U or from some domain VTx with the VNIF.
Additionally, I similarly tested the VNIF in the following environments
today(On October 3 2006).
- Architecture : x86
- Xen change set: 11686
- Domain 0 : kernel2.6.16.29-xen
- Domain U : kernel2.6.16.29-xen
- Domain VTx : kernel2.6.16
As a result, a kernel of domain VTx with the VNIF does panic when I use
"xm network-attach domainVTx eth1" in a domain 0.
Even if that command succeeds, it similarly does hang when it recieves a
packet.
What's happend?
Thank you.
--
FUJITSU COMPUTER TECHNOLOGIES LIMITED
Development Dept. 5 Division 1
Hirofumi Tsujimura
E-MAIL: tsujimura.hirof@jp.fujitsu.com
[-- Attachment #2: Screenshot-1.png --]
[-- Type: image/png, Size: 104349 bytes --]
[-- Attachment #3: Screenshot-2.png --]
[-- Type: image/png, Size: 105192 bytes --]
[-- Attachment #4: Screenshot-3.png --]
[-- Type: image/png, Size: 104726 bytes --]
[-- Attachment #5: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2006-10-03 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 8:19 Hirofumi Tsujimura [this message]
2006-10-13 5:42 ` a domain VTx with the VNIF does hang Hirofumi Tsujimura
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=45221D0B.9040406@jp.fujitsu.com \
--to=tsujimura.hirof@jp.fujitsu.com \
--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.