[Xen-bugs] [Bug 1326] Unable to reboot/shutdown domU if dom0-cpus != 0

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

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


dan.foster@xxxxxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dan.foster@xxxxxxxxxxxxx




------- Comment #4 from dan.foster@xxxxxxxxxxxxx  2009-06-16 06:45 -------
I am seeing the same bug on a Dell PowerEdge 1900:

release                : 2.6.26-2-xen-amd64
version                : #1 SMP Fri May 29 00:30:34 UTC 2009
machine                : x86_64
nr_cpus                : 4
nr_nodes               : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 1995
hw_caps                :
bfebfbff:20100800:00000000:00000140:0004e33d:00000000:00000001
total_memory           : 2047
free_memory            : 1748
node_to_cpu            : node0:0-3
xen_major              : 3
xen_minor              : 2
xen_extra              : -1
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.3.1 (Debian 4.3.1-2)
cc_compile_by          : waldi
cc_compile_domain      : debian.org
cc_compile_date        : Sat Jun 28 09:32:18 UTC 2008
xend_config_format     : 4


Like with the above comment, this is running Debian Lenny. Using a 2.6.18
kernel allowed dom0-cpus to be != 0 and still reboot the guest.


-- 
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