From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NtpZR-0001DA-Nj
	for qemu-devel@nongnu.org; Mon, 22 Mar 2010 17:54:01 -0400
Received: from [199.232.76.173] (port=56381 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NtpZR-0001Cr-BF
	for qemu-devel@nongnu.org; Mon, 22 Mar 2010 17:54:01 -0400
Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim
	4.60) (envelope-from <anthony@codemonkey.ws>) id 1NtpZN-0004jm-2v
	for qemu-devel@nongnu.org; Mon, 22 Mar 2010 17:54:00 -0400
Received: from mail-px0-f173.google.com ([209.85.216.173]:42873)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1NtpZM-0004jg-Oq
	for qemu-devel@nongnu.org; Mon, 22 Mar 2010 17:53:56 -0400
Received: by pxi3 with SMTP id 3so2263620pxi.28
	for <qemu-devel@nongnu.org>; Mon, 22 Mar 2010 14:53:55 -0700 (PDT)
Message-ID: <4BA7E6F0.5010501@codemonkey.ws>
Date: Mon, 22 Mar 2010 16:53:52 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs
	in	libvirt
References: <4BA7C40C.2040505@codemonkey.ws>
	<20100322201003.GC28709@redhat.com> <4BA7E23A.2070502@redhat.com>
In-Reply-To: <4BA7E23A.2070502@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "libvir-list@redhat.com" <libvir-list@redhat.com>, qemu-devel <qemu-devel@nongnu.org>

On 03/22/2010 04:33 PM, Gerd Hoffmann wrote:
>   Hi,
>
>> Stepping back a bit first, there are the two core areas in which 
>> people can
>> be limited by libvirt currently.
>
>>   2. Command line flags
>
> For me:  This one, and monitor access.
>
> libvirt is very unfriendly to qemu hackers.  There is no easy way to 
> add command line switches.  There is no easy way to get access to the 
> monitor.  I can get it done by pointing <emulator> to a wrapper script 
> and mangle the qemu command line there.  But this sucks big time.  And 
> it doesn't integrate with libvirt at all.

It's not just developers.  As we're doing deployments of qemu/kvm, we 
keep running into the same problem.  We realize that we need to use a 
feature of qemu/kvm that isn't modelled by libvirt today.  I've gone as 
far as to temporarily pausing libvirtd, finding the pty fd from 
/proc/<pid>, and hijacking the monitor session temporarily.

The problem is, it's not always easy to know what the most important 
features are.

>
> When hacking qemu, especially when adding new command line options or 
> monitor commands, I want to have a easy way to test this stuff.  Or I 
> just wanna able to type some 'info $foo' commands for debugging and 
> trouble shooting purposes.  libvirt makes it harder not easier to get 
> the job done.
>
> Image you could ask libvirt to create an additional monitor and expose 
> it like a serial console.  virt-manager lists it as text console.  Two 
> mouse clicks open a new window (or tab) with a terminal emulator 
> linked to the monitor.  Wouldn't that be cool?
>
> Other issues I've trap into:
>
> -boot
>   libvirt (or virt-manager?) supports only the very old single letter
>   style.  You can't specify '-boot order=cd,menu=on'.

You can, you specify multiple <boot> options (but you can't touch things 
like menu=on).

Regards,

Anthony Liguori

> -enable-nested
>   not available.
>
> serial console doesn't work for remote connections.
>
> cheers,
>   Gerd