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/
Home Products Support Community News


[Xen-bugs] [Bug 183] New: >1 virtual nics crashes domU

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 183] New: >1 virtual nics crashes domU
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 23 Aug 2005 19:35:49 +0000
Delivery-date: Tue, 23 Aug 2005 19:35:52 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: >1 virtual nics crashes domU
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: dykman@xxxxxxxxxx

Running FC3 dom0 and domUs on x86, setting nics=2 causes a crash during domU
Setting nics=1, the domU starts fine and networking seems to be fine.
This config worked fine with an older build.

hg tip:
changeset:   6333:648c366d588b393a5a0eaaf3a79c5ad9ce2ed79f
tag:         tip
user:        kaf24@xxxxxxxxxxxxxxxxxxxx
date:        Tue Aug 23 09:53:04 2005
summary:     Link xentop with ncurses. Distros generally do not ship

On the console:

INIT: Entering runlevel: 4
Entering non-interactive startup
Starting sysstat:  [  OK  ]
Checking for new hardware [  OK  ]
Applying iptables firewall rules: iptables-restore v1.2.11: iptables-restore:
unable to initializetable 'filter'

Error occurred at line: 3
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
Starting pcmcia:  [  OK  ]
Setting network parameters:  [  OK  ]
Bringing up loopback interface:  [  OK  ]
Bringing up interface eth0:  modprobe: FATAL: Module ip_tables not found.

[  OK  ]
Bringing up interface eth1:  Unable to handle kernel paging request at virtual
address c77c76c0
 printing eip:
*pde = ma 1b499067 pa 00022067
*pte = ma 00000000 pa 55555000
Oops: 0002 [#1]

xm dmesg shows:

(XEN) DOM9: (file=mm.c, line=461) Non-privileged attempt to map I/O space 
(XEN) (file=/home/dykman/Xen/3.unstable/x/xen-unstable.hg/xen/include/asm/mm.h,
line=201) Error pfn 0: rd=ffbd5080, od=ff194080, caf=80000003, taf=f0000003
(XEN) DOM9: (file=mm.c, line=349) Could not get page ref for pfn 0
(XEN) DOM9: (file=mm.c, line=2216) Could not get page for mach->phys update
(XEN) (file=grant_table.c, line=526) Bad handle (0).
(XEN) (file=grant_table.c, line=1071) Grant unref rd(9) ld(0) frm(13c36) 
(XEN) (file=grant_table.c, line=526) Bad handle (1).
(XEN) (file=grant_table.c, line=1071) Grant unref rd(9) ld(0) frm(13c32) 

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 183] New: >1 virtual nics crashes domU, bugzilla-daemon <=