I like the idea of it. I don't like the magic strings in 'details', but it sounds like VMware supports it so this patch allows for it as well. It seems pretty useful to be able to specify the desired nic/storage driver when registering a template, rather than just saying 'all CentOS is virtio nic and virtio disk', especially with upcoming things like virtio-scsi, where newer operating systems will have multiple good options to choose from.
If you need to build your own agent, you can use this patch: http://marcus.mlsorensen.com/cloudstack-extras/models.43.patch On Thu, Apr 24, 2014 at 9:33 AM, Nux! <n...@li.nux.ro> wrote: > On 24.04.2014 15:14, Marcus wrote: > >> Well, the agent is what decides. The 'vm start' command is sent to the >> agent will all of the relevant details, and the agent creates the libvirt >> xml to start the vm. >> > > Ahh, alright, makes sense. > Well, it'd be great if it was possible, but I believe the cases this > feature would address are quite rare, especially as everything supports > VirtIO more and more. > I personally can live without it. Having said that, if you think you have > a good patch available I can test it out, but I'd need to apply it to my > 4.3+ipset build. > > Thanks! > > Lucian > > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro >
