| Message ID | 20240812130606.90410-11-edgar.iglesias@gmail.com (mailing list archive) |
|---|---|
| State | Superseded |
| Headers | show |
| Series | xen: pvh: Partial QOM:fication with new x86 PVH machine | expand |
On Mon, 12 Aug 2024, Edgar E. Iglesias wrote: > From: "Edgar E. Iglesias" <edgar.iglesias@amd.com> > > Signed-off-by: Edgar E. Iglesias <edgar.iglesias@amd.com> Reviewed-by: Stefano Stabellini <sstabellini@kernel.org> > --- > MAINTAINERS | 1 + > docs/system/i386/xenpvh.rst | 49 +++++++++++++++++++++++++++++++++++++ > docs/system/target-i386.rst | 1 + > 3 files changed, 51 insertions(+) > create mode 100644 docs/system/i386/xenpvh.rst > > diff --git a/MAINTAINERS b/MAINTAINERS > index a24c2e14d9..da4c9d4d46 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -560,6 +560,7 @@ F: include/sysemu/xen.h > F: include/sysemu/xen-mapcache.h > F: stubs/xen-hw-stub.c > F: docs/system/arm/xenpvh.rst > +F: docs/system/i386/xenpvh.rst > > Guest CPU Cores (NVMM) > ---------------------- > diff --git a/docs/system/i386/xenpvh.rst b/docs/system/i386/xenpvh.rst > new file mode 100644 > index 0000000000..354250f073 > --- /dev/null > +++ b/docs/system/i386/xenpvh.rst > @@ -0,0 +1,49 @@ > +Xen PVH machine (``xenpvh``) > +========================================= > + > +Xen supports a spectrum of types of guests that vary in how they depend > +on HW virtualization features, emulation models and paravirtualization. > +PVH is a mode that uses HW virtualization features (like HVM) but tries > +to avoid emulation models and instead use passthrough or > +paravirtualized devices. > + > +QEMU can be used to provide PV virtio devices on an emulated PCIe controller. > +That is the purpose of this minimal machine. > + > +Supported devices > +----------------- > + > +The x86 Xen PVH QEMU machine provide the following devices: > + > +- RAM > +- GPEX host bridge > +- virtio-pci devices > + > +The idea is to only connect virtio-pci devices but in theory any compatible > +PCI device model will work depending on Xen and guest support. > + > +Running > +------- > + > +The Xen tools will typically construct a command-line and launch QEMU > +for you when needed. But here's an example of what it can look like in > +case you need to construct one manually: > + > +.. code-block:: console > + > + qemu-system-i386 -xen-domid 3 -no-shutdown \ > + -chardev socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-3,server=on,wait=off \ > + -mon chardev=libxl-cmd,mode=control \ > + -chardev socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-3,server=on,wait=off \ > + -mon chardev=libxenstat-cmd,mode=control \ > + -nodefaults \ > + -no-user-config \ > + -xen-attach -name g0 \ > + -vnc none \ > + -display none \ > + -device virtio-net-pci,id=nic0,netdev=net0,mac=00:16:3e:5c:81:78 \ > + -netdev type=tap,id=net0,ifname=vif3.0-emu,br=xenbr0,script=no,downscript=no \ > + -smp 4,maxcpus=4 \ > + -nographic \ > + -machine xenpvh,ram-low-base=0,ram-low-size=2147483648,ram-high-base=4294967296,ram-high-size=2147483648,pci-ecam-base=824633720832,pci-ecam-size=268435456,pci-mmio-base=4026531840,pci-mmio-size=33554432,pci-mmio-high-base=824902156288,pci-mmio-high-size=68719476736 \ > + -m 4096 > diff --git a/docs/system/target-i386.rst b/docs/system/target-i386.rst > index 1b8a1f248a..23e84e3ba7 100644 > --- a/docs/system/target-i386.rst > +++ b/docs/system/target-i386.rst > @@ -26,6 +26,7 @@ Architectural features > i386/cpu > i386/hyperv > i386/xen > + i386/xenpvh > i386/kvm-pv > i386/sgx > i386/amd-memory-encryption > -- > 2.43.0 >
diff --git a/MAINTAINERS b/MAINTAINERS index a24c2e14d9..da4c9d4d46 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -560,6 +560,7 @@ F: include/sysemu/xen.h F: include/sysemu/xen-mapcache.h F: stubs/xen-hw-stub.c F: docs/system/arm/xenpvh.rst +F: docs/system/i386/xenpvh.rst Guest CPU Cores (NVMM) ---------------------- diff --git a/docs/system/i386/xenpvh.rst b/docs/system/i386/xenpvh.rst new file mode 100644 index 0000000000..354250f073 --- /dev/null +++ b/docs/system/i386/xenpvh.rst @@ -0,0 +1,49 @@ +Xen PVH machine (``xenpvh``) +========================================= + +Xen supports a spectrum of types of guests that vary in how they depend +on HW virtualization features, emulation models and paravirtualization. +PVH is a mode that uses HW virtualization features (like HVM) but tries +to avoid emulation models and instead use passthrough or +paravirtualized devices. + +QEMU can be used to provide PV virtio devices on an emulated PCIe controller. +That is the purpose of this minimal machine. + +Supported devices +----------------- + +The x86 Xen PVH QEMU machine provide the following devices: + +- RAM +- GPEX host bridge +- virtio-pci devices + +The idea is to only connect virtio-pci devices but in theory any compatible +PCI device model will work depending on Xen and guest support. + +Running +------- + +The Xen tools will typically construct a command-line and launch QEMU +for you when needed. But here's an example of what it can look like in +case you need to construct one manually: + +.. code-block:: console + + qemu-system-i386 -xen-domid 3 -no-shutdown \ + -chardev socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-3,server=on,wait=off \ + -mon chardev=libxl-cmd,mode=control \ + -chardev socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-3,server=on,wait=off \ + -mon chardev=libxenstat-cmd,mode=control \ + -nodefaults \ + -no-user-config \ + -xen-attach -name g0 \ + -vnc none \ + -display none \ + -device virtio-net-pci,id=nic0,netdev=net0,mac=00:16:3e:5c:81:78 \ + -netdev type=tap,id=net0,ifname=vif3.0-emu,br=xenbr0,script=no,downscript=no \ + -smp 4,maxcpus=4 \ + -nographic \ + -machine xenpvh,ram-low-base=0,ram-low-size=2147483648,ram-high-base=4294967296,ram-high-size=2147483648,pci-ecam-base=824633720832,pci-ecam-size=268435456,pci-mmio-base=4026531840,pci-mmio-size=33554432,pci-mmio-high-base=824902156288,pci-mmio-high-size=68719476736 \ + -m 4096 diff --git a/docs/system/target-i386.rst b/docs/system/target-i386.rst index 1b8a1f248a..23e84e3ba7 100644 --- a/docs/system/target-i386.rst +++ b/docs/system/target-i386.rst @@ -26,6 +26,7 @@ Architectural features i386/cpu i386/hyperv i386/xen + i386/xenpvh i386/kvm-pv i386/sgx i386/amd-memory-encryption