On 07/29/11 13:36, bala suru wrote: Hello, if VM is running at localhost eg. your workstation, I do: % netstat -nlp; look for '127.0.0.1:590x' as libvirt assigns VNC ports automatically and in incremental order. (Note: this, however, is not a rule. And you can assign whatever port you want by hand.) ~~~ SNIP ~~~ tcp 0 0 localhost:5901 *:* LISTEN - ~~~ SNIP ~~~ Then I just use VNC client like % vncviewer localhost:5901; to connect to VM. Have you tried to hit a key or move the mouse? Console/screen might be in suspend mode in order to "save" power. Also, there might be few catches which depend on your setup. 1] are you sure VM has VNC console assigned? Use % virsh; and 'dumpxml <domain>' command to check out. ~~~ SNIP ~~~ <graphics type='vnc' port='5901' autoport='yes'/> ~~~ SNIP ~~~ 2] it might be password protected, TLS might be required etc. etc. If it's at remote host, I recommend to use SSH to tunnel VNC port. You can find how-to at internet. You can also use 'virt-manager' which is included as package in many distributions. Well, at least in Fedora, Debian and, I believe, Ubuntu. I hope lines above help you a bit. Regards, Zdenek -- Zdenek Styblik email: stybla(a)turnovfree.net jabber: stybla(a)jabber.turnovfree.net

? 2011?07?29? 19:36, bala suru ??: <snip> </snip> This means you don't configure a "vnc" graphic for your guest. See # virsh help vncdisplay For what the command does. Except the vnc method, you might want to use text console, do like below will work: 1. Add console=ttyS0,115200 to guest kernel line. 2. Add the following XML section to a domain. <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target port='0'/> </console> 3. # virsh start $domain 4. # virsh console $domain Osier