Re: Clonezilla not recognising network adaptor

Windows/GUI user here, so please forgive me if I am not an linux expert.

I just encountered this problem was well when trying to clone a Windows VM because multiple ESXi migration attempts within XOA was not working for Windows VMs for me (No bootable device Ticket#7718434) ... On a side note migrating Linux VMs from ESXi to XCP-NG worked, but only if you didn't have a snapshot on VMware, otherwised it failed for me too.

Back to the original problem: I tried with clonezilla-live-3.1.0-22-amd64.iso (debian based) which did not even boot.
Then I tried with the alternate stable clonezilla-live-20230426-lunar-amd64.iso one (ubuntu based). There I was able to boot, but never had a network device, like in the screenshot of the original poster. Changing to e1000 in advanced settings didn't help either.

It might seem unlogical but the solution was that you have to create a Linux based templated (in my case I used Ubuntu 22 template) within XOA to create a new VM and then you will have a network adapter in clonezilla and you can then migrate the Windows VM.

Note that - in my case when I tried - cloning only worked one disk at a time, choosing the same disk on the source and on the destination, otherwise it will not work (clonezilla will not start the cloning). After the cloning you can restart the cloning process (without rebooting) and choose the second disk. Also important: the destination disk needs to be at least the same size or bigger than the source disk (even if it is not filled up on the OS level)

I also uninstalled vmware tools on the old windows VM and installed the citrix tools on the old VM before the migration, but I don't know if this was necessary.

After some trial and error I even figured out how to use the xe command. If you already made a Windows template, you could SSH into the XCP-NG host and use this exact command to change it to linux:

xe vm-param-set uuid=<copy-UUID-from_XOA> platform:device_id=0001

and then the network device will appear in clonezilla even after using a Windows based template!!! I however didn't keep on going with this aproach, since my Ubuntu based template windows machine was working fine. Now I am booting Windows with the Ubuntu template, don't ask my why this works, I'm just happy that after about 8 migration attempts this one finally worked

However if you used the command I guess you should probably change it back to
xe vm-param-set uuid=<copy-UUID-from_XOA> platform:device_id=0002
after the cloning has finished.

I hope this is useful to others and will save them some time

@olivierlambert said in updater could not fetch data from xen-orchestra.com server (unexpected error 22). Please check your connection:

You tried to register with a deleted account I think, causing the issue. Could it be possible? (we do not delete account automatically except if you ask us to do so)

Ah, thank you, yes this is correct. I didn't remember deleting the account. And I was afraid that the 7 day trial period was too short for testing, so I used the old (deleted) accont. However strange that it accepted the old deleted account in the registration field, but I guess this is because the accound didn't really got deleted just de-activated, however then the registration should have failed I guess Thanks for clearing this up!

By the way, when I try to leave feedback via the

"Help us to improve this page! (opens new window)"

on this page

https://xen-orchestra.com/docs/general-troubleshooting.html

because I wanted to state that the tail command does not work and the hyperlink right beside it neither...

I was forwarded to a github page, where I first needed an account, which I then did because I wanted to help with the documentation, and then I got this error message on github:

You need to fork this repository to propose changes.

Okay, sorry please ignore my post, after registering with a different user, the upgrade now worked fine. I think the error message before had to do with using a user which was not allowed for a trial. Perhaps one could state this in the error message, for example "Trial expired" or similar

I'll leave the post online if anybody else has a similar problem

Hi,

I am new to XOA so I searched this forum but couldn't find anything in this regard.

I am trying the trial version of XOA which I registered yesterday.

In Registration area it states "registered to ...".

When trying to upgrade via the GUI I get this error message:

4/25/2023, 10:24:56 AM: Start updating...
4/25/2023, 10:24:57 AM: updater could not fetch data from xen-orchestra.com server (unexpected error 22). Please check your connection

regularly around every 10minutes.

When I ssh into the console:

[04:38 25] xoa@xoa:~$ xoa check
....
✔ Node version
✔ Memory
✔ xo-server config syntax
✔ Disk space for /
✔ Disk space for /var
✔ Native SMB support
✔ Fetching VM UUID
✔ xoa-support user
✔ XOA version
✔ Appliance registration
✔ NTP synchronization
✔ local SSH server
✔ npm version
✔ Internet connectivity
✖ XOA status: not up-to-date, please run xoa-updater

ping also works...

[04:39 25] xoa@xoa:~$ ping xen-orchestra.com
PING xen-orchestra.com(2a01:240:ab08::4 (2a01:240:ab08::4)) 56 data bytes
64 bytes from 2a01:240:ab08::4 (2a01:240:ab08::4): icmp_seq=1 ttl=57 time=43.2 ms
64 bytes from 2a01:240:ab08::4 (2a01:240:ab08::4): icmp_seq=2 ttl=57 time=41.4 ms

[04:46 25] xoa@xoa:~$ xoa-updater --upgrade

✖ {
  message: 'updater could not fetch data from xen-orchestra.com server (unexpected error 22). Please check your connection'
}

There is no firewall between xoa and the internet, just a router.

When I hover the mouse over the xoa upgrade icon it just turns into a red no entry sign.

I checked this page:
https://xen-orchestra.com/docs/updater.html
but couldn't find any more information.

I checked this page:
https://xen-orchestra.com/docs/general-troubleshooting.html

So I tried

tail -f /var/log/syslog

which gave me

*tail: cannot open '/var/log/syslog' for reading: Permission denied
tail: no files remaining*

Clicking on the "learn more" Link at
https://xen-orchestra.com/docs/general-troubleshooting.html redirected me to
https://xen-orchestra.com/docs/logs.html
which resulted in
"This xen-orchestra.com page can’t be foundNo webpage was found for the web address: https://xen-orchestra.com/docs/logs.html"

I guess I must be missing something very obvious....

Any ideas?