From: Gleb Natapov Subject: Re: KVM call minutes for 2013-08-06 Date: Tue, 6 Aug 2013 20:01:01 +0300 Message-ID: <20130806170101.GE15901@redhat.com> References: <878v0ehmun.fsf@elfo.elfo> <52011A98.6090104@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: quintela@redhat.com, KVM devel mailing list , qemu-devel qemu-devel To: Paolo Bonzini Return-path: Received: from mx1.redhat.com ([209.132.183.28]:35997 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755723Ab3HFRBG (ORCPT ); Tue, 6 Aug 2013 13:01:06 -0400 Content-Disposition: inline In-Reply-To: <52011A98.6090104@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Aug 06, 2013 at 05:47:36PM +0200, Paolo Bonzini wrote: > On 08/06/2013 05:15 PM, Juan Quintela wrote: > >* pvpanic > >- was added by default in 1.5, this might have been too rash: > > - might change guest behaviour if guest is set to reboot on panic > > Interesting, but it looks like either a feature or a driver bug. > More like the device bug. The behaviour should be to notify management without stopping the VM. Management (if present and configured for do so) stops the VM. > > - might cause slightly annoying warnings/queries from device > > manager > > - generally somewhat inelegant/non-symmetrical, libvirt > > developers prefer "no magic devices" > >- conclusions: > > - for -M 1.6, will change QEMU don't add by default, teach libvirt to add > > with -device pvpanic > > This just moves the problem to a layer where it's harder to fix it. > It will just appear to work because no one will use pvpanic, which > is not a solution. > > Paolo > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Gleb.