Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

last time I had virt-manager + Desktop on my centos server everything was fine then I removed desktop for more security. and after a while I installed it again and now when I open virt-manager it doesn't show the list of KVMs but it's connected and displays the details.

can anyone please explain how Can I fix it ?

share|improve this question
    
Explain what do you mean by saying it doesn't show the list of KVMs but it's connected and displays the details? What details does it show then? Also you don't really need GUI on your server, it's a server afterall. Simple virsh -c qemu:///system list --all would do. –  Ihor Kaharlichenko Aug 17 '12 at 10:25
    
Thanks, I mean by clicking on localhost (QEMU) It's pops a windows containing details. I could connect to virt-manager remotely and it works fine. I need GUI to create VMs. Thanks –  Zim3r Aug 17 '12 at 11:30
    
It contains details of what? Of the connection? Or does it show the list of kvm guests? Also, you can't connect to virt-manager since it is a GUI, but you can connect with it to a remote server, that's what I usually do to manage my hosts usually. –  Ihor Kaharlichenko Aug 17 '12 at 11:34
    
When I open virt-manager in my server from VNC, It shows the hypervisor connection but I also have 5 VMs running that it doesn't show those VMs. details is equal to right clicking on hypervisor connection and select details. –  Zim3r Aug 17 '12 at 11:37
add comment

1 Answer

up vote 2 down vote accepted

Assuming you KVM host server's (CentOS) IP is $SERVER.

Run the following in console:

localhost$ virsh -c qemu+ssh://$SERVER/system list --all

This should show the list of libvirt quests as seen from your PC. Here's an example output (taken from my server):

 ID Name                 Status
----------------------------------
  1 freebsd9             running
  3 router               running
  - node1                shut off

Now run this:

localhost$ ssh $SERVER
centos-server$ virsh -c qemu:///system list --all

This should show the list of libvirt quests as seen from the server. Here's an example output (taken from my server):

 ID Name                 Status
----------------------------------
  1 freebsd9             running
  3 router               running
  - node1                shut off

As you can see the outputs are pretty much the same, as they should be.

In your case both of them should list 5 running guests. If not, you can at least figure out "who's lying", the local vision or the remote one.

EDIT:

You don't need to connect to your CentOS server via VNC just to have virt-manager's GUI to config your KVM guests. As I already said having a GUI on the server installed is... weird, bad practice, etc.

Instead install virt-manager on your local PC and connect from it to the CentOS server. It even works faster since you don't work over vnc!

Just add a new remote connection via File > Add Connection menu of the virt-manager, then fill your connection details like this:

enter image description here

share|improve this answer
    
Thanks, listing VMs is not the only problem I want to edit them through virt-manager and something I noticed now is it works fine remotely but on It doesn't work through VNC in my server –  Zim3r Aug 17 '12 at 11:59
    
Thanks again. I tried this before but it's way too slow. I don't know why. SSH and VNC are OK but remote virt-manager is very slow. what do you think causes this? –  Zim3r Aug 17 '12 at 12:34
    
What exactly is very slow? GUI response? Locally running GUI applications will always perform better then the ones shown via some kind of remote desktop (VNC, RDP, whatever). From my experience managent of remote KVM-hosts in virt-manager performs are smooth as the local ones. –  Ihor Kaharlichenko Aug 17 '12 at 12:41
    
I can easily manage VMs via VNC but Yes GUI response in remote virt-manager is really a pain. –  Zim3r Aug 17 '12 at 12:50
    
That's exactly what I am suggesting to fix: run virt-manager locally and connect to the remote libvirt host instead of running virt-manager remotely via VNC but connecting to a local libvirt host. –  Ihor Kaharlichenko Aug 17 '12 at 12:52
show 1 more comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.