From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33723) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4VK7-0008U4-Fp for qemu-devel@nongnu.org; Wed, 09 Nov 2016 11:02:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4VK4-0004y0-Dw for qemu-devel@nongnu.org; Wed, 09 Nov 2016 11:02:03 -0500 Received: from mx1.redhat.com ([209.132.183.28]:39224) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c4VK4-0004xV-8T for qemu-devel@nongnu.org; Wed, 09 Nov 2016 11:02:00 -0500 Date: Wed, 9 Nov 2016 16:01:53 +0000 From: "Daniel P. Berrange" Message-ID: <20161109160153.GJ22181@redhat.com> Reply-To: "Daniel P. Berrange" References: <20161109030146.GA3802@dhcp-128-65.nay.redhat.com> <20161109104059.bvw5h4k4v77pw2rl@kamzik.brq.redhat.com> <9144d6b1-a1c9-e727-4673-9df10b227fdb@redhat.com> <20161109113735.GF22181@redhat.com> <20161109114809.cawi6tpsxwn5vfql@kamzik.brq.redhat.com> <20161109115819.GG22181@redhat.com> <20161109122051.ztllxmhwsalds2qw@kamzik.brq.redhat.com> <20161109144740.GI22181@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] virsh dump (qemu guest memory dump?): KASLR enabled linux guest support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek Cc: Andrew Jones , Dave Young , qiaonuohan@cn.fujitsu.com, bhe@redhat.com, anderson@redhat.com, qemu-devel@nongnu.org On Wed, Nov 09, 2016 at 04:38:36PM +0100, Laszlo Ersek wrote: > On 11/09/16 15:47, Daniel P. Berrange wrote: > >>> That doesn't help with trying to diagnose a crash during boot up, since > >>> the guest agent isn't running till fairly late. I'm also concerned that > >>> the QEMU guest agent is likely to be far from widely deployed in guests, > > I have no hard data, but from the recent Fedora and RHEL-7 guest > installations I've done, it seems like qga is installed automatically. > (Not sure if that's because Anaconda realizes it's installing the OS in > a VM.) Once I made sure there was an appropriate virtio-serial config in > the domain XMLs, I could talk to the agents (mainly for fstrim's sake) > immediately. I'm thinking about cloud deployment where people rarely use Anaconda directly - they'll use a pre-built cloud image, or customize the basic cloud image. Neither Fedora or Ubuntu include the qemu guest agent in their cloud images AFAICT, so very few OpenStack deployments will have QEMU guest agent in at this time. Of course we could try to get distros to embed qemu guets agent by default, but its not clear if we'd succeed, given how aggressive they are at stripping stuff out to create the smallest practical images. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|