I see you mention 4.3, is it your own build or from the release artifacts?
On Wed, Apr 23, 2014 at 10:13 PM, Marcus <shadow...@gmail.com> wrote: > Guest OS types that will get Virtio disks include: > > Ubuntu > Fedora > CentOS > RedHat 6 > Debian > Other PV > > And unfortunately, they also get virtio nics since they both run the OS > through the same isPVEnabled() method to decide between hardware. > > This random "details" parameter is kind of interesting. I'll have to see > if it gets passed along with StartCommand. I really dislike the trend of > using a 'details' dumping ground for undocumented tweaks, but if it's > already something that VMware is using then we could parse the details for > the same info, if it's being passed along. > > What version of cloudstack are you using? And what OS is the guest agent > running on? > > > > On Wed, Apr 23, 2014 at 7:42 PM, ilya musayev < > ilya.mailing.li...@gmail.com> wrote: > >> I'm KVM useless, perhaps Marcus knows the way. >> >> My mysql output is very different from yours btw. >> >> Regards >> ilya >> >> On 4/23/14, 4:44 AM, Nux! wrote: >> >>> On 23.04.2014 11:35, Nux! wrote: >>> >>>> 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 >>>>> >>>> >>>> I'll go this route and see if it helps. Thanks a lot! >>>> >>> >>> I can confirm it doesn't work, but thank you anyway, it was worth >>> trying. :-) >>> >>> Lucian >>> >>> >> >
