[Xen-bugs] [Bug 1771] New: [VT-D] xen panic when the second time to creating guest with a NIC assigned

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1771

           Summary: [VT-D] xen panic when the second time to creating guest
                    with a NIC assigned
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Windows
            Status: NEW
          Severity: normal
          Priority: P1
         Component: HVM
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: yongjie.ren@xxxxxxxxx


Xen will panic when the second time to creating guest with a NIC assigned.
If not using vt-d feature, using a vif in config file instead, the issue
doesn't occur. And we found that using SR-IOV NIC doesn't have this issue too.
Though the last line in the log shows "(XEN) Reboot in five seconds...",
domain0 always hangs here and couldn't boot up before physical poweroff and
poweron.
See xen call trace int the end of the bug description.

Reproduce steps:
1.prepare a config file with "pci = [ '07:01.0' ]" ; the NIC 07:01.0 is stubbed
using pciback in host.
2.xl create myconfig   ( to create a rehel6 guest)
3.in guest, run "shutdown -h now" to shutdown the guest.
4.xl create myconfig  ( to create a guest the second time)
5.you will see XEN panic.  ï¼?sometimes xen doesn't panic when creating the
guest, but it panic when you shutdown the guest in guest using 'shutdown -h
now')

Environment:
Service Arch (ia32/ia32e/IA64): ia32e
Guest Arch (ia32/ia32e/IA64): ia32e
Guest OS Type (Linux/Windows): Linux
xen-changeset:   23607:2f63562df1c4
xen-date:        Mon Jun 27 17:37:12 2011 +0100

pvops git:
commit 6d94b752e1363757f8eb4558e6f721a3e703cfe2
Author: Ian Campbell <ian.campbell@xxxxxxxxxx>
Date:   Wed Jun 1 16:48:15 2011 +0100

ioemu git:
commit e3073b9dbf3217f619a4537197067231111d400e
Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date:   Tue Jun 21 18:05:10 2011 +0100

xen call trace: (more details, pls see the attachment)

(XEN) irq.c:344: Dom4 callback via changed to Direct Vector 0xe9
(XEN) domctl.c:1056:d0 ioport_map:remove f_gport=c100 f_mport=d000 np=40
(XEN) domctl.c:1032:d0 ioport_map:add f_gport=c100 f_mport=d000 np=40
(XEN) irq.c:264: Dom4 PCI link 0 changed 5 -> 0
(XEN) irq.c:264: Dom4 PCI link 1 changed 10 -> 0
(XEN) irq.c:264: Dom4 PCI link 2 changed 11 -> 0
(XEN) irq.c:264: Dom4 PCI link 3 changed 5 -> 0
[ 1316.918699] mtrr: type mismatch for f0000000,2000000 old: write-back new:
write-combining
INIT: Id "co" respawning too fast: disabled for 5 minutes
(XEN) irq.c:1740: dom4: forcing unbind of pirq 16
(XEN) Assertion 'entry->next->prev == entry' failed at
/home/nightly/builds_xen_unstable/xen-src-23607-20:172
(XEN) ----[ Xen-4.2-unstable  x86_64  debug=y  Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e008:[<ffff82c480126fa3>] set_timer+0x18e/0x22b
(XEN) RFLAGS: 0000000000010013   CONTEXT: hypervisor
(XEN) rax: ffff83027fa730e0   rbx: 0000000000000000   rcx: ffff82c4802e0568
(XEN) rdx: ffff82c4802a7f18   rsi: 000001a4cce5a2be   rdi: ffff82c4802e0560
(XEN) rbp: ffff82c4802a7e20   rsp: ffff82c4802a7dd0   r8:  00000000000013f8
(XEN) r9:  ffff82c4802e0780   r10: ffff82c4802d96e0   r11: 000001a5cac828f0
(XEN) r12: ffff82c4802e0560   r13: 0000000000000000   r14: ffff82c4802e0600
(XEN) r15: ffff82c4802cff00   cr0: 000000008005003b   cr4: 00000000000026f0
(XEN) cr3: 000000004544b000   cr2: ffff88007d375d68
(XEN) ds: 002b   es: 002b   fs: 0000   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff82c4802a7dd0:
(XEN)    ffff82c4802e0600 000001a4cce5a2be 0000000000000082 ffff82c4802a7f18
(XEN)    ffff82c4802e0520 ffff8300bf658000 ffff8300bf657000 0000000001c9c380
(XEN)    ffff82c4802e0560 ffff82c48024f1c0 ffff82c4802a7ea0 ffff82c480121e7b
(XEN)    000001a4cb1bdf3e ffff82c4802e0540 ffff82c4801238a2 ffff83013ffe6638
(XEN)    ffff8300bf658000 0000000001c9c380 ffff83013ffd5c00 ffff82c4802e0600
(XEN)    ffffffffffffffff 0000000000000000 0000000000000000 ffffffffffffffff
(XEN)    ffff82c4802a7f18 ffff82c4802c4880 ffff82c4802a7ee0 ffff82c48012331a
(XEN)    ffff82c4802c4880 ffff82c4802a7f18 ffff8300bf657000 ffff8300bf658000
(XEN)    0000000000000002 ffff82c48024f1c0 ffff82c4802a7ef0 ffff82c480123351
(XEN)    ffff82c4802a7f10 ffff82c4801539c5 ffff82c480123351 0000000000000000
(XEN)    ffff82c4802a7d28 0000000000000000 0000000000000000 0000000000000000
(XEN)    0000000000000000 ffff88007fcc5f10 ffffffff81877070 0000000000000246
(XEN)    ffff88007fe73da0 ffff88007fcc5df0 0000000000000000 0000000000000000
(XEN)    ffffffff810093aa ffff88007fcc5f20 00000000deadbeef 00000000deadbeef
(XEN)    0000010000000000 ffffffff810093aa 000000000000e033 0000000000000246
(XEN)    ffff88007fcc5ef8 000000000000e02b 000000000000beef 000000000000beef
(XEN)    000000000000beef 000000000000beef 0000000000000000 ffff8300bf657000
(XEN)    0000000000000000 0000000000000000
(XEN) Xen call trace:
(XEN)    [<ffff82c480126fa3>] set_timer+0x18e/0x22b
(XEN)    [<ffff82c480121e7b>] schedule+0x132/0x61b
(XEN)    [<ffff82c48012331a>] __do_softirq+0x87/0x98
(XEN)    [<ffff82c480123351>] do_softirq+0x26/0x28
(XEN)    [<ffff82c4801539c5>] idle_loop+0x55/0x57
(XEN)    
(XEN) 
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Assertion 'entry->next->prev == entry' failed at
/home/nightly/builds_xen_unstable/xen-src-23607-20:172
(XEN) ****************************************
(XEN) 
(XEN) Reboot in five seconds...


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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