|
|
|
|
|
|
|
|
|
|
xen-users
[Xen-users] cannot start VM after 100 or so VMs have been started
Hi, all: Now, I do one test for xen-3.4.0. but met a strange problem
The test computer is: CPU: Inter(R) Core(TM)2 Duo CPU Memory: 4G Each VM (DomU): 1 vcpu. 16M mem
For 4G mem, except the Mem for xen use, if each VM use 16M mem, I can start almost 200 VMs. because 16M * 200 = almose 3.2 G, There're still have enough mem for xen use
I start VMs for 0 to 200. But I found any VM cannot be started after 106 VMs have been started.
the error message in /var/log/xen/xend.log is: [2009-11-26 18:34:17 3366] DEBUG (XendDomain:452) Adding Domain: 106 [2009-11-26 18:34:17 3366] DEBUG (XendDomainInfo:2496) XendDomainInfo.initDomain: 106 256 [2009-11-26
18:34:17 3366] DEBUG (XendDomainInfo:2520)
_initDomain:shadow_memory=0x0, memory_static_max=0x1000000,
memory_static_min=0x0.
[2009-11-26 18:34:17 3366] DEBUG (balloon:172) Balloon: 4480 KiB free; 0 to scrub; need 17408; retries: 20. [2009-11-26 18:34:17 3366] DEBUG (balloon:187) Balloon: setting dom0 target to 2316 MiB. [2009-11-26 18:34:17 3366] DEBUG (XendDomainInfo:1302) Setting memory target of domain Domain-0 (0) to 2316 MiB.
[2009-11-26 18:34:17 3366] DEBUG (balloon:166) Balloon: 17792 KiB free; need 17408; done. [2009-11-26 18:34:17 3366] INFO (image:173) buildDomain os=linux dom=106 vcpus=1 [2009-11-26 18:34:17 3366] DEBUG (image:661) domid = 106
[2009-11-26 18:34:17 3366] DEBUG (image:662) memsize = 16 [2009-11-26 18:34:17 3366] DEBUG (image:663) image = /tmp/xen-test/mini-os.gz [2009-11-26 18:34:17 3366] DEBUG (image:664) store_evtchn = 1
[2009-11-26 18:34:17 3366] DEBUG (image:665) console_evtchn = 2 [2009-11-26 18:34:17 3366] DEBUG (image:666) cmdline = [2009-11-26 18:34:17 3366] DEBUG (image:667) ramdisk = [2009-11-26 18:34:17 3366] DEBUG (image:668) vcpus = 1
[2009-11-26 18:34:17 3366] DEBUG (image:669) features = [2009-11-26 18:34:17 3366] DEBUG (image:670) flags = 0 [2009-11-26 18:34:17 3366] ERROR (XendDomainInfo:2578) XendDomainInfo.initDomain: exception occurred
Traceback (most recent call last): File "usr/lib/python2.6/site-packages/xen/xend/XendDomainInfo.py", line 2551, in _initDomain channel_details = self.image.createImage() File "usr/lib/python2.6/site-packages/xen/xend/image.py", line 156, in createImage
return self.createDomain() File "usr/lib/python2.6/site-packages/xen/xend/image.py", line 175, in createDomain result = self.buildDomain() File "usr/lib/python2.6/site-packages/xen/xend/image.py", line 979, in buildDomain
rc = LinuxImageHandler.buildDomain(self) File "usr/lib/python2.6/site-packages/xen/xend/image.py", line 683, in buildDomain vhpt = self.vhpt) Error: (1, 'Internal error', 'launch_vm: SETVCPUCONTEXT failed (rc=-1)\n')
[2009-11-26 18:34:17 3366] ERROR (XendDomainInfo:476) VM start failed If I destroy one VM, I can start it or another VM successfully. But the total num of VMs are almost 106.
Could anyone give me some hints? Many thanks!
|
好玩贺卡等你发,邮箱贺卡全新上线!_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [Xen-users] cannot start VM after 100 or so VMs have been started,
xen <=
|
|
|
|
|