[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333698#comment-14333698
 ] 

Amogh Vasekar commented on CLOUDSTACK-8265:
-------------------------------------------

Hi,

You'd simply need to do this for KVM, VMware and LXC :
INSERT IGNORE INTO `cloud`.`guest_os_hypervisor` (uuid,hypervisor_type, 
hypervisor_version, guest_os_name, guest_os_id, created, is_user_defined) 
VALUES (UUID(),'VMware', '<vmware version supporting this OS>', '<vmware name 
for the OS>', <'id of OS in guest_os table'>, now(), 0);

INSERT IGNORE INTO `cloud`.`guest_os_hypervisor` (uuid,hypervisor_type, 
hypervisor_version, guest_os_name, guest_os_id, created, is_user_defined) 
VALUES (UUID(),'KVM', 'default', '<KVM name for the OS>', <'id of OS in 
guest_os table'>, now(), 0);

INSERT IGNORE INTO `cloud`.`guest_os_hypervisor` (uuid,hypervisor_type, 
hypervisor_version, guest_os_name, guest_os_id, created, is_user_defined) 
VALUES (UUID(),'LXC', 'default', '<LXC name for the OS>', <'id of OS in 
guest_os table'>, now(), 0);


> table guest_os_hypervisor is missing newer os types, results in bad vms
> -----------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8265
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8265
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.5.0
>            Reporter: Marcus Sorensen
>            Assignee: Anthony Xu
>            Priority: Blocker
>             Fix For: 4.5.0
>
>
> During testing of 4.5 I noticed that 1)Someone has added new OS types for 
> templates (e.g. Ubuntu 14.04), and 2) these are missing, at least for KVM, 
> from table guest_os_hypervisor, which results in suboptimal hardware 
> selection for these types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to