On Thu, Jun 07, 2007 at 03:00:58PM +0900, Masayuki Sunou wrote: > Hi > > When virt-mangager is set the following configuration and VM is created, > the console is not displayed automatically long time. > (it displays "The console is currently unavailable") > > 1. Set "Status monitoring" to long time.(ex: 60 seconds). > 2. Set "Automatically open consoles" to "For new domains". > > This patch fixes it by waiting start of the console.(like virt-install) This is bad - you can't have a while loop which sits for 5 seconds in an even handler in GTK because it will block all UI events from running. > Note: > # 5 seconds, .25 second sleeps > --> 5 : Virt-manager waits only for short time.(5 seconds) > Because virt-manager have a means to connect with a console > easily again. (unlike virt-install) The console code already has support for auto-connecting to the console with retries. When popping up the console it will retry after 125 ms, 250ms, 500ms, 1s, 2s and then every 2s upto 10 times. I'm interested to know what this isn't working for you ? Check the log file /root/.virt-manager/virt-manager.log which should show you messages every time it tries to open the console. The code for re-trying the console connection is in src/virtManager/console.py in the try_login() method. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
