Hi Guys.

Just a note for dumb bums like me... I tried out XO Lite (coming along nicely) but it took be a bit to work out that it needed to be installed on the pool master.

I put it onto one of the slaves, and tried to log in, but got no feedback at all, just nothing changed.

I eventually looked in the xo logs and found it was complaining about being on the slave not the master.. duh.. when you think about it.. but some feedback in the gui would help

I'm running XO as well, not from sources.. but today, everthing worked as it should??

Lets see what happens tomorrow.

Not wanting to be a "me too" but I'm seeing exactly the same thing.

Some VM's (unfortunately in my case large ones) and doing daily fulls rather than deltas.

Backup taking 14 hours instead of 2 or 3.

Similar etup to @S-Pam with nfs as the remote target.

@olivierlambert Ahh... it is 10 on the inside. 9 on the wrapper

@mathiashedberg I've just checked the ones I built that started all of this... they are deb 9.

Peter.

@benjireis I did all of that... (with sudo first)... same result though.

Do you want me to start a ticket and a tunnel?

Peter.

Hy Guys,

just having a look at the new kubernetes cluster creation (was about to start trying microk8s when I found this good stuff).

I have run the creation, got the master and three workers running, got the green finished popup (after a long time) and can log into the master and nodes happily, however,

kubectl get nodes (on the master) gives me
The connection to the server localhost:8080 was refused - did you specify the right host or port?

Not sure where to go from here to be honest.

Peter.

Thanks for the input @tony and @stormi. Turns out I've managed to get most of the machines back on the second node after getting some help to force it back to being the master and powering off dead VM's etc. so I think I've avoided having to do this.

It is really useful info however, and I will probably give this a try at some point just so I can if I ever need too.

Thanks again.

Hi Guys,

I'm a bit stuck here. My XCP system has crashed horribly (in another thread) and I really need to get one of the VM's running somewhere reasonably quickly.

As the VM was running on shared storage I have the vhd file on the storage, but the question is, which one of the dozens of vhd files is the one I need.

Is there any way to determine which vhd was attached to which vm without the ability to connect to a running XO or XSconsole?

I'm guessing there probably isn't, but thought it worth the ask.

Peter.

Yep.. that did it... started it on the older host, and can now migrate it backwards and forwards with on issues...

Thanks Olive... as always.

Peter.

Ohh... OK. That's interesting. I must have done it the other way the first time I set this up because I've been migrating it backwards and forwards happily for a while (the joys of lab hardware where everything is different).

Thanks Oliver, I'll give it a go.

Peter.

Hi Guys,

I've just had to reformat and re-add one of my hosts to the pool after some issues yesterday. Everything is happy, except, when I try and migrate the docker host I have running onto this host (that used to work fine) I get "The host does not have some of the CPU features that the VM is currently using" in XCP-ng Center and "The VM is incompatible with the CPU features of the destination host. Would you like to force it anyway?" in XO.

I have yum installed xscontainer on it (and rebooted) but no joy at the moment.

Ideas??

I've not imported full VM's but have imported a number of disks and they worked reasonably quickly I guess, although I have only very limited reference from another much more powerful setup to compare with.

Peter.

@badrAZ Yep.. that did the trick..

All working now.. nice.

Um... no.. I have "no plugins found" under settings->plugins. Maybe need to install it??

P.

OK, no dramas. That explains it. UI change would be a good thing.

Just following the bouncing ball on https://xen-orchestra.com/blog/xo-audit/ in my lab XOA from sources (recently updated and re-built) and it doesn't seem to want to work. Not a show stopper for my by any means, just thought I'd report it incase this was a problem.

When I try and generate a new fingerprint I get..

vm.stats
{
  "id": "dad6b031-f28f-2d5b-d345-1ff8e328f422"
}
{
  "message": "Unable to get the true granularity: 60",
  "name": "FaultyGranularity",
  "stack": "FaultyGranularity: Unable to get the true granularity: 60
    at XapiStats._getAndUpdateStats (/home/pnunn/xen-orchestra/packages/xo-server/src/xapi-stats.js:378:13)"
} 

Again, not sure if this needs to be registered to make this work or not... but there you go.

Peter.

Running two hosts on the beta in my lab and so far have had no issues at all (touch wood). Looking forward to this hitting production.

P.

@pnunn Got it....

guest tools hadn't installed correctly.

Manually installed them.. ran the xscontainer-prepare-vm again and now have a container tab on the core OS machine showing the containers running.

P.

I tried the commands in "can-t-start-docker-container-from-xoa" but it blew up unfortunately.

xscontainer-prepare-vm -v 0390f015-9302-ccbd-e4af-1bbbba283cfd -u core
Would you like to push a pool-specific public SSH key into the ~/.ssh/authorized_keys file of the specified VM and therefore authorize hosts in the pool to interact with the containers inside the VM?
Answer y/n:
y
Traceback (most recent call last):
  File "/usr/bin/xscontainer-prepare-vm", line 272, in <module>
    sys.exit(main())
  File "/usr/bin/xscontainer-prepare-vm", line 246, in main
    resultcode = _handle_ssh(session, options)
  File "/usr/bin/xscontainer-prepare-vm", line 139, in _handle_ssh
    resultcode = push_ssh_key(session, options.vmuuid, options.username)
  File "/usr/bin/xscontainer-prepare-vm", line 80, in push_ssh_key
    print(docker.ERROR_CAUSE_NETWORK)
AttributeError: 'module' object has no attribute 'ERROR_CAUSE_NETWORK'

Maybe related, when I tried to look at the current sshhostkey it said the parameter didn't exist.

Not too concerned, portainer seems to be the go instead. But thought I'd report my experiences.