Nux,
Pretext: This applies to VMware and could possible apply to KVM - but
i'm not 100% certain on that - so its an educated guess of things you
can try.
I see 2 ways of addressing your problem.
1) If VMs are already in cloudstack, but have the wrong SCSI adapter,
i'm under assumption you can alter the cloud.user_vm_details table for
each respective VM id. I would use Windows host as an example to trace
one flow. Once the change is made, power down the vm through cloudstack
and start it back up.
2) If you building out the VMs via templates, when you go through import
process, you can try altering vm_details tag. For example this is how i
did it in cloudmonkey:
register template format=ova hypervisor=vmware name=OL63-26-TMPLT
url=http://reposerver.example.com/6.3-26/ol-6.3-26.ova ispublic=true
isfeatured=true passwordenabled=false details[0].rootDiskController=scsi
details[0].nicAdapter=E1000 details[0].keyboard=us ostypeid=148
zoneid=-1 displaytext=OL63-26-TMPLT
see if you can change details[0].rootDiskController=scsi to
details[0].rootDiskController=virtio
If i understood developers correctly last time we spoke on adding custom
parameters to vmware, you can pass on the parameters via details
argument and cloudstack does not sanitize the input, it just passes it
on to vmware (the only place that has some checking - is the UI, not
really backend restriction)
Let me know if KVM behaves the same way as vmware.
Regards
ilya
On 4/22/14, 1:36 AM, Nux! wrote:
Hi,
I need to migrate some VMs from OnApp to Cloudstack and they are
defined with VirtIO storage and e1000 NICs. In the past Cloudstack's
"Windows PV" OS type was giving me the same (VirtIO + e1000), but I
see in 4.3 this is no longer the case and "Windows PV" defaults to
VirtIO everywhere which is good but doesn't help me.
Is there any other type that could provide me virtio+e100 or how can I
add myself a new os type? Haven't seen any such option in the
api/cloudmonkey.
Lucian
