Hi,

You may want to follow this thread for the VDI not visible issue.

Dan

Just go to Settings > Servers tab in XO and remove the entry associated with this pool.

@tmnguyen You can open a support ticket and request that we reactivate your XOSTOR trial licenses to match your existing XOA trial.

@Bytevenidos You can try that, but it most likely won't work.

I've confirmed with the dev team that the end point to mount an ISO doesn't currently exist for the REST API. However, it does exist in the older JSON-RPC API, which you can access using xo-cli --

vm.insertCd id=<string> cd_id=<string> [force=<boolean>]

@olivierlambert It's even older than that.

https://github.com/vatesfr/xen-orchestra/blob/master/CHANGELOG.v5.md#5540-2020-12-29

https://xen-orchestra.com/blog/xen-orchestra-5-54/

That XOA version was released over 5 years ago. You really should share these kind of details in advance to avoid nonproductive exchanges. I recommend that you revisit the reason that they are "stuck" on this old version.

In current releases of XOA, you can resolve the issue by running a successful backup job that includes the affected VM.

To manually resolve the issue, you need to clear the left over keys in the blocked-operation parameter. For example, this will clear these keys for a VM with UUID be0a9812-fd14-be75-e2fa-40c31ce8875c --

vm_uuid=be0a9812-fd14-be75-e2fa-40c31ce8875c
xe vm-param-remove uuid=$vm_uuid param-name=blocked-operations param-key=migrate_send
xe vm-param-remove uuid=$vm_uuid param-name=blocked-operations param-key=pool_migrate

@Bytevenidos I don't see an endpoint in the REST API for mounting an ISO. However, you should be able to mount the ISO during the VM creation. I will ask around about using the REST API to mount and eject ISOs.

@Bytevenidos Are you up-to-date?

You attach a VDI to a VM by creating a VBD. Take a look at the POST /vbds endpoint.

@allySalami I'm not sure how that could be. You checked the VM's Advanced tab, correct? Are you running XOA or XO from sources? What is your current version / commit?

Check the VM's Advanced tab to see if this option is enabled --

@acebmxer There are older versions of the guest tools still available on Github.

@acebmxer said in Host compatibility:

Maybe if i shutdown the vms and boot backup all will be good?

This is generally correct. If the VMs haven't been migrated or rebooted since the additional host was added to the pool, then you can encounter this situation due to CPU masking.

See the docs for an explanation of Homogeneous vs Heterogeneous Pools.

@Pilow said in Network Management lost, No Nic display Consol:

you can try the command on MASTER host, you should see

master:ip_of_the_master

Slight correction. On the master, you should only have

master

without the colon and IP address.

@DustinB said in Recommended DELL Hardware ?:

Doesn't using non-shared storage ultimately cause the VM to be started on the other host?

No. Live migration can occur between hosts even if:

• the VDI are located on non-shared storage
• the hosts are in completely different pools

For the cross pool migration to succeed, both pools need to support a common instruction set. Otherwise, use the Warm Migration feature that does reboot the VM so that it is running the correct instruction set on the destination host.

@DustinB said in Recommended DELL Hardware ?:

With local storage on each hosts, you won't be able to live migrate from 1 host to the other.

That's incorrect. The migrations will take significantly longer because the VDI will be migrated along with the VM's memory, but you can live migrate VMs between hosts even if the VDI are stored on local storage.

@olivierlambert New thread is here

It is difficult to know the source of the problem without more details from your logs. Can you run the following commands on your XCP-ng host and then attach the generated files here?

grep -A 15 -B 15 -i error /var/log/xensource.log/xensource > xensource.txt
grep -A 15 -B 15 -i exception /var/log/SMlog > smlog.txt
dmesg -T|grep -Eiv 'guest|capacity|promiscuous' > dmesg.txt

Hi @Tristis-Oris Have you tried this option on the secondary menu?

What OS are you running on the VMs? Do you have the guest tools installed on them?