On Oct 18, 2013, at 9:37 PM, raj kumar wrote:
> Hi guys,
>
> I'm running out of time on cloudstack implementation.
>
> java agent is not running in ssvm, but running console system vm.
>
> In ssvm, I'm getting repeated error:
>
> /var/log/cloud.log shows,
>
> ERROR [cloud.agent.AgentShell]
Hi
I realize this question may be more related to Xen OSS/ XenServer however
all the suggestions I found to my problem implies working on the Xen server
while my Xen server is managed by CloudStack so a stopped VM in CloudStack
doesn't even show up on the XeServer.
I have to migrate a VM (install
thank you;
I found the file :
[root@kvm1 .ssh]# ls
id_rsa.cloud id_rsa.pub.cloud known_hosts
[root@kvm1 .ssh]#
[root@kvm1 network-scripts]# ssh -i ~/.ssh/id_rsa.cloud -p 3922 169.254.2.56
ssh: connect to host 169.254.2.56 port 3922: No route to host
[root@kvm1 network-scripts]#
I get no route
Hy,
Can you try to vnc to sysvm machine?
root/password should be work, if you use the default sysvm template.
Peter
2013.10.19. 17:33 keltezéssel, motty cruz írta:
thank you;
I found the file :
[root@kvm1 .ssh]# ls
id_rsa.cloud id_rsa.pub.cloud known_hosts
[root@kvm1 .ssh]#
[root@kvm1 net
I'm using packages.
As I mentioned, console system vm is running fine.
On Sat, Oct 19, 2013 at 4:13 PM, Sebastien Goasguen wrote:
>
> On Oct 18, 2013, at 9:37 PM, raj kumar wrote:
>
> > Hi guys,
> >
> > I'm running out of time on cloudstack implementation.
> >
> > java agent is not running in
Can you check whether zone is enabled? if not enabled it.
On Sat, Oct 19, 2013 at 9:34 PM, Erdősi Péter wrote:
> Hy,
>
> Can you try to vnc to sysvm machine?
> root/password should be work, if you use the default sysvm template.
>
>
> Peter
>
> 2013.10.19. 17:33 keltezéssel, motty cruz írta:
>
It is not possible due the reason you mentioned
On 19-Oct-2013, at 3:43 AM, Andrija Panic wrote:
> Hi,
>
> I have 2 hosts with all local primary storage, and we have obtained new
> shared primary storage now.
>
> What would be a good/possible way to migrate existing volumes from local to
> sha
Thanks for reply.
And what about creating new VM, cloning old VM's volume to the new volume
(copy/scp, dd, something), and then delete old VM and assign IP address of
old VM to the new VM (by editing the database) ???
Any hack to make this possible ?
Thanks
On 19 October 2013 19:22, Koushik D
Thanks for you support on this matter! it is of a streamly importance. I
can't VNC into the macine, I get the error "no route to hosts"
yes the zone is enable!
I personally don't think it has to do with VLANs because management traffic
does not have VLANs but I could be wrong, also I disabled ipt
management traffic is an separate interface eth1 bridge to cloudbr1,
public traffic and guest on eth0 bridge to cloudbr0
I can't ping public ip, private(management) or local lik
Public IP Address 98.234.34.208
Private IP Address 10.107.0.89
Link Local IP Address 169.254.1.180
both system VMs are
Hy,
2013.10.19. 19:59 keltezéssel, motty cruz írta:
Thanks for you support on this matter! it is of a streamly importance. I
can't VNC into the macine, I get the error "no route to hosts"
But this is not goes over ethernet. Just connect to the vm-s console
same as a non-cloud kvm vm.
You shoul
Log into the vm console, can the system vm ping the respective gateways of each
interface? Are the interfaces configured properly? Can you ping the management
server from the system vm?
Ahmad
> On Oct 19, 2013, at 11:58 AM, motty cruz wrote:
>
> management traffic is an separate interface eth
Hello,
I have a situation where CS has emailed a alert saying host 2 (was the pool
master) is down:
I have found the following :
Checking finds XenServer Host 2 running but not accessible in the pool, its
console show "No VMs Running on this host"
CouldStack reports Host 2 down but also reports
you can try a toolstack restart first (might want to kill hung processes
like xapi). if that doesnt get you far emergency reset pool master to host
2, and do a force reconnect from within cloudstack on host2.
On Sat, Oct 19, 2013 at 1:48 PM, CSG - Ashley Lester <
[email protected]>
Ashley,
I was just playing with this in my own lab...
I'm currently running XenServer 6.2. From what I can tell, CloudStack relies
on the underlying hypervisor to do HA.
I'm thinking CloudStack uses the restart.retry.interval variable to test
whether the host/vm is alive even if the underlying
CloudStack initially queries the host (host1 in this case), but if it fails
to connect to that host.. it will do further investigation by querying the
vm from another host in the cluster. Thats probably why it hasnt tried to
HA your vm's, it can see they're alive from host2.
On Sat, Oct 19, 2013
The email alerts from CS show that it did try HA
Unable to restart csgtest which was running on host name: CSG-XS-H2(id:6),
availability zone: 1, pod: Pod1
What would be the effect on the running VM's for the following : toolstack
restart first (might want to kill hung processes like xapi). if
Thanks Fazy,
when I ran the command dumpxml s-28-VM,
[root@kvm1 networks]# virsh
Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands
'quit' to quit
virsh # dumpxml s-28-VM
On Sat, Oct 19, 2013 at 12:05 PM, Erdősi Péter wr
if you do a toolstack restart, nothing should happen to the vm's. Not 100%
sure but I think the pool master reset (changing the pool master) shouldnt
impact running vm's either. YMMV
On Sat, Oct 19, 2013 at 2:49 PM, CSG - Ashley Lester <
[email protected]> wrote:
> The email alerts
19 matches
Mail list logo
