From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Richard W.M. Jones" <rjones@redhat.com>,
Bharata B Rao <bharata@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for September 25th
Date: Tue, 25 Sep 2012 15:30:17 +0200 [thread overview]
Message-ID: <5061B1E9.2020909@redhat.com> (raw)
In-Reply-To: <87obkucl9q.fsf@codemonkey.ws>
Il 25/09/2012 14:57, Anthony Liguori ha scritto:
> The call is a bit late for Bharata but I think copying is the way to go.
>
> Something I've been thinking about since this discussion started
> though. Maybe we could standardize on using URIs as short-hand syntax
> for backends.
>
> For example:
>
> qemu -hda file:///foo.img
>
> Or:
>
> qemu -device virtio-net-pci,netdev=tap:///vnet0?script=/etc/qemu-ifup
>
> Or:
>
> qemu -device \
> isa-serial,index=0,chr=tcp://localhost:1025/?server=on&wait=off
>
> This works particularly well with a "treat unknown options as -device"
> mechanism so that we could do:
>
> qemu -isa-serial chr=tcp://localhost:1025/?server=on&wait=off
>
> We could even introduce a secondary implied option to shorten this
> further to:
>
> qemu -isa-serial tcp://localhost:1025/?server=on&wait=off
Interesting idea...
Paolo
next prev parent reply other threads:[~2012-09-25 13:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 11:28 [Qemu-devel] KVM call agenda for September 25th Juan Quintela
2012-09-24 11:48 ` Paolo Bonzini
2012-09-25 12:13 ` Richard W.M. Jones
2012-09-25 12:57 ` Anthony Liguori
2012-09-25 13:05 ` Richard W.M. Jones
2012-09-25 13:14 ` Luiz Capitulino
2012-09-25 13:30 ` Paolo Bonzini [this message]
2012-09-25 14:51 ` Kevin Wolf
2012-09-25 15:33 ` Bharata B Rao
2012-09-25 15:37 ` Paolo Bonzini
2012-09-25 19:42 ` Anthony Liguori
2012-09-26 7:10 ` Markus Armbruster
2012-09-25 13:27 ` Luiz Capitulino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5061B1E9.2020909@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=bharata@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rjones@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).