[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] transfer (v)CPU from Dom0 to DomU


  • To: xen-users@xxxxxxxxxxxxx
  • From: Yannick Barbeaux <ybarbeaux@xxxxxxxxx>
  • Date: Mon, 15 Oct 2012 15:44:56 +0200
  • Delivery-date: Mon, 15 Oct 2012 15:30:06 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

Hello,

As the title says, I am willing to transfer one CPU Core from my dom0 to one of my virtual machine.
I have not found any easy "how-to" explaining clearly the step-by-step procedure.

Here are the details of the CPU distribution:

dom0:/# xm vcpu-list 
Name                                ID  VCPU   CPU State   Time(s) CPU Affinity
Domain-0                             0     0     0   r--   12503.2 any cpu
Domain-0                             0     1     1   -b-    1136.3 any cpu
Domain-0                             0     2     -   --p       7.2 any cpu
Domain-0                             0     3     -   --p       1.3 any cpu
srv1.mydom.be                    1     0     2   -b-   24588.0 2
srv2.mydom.be                    9     0     3   -b-    8727.8 0,3

srv1 is hosting a mail server (postfix,cyrus) and running fine
srv2 is hosting a website (apache) and is sometimes very (too) busy. I added 1GB of memory in the xen config file and that helped but the limit is now the CPU load.

As dom0 (running debian 5.0.10) does not host many services, I think that only one core would be enough (CPU is 99% idle most of the time).

I am definitely not an expert using Xen so could someone explain me how to transfer CPU assignation?

Should I use VCPUs or only CPUs?

Here are the cpuinfo for all my domains: 
the actual situation is : dom0 has 2 processors while srv1 and srv2 have only one:

dom0:/# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU           X3220  @ 2.40GHz
stepping : 11
cpu MHz : 2400.166
cache size : 4096 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu de tsc msr pae cx8 apic mtrr cmov pat clflush acpi mmx fxsr sse sse2 ss ht nx constant_tsc pni ssse3
bogomips : 4802.91
clflush size : 64
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU           X3220  @ 2.40GHz
stepping : 11
cpu MHz : 2400.166
cache size : 4096 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu de tsc msr pae cx8 apic mtrr cmov pat clflush acpi mmx fxsr sse sse2 ss ht nx constant_tsc pni ssse3
bogomips : 4802.91
clflush size : 64
power management:

srv1:~# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU           X3220  @ 2.40GHz
stepping : 11
cpu MHz : 2400.084
cache size : 4096 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu de tsc msr pae cx8 apic cmov pat clflush acpi mmx fxsr sse sse2 ss ht nx constant_tsc up pni ssse3
bogomips : 4806.37
clflush size : 64
power management:


srv2:/# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU           X3220  @ 2.40GHz
stepping : 11
cpu MHz : 2400.082
cache size : 4096 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu de tsc msr pae cx8 apic cmov pat clflush acpi mmx fxsr sse sse2 ss ht nx constant_tsc up pni ssse3
bogomips : 4803.14
clflush size : 64
power management:


Thank you for your help,

Yannick
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.