Re: Attached volume is not visible within the vm

2018-04-06 Thread soundar rajan
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 wrote: > Hi, > > I have created a 5 GB volume

Re: Attached volume is not visible within the vm

2018-04-06 Thread Sateesh Chodapuneedi
What hypervisor the windows vm is deployed on? Regards, Sateesh -Original Message- From: soundar rajan Reply-To: "users@cloudstack.apache.org" Date: Friday, 6 April 2018 at 12:59 PM To: "d...@cloudstack.apache.org" , "users@cloudstack.apache.org" Subject: Re: Attached volume is not

Re: Attached volume is not visible within the vm

2018-04-06 Thread soundar rajan
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 > Reply-To: "users@cloudstack.apache.

Re: Untagged Networking for Advanced Zone possible?

2018-04-06 Thread Dag Sonstebo
Hi Parth, Keep in mind you are in unchartered waters – so there may be some stumbling blocks before you get this to work. I suspect what you have to do is change cloudbr1 such that it is backed by a fake or dummy ethernet interface. What seems to happen is the agent script looks for the networ

Re: Attached volume is not visible within the vm

2018-04-06 Thread soundar rajan
Thanks guys, got it fixed by installing the virto drivers from fedora site On Fri, Apr 6, 2018 at 1:56 PM, soundar rajan 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 wi

Re: Untagged Networking for Advanced Zone possible?

2018-04-06 Thread Parth Patel
Hi Dag, Thanks for the response. I am currently looking into VLANs and network configuration for my case. But I want to know one thing: are "untagged" VLAN networks sufficient for an advanced zone to function with two networks? I did not state I do not want to use VLANs for networking but I wanted

Re: Untagged Networking for Advanced Zone possible?

2018-04-06 Thread Dag Sonstebo
Hi Parth, Take a look through the full email trail – I think we discussed this earlier on. In short the answer is no – by definition you can not run completely untagged isolated networks in an advanced zone – but “tagged” means different things for L2 and L3 isolation. The real answer - “it dep

Re: Upgrade CloudStack from 4.9.2.0 to 4.11.0

2018-04-06 Thread Melanie Desaive
Hi Dag, Stephan and I posted the issues we encountered after upgrading to 4.11 on https://github.com/apache/cloudstack/issues. Those are: Admin Dashboard System Capacity broken with German Locale #2539 problem adding new shared network NIC to VM "A NIC with this MAC address exits for network:" #

Re: Untagged Networking for Advanced Zone possible?

2018-04-06 Thread Parth Patel
Hi Dag, Thank you for guiding me, i know it's a weird use case and probably would never be required in a production environment. I will definitely try to make a dummy interface and give it to the guest network target bridge. I know it would be out of the scope of this email trail for you to explai

Re: Untagged Networking for Advanced Zone possible?

2018-04-06 Thread Dag Sonstebo
Hi Parth, No problem, glad I could help. Let us know how you get on with the dummy interface bridge. With regards to your tagging question – yes this is quite a big and complicated topic. Suffice to summarise it as follows: - Basic zones use a larger L3 network, and guest isolation is done by

Re: Upgrade CloudStack from 4.9.2.0 to 4.11.0

2018-04-06 Thread Dag Sonstebo
Hi Melanie and Stephan, Thanks for logging and glad none of these are show stoppers for you. Regards, Dag Sonstebo Cloud Architect ShapeBlue On 06/04/2018, 13:07, "Melanie Desaive" wrote: Hi Dag, Stephan and I posted the issues we encountered after upgrading to 4.11 on https: