Features/Usability: Difference between revisions
(Created page with '== Summary == Provide infrastructure to allow a management tool to present both an rtl8139 and virtio-net network adapter, detect when a driver is loaded for virtio-net, and ena…') |
No edit summary |
||
| Line 1: | Line 1: | ||
== Summary == | == Summary == | ||
Improve out-of-the-box usability for QEMU when using KVM to in a typical desktop environment. | |||
== Owner == | == Owner == | ||
| Line 8: | Line 8: | ||
== Detailed Summary == | == Detailed Summary == | ||
Most of the first impressions people get of QEMU/KVM is running QEMU directly from the command line as a casual desktop user. Even if this isn't a common use-case, it's an important one because those impressions can be lasting even if the user is ultimately going to use QEMU for development or server virtualization. | |||
The following issues have been identified as usability problems with running QEMU directly while using KVM in a typical desktop environment: | The following issues have been identified as usability problems with running QEMU directly while using KVM in a typical desktop environment: | ||
Revision as of 00:27, 22 March 2010
Summary
Improve out-of-the-box usability for QEMU when using KVM to in a typical desktop environment.
Owner
- Name: Anthony Liguori
- Email: anthony@codemonkey.ws
Detailed Summary
Most of the first impressions people get of QEMU/KVM is running QEMU directly from the command line as a casual desktop user. Even if this isn't a common use-case, it's an important one because those impressions can be lasting even if the user is ultimately going to use QEMU for development or server virtualization.
The following issues have been identified as usability problems with running QEMU directly while using KVM in a typical desktop environment:
- Issue1..
- Issue2..