From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: li zhang <zhlcindy@gmail.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, zhlcindy@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [qemu-devel][RFC] Enable usb with default options
Date: Wed, 06 Jun 2012 13:31:55 +1000 [thread overview]
Message-ID: <1338953515.7150.150.camel@pasglop> (raw)
In-Reply-To: <CAD8of+pci+Kv2BeH_sAhh=4qi3gRdZtn+ByxOWULJZvOVEFH1A@mail.gmail.com>
On Wed, 2012-06-06 at 10:52 +0800, li zhang wrote:
> Hi Anthony,
>
>
> Any comment on this?
Allright, this is all quite confusing...
He's what I think should happen:
When no option is passed -at-all-, we should have vga std and usb ohci +
usb mouse + usb ps2.
When -nodefault is passed, we should have none of the above.
-vga should only affect vga (a shortcut for -device
pick_your_vga_poison)
-usb should be essentially useless by default unless -nodefault is
passed in which case it is necessary to enable usb support, and -device
(or equivalent) to manually add the keyboard and mouse (libvirt).
That's the best I can think of ... however it might be a bit tricky
seeing how qemu does things in vl.c at the moment, we might want to
introduce a default_usb variable which is used to set usb_enabled.
BTW. The mac models should essentially behave the same, at least the
64-bit one (32-bit supports CUDA for keyboard/mouse so USB isn't
strictly necessary).
Cheers,
Ben.
>
> Thanks.
>
> On Tue, Jun 5, 2012 at 5:48 PM, li zhang <zhlcindy@gmail.com> wrote:
> Hi all,
>
> For pseries, when creating VMs with "-vga std",
> it requires usb mouse and usb kbd devices to be added.
>
> But with default options, vga is enabled and usb is disabled.
> User may use default options as the following commands:
>
> $qemu -M pseries
>
> If vga is enabled, usb mouse and usb kbd is disabled,
> the mouse and kbd can't be used. So it's very hard for
> users to use.
>
> I think it's necessary to enable usb with default options.
>
> Any idea about that?
> Your comments are very appreciated. :)
>
> Thanks.
> -Li
>
>
>
>
> --
>
>
> Best Regards
> -Li
>
>
next prev parent reply other threads:[~2012-06-06 3:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 9:48 [Qemu-devel] [qemu-devel][RFC] Enable usb with default options li zhang
2012-06-06 2:52 ` li zhang
2012-06-06 3:31 ` Benjamin Herrenschmidt [this message]
2012-06-06 5:42 ` Anthony Liguori
2012-06-06 6:03 ` li zhang
2012-06-06 21:13 ` Benjamin Herrenschmidt
2012-06-07 1:15 ` Anthony Liguori
2012-06-07 3:00 ` Benjamin Herrenschmidt
2012-06-07 3:03 ` Anthony Liguori
2012-06-07 4:52 ` li zhang
2012-06-07 4:39 ` li zhang
2012-06-07 4:43 ` Anthony Liguori
2012-06-07 4:53 ` li zhang
2012-06-07 8:07 ` Markus Armbruster
2012-06-07 9:19 ` Anthony Liguori
2012-06-07 10:05 ` Markus Armbruster
2012-06-07 11:51 ` Anthony Liguori
2012-06-12 8:06 ` Markus Armbruster
2012-06-07 8:32 ` Hans de Goede
2012-06-07 8:40 ` Benjamin Herrenschmidt
2012-06-07 8:49 ` Paolo Bonzini
2012-06-07 8:52 ` Hans de Goede
2012-06-07 9:05 ` Gerd Hoffmann
2012-06-07 9:17 ` Benjamin Herrenschmidt
2012-06-07 9:29 ` Li Zhang
2012-06-07 9:16 ` Benjamin Herrenschmidt
2012-06-07 9:50 ` Hans de Goede
2012-06-07 11:19 ` Benjamin Herrenschmidt
2012-06-07 11:35 ` Gerd Hoffmann
2012-06-07 8:54 ` Gerd Hoffmann
2012-06-06 22:14 ` Andreas Färber
-- strict thread matches above, loose matches on Subject: below --
2012-06-05 7:19 Li Zhang
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=1338953515.7150.150.camel@pasglop \
--to=benh@au1.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=zhlcindy@gmail.com \
--cc=zhlcindy@linux.vnet.ibm.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).