Instead of falling back to system emulation when /dev/kvm is not
available, let the user decide explicitly whether they want
hardware-assisted KVM virtualization or full emulation.
Signed-off-by: Alberto Faria <afaria@redhat.com>
Containerdisks now set their entrypoint to "no-entrypoint", so we can
drop the empty "" argument to podman-run and equivalents in most cases.
Signed-off-by: Alberto Faria <afaria@redhat.com>
Using these options requires binding the device to the vfio-pci driver
in the host, and may require special configuration of locked memory
limits.
Without these options, the user has to customize the libvirt XML
directly to achieve PCI device passthrough, which should make it clearer
that they have to take care of all these details.
Signed-off-by: Alberto Faria <afaria@redhat.com>
In step 1, since editing /etc is not desirable for rootless Podman,
mention the alternative location that will have the same effect.
In step 2, there's no need for the disclaimer paragraph about Docker
lacking --latest in an example that already can't use Docker because
of lack of --rootfs a couple paragraphs above. And even for Podman,
make it clear that the initial example is limited, in that the qcow2
image has no ssh keys, root password, or alternative users installed
yet.
Signed-off-by: Eric Blake <eblake@redhat.com>
It allows passing regular files and block devices in any format that
QEMU understands (e.g., raw, qcow2) through to the guest as block
devices.
Signed-off-by: Alberto Faria <afaria@redhat.com>
Use it to pass in an XML file to be merged into the generated libvirt
domain XML definition. It may be specified multiple times.
Signed-off-by: Alberto Faria <afaria@redhat.com>
When specified, the container does not launch a VM but instead simply
outputs the generated libvirt domain XML and exits.
Signed-off-by: Alberto Faria <afaria@redhat.com>
When used in conjunction with --rootfs, changes are propagated back to
the user's original image file.
Signed-off-by: Alberto Faria <afaria@redhat.com>