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 709] [XEN-HVM] xm-test hangs during enforce_dom0_cpus te

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 709] [XEN-HVM] xm-test hangs during enforce_dom0_cpus test
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 25 Jul 2006 08:24:19 -0700
Delivery-date: Tue, 25 Jul 2006 08:25:23 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-709-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
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

------- Comment #2 from ricardoz@xxxxxxxxxx  2006-07-25 08:24 -------
After I do Ctrl-c, I check xm list and there is only 1 cpu assigned to dom0 as
a result of the test not finishing. I just use "xm vcpu-set 0 16" to get my
cpus back. This has been working for my until right now that I tried it and
dom0 kernel panic.

vmxdom2:/usr/xen/xen-unstable.hg/tools/xm-test # Unable to handle kernel paging
request at fffffffffffffff8 RIP: 
PGD 103067 PUD 16f6067 PMD 0 
Oops: 0000 [1] SMP 
CPU 3 
Modules linked in: bridge iptable_filter ip_tables x_tables tun joydev st
sr_mod ide_cd cdrom ipv6 button battery ac dm_mod tg3 reiserfs fan thermal
processor serverworks sg sd_mod
Pid: 0, comm: swapper Not tainted #1
RIP: e030:[<ffff8800017fd078>] [<ffff8800017fd078>]
RSP: e02b:ffff88001231beb0  EFLAGS: 00010817
RAX: ffff880000017fd8 RBX: ffffffff801433f0 RCX: 000000000000010d
RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffffffff801433f0
RBP: 0000000000000000 R08: ffffffff80372ce8 R09: 0000000000000000
R10: ffff880000c0e410 R11: 0000000000000246 R12: ffff8800017fd070
R13: 0000000000000000 R14: ffff880000017e88 R15: ffff880000017e88
FS:  0000000000000000(0000) GS:ffffffff804ac180(0000) knlGS:0000000000000000
CS:  e033 DS: 002b ES: 002b
Process swapper (pid: 0, threadinfo ffff880000016000, task ffff880000c0e080)
Stack: ffffffff801136d8 ffff88001cfab540 0000000000000000 000000000000010d 
       ffffffff80150105 ffffffff804b5b00 0000000000008680 000000000000010d 
       ffff88001cfab540 ffffffff804b5b28 
Call Trace: <IRQ> <ffffffff801136d8>{smp_call_function_interrupt+79}
       <ffffffff80150105>{handle_IRQ_event+78} <ffffffff801501e8>{__do_IRQ+153}
       <ffffffff8010d61d>{do_IRQ+60} <ffffffff8023b1bb>{evtchn_do_upcall+134}
       <ffffffff8010b60a>{do_hypervisor_callback+30} <EOI>

Code: c8 3e 38 19 00 88 ff ff 30 01 2b 1d 00 88 ff ff 80 96 98 00 
RIP [<ffff8800017fd078>] RSP <ffff88001231beb0>
CR2: fffffffffffffff8
 <0>Kernel panic - not syncing: Aiee, killing interrupt handler!
 (XEN) Domain 0 crashed: rebooting machine in 5 seconds.

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

Xen-bugs mailing list