In addition to the classic VNC backend add a spice backend to allow
leveraging more benefits of the QXL driver in the guest.
That allows users to upgrade their uvtool guest to a full Desktop and
get some meaningful performance. If they later on add the qxl.ko from
linux-modules-extra they even will get KMS and more extra features.
This will use the same "local only" mechanism that VNC uses to avoid
opening up to the world too much.
Signed-off-by: Christian Ehrhardt <email address hidden>
We know that we will run Ubuntu guests which work fine with QXL
video. That not only avoids recent issues with cirrus (LP: #1818877)
but should also be slightly faster.
My hosting provider requires me to use Mac addresses provided by
themselves so that their network will accept my ethernet packets. They
also require a strict proscribed static IP allocation. Without the
correct Mac address, my VM cannot send/receive data to/from the network.
However, the problem that I have when using the `--bridge br0` is that
the Mac address for the vnet adapter created for that bridge is
seemingly randomly assigned.
I attach a patch that adds a `--mac` parameter to uvt-kvm which allows
the user to specify the Mac address for the interface. I have tested it
here and it sets the Mac correctly, both when using a bridge and when
not using a bridge.
With the upstream discussion aournd switching the qemu default as well
as more and more people wanting to work with PCIe uvtool should have
a way to override the default machine type.
This adds an argument to do so, the rest will as usual be filled in by
libvirt as needed (e.g. PCIe Bus structure).
Signed-off-by: Christian Ehrhardt <email address hidden>
The body of that element defines a path where the per-guest custom copy
should be stored.
That has two issues:
1. multiple guests would clash
2. the path could be not writable by default
Fortunately if just not specified at all libvirt will make sane
defaults.
Signed-off-by: Christian Ehrhardt <email address hidden>
This allows users of uvtool to easily change from the compatibility
focused default cpu type to host-passthrough which will expose as much
as possible to the guest.
Anything in between is too specific for uvtool and can be setup via
libvirt after creating the guest.
Signed-off-by: Christian Ehrhardt <email address hidden>
This does not cause any issues, but apic, pae and such are just not
existant on s390x. So there might be a case in the future were having
these int he template becomes a problem, therefore remove them now.
Signed-off-by: Christian Ehrhardt <email address hidden>
