Re: Can't launch VMs

Never thought of that. will have to write an update for that as well On Tue, Oct 7, 2014 at 8:30 AM, Carlos Reátegui wrote: > That was definitely a bug but will not fix my problem. See my comment in > the JIRA. > > > On Oct 6, 2014, at 11:04 PM, Daan Hoogland > wrote: > > I just had a look at

Re: Can't launch VMs

That was definitely a bug but will not fix my problem. See my comment in the JIRA. On Oct 6, 2014, at 11:04 PM, Daan Hoogland wrote: > I just had a look at the code and found a bug. It might have not thrown an > exception where it should have. sorry about that. I am fixing that and will > p

Re: Can't launch VMs

I just had a look at the code and found a bug. It might have not thrown an exception where it should have. sorry about that. I am fixing that and will port it to later versions. On Tue, Oct 7, 2014 at 7:56 AM, Carlos Reátegui wrote: > What is it looking for? > > Where is that code? Maybe I can

Re: Can't launch VMs

What is it looking for? Where is that code? Maybe I can have a look. On Oct 6, 2014, at 10:54 PM, Daan Hoogland wrote: > > On Mon, Oct 6, 2014 at 9:41 PM, Carlos Reátegui wrote: > 2014-09-29 09:56:03,519 DEBUG [c.c.u.d.Upgrade430to431] (main:null) updating > vlan URIs > 2014-09-29 09:56:03,

Re: Can't launch VMs

On Mon, Oct 6, 2014 at 9:41 PM, Carlos Reátegui wrote: > 2014-09-29 09:56:03,519 DEBUG [c.c.u.d.Upgrade430to431] (main:null) > updating vlan URIs > 2014-09-29 09:56:03,523 DEBUG [c.c.u.d.Upgrade430to431] (main:null) Done > updateing vlan URIs > ​This is what I wanted to have confirmed. It should

Re: Can't launch VMs

72.30.45.1 | >> 172.30.45.163 | vlan://untagged | Dhcp | Deallocating | Start | >> | 46 | 37 | 204 | 255.255.255.0 | 172.30.45.1 | >> 172.30.45.167 | vlan://untagged | Dhcp | Deallocating | Start | >> | 22 | 13 |204 | 255.255.255

Re: Can't launch VMs

| Deallocating | Start | >>> | 107 | 79 | 204 | 255.255.255.0 | 172.30.45.1 | >>> 172.30.45.155 | vlan://untagged | Dhcp | Reserved | Start | >>> | 20 | 11 |204 | 255.255.25

Re: Can't launch VMs

| Dhcp | Deallocating | Start | >> | 101 | 71 |204 | 255.255.255.0 | 172.30.45.1 | >> 172.30.45.163 | vlan://untagged | Dhcp | Deallocating | Start | >> | 46 | 37 | 204 | 255.255.255.0 | 172.30.45.1 | >> 172.30.45.167 | vlan://

Re: Can't launch VMs

n://untagged | Dhcp | Deallocating | Start | >> | 101 | 71 |204 | 255.255.255.0 | 172.30.45.1 | >> 172.30.45.163 | vlan://untagged | Dhcp | Deallocating | Start | >> | 46 | 37 | 204 | 255.255.255.0 | 172.30.45.1 | >> 172.30.45.167 | vlan

Re: Can't launch VMs

255.255.255.0 | 172.30.45.1 | > 172.30.45.173 | NULL| Dhcp | Deallocating | Start | > +-+-++---+-+-------+-----+--+--+-+ > 92 rows in set (0.00 sec) > > > >

Re: Can't launch VMs

| > > +-+-++-------+---------+---+-+--+--+-+ > 92 rows in set (0.00 sec) > > > > > On Oct 3, 2014, at 2:

Re: Can't launch VMs

ll? Should be vlan://untagged > > > From: Carlos Reátegui > Reply-To: "dev@cloudstack.apache.org" > Date: Friday, October 3, 2014 at 12:48 PM > To: "dev@cloudstack.apache.org" > Cc: Daan Hoogland > Subject: Re: Can't launch VMs > >

Re: Can't launch VMs

t;dev@cloudstack.apache.org" Date: Friday, October 3, 2014 at 12:48 PM To: "dev@cloudstack.apache.org" Cc: Daan Hoogland Subject: Re: Can't launch VMs Don’t know how to “check your Œnetworks¹ table and see if the URI is correct." Here is my networks table:

Re: Can't launch VMs

er hits line 1025 instead. > So, check your Œnetworks¹ table and see if the URI is correct. > > > From: Carlos Reátegui > Reply-To: "dev@cloudstack.apache.org" > Date: Friday, October 3, 2014 at 12:15 PM > To: "dev@cloudstack.apache.org" > Subject

Re: Can't launch VMs

e: Friday, October 3, 2014 at 12:15 PM To: "dev@cloudstack.apache.org" Subject: Re: Can't launch VMs Thanks for having a look. Inline... On Oct 3, 2014, at 11:38 AM, Chiradeep Vittal wrote: > Not sure what is a ³basic zone no security groups². Basic Zone type with th

Re: Can't launch VMs

Thanks for having a look. Inline... On Oct 3, 2014, at 11:38 AM, Chiradeep Vittal wrote: > Not sure what is a “basic zone no security groups”. Basic Zone type with the following Network Offering: DefaultSharedNetworkOffering as opposed to the default/first option DefaultSharedNetworkOffering

Re: Can't launch VMs

Not sure what is a “basic zone no security groups”. Check your vlan table to see if there has been any allocation of vlans? From: Carlos Reategui mailto:create...@gmail.com>> Reply-To: "dev@cloudstack.apache.org" mailto:dev@cloudstack.apache.org>>, "car...@reat