Hi nitin,
Currently I'm using this[1] system vm template. Are there any alternative
url which I can use?
[1] -
http://jenkins.buildacloud.org/job/build-systemvm-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvmtemplate-master-xen.vhd.bz2
On Thu, Oct 16, 2014 at 8:08 AM, Asanka s
HI nitin,
Yes, I upgraded the system vm template to the latest version. So which
template can I use? Could you please give me a link?
On Thu, Oct 16, 2014 at 5:14 AM, Nitin Mehta wrote:
> Did you upgrade your system vm templates ? There is an issue in the latest
> ones where the template version
Did test this on 4.4.1-RC3, did work well with OSX client.
I've used
http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.1-7-xen.vhd.bz2
from 4.4.1 release-notes on xenserver.
does the issue still persist?
regards,
On Thu, Oct 9, 2014 at 5:27 PM, Steve Searles wrote:
> Hello ever
Did you upgrade your system vm templates ? There is an issue in the latest
ones where the template version is not in the correct format and is
resulting in that.
On 15/10/14 6:08 AM, "Asanka sanjaya Herath" wrote:
>I'm getting this error when I'm going to start instances in cloudstack. I
>was ab
Ah, I see. I believe you'd need access to whatever IP the consoleproxy vm
is listening on. I don't actually use the console proxy vm for my purposes,
but I don't think you need to open the vnc console or libvirt ports to the
outside. If the console proxy works internally, you probably just don't
ha
Would this be on the Console VM, Or from the node? Need to know which local IP
I need to redirect it to.
I see in the log, it’s coming from 192.168.1.43 (which is console vm) so I
suspect there?
--
Mo
Sent with Airmail
On October 15, 2014 at 1:00:12 PM, Marcus (shadow...@gmail.com) wrote:
>From outside, (say from hotel, through home router, to mgmt server) you
need access to the web ui and for the web ui to have access to the api
server. That would just be 8080 (UI) and 8096(API), I believe. you wouldn't
need libvirt and the others unless you are stringing mgmt servers and hosts
acr
Hello,
I’ve setup Cloudstack on my home server. However, it works without issues
locally. When I attempt to pull up console outside, it times out. I have of
course enabled ports for SSH / UI, so I can setup instances, but I am not sure
what else I need to permit through my router to allow all t
Martin, those where a release candidate and shouldn't have been there yet.
A new release candidate is under vote now (see the dev list) You'll have to
create your own rpms from it.
sorry for the inconvenience,
Daan
2014-10-15 17:19 GMT+02:00 Martin Emrich :
> Hi!
>
>
>
> Last Week I ran yum up
Hi!
Last Week I ran yum update on my preproduction management server (4.4.0) , and
ended up with CS 4.4.1. After fixing some stuff (manually patching the DB,
inserting the new systemvm) I got it running again.
Now I tried installing CS 4.4.1 on my playground server, but the packages seem
to be
I've managed to get link local working my modifying the routing (disable
the fw atm too).
/sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
0.0.0.0 10.158.231.1 0.0.0.0 UG0 00 eth1
150.158.231.0
I've started out with cloudstack a couple days ago and I've hit a bit of a
brick wall.
The installation is running on a system that has two network interfaces, a
public one and private one (connecting to a local network).
auto eth0
iface eth0 inet manual
auto eth1
iface eth1 inet static
I'm getting this error when I'm going to start instances in cloudstack. I
was able to add instances without having any issue till today. But I
suddenly got this error today. Any ideas?
INFO [c.c.s.StorageManagerImpl] (Work-Job-Executor-6:ctx-c9612ed8
job-55/job-56 ctx-6055652d) Storage pool null
If you have assigned a certificate then it will be 443, otherwise it is
going over port 80.
On 10/14/14, 5:54 PM, "Mo" wrote:
>Hello,
>
>Locally I can access the console of my instances without issue. Outside
>of my network, I have trouble; therefore, I need to open ports. The
>problem is,
Hi Tim,
Have you tested whether your VM instances can ping their respective virtual
routers. This will help narrow down where the issue is occurring. If VM-VR
comms is failing, migrate VR to same host as VM and try again, to rule out
infrastructure (ie switches/VLANs etc). That would leave you
15 matches
Mail list logo
