Hello,
it''s my first time with Xen on a dual processor machine. Everything was
fine until I decided to assign 1 VCPU to Dom0 and pin it to CPU 1.
Since then Domain-0 only sees 1 CPU and no vcpu-set / vcpu-pin seems to
be able to get it back. When I boot the plain vanilla FC5 SMP kernel
then both CPUs are there.
I must be missing something obvious (and probably did something really
stupid) so please be kind with me...
Thanks for your help!
Cheers,
Andrej
Diagnostical info:
xm list --long
(domain
(domid 0)
(uuid 00000000-0000-0000-0000-000000000000)
(ssidref 0)
(vcpus 2)
(vcpu_avail 7)
(cpu_weight 1.0)
(memory 454)
(maxmem 454)
(name Domain-0)
(on_poweroff destroy)
(on_reboot restart)
(on_crash restart)
(state r-----)
(shutdown_reason poweroff)
(cpu_time 2629.21563207)
(online_vcpus 1)
)
root@vt ~]# grep cpu /etc/xen/xend-config.sxp
(dom0-cpus 0)
[root@vt ~]# xm info
system : Linux
host : vt.lan.intersales.de
release : 2.6.16-1.2096_FC5xen0
version : #1 SMP Wed Apr 19 05:49:52 EDT 2006
machine : i686
nr_cpus : 1
nr_nodes : 1
sockets_per_node : 1
cores_per_socket : 1
threads_per_core : 1
cpu_mhz : 2799
hw_caps :
bfebfbff:20100000:00000000:00000180:0000e4bd:00000000:00000001
total_memory : 503
free_memory : 30
xen_major : 3
xen_minor : 0
xen_extra : .0
xen_caps : xen-3.0-x86_32 hvm-3.0-x86_32
platform_params : virt_start=0xfc000000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.0 20060304 (Red Hat 4.1.0-3)
cc_compile_by : bhcompile
cc_compile_domain : build.redhat.com
cc_compile_date : Wed Apr 19 05:11:40 EDT 2006
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
joseph kacmarcik wrote:> >> it''s my first time with Xen on a dual processor machine. Everything >> was fine until I decided to assign 1 VCPU to Dom0 and pin it to CPU 1. >> Since then Domain-0 only sees 1 CPU and no vcpu-set / vcpu-pin seems >> to be able to get it back. When I boot the plain vanilla FC5 SMP >> kernel then both CPUs are there. >> I must be missing something obvious (and probably did something >> really stupid) so please be kind with me... > > check out @line 124 of /etc/xen/xend-config.sxp. should be in the form > of: (dom0-cpus n) > > where n is number of cpu''s available to the dom0. > > hope it helps. > joe >thanks joe, but - nope, checked that (it''s also in my initial mail). The value remains unchanged as ''0'', which according to the comments in this file means that all cpus will be used. Bye, Andrej _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> it''s my first time with Xen on a dual processor machine. Everything was > fine until I decided to assign 1 VCPU to Dom0 and pin it to CPU 1. > Since then Domain-0 only sees 1 CPU and no vcpu-set / vcpu-pin seems to > be able to get it back. When I boot the plain vanilla FC5 SMP kernel > then both CPUs are there. > I must be missing something obvious (and probably did something really > stupid) so please be kind with me...check out @line 124 of /etc/xen/xend-config.sxp. should be in the form of: (dom0-cpus n) where n is number of cpu''s available to the dom0. hope it helps. joe _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> thanks joe, but - nope, checked that (it''s also in my initial mail). The > value remains unchanged as ''0'', which according to the comments in this > file means that all cpus will be used.does your dom0 kernel config have CONFIG_SMP=y? try ''sudo xm dmesg | grep CPU'' if you can run domU''s on different cpu''s, the dom0 must be able to see more than one. joe _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
joseph kacmarcik wrote:> >> thanks joe, but - nope, checked that (it''s also in my initial mail). >> The value remains unchanged as ''0'', which according to the comments >> in this file means that all cpus will be used. > > does your dom0 kernel config have CONFIG_SMP=y? > > try ''sudo xm dmesg | grep CPU'' > > if you can run domU''s on different cpu''s, the dom0 must be able to see > more than one. > > joe >it must have CONFIG_SMP set since it worked initially until I started messing with vcpu-set / vcpu-pin. dmesg says: (XEN) Initializing CPU#0 (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K (XEN) CPU: L2 cache: 2048K (XEN) CPU: Physical Processor ID: 0 (XEN) CPU: Processor Core ID: 0 (XEN) Intel machine check reporting enabled on CPU#0. (XEN) CPU0: Intel P4/Xeon Extended MCE MSRs (24) available (XEN) CPU0: Thermal monitoring enabled (XEN) CPU0: Intel Genuine Intel(R) CPU 2.80GHz stepping 02 (XEN) Brought up 1 CPUs (XEN) Dom0 has maximum 1 VCPUs I think this must be some kind of "boot problem": I told Domain0 to use 1 CPU only. I can''t tell it to change it because I need Dom0 for this and it is seeing only one cpu... any more ideas? thx, Andrej _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> it must have CONFIG_SMP set since it worked initially until I started > messing with vcpu-set / vcpu-pin. > > dmesg says: > (XEN) Initializing CPU#0 > (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K > (XEN) CPU: L2 cache: 2048K > (XEN) CPU: Physical Processor ID: 0 > (XEN) CPU: Processor Core ID: 0 > (XEN) Intel machine check reporting enabled on CPU#0. > (XEN) CPU0: Intel P4/Xeon Extended MCE MSRs (24) available > (XEN) CPU0: Thermal monitoring enabled > (XEN) CPU0: Intel Genuine Intel(R) CPU 2.80GHz stepping 02 > (XEN) Brought up 1 CPUs > (XEN) Dom0 has maximum 1 VCPUs > > > I think this must be some kind of "boot problem": I told Domain0 to use > 1 CPU only. I can''t tell it to change it because I need Dom0 for this > and it is seeing only one cpu... > any more ideas?if you issue ''xm vcpu-set 0 2'' and reboot, do you still only see one cpu? failing that, i''d be stumped as well. does your lilo/grub kernel line have any options related to xen other than dom0_mem? joe _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
joseph kacmarcik wrote:> >> it must have CONFIG_SMP set since it worked initially until I started >> messing with vcpu-set / vcpu-pin. >> >> dmesg says: >> (XEN) Initializing CPU#0 >> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K >> (XEN) CPU: L2 cache: 2048K >> (XEN) CPU: Physical Processor ID: 0 >> (XEN) CPU: Processor Core ID: 0 >> (XEN) Intel machine check reporting enabled on CPU#0. >> (XEN) CPU0: Intel P4/Xeon Extended MCE MSRs (24) available >> (XEN) CPU0: Thermal monitoring enabled >> (XEN) CPU0: Intel Genuine Intel(R) CPU 2.80GHz stepping 02 >> (XEN) Brought up 1 CPUs >> (XEN) Dom0 has maximum 1 VCPUs >> >> >> I think this must be some kind of "boot problem": I told Domain0 to >> use 1 CPU only. I can''t tell it to change it because I need Dom0 for >> this and it is seeing only one cpu... >> any more ideas? > > if you issue ''xm vcpu-set 0 2'' and reboot, do you still only see one cpu? > > failing that, i''d be stumped as well. does your lilo/grub kernel line > have any options related to xen other than dom0_mem?tried that but didn''t help either... any more ideas? thx, Andrej _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users