Hi all, I''ve a linux dom0, a dom1 winxp sp2 (WinXP) and another winxp sp2 with 2 vcpu (WinXP_02) Dom2 uses all the dom0 idle: I mean this vm uses too much resources, it seems something wrong in configuration. This is strange because the other win xp uses very few resources I''ll attach some useful output.. Suggestions? (domain (domid 4) (on_crash restart) (uuid f1bff0c3-812d-71e9-52e2-e107c7cb4943) (bootloader_args ) (vcpus 2) (name WinXP_02) (on_poweroff destroy) (on_reboot restart) (bootloader ) (maxmem 1526) (memory 1526) (shadow_memory 14) (cpu_weight 256) (cpu_cap 0) (features ) (on_xend_start ignore) (on_xend_stop ignore) (start_time 1191851529.85) (cpu_time 1146.68402986) (online_vcpus 2) (image (hvm (kernel /usr/lib/xen/boot/hvmloader) (boot c) (device_model /usr/lib/xen/bin/qemu-dm) (pae 1) (rtc_timeoffset 0) (usb 1) (notes (SUSPEND_CANCEL 1)) ) ) (status 2) (state r-----) (store_mfn 390654) (device (vif (bridge eth0) (mac 00:16:3e:06:e4:1f) (script vif-bridge) (uuid 3d0cff4d-cc7c-6934-d0c0-eb34841fa994) (backend 0) ) ) (device (vbd (uname phy:/dev/VolGroup00/WinXP_02) (uuid dfdbdf2d-edaa-d78d-2579-1d39cb50754e) (mode w) (dev hda:disk) (backend 0) (bootable 1) ) ) (device (vkbd (backend 0))) (device (vfb (vncunused 1) (type vnc) (uuid f7c06dbe-e869-7f05-9f91-d8850bc0566d) ) ) ) I changed the xen scheduler giving more weight to WinXP_02 but it wasn''t useful [root@localhost ~]# xm sched-credit Name ID Weight Cap Domain-0 0 256 0 WinXP 5 256 0 WinXP_02 4 512 0 [root@localhost ~]# xm vcpu-list Name ID VCPU CPU State Time(s) CPU Affinity Domain-0 0 0 0 r-- 822.8 any cpu Domain-0 0 1 0 --- 431.7 any cpu WinXP 5 0 0 -b- 139.1 any cpu WinXP 5 1 0 -b- 140.2 any cpu WinXP_02 4 0 0 --- 624.8 any cpu WinXP_02 4 1 1 r-- 621.8 any cpu _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hi all, I''ve a linux dom0, a dom1 winxp sp2 (WinXP) and another winxp sp2 > with 2 vcpu (WinXP_02) > Dom2 uses all the dom0 idle: I mean this vm uses too much resources, it > seems something wrong in configuration. > > This is strange because the other win xp uses very few resourcesAre the guests completely identical? It does seem strange that it''s using more resources if they''re the same.> I''ll attach some useful output..<snip>> I changed the xen scheduler giving more weight to WinXP_02 but it wasn''t > useful > [root@localhost ~]# xm sched-credit > Name ID Weight Cap > Domain-0 0 256 0 > WinXP 5 256 0 > WinXP_02 4 512 0Giving more weight to a domain will cause it to run more, not less. So increasing the weight would be expected to increase its CPU utilisation (see http://wiki.xensource.com/xenwiki/CreditScheduler).> [root@localhost ~]# xm vcpu-list > Name ID VCPU CPU State Time(s) CPU > Affinity > Domain-0 0 0 0 r-- 822.8 any cpu > Domain-0 0 1 0 --- 431.7 any cpu > WinXP 5 0 0 -b- 139.1 any cpu > WinXP 5 1 0 -b- 140.2 any cpu > WinXP_02 4 0 0 --- 624.8 any cpu > WinXP_02 4 1 1 r-- 621.8 any cpuIt says both domain 5''s CPUs are blocked on IO, which suggests they''re waiting for IO and therefore can''t run. It looks like domain 4 isn''t blocked on IO and so it''s continuing to run. By the way, it looks like you have two vcpus in dom0? That''s not usually necessary; giving dom0 just one vcpu should still enable it to serve other domains well and will leave more CPU time for other uses. Does that help you somewhat? What are you expected / wanting to happen? Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Reasonably Related Threads
- [Bug 777] New: Suspect bug in __do_replace()
- [Bug 777] Suspect bug in __do_replace()
- smbclient connection problem from MVS to Windows suspect EBCDIC to ASCII conversion problem
- Suspect error in windows version of 3.60
- Suspect error in windows version of 3.60