acrncontainerscricri-odockerfirecrackerk8skuberneteskvmociqemusecurityvirtual-machinevirtualization

Samuel Ortiz e543c3383d qemu: Probe each qemu device with a driver ... Having separate structures for the qemu driver definitions and each possible device definitions is confusing and error prone as one needs to be very careful using matching IDs and names in both structures. As the driver parameter can be derived from the device ones, this patch changes the Device and Driver structures to be linked together, i.e. each driver needs to have its corresponding device. For example this allows us to build the following 9pfs qemu parameters: "-fsdev local,id=foo,path=/bar/foo,security-model=none -device virtio-9p-pci,fsdev=foo,mount_tag=rootfs" from these structures: fsdev := FSDevice{ Driver: Local, ID: "foo", Path: "/bar/foo", MountTag: "rootfs", SecurityModel: None, } driver := Driver{ Driver: Virtio9P, Device: fsdev, } Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>		2016-09-17 00:41:13 +02:00
examples_test.go	qemu: Add configuration structure to simplify LaunchQemu	2016-09-17 00:41:13 +02:00
qemu_test.go	qemu: Probe each qemu device with a driver	2016-09-17 00:41:13 +02:00
qemu.go	qemu: Probe each qemu device with a driver	2016-09-17 00:41:13 +02:00
qmp_test.go	ciao-launcher, qemu: Upgrade to new context package.	2016-09-12 11:51:00 +01:00
qmp.go	ciao-launcher, qemu: Upgrade to new context package.	2016-09-12 11:51:00 +01:00