I have started to migrate one CentOS5 machine from xen to kvm. The stability of the machine is much better (too much crashes with xen). I was used to do a "xm list" to get a list of clients. On the KVM machine I need to do a "virsh list". What I miss in that overview is the memory size of clients. I found "virsh dominfo <client>" but that is for just that one client (and I have several running). The same question for "xm top". I found that there seems to exist virt-top, but I could not find this in a repository for Centos5. virt-manager is a little overkill on this machine (it does work though but I like command line quick info). Theo
> What I miss in that overview is the memory size of clients. I found > "virsh dominfo <client>" but that is for just that one client (and I > have several running). > The same question for "xm top". I found that there seems to exist > virt-top, but I could not find this in a repository for Centos5. >For the memory thing off the top of my head I can't think of anything in a single command... but a quick virsh list | awk '$2 ~ /running/ {print $1}' | while read guest; do virsh dominfo $guest | grep memorything .... adapted slightly since that's untested and just quickly knocked out from rough memory shoudl help... With regards to virt-top that's on CentOS 6 .... for the underlying hosts you really want to be on C6 rather than C5 at this point due to much improved libvirt/kvm features - things like ksm and transparent huge pages are new and help... and then things like the newer scheduler and kernel is a bonus... Leave your guests on C5 or whatever they are on while you migrate sensibly... but there is no good reason for the hosts systems to be runnin C5 at this point... if you are only just starting to migrate form xen to kvm seriously get on C6 and do yourself a huge favour... James
Lamar Owen
2011-Dec-09 14:38 UTC
[CentOS] ESX to KVM on CentOS (was:Re: How to list virt machine size with virsh?)
On Friday, December 09, 2011 07:39:54 AM James Hogarth wrote:> Funny thing I went through a similar thing a ways back - but for me > was vmware esx 3.5 to centos 5.5James, I'd be interested in knowing some of how you handled the ESX to KVM migration, and some caveats you might have found along the way.