http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1328
------- Comment #3 from ikedaj@xxxxxxxxxxxxxxxxx 2008-09-28 19:27 -------
Hi Tom,
I got it!
We havet to set "cpu" entry in /etc/xen/<Domain> to assign certain CPUs to one
VPU.
It can be also set with "xm vcpu-pin" from command line.
You can check its status using "xm vcpu-list".
This is my configuration;
-----------------------------------------------------------------
name = "dom-ua1"
uuid = "94d0f9b4-08f6-448c-8c9b-91ca999a5f4b"
maxmem = 2048
memory = 2048
vcpus = 1 # the number of vcpu is "1"
cpus = "0" # assigned cpus is allocated at "0"
bootloader = "/usr/bin/pygrub"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
vfb = [ "type=vnc,vncunused=1,keymap=ja" ]
disk = [ "phy:/dev/sdf1,xvda,w","tap:aio:/dev/sdf3,/dev/sdf,w!", ]
vif = [ "ip=192.168.201.146/24,mac=00:16:3e:13:32:27,bridge=xenbr0",
"ip=192.168.101.146/24,mac=00:16:3e:13:32:28,bridge=xenbr1",
"ip=192.168.102.146/24,mac=00:16:3e:13:32:29,bridge=xenbr2",
"ip=192.168.16.146/22,mac=00:16:3e:13:32:30,bridge=xenbr3", ]
-----------------------------------------------------------------
!!! NOTICE !!! :)
The live migration would work fine the above setting.
but if you call "xm vcpu-list" after migration,
you would find that the status of cpu is changed like "any cpu".
It seems that the live migration can not take over this configuration for now.
It might be improved with the latest version, I hope.
So, you had better to reset the cpu status with "xm vcpu-pin" after migration,
if not, the return migration would fail.
If you can confirm that this configuration can work fine,
close this buggzila, please.
Thanks!
--
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
|
Home