This repository has been archived by the owner on May 12, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 374
virtcontainers: NEMU virt machine type not fully supported #804
Comments
sboeuf
pushed a commit
to sboeuf/runtime-1
that referenced
this issue
Oct 2, 2018
The virt machine type provided by the NEMU project needs to be supported the same way we support pc and q35 machine types. First, this patch takes care of adding the hotpluggable block device capability to this machine type, this way when using devicemapper, we prevent the code from falling back on using 9pfs instead of SCSI. It also add one or several bridges to this machine type, as the code is tightly coupled to the fact that a bridge is required for PCI hotplug. At last, it changes the name of the PCI host bridge (main bus), to use "pcie.0". The default set up from pc machine type "pci.0" is not suitable for this machine type. Fixes kata-containers#804 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
sboeuf
pushed a commit
to sboeuf/runtime-1
that referenced
this issue
Oct 3, 2018
The virt machine type provided by the NEMU project needs to be supported the same way we support pc and q35 machine types. First, this patch takes care of adding the hotpluggable block device capability to this machine type, this way when using devicemapper, we prevent the code from falling back on using 9pfs instead of SCSI. It also add one or several bridges to this machine type, as the code is tightly coupled to the fact that a bridge is required for PCI hotplug. At last, it changes the name of the PCI host bridge (main bus), to use "pcie.0". The default set up from pc machine type "pci.0" is not suitable for this machine type. Fixes kata-containers#804 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
sboeuf
pushed a commit
to sboeuf/runtime-1
that referenced
this issue
Oct 3, 2018
The virt machine type provided by the NEMU project needs to be supported the same way we support pc and q35 machine types. First, this patch takes care of adding the hotpluggable block device capability to this machine type, this way when using devicemapper, we prevent the code from falling back on using 9pfs instead of SCSI. It also add one or several bridges to this machine type, as the code is tightly coupled to the fact that a bridge is required for PCI hotplug. At last, it changes the name of the PCI host bridge (main bus), to use "pcie.0". The default set up from pc machine type "pci.0" is not suitable for this machine type. Fixes kata-containers#804 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
sboeuf
pushed a commit
to sboeuf/runtime-1
that referenced
this issue
Oct 3, 2018
The virt machine type provided by the NEMU project needs to be supported the same way we support pc and q35 machine types. First, this patch takes care of adding the hotpluggable block device capability to this machine type, this way when using devicemapper, we prevent the code from falling back on using 9pfs instead of SCSI. It also add one or several bridges to this machine type, as the code is tightly coupled to the fact that a bridge is required for PCI hotplug. At last, it changes the name of the PCI host bridge (main bus), to use "pcie.0". The default set up from pc machine type "pci.0" is not suitable for this machine type. Fixes kata-containers#804 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
zklei
pushed a commit
to zklei/runtime
that referenced
this issue
Nov 22, 2018
The virt machine type provided by the NEMU project needs to be supported the same way we support pc and q35 machine types. First, this patch takes care of adding the hotpluggable block device capability to this machine type, this way when using devicemapper, we prevent the code from falling back on using 9pfs instead of SCSI. It also add one or several bridges to this machine type, as the code is tightly coupled to the fact that a bridge is required for PCI hotplug. At last, it changes the name of the PCI host bridge (main bus), to use "pcie.0". The default set up from pc machine type "pci.0" is not suitable for this machine type. Fixes kata-containers#804 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need to fix the hypervisor implementation for
qemu
if we want to be able to use NEMUvirt
machine type with Kata Containers.The text was updated successfully, but these errors were encountered: