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

Sanjay Tripathi commented on CLOUDSTACK-7222:
---------------------------------------------

We need to document this behaviour.

CloudStack is not checking the minimum memory required to deploy a VM, it will 
just goahead with the VM deployment and later VM may go to repair state if the 
memory(or any other resource) in compute offering is less then the min. reqd. 
memory for that guestOS.

> [GPU] Windows 2012 Server instance created from Windows with PV drivers 
> installed and using vGPU offering is going to repair state and moved to 
> stopped state with low memory 
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7222
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7222
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Doc
>    Affects Versions: 4.5.0
>            Reporter: Sailaja Mada
>            Assignee: Sanjay Tripathi
>            Priority: Minor
>             Fix For: 4.5.0
>
>         Attachments: apilog.log, management-server.log
>
>
> Steps:
> 1. Install and Configure Adv zone using Xen 6.2.5 which has GRID K2
> 2. Create Service Offering using K2 - K200 profile of vGPU
> 3. Deploy windows 2012 instance with ISO using normal compute offering 
> without GPU 
> 4. Install Windows 2012 instance and install PV drivers
> 5. Stop the VM and create template from ROOT volume
> 6. Deploy windows 2012 instance using this template with vGPU K200 service 
> offering
> 7. Windows instance got created using this card on XenServer.  But got into 
> repair state after sometime. 
> 8. Later this VM got into stopped state.
> 9. Tried to start instance manually , Cloudstack says Instance started and 
> instance moved to running state. But XenServer failed to start the instance.
> 10. Later Cloudstack also marked the instance in stopped state.
> Attached detailed logs



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

Reply via email to