We are now live again with all the VMs - which is a relief.

The above steps from @stormi were great, the one thing I notced was the /etc/stunnel/certs directory didn't exist. I created that manually and everything else seemed happy.

I did have to mess about a bit with the fibre NICs, but I've repeated the previous renaming and that's now running fine.

Thanks very much for all the help - I appreciate it.

@stormi
Hi - thanks very much for the detailed steps. That's definitely made progress.

I think the emergency network reset that was recommended yesterday will need resolving, but xsconsole has settled down already (I'll check the logs shortly)

@stormi
Thanks for this, I've not deleted anything manually (certainly not knowingly!), I'm pleased to hear there's a way to resolve it.

The output is:
xapi-core-24.19.2-1.4.xcpng8.3.x86_64

@stormi
Thanks for getting back to me.

Here's the last 500 lines...xensource.txt

@flakpyro
Thanks for your suggestion. I have tried with the release of 8.3 but I'm having just as many problems with that and XAPI is still bouncing up and down

@Tim-PT
OK - I'm stuck and need to get this moving - I've got a second host that I was trying to add to the pool, is there any way to get the VMs that are on an NFS share working on the new host?

Is that likely to be any easier/quicker to get things up and running again than trying with this host that hasn't updated cleanly?

@olivierlambert yum update is telling me that no packages are marked for update, xe-toolstack-restart hasn't made a difference. At this stage I've restarted the host multiple times too and no difference

DNS was originally pointing at a VM which is no longer available, I've changed this on the host now but I'm getting a message about the mirror being excluded:

@Tim-PT
xapi is not happy

@olivierlambert Thanks very much for the reply. I'll check there now.

I may need to start the trial of your support if I can't get this up

I've made the mistake of restarting an unresponsive host, its the pool master on a single host pool running 8.3 RC1

I've tried to update it so I could add another host to the pool, but after the updates I lost all contact via XO. The VMs were still running, until I restarted the host - now I can't get any VMs up and running again.

The host comes back up and I can ssh to it, but things aren't running right, If I try to view VMs via xsconsole I am see the error: "(''NoneType' object has no attribute 'xenapi'')", but even this is inconsistent, I get the error but then the VM list appears.

However staying on the All VMs section alternates between showing me a list of VMs and telling me there are no VMs present.

Checking the VM that should be running XP tells me that it is running, but it isn't.

I'm a bit stuck - can anyone point me in the right direction please?

@Danp
RTFM is so often the correct answer - this was my error
I've followed those instructions and done this with the VM shut down and it's completed in seconds.

The migrated machine has boosted up, although with a small delay. I think that's linked to an issue with the NIC. It's not landed on the network but I'll keep digging into what netplan might be doing there.

Thanks very much for your help and for your pateince.

@Danp

I thought I could do the migration live - so this might all be my fault.

I will go through the migration checklist now and give that a test - I've updated XO to commit 034d4 so should be ready to test another migration before I leave the office today.

Thanks very much for your help

@olivierlambert
Apologies - I wasn't clear at all about that!

I used the script at https://github.com/ronivay/XenOrchestraInstallerUpdater and it does seem to be using systemd

I have found some interesting info so far, but I'm going to make sure I'm fully updated and have a recent log entry to reference.

Thanks very much for yoru help and patience

@olivierlambert

Thanks for getting back to me.

1. I don't see any stats in the new VM itself, the machine never gets as far as starting up. No disk shows up under the disks tab on the VM itself. On the host, I see a small spike of traffic when I start the import, but nothing that looks like it's copying anything.
2. I'm looking into this - I've not actually used that yet. I'm assuming I shoud find what I need with something like the following: "journalctl -u xo-server"
3. I'm going to cancel the existing job and remove the empty "importing" VM then try getting XO up to date and see how that goes

Regarding point 2, I've found the following:
error: Error: ServerFaultCode: Current license or ESXi version prohibits execution of the requested operation.: {"RestrictedVersionFault":{"attributes":{"xsi:type":"RestrictedVersion"}}}

This seems strange as I managed to import from the same free ESXi system on to my original test on XCP-ng 8.2 (although that was just running on old desktop hardware as a test)

I'll update XO and get an up to date log of what happens then.

Hello

I'm trying to do an import from VMware (ESXi 8.0.1), I've tried multiple times through XO but I only seem to get as far as the import button showing the spinning icon:

I even left one of these running overnight earlier this week, but nothing completed.
I do get as far as the VM being created but it seems to remain in the Importing state.

I'm using XO (commit 7fc5b) I did update that earlier today, but I'm now behind the master again.

I'm using 8.3.0 and XO is reporting the host as up-to-date.

I've tried with the Ubuntu 22.04 template as the VM I'm trying to import is that version, is it worth testing on another template?

Are there any known issues with import currently? Or is this just "one of those things" and I should abandon that test VM and either resort to the clonezilla approach or try another VM?

There's only one entry for today under "settings > logs" but I'm not used to reading those logs to work out what's going on.
The initially concerning part for me is under:

host.getSmartctlHealth
{
  "code": "4",
  "params": [
    "Command '['smartctl', '-j', '-H', '/dev/sda']' failed with code: 4",
    "stdout: '{
  \"json_format_version\": [
    1,
    0
  ],

Apologies if I've not provided a critical piece of information, please let me know what other information you require and I'll post an update.

Thanks very much