You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sanjay Tripathi (JIRA)" <ji...@apache.org> on 2013/07/29 11:03:48 UTC

[jira] [Assigned] (CLOUDSTACK-3853) System VM Template for Hyper-V has wrong guest OS type Information on the Database

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sanjay Tripathi reassigned CLOUDSTACK-3853:
-------------------------------------------

    Assignee:     (was: Sanjay Tripathi)
    
> System VM Template for Hyper-V has wrong guest OS type Information on the Database
> ----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3853
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3853
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>         Environment: Default template database, e.g.
> mysql> select URL from template_view where hypervisor_type='Hyperv';
> +---------------------------------------------------------------------------+
> | url                                                                       |
> +---------------------------------------------------------------------------+
> | http://download.cloud.com/templates/acton/acton-systemvm-02062012.vhd.bz2 |
> +---------------------------------------------------------------------------+
> 1 row in set (0.00 sec)
>            Reporter: Donal Lafferty
>
> Image recorded as Hyper-V system VM is not a valid Hyper-V image.  It will not boot :(
> Fortunately, the more recent builds of the Hyper-V system VM do boot.  This image has been examined, and it has the correct drivers for Hyper-V.  See http://dlafferty.blogspot.co.uk/2013/07/installing-hyper-v-pv-drivers-for-linux.html for details of the required drivers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira