On 6/24/21 5:31 AM, Andrija Panic wrote:
> LXC is nothing short of untested recently (for years) - the ones that DO
> work (used in production by people) are KVM, XenServer/XCP-ng, VMware.
> That's all.
> LXC, OVM and co, are most probably doomed, to be honest.
Thanks, I'm not surprised to hear
LXC is nothing short of untested recently (for years) - the ones that DO
work (used in production by people) are KVM, XenServer/XCP-ng, VMware.
That's all.
LXC, OVM and co, are most probably doomed, to be honest.
Best,
On Wed, 23 Jun 2021 at 09:27, Joshua Schaeffer
wrote:
>
> A thing that
A thing that I briefly touched somewhere upstairs ^^^ - for each
traffic
type you have defined - you need to define a traffic label - my
deduction
capabilities make me believe you are using KVM, so you need to set
your KVM
traffic label for all your network
You're most welcome!
(and apologies about the naming convention jokes - I also would name things
in a meaningful way instead of bond0/1 etc - the same way I'm switching
back from those "predictable interface names "ensp0p1" and similar to
old-fashioned eth0, eth1 etc - not sure what kind of drugs
Andrija,
Thanks so much for all the details. I'm out of the office for the next
couple of days so will update my cloud with your suggestions when I get
back.
As far as the "fancy" naming, I just never found names like bondX useful
when Linux allows naming the network device something else.
BTW, once you thing you have fixed all your network configuration issues -
destroy all system VM (CPVM, SSVM and restart all networks with "cleanup" -
so that new VMs are created_
Inside SSVM, run the the following script, which should give you results
similar as below - confirming that your SSVM
Since you really bothered to provide so very detailed inputs and help us
help you (vs what some other people tend to do) - I think you really
deserved a decent answer (and some explanation).
The last question first -even though you don't specify/have dedicated
Storage traffic, there will be an
So Suresh's advise has pushed me in the right direction. The VM was up but the
agent state was down. I was able to connect to the VM in order to continue
investigating and the VM is having network issues connecting to both my load
balancer and my secondary storage server. I don't think I'm
" There is no secondary storage VM for downloading template to image store
LXC_SEC_STOR1 "
So next step to investigate why there is no SSVM (can hosts access the
secondary storage NFS, can they access the Primary Storage, etc - those
tests you can do manually) - and as Suresh advised - one it's
HI Joshua,
What is the agent state of secondarystoragevm in the UI. If it is not 'Up', you
can SSH to it and check the status of agent service there (service cloud
status). Have you noticed any errors in the ssvm log at '
/var/log/cloud/cloud.out' if the service is running.
Regards,
Suresh
I've setup ACS 4.15 and created the first zone on it using the wizard through
primate. The zone is enabled and isn't showing any issues in the UI. I can see
two system vm's running (secondarystoragevm and consoleproxy) and can SSH into
the VM's from the compute node. However when I try to add a
11 matches
Mail list logo
