From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: KVM console dying
Date: Mon, 21 Apr 2008 15:45:17 -0300
Message-ID: <20080421184517.GA7402@dmt>
References: <20080421181936.GA7100@dmt> <480CDBC0.5000106@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	Alan Pevec <apevec@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Return-path: <kvm-devel-bounces@lists.sourceforge.net>
Content-Disposition: inline
In-Reply-To: <480CDBC0.5000106@codemonkey.ws>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/kvm-devel>,
	<mailto:kvm-devel-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=kvm-devel>
List-Post: <mailto:kvm-devel@lists.sourceforge.net>
List-Help: <mailto:kvm-devel-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/kvm-devel>,
	<mailto:kvm-devel-request@lists.sourceforge.net?subject=subscribe>
Sender: kvm-devel-bounces@lists.sourceforge.net
Errors-To: kvm-devel-bounces@lists.sourceforge.net
List-Id: kvm.vger.kernel.org

On Mon, Apr 21, 2008 at 01:24:00PM -0500, Anthony Liguori wrote:
> Marcelo Tosatti wrote:
> >From: Alan Pevec <apevec@redhat.com>
> >
> >  
> >>- add serial console, workaround for F9 livecd KVM guest dying with 
> >>standard console only.
> >> VNC console will go blank but node will continue to boot
> >>    
> >
> >With only console=tty qemu-kvm dies when, AFAICT from udevdebug output, 
> >start_udev is processing console rules.
> >
> >Here is backtrace:
> >
> >Program received signal SIGSEGV, Segmentation fault.
> >
> >[Switching to Thread -1208993168 (LWP 16163)]
> >
> >0x0095337d in memmove () from /lib/libc.so.6
> >
> >Missing separate debuginfos, use: debuginfo-install SDL.i386 alsa-lib.i386 
> >glibc.i686 gnutls.i386 libgcrypt.i386 libgpg-error.i386 zlib.i386
> >  
> 
> The info that's needed is what the size of the vnc frame buffer is.  My 
> suspicion is that we're racing.  A VCPU IO operation will trigger the 
> bit blit which will cause this vnc_copy path to hit.  However, the VNC 
> server is not thread safe so if the IO thread is running simultaneously, 
> very bad things could happen.
> 
> Is this with standard KVM or your lock break-up patches?

Standard KVM.

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone