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.

@badrAZ Yep.. that did the trick..

All working now.. nice.

Hi guys,

I'm trying to follow the directions here Docker-in-XCP-ng to get a core.os host working to play with docker on xcp.

However, I'm not getting far.

I have finally managed to get the coreos VM installed but I'm not seeing any sign of docker on the interface anywhere.

I'm can't ssh into the vm because it seems the ssh keys have been ignored from the cloud config (and I see from the core.os docs that cloud-config is deprecated anyway, not sure if that's the issue) so I'm stuck using the XEO console for the moment which is a pain because you can't paste into it.

I manually added my ssh keys to the core users .ssh/authorized_keys file, but to no avail.

Has anyone managed to get this working? I'm curious how.

I might also say, that although the coreOS vm is not saying that tools are not installed, I'm not seeing an IP address in the networking tab either.

Ta
Peter.

OK, seems I wasn't trying hard enough.

I was trying to mount the tools under the iso list, but when I look further down the list to xc-ng Tools it turns out I can mount the tools from there as long as I do it manually (mount /dev/sr0 /media/blahblah).

Installed now, all good.

Groan... maybe testing with a machine what actually boots in kvm to start with would be a good idea... trust me to pick a broken machine to test with... now.. lets try that again shall we? Sorry for wasting your time all... will report back how I go with a working machine.

P.

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.