[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] xl doesn't honour the parameter cpu_weight from my config file while xm does honour it
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="vdrserver for my clients" memory=768 maxmem=2048 vcpus=1 cpus="1" cpu_weight = 128 on_poweroff="destroy" on_reboot="restart" on_crash="destroy" localtime=0 keymap="de" builder="linux" bootloader="/usr/bin/pygrub" bootargs="" extra="console=hvc0 tmem cgroup_disable=memory independent_wallclock=1 iommu=soft" nographic=1 keymap = 'de' disk=[ 'phy:/dev/mapper/xenimages-vdrserver,xvda1,w', 'phy:/dev/mapper/xenimages-swap_vdrserver,xvda2,w', ] vif=[ 'mac=00:00:00:00:00:80,bridge=br0', ] pci = [ '06:00.0', '06:01.0', '00:12.2', '00:13.2'] --snip-- -- Gruß Dieter -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the >From field. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |