Thanks guys, got it fixed by installing the virto drivers from fedora site On Fri, Apr 6, 2018 at 1:56 PM, soundar rajan <bsoundara...@gmail.com> wrote:
> hypervisor deployed on KVM centos > > On Fri, Apr 6, 2018 at 1:09 PM, Sateesh Chodapuneedi < > sateesh.chodapune...@accelerite.com> wrote: > >> What hypervisor the windows vm is deployed on? >> >> Regards, >> Sateesh >> >> -----Original Message----- >> From: soundar rajan <bsoundara...@gmail.com> >> Reply-To: "users@cloudstack.apache.org" <users@cloudstack.apache.org> >> Date: Friday, 6 April 2018 at 12:59 PM >> To: "d...@cloudstack.apache.org" <d...@cloudstack.apache.org>, " >> users@cloudstack.apache.org" <users@cloudstack.apache.org> >> Subject: Re: Attached volume is not visible within the vm >> >> I am able to view the disk in linux vm centos. The same not working in >> windows. Do i need to install any additional package in windows >> server? >> >> I tried rebooting the windows vm didnt work. >> >> Please help!! >> >> On Fri, Apr 6, 2018 at 11:56 AM, soundar rajan < >> bsoundara...@gmail.com> >> wrote: >> >> > Hi, >> > >> > I have created a 5 GB volume in the storage and attached the volume >> to a >> > vm status shows ready and success >> > >> > when i login to the vm and access the disk management i dont see >> that disk >> > inside the windows server. >> > >> > Tried rescan disk option no luck any idea? >> > >> > OS: Windows Server 2012 R2 >> > >> > cloudstack : 4.11 >> > >> > >> > Regards >> > Shyam >> > >> >> >> DISCLAIMER >> ========== >> This e-mail may contain privileged and confidential information which is >> the property of Accelerite, a Persistent Systems business. It is intended >> only for the use of the individual or entity to which it is addressed. If >> you are not the intended recipient, you are not authorized to read, retain, >> copy, print, distribute or use this message. If you have received this >> communication in error, please notify the sender and delete all copies of >> this message. Accelerite, a Persistent Systems business does not accept any >> liability for virus infected mails. >> > >
