search for: cpu_weight

# HG changeset patch # User Lutz.Dube # Node ID ca2c8c262dbaa6b2521cec60af7cd688dabdf850 # Parent 8992134dcfd0b9e1e86f4111e68a8aa48bd33c3c Values of cpu_weight and cpu_cap are lost after xend restart For managed domains in state ''halted'' I always get default values for cpu_cap / cpu_weight after xend restart. This is because the names of parameters differ between a SXP file to create a VM (here the parameter names are cpu_cap / cpu_weig...

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU config looks like this: --snip-- name="vdrserver" description="vdrser...

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU config looks like this: --snip-- name="vdrserver" description="vdrser...

Currently with the credit scheduler, cpu_weight cannot be assigned to guest domains at boot time.(it can be set with xm sched-weight after booting) This patch allows CPU weight, and CAP to be set by the Xen configuration files. Specification: The following can be added to the Xen configuration files. 1.CPU WEIGHT [OPTIONAL] cpu_weight = cpu...

Hi, all, is cpu_weight parameter working for hvm domU? Thanks. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, This patch fixes the Bug:835 issue. # xm create /home/kanno/smp-domU.conf cpu_weight=512 cpu_cap=150 Using config file "/home/kanno/smp-domU.conf". Started domain vm1-smp # xm sched-credit -d vm1-smp {''cap'': 150, ''weight'': 512} Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com> Best regards, Kan __________________...

...''t RESTART be semantically the same as SHUTDOWN && CREATE ?! Regards, Volker > > > That may well be the case, but it probably takes a bit more digging > > before that can be solved. > > It actually works. It was my fault. > > I tested it by setting cpu_weight in the config and the RESTARTING the > domain. This did not read the new value but use the last one. > SHUTDOWN and CREATE does recognize the new value in the config file. > > Sorry to bother you. > > Regards > Dominik > > _____________________________________________...

