Hi Ivan, Thanks for the information. It was useful.
Let me elaborate by use cases a bit more. I have PCI host devices with sriov capabilities. I may have 48 virtual functions (VF) on a host. I want to assign the VFs to some VM but not all. So I need some control which VMs gets the VF and others don't. Also, I need to keep track which VFs are already assigned and which are free. Lastly, I want to expose the VFs to containers running on VMs created by the upcoming Cloudstack Kubernetes Service (AKS, pull #3680). Looking at the first feature you mentioned, I don't think I can use that. It has no control on which VMs to add the extraconfig. It is all or nothing. The second feature, which you started to work on seems to have more potential. Do you see it can support my use case? Thanks, Sakari On Fri, Jan 24, 2020 at 6:08 PM Ivan Kudryavtsev <i...@bw-sw.com> wrote: > Sakari, looks like you are looking for this one: > https://github.com/apache/cloudstack/pull/3510 > > Also, Im working on implementation, which handles it another way: > https://github.com/apache/cloudstack/issues/3823 > > пт, 24 янв. 2020 г., 17:45 Sakari Poussa <spou...@gmail.com>: > > > Hi, > > > > Is there a way to pass extra parameters to KVM VMs when they start? That > > is, to the qemu.system-x86_64 command. > > > > I am looking a way to expose SRIOV PCI device to the VM and I need to > pass > > extra parameters like this > > > > qemu.system-x86_64 -device vfio-pci,host=3f:01.0 <normal-args> > > > > Is this possible somehow? > > > > -- > > Thanks, Sakari > > > -- Sakari Poussa 040 348 2970
