Hi,
> q35-emulated.cfg # emulated guest
> q35-virtio-common.cfg # shared by all VirtIO guests
> q35-virtio-graphical.cfg # VirtIO guest, graphical console
> q35-virtio-serial.cfg # VirtIO guest, serial console
Looks good to me.
> > > +[device "tablet"]
> > > +
On Tue, 2017-01-31 at 15:03 -0600, Eric Blake wrote:
> > Note that you can specify -readconfig multiple times, so you can split
> > out common stuff and ask people to run "qemu -readconfig
> > q35-paravirt-base.cfg -readconfig q35-paravirt-$style.cfg"
>
> Can we add #include-like semantics, so
On Tue, 2017-01-31 at 21:34 +0100, Gerd Hoffmann wrote:
> > docs/q35-chipset.cfg | 152
> >
>
> Please leave q35-chipset.cfg there.
>
> The purpose of q35-chipset.cfg is to document how you can build a
> virtual machine which comes as close as
On 01/31/2017 02:34 PM, Gerd Hoffmann wrote:
>
> Note that you can specify -readconfig multiple times, so you can split
> out common stuff and ask people to run "qemu -readconfig
> q35-paravirt-base.cfg -readconfig q35-paravirt-$style.cfg"
Can we add #include-like semantics, so that one .cfg
Hi,
> Both configuration file are full commented, neatly
> organized, and use paravirtualized devices instead of
> emulated devices whenever possible for a better user
> experience. Moreover, they follow the PCI Express
> Guidelines (docs/pcie.txt) for their topology.
> ---
> I plan to provide
Instead of having a single sample configuration file,
now we have two: one gives access to the guest through
the serial console and only includes a minimal set of
devices, the other uses a graphical console and includes
extra devices such as an audio card.
Both configuration file are full