...ys "Error: cap is out of range". Vcpu cannot be set higher than 1 - regardless of boot/config/command line. Low performance is equivalent to the cap setting. See ''xm list --long'': (domain (domid 0) (uuid 00000000-0000-0000-0000-000000000000) (vcpus 8) (cpu_weight 1.0) (memory 256) (shadow_memory 0) (maxmem 256) (features ) (name Domain-0) (on_poweroff destroy) (on_reboot restart) (on_crash restart) (state r-----) (shutdown_reason poweroff) (cpu_time 458.198750944) (online_vcpus 8) ) (domain (domid 5) (...

Are there any examples of bvt scheduler parameters usage? If I understand it right, bvt provides me with option to scale domain''s CPU usage. Eg. I have 2 (non-zero) domains pinned to the same CPU. Can I assign eg. 30% of CPU time to domain 1 and 70% to domain 2? (I mean in peaks when both domains are not idle and require the CPU time) If yes, how should I build the "xm bvt"

...ance. Again, this is only true if your xen version supports cpu_cap. > 2. if i have 2 domu, one with vcpu=4 and second with vcpu=1, they will have > same perfomance if one of them is idle, and half of perfomance if they are > both loaded? No, see above. If both domUs have the same vcpus, cpu_weight, and cpu_cap, then the answer is yes. > > 3. the only way to limit load is cpu_cap and for QOS is cpu_weight? vcpus and cpu_cap can limit cpu load. Note that there are other factors that can affect system load, one of the them is disk I/O. > > 3. May be you mistake with: > >&gt...

...n PV while the domU on Xen4CentOS reports itself as Xen HVM. == First domU == virt-what and cPanel scripts report domU as: xenpv dom0: 2.6.18-371.6.1.el5xen Xen 4.1.2 domU Config: bootloader = '/usr/bin/pygrub' extra = '' memory = 6144 hostname = 'web2.x.ca' cpu_weight = 256 name = 'vm115' vif = ['ip=205.X.X.X, vifname=vifvm115.0, mac=00:16:3e:7a:X:X'] vnc = 0 vcpus = 6 vncviewer = 0 serial = 'pty' disk = ['phy:/dev/xen/vm115_img,xvda1,w', 'phy:/dev/xen/vm115_swap,xvda2,w'] domU kernel:...

...1032], [''uuid'', ''784a8298-94bb-ff8a-edb3-6053a67fca75''], [''memory'', 31], [''name'', ''Dom2N7mig''], [''ssidref'', 0], [''vcpus'', 1], [''vcpu_avail'', 1], [''cpu_weight'', 1.0], [''on_poweroff'', ''destroy''], [''on_reboot'', ''restart''], [''on_crash'', ''restart''], [''maxmem'', 31], [''image'', [''linux'', ['...

.../vmlinuz-2.6.16-1-xen-vserver-686'], ['ip', ':1.2.3.4:::10-1-1-138:eth0:on'], ['root', '/dev/hda1'], ['args', '3']], 'on_poweroff': None, 'cpus': None, 'name': 'vm01', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'vcpu_avail': None, 'memory': 128, 'device': [('vbd', ['vbd', ['uname', 'file:/vserver/images/vm01.img'], ['dev', 'hda1'], ['mode', 'w']]), ('vbd', ['vbd', ['uname', 'file...

.../vmlinuz-2.6.16-1-xen-vserver-686'], ['ip', ':1.2.3.4:::10-1-1-138:eth0:on'], ['root', '/dev/hda1'], ['args', '3']], 'on_poweroff': None, 'cpus': None, 'name': 'vm01', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'vcpu_avail': None, 'memory': 128, 'device': [('vbd', ['vbd', ['uname', 'file:/vserver/images/vm01.img'], ['dev', 'hda1'], ['mode', 'w']]), ('vbd', ['vbd', ['uname', 'file...

...d.XendDomainInfo 31150] DEBUG (XendDomainInfo:200) XendDomainInfo.create([''domain'', [''domid'', 26], [''uuid'', ''xxxxxx-c425-7b20-8207-xxxxxxxxxxxx''], [''vcpus'', 1], [''vcpu_avail'', 1], [ ''cpu_weight'', 1.0], [''memory'', 1000], [''shadow_memory'', 0], [''maxmem'', 1000], [''features'', ''''], [''name'', ''auto-input-vm1''], [''on_poweroff'', ''destroy&...

...tally discover a quite useful feature in the Xen HVM configuration file. I here by suggest it to be added in the example file located at </usr/share/doc/xen-utils-common/examples/xmexample.hvm.gz>. It seems that you can configure Xen 3.1's Credit-Based CPU Scheduler by adding settings cpu_weight=128 and cpu_cap=20 in the configuration file itself. Though I haven't located any references to this feature from Xen's documentation or anywhere at the internet. More information about the Xen Credit Scheduler at <http://wiki.xensource.com/xenwiki/CreditScheduler>. PS: I discove...

...e xen 3.2 running on an 8 core server. I tried to set xm sched-credit -d mydomain --weight=1024 --cap=800 and got: Error: cap is out of range. I thought 8 cores are 800% ?! So, do I have du use 100 (for 100%) instead of 800 (for 100%)? And what about vcpus in my domu config? Must I set vcpus when cpu_weight is set? If yes (e.g. vcpus = 2) does this restrict cpu_weight only to 2 cpus?? Very confusing :) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...ards, Kan diff -r 2a8eaba24bf0 tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py Tue Feb 26 15:11:51 2008 +0000 +++ b/tools/python/xen/xend/XendDomainInfo.py Thu Feb 28 18:27:49 2008 +0900 @@ -1406,9 +1406,6 @@ class XendDomainInfo: def setWeight(self, cpu_weight): self.info[''vcpus_params''][''weight''] = cpu_weight - def setResume(self, state): - self._resume = state - def getRestartCount(self): return self._readVm(''xend/restart_count'') ______________________________...

...mainInfo:177) XendDomainInfo.create([''domain'', [''domid'', 5], [''uuid'', ''1d7f1bb2-eaa8-f7ff-bc2a-92097a3ac24e''], [''ssidref'', 0], [''vcpus'', 1], [''vcpu_avail'', 1], [''cpu_weight'', 1.0], [''memory'', 1 28], [''maxmem'', 128], [''name'', ''vmintraweb1''], [''on_poweroff'', ''destroy''], [''on_reboot'', ''restart''], [''on_crash'...

Hi List, (Long time lecher, first time poster) Not sure if this is the best place to ask, but here goes.. I have a few test Guests on a Xen host, and I would like to start monitoring (and maybe restricting) the network traffic of the guests but not the Host. No I know this can be done with iptables, but I just wondered if anyone knew of a package or how-to to set this up with Xen on CentOS 5 ?