The error you are seeing in you agent.log seems for me like an "old friend".
Take a look into this:
https://github.com/apache/cloudstack/issues/5491#issue-1003559121
You can check it quiet fast.
Connect to one of the hosts and try to mount the nfs-share manually to an
temp-folder.
suggest to use t
It appears that it has the capability to use nfs4 (It's using Ceph Octopus),
but it is not clear whether it is using nfs3 or nfs4. I *think* it is using nfs4
On 2021/10/07 16:14:36, "vas...@gmx.de" wrote:
> reading the agent.log you have trouble mounting the storage properly.
> Does your nfs-se
On KVM, Cloudstack relies on the underlying Linux OS to do the base
network configuration. Linux "port groups" are called "bonds" and
virtual switches are called "bridges". In the Linux OS you set up the
bond0 for all of the ports that will be part of the port group, with
whatever parameters yo
reading the agent.log you have trouble mounting the storage properly.
Does your nfs-server for providing secondary storage provide nfs4 ?
Am Do., 7. Okt. 2021 um 15:33 Uhr schrieb Peter Stine <
petrus.st...@gmail.com>:
> Hey everyone,
>
> I had to rework my network and reinstall cloudstack. Whi
Hi,
Thank you for the provided information, I will test.
Regards,
Cristian
-Original Message-
From: vas...@gmx.de
Sent: Thursday, October 7, 2021 6:37 PM
To: users@cloudstack.apache.org
Subject: Re: Multiple Network labels - custom
it should work , as i am am using this for provi
it should work , as i am am using this for providing some "special"
networks myself in my environment.
maybe for a better understanding you can take a look at the following
https://www.shapeblue.com/understanding-cloudstacks-physical-networking-architecture/
and there the section "advanced network
Hey everyone,
I had to rework my network and reinstall cloudstack. While I am getting the
hosts to appear, they will not start any system VMs. They keep failing and
iterating. It looks like there is an error in libvirtd (I am also using systemd
for my networking), but I can't quite seem to figu
Hi,
In a much simpler way.
I have 2 networks, 1 shared and 1 isolated, the problem i have here,
both are using the same guest traffic label, because of this, I'm not able
to use these on different labels/nics, both are using the same traffic
type. Even if I add an additional physical networ
just my thoughts.
if i am understanding your intention correctly, you want to use a dedicated
physical network on the hosts for "customized" guest traffic, correct?
You will need to add a "new" physical network to the zone with the
networklabel, assaign the traffic type "guest" and start to use
Hi Piotr,
As far as I know, vlan trunk is supported only by OVS on kvm.
Unfortunately, this feature is not supported in cloudstack.
-Wei
On Thu, 7 Oct 2021 at 09:21, Piotr Pisz wrote:
> Hi,
>
> In vSphere it is possible to create port group with vlan range 1-4094, can
> we done the same on kvm
Hi,
In vSphere it is possible to create port group with vlan range 1-4094, can
we done the same on kvm with L2 network (on openvswitch or bridge)?
Can we use in cloudstack vm with vlan trunk?
Regards,
Piotr
11 matches
Mail list logo
