From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: KVM call minutes for 2013-08-06 Date: Tue, 06 Aug 2013 17:47:36 +0200 Message-ID: <52011A98.6090104@redhat.com> References: <878v0ehmun.fsf@elfo.elfo> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: KVM devel mailing list , qemu-devel qemu-devel To: quintela@redhat.com Return-path: Received: from mail-wi0-f182.google.com ([209.85.212.182]:37377 "EHLO mail-wi0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754802Ab3HFPro (ORCPT ); Tue, 6 Aug 2013 11:47:44 -0400 Received: by mail-wi0-f182.google.com with SMTP id hi8so591327wib.3 for ; Tue, 06 Aug 2013 08:47:42 -0700 (PDT) In-Reply-To: <878v0ehmun.fsf@elfo.elfo> Sender: kvm-owner@vger.kernel.org List-ID: 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. > - 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