You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Nux! <nu...@li.nux.ro> on 2014/04/22 10:36:46 UTC
Creating or customising OS type
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
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
Re: Creating or customising OS type
Posted by Nux! <nu...@li.nux.ro>.
On 25.04.2014 01:31, Marcus wrote:
> Since other hypervisors are already doing it, I have no problem making
> the
> KVM agent 'aware' of the magic strings. I'll commit this for future
> releases.
Wunderbar! Thanks, Marcus.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
Re: Creating or customising OS type
Posted by Amogh Vasekar <am...@citrix.com>.
Hi,
Might this be of use to you?
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Proposal+-+Ability+t
o+add+new+guest+OS+mappings
Thanks,
Amogh
On 5/18/14 7:33 PM, "Marcus" <sh...@gmail.com> wrote:
>Not sure exactly, there is some details table or column associated with
>the
>template you register, and it is passed as details to the agent in a
>StartCommand.
>On Apr 25, 2014 2:27 AM, "Nux!" <nu...@li.nux.ro> wrote:
>
>> On 25.04.2014 01:31, Marcus wrote:
>>
>>> Since other hypervisors are already doing it, I have no problem making
>>>the
>>> KVM agent 'aware' of the magic strings. I'll commit this for future
>>> releases.
>>>
>>
>> Marcus,
>>
>> So I learn a new thing today, too, can you tell me where in the DB is
>>kept
>> this information that we pass via cloudmonkey? i.e. what is telling the
>> agent to use these specifics, VirtIO devices, Intel NICs and so on?
>>
>> Lucian
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
Re: Creating or customising OS type
Posted by Marcus <sh...@gmail.com>.
Not sure exactly, there is some details table or column associated with the
template you register, and it is passed as details to the agent in a
StartCommand.
On Apr 25, 2014 2:27 AM, "Nux!" <nu...@li.nux.ro> wrote:
> On 25.04.2014 01:31, Marcus wrote:
>
>> Since other hypervisors are already doing it, I have no problem making the
>> KVM agent 'aware' of the magic strings. I'll commit this for future
>> releases.
>>
>
> Marcus,
>
> So I learn a new thing today, too, can you tell me where in the DB is kept
> this information that we pass via cloudmonkey? i.e. what is telling the
> agent to use these specifics, VirtIO devices, Intel NICs and so on?
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
Re: Creating or customising OS type
Posted by Nux! <nu...@li.nux.ro>.
On 25.04.2014 01:31, Marcus wrote:
> Since other hypervisors are already doing it, I have no problem making
> the
> KVM agent 'aware' of the magic strings. I'll commit this for future
> releases.
Marcus,
So I learn a new thing today, too, can you tell me where in the DB is
kept this information that we pass via cloudmonkey? i.e. what is telling
the agent to use these specifics, VirtIO devices, Intel NICs and so on?
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
Re: Creating or customising OS type
Posted by Marcus <sh...@gmail.com>.
Since other hypervisors are already doing it, I have no problem making the
KVM agent 'aware' of the magic strings. I'll commit this for future
releases.
On Thu, Apr 24, 2014 at 6:10 PM, Nux! <nu...@li.nux.ro> wrote:
> On 25.04.2014 00:37, Marcus wrote:
>
>> updated the patch. You can also see if specifying nicAdapter works in your
>> existing build.
>>
>
> I've broken the existing build, but the new patch works a treat, thanks!
> I tried both with just disk=virtio and with disk & net of type virtio.
>
> Good job! Do you see this feature important enough to be relied upon? Just
> so I know if I should use it in production or not, ideally it should make
> it in subsequent releases.
>
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
Re: Creating or customising OS type
Posted by Nux! <nu...@li.nux.ro>.
On 25.04.2014 00:37, Marcus wrote:
> updated the patch. You can also see if specifying nicAdapter works in
> your
> existing build.
I've broken the existing build, but the new patch works a treat,
thanks!
I tried both with just disk=virtio and with disk & net of type virtio.
Good job! Do you see this feature important enough to be relied upon?
Just so I know if I should use it in production or not, ideally it
should make it in subsequent releases.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
Re: Creating or customising OS type
Posted by Marcus <sh...@gmail.com>.
updated the patch. You can also see if specifying nicAdapter works in your
existing build.
On Thu, Apr 24, 2014 at 4:43 PM, Nux! <nu...@li.nux.ro> wrote:
> On 24.04.2014 17:28, Marcus wrote:
>
>> 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
>>
>
> I've patched ACS with this and generated a new set of RPMs, after the
> update however I was not only unable to create the custom type, but all
> templates failed.
> See agent logs here:
> http://fpaste.org/96815/13983790/raw/
>
> This is how I added the template:
> cloudmonkey register template ostypeid=73188ae8-a44f-11e3-bae5-f6145f6a2f37
> passwordenabled=true isfeatured=true ispublic=true url=
> http://10.193.172.130/templates/windows_migration_50G.qcow2name=virto_e1000_50 hypervisor=kvm zoneid=a6572c99-b268-4a6b-8bd0-bf2cafa4c04b
> format=qcow2 details[0].rootDiskController=virtio
> displaytext=virto_e1000_50
>
> "ostypeid=73188ae8-a44f-11e3-bae5-f6145f6a2f37" means Windows 2008.
>
>
> Lucian
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
Re: Creating or customising OS type
Posted by Nux! <nu...@li.nux.ro>.
On 24.04.2014 17:28, Marcus wrote:
> 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
I've patched ACS with this and generated a new set of RPMs, after the
update however I was not only unable to create the custom type, but all
templates failed.
See agent logs here:
http://fpaste.org/96815/13983790/raw/
This is how I added the template:
cloudmonkey register template
ostypeid=73188ae8-a44f-11e3-bae5-f6145f6a2f37 passwordenabled=true
isfeatured=true ispublic=true
url=http://10.193.172.130/templates/windows_migration_50G.qcow2
name=virto_e1000_50 hypervisor=kvm
zoneid=a6572c99-b268-4a6b-8bd0-bf2cafa4c04b format=qcow2
details[0].rootDiskController=virtio displaytext=virto_e1000_50
"ostypeid=73188ae8-a44f-11e3-bae5-f6145f6a2f37" means Windows 2008.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
Re: Creating or customising OS type
Posted by Marcus <sh...@gmail.com>.
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! <nu...@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
>
Re: Creating or customising OS type
Posted by Nux! <nu...@li.nux.ro>.
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
Re: Creating or customising OS type
Posted by Marcus <sh...@gmail.com>.
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.
On Thu, Apr 24, 2014 at 2:30 AM, Nux! <nu...@li.nux.ro> wrote:
> On 24.04.2014 07:58, Marcus wrote:
>
>> I have an agent for you to try. you can force install the RPM over the top
>> of your existing 4.3 one and restart the agent. If you have an issue you
>> can just reinstall the stock RPM and restart the agent again. It reads the
>> details per Ilya's register template method, if they don't exist it does
>> the default thing.
>>
>> http://marcus.mlsorensen.com/cloudstack-extras/nux/
>> cloudstack-agent-4.3.0-1.el6.x86_64.rpm
>>
>> If that works I can commit the fix. It worked for me, but I was testing
>> master.
>>
>
> Hi Marcus and thanks, but I'm not following here. What does the agent have
> to do with my problem?
> I'm just trying to find a profile that would give me virtio_blk+e1000; in
> 4.2 "Windows PV" did this, but not in 4.3 (which, again, is great, but
> doesn't help me right now).
>
> I'm on 4.3 release + ipset patch[1].
>
> Anyway, this is not really a tragedy, I can just move them on the "Windows
> 2008" profile which gives me IDE blk (I know..) and E1000 nic.
>
>
> Lucian
>
> [1] https://issues.apache.org/jira/browse/CLOUDSTACK-6240
>
>
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
Re: Creating or customising OS type
Posted by Nux! <nu...@li.nux.ro>.
On 24.04.2014 07:58, Marcus wrote:
> I have an agent for you to try. you can force install the RPM over the
> top
> of your existing 4.3 one and restart the agent. If you have an issue
> you
> can just reinstall the stock RPM and restart the agent again. It reads
> the
> details per Ilya's register template method, if they don't exist it
> does
> the default thing.
>
> http://marcus.mlsorensen.com/cloudstack-extras/nux/cloudstack-agent-4.3.0-1.el6.x86_64.rpm
>
> If that works I can commit the fix. It worked for me, but I was
> testing
> master.
Hi Marcus and thanks, but I'm not following here. What does the agent
have to do with my problem?
I'm just trying to find a profile that would give me virtio_blk+e1000;
in 4.2 "Windows PV" did this, but not in 4.3 (which, again, is great,
but doesn't help me right now).
I'm on 4.3 release + ipset patch[1].
Anyway, this is not really a tragedy, I can just move them on the
"Windows 2008" profile which gives me IDE blk (I know..) and E1000 nic.
Lucian
[1] https://issues.apache.org/jira/browse/CLOUDSTACK-6240
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
Re: Creating or customising OS type
Posted by ilya musayev <il...@gmail.com>.
Marcus,
I was away for a bit and missed this message, i'll be standing up KVM
environments soon and can try this commit - though it may take some time.
Thank you,
Regards
ilya
On 4/24/14, 2:58 AM, Marcus wrote:
> I have an agent for you to try. you can force install the RPM over the
> top of your existing 4.3 one and restart the agent. If you have an
> issue you can just reinstall the stock RPM and restart the agent
> again. It reads the details per Ilya's register template method, if
> they don't exist it does the default thing.
>
> http://marcus.mlsorensen.com/cloudstack-extras/nux/cloudstack-agent-4.3.0-1.el6.x86_64.rpm
>
> If that works I can commit the fix. It worked for me, but I was
> testing master.
>
>
> On Wed, Apr 23, 2014 at 10:59 PM, Marcus <shadowsor@gmail.com
> <ma...@gmail.com>> wrote:
>
> 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 <shadowsor@gmail.com
> <ma...@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.lists@gmail.com
> <ma...@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
>
>
>
>
>
Re: Creating or customising OS type
Posted by Marcus <sh...@gmail.com>.
I have an agent for you to try. you can force install the RPM over the top
of your existing 4.3 one and restart the agent. If you have an issue you
can just reinstall the stock RPM and restart the agent again. It reads the
details per Ilya's register template method, if they don't exist it does
the default thing.
http://marcus.mlsorensen.com/cloudstack-extras/nux/cloudstack-agent-4.3.0-1.el6.x86_64.rpm
If that works I can commit the fix. It worked for me, but I was testing
master.
On Wed, Apr 23, 2014 at 10:59 PM, Marcus <sh...@gmail.com> wrote:
> 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 <sh...@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.lists@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
>>>>
>>>>
>>>
>>
>
Re: Creating or customising OS type
Posted by Marcus <sh...@gmail.com>.
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 <sh...@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.lists@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
>>>
>>>
>>
>
Re: Creating or customising OS type
Posted by Marcus <sh...@gmail.com>.
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
<il...@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
>>
>>
>
Re: Creating or customising OS type
Posted by ilya musayev <il...@gmail.com>.
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
>
Re: Creating or customising OS type
Posted by Nux! <nu...@li.nux.ro>.
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
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
Re: Creating or customising OS type
Posted by Nux! <nu...@li.nux.ro>.
On 23.04.2014 04:50, ilya musayev wrote:
> 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.
Thanks Ilya,
>
> 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.
For some reason this table in my case is almost empty:
http://img.nux.ro/4Jh-Selection_061.png
>
> 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!
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
Re: Creating or customising OS type
Posted by ilya musayev <il...@gmail.com>.
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
>