Oh that's great! Nice catch 🙂 How did you find the root cause?

Perfect, enjoy XCP-ng and XO!

Hi,

This error is telling you that you don't have enough free space on the SR where the VDI currently reside.

Regards,
Dan

@McHenry Yes, XCP sees and uses all threads (8 core + SMT x2 threads = 16 logical cores). So you can assign all of them to a VM as long as the VM can use them.

XO shows 16 "cores" (total threads) and 1 socket. It also shows hyperthreading is enabled. XCP/XO does not differentiate between cores, threads, E-Cores or P-Cores.....a thread is an assignable core resource.

You can assign 16 logical vCPU that includes real cores and SMT threads.

Some programs do not work well with hyperthreading in a VM environment. So you may wish to disable SMT depending on the workload.

@m-mirzayev said in ISCSI mount - SR_BACKEND_FAILURE_432:

@john-c
Would you mind to post your custom.conf so i have a reference?

@m-mirzayev I don’t use multipath personally however, though managed to get Microsoft Copilot to put what you gave above into a valid structure. I also remember people in the past having trouble with multipath, so Vates employees implemented this /etc/multipath/conf.d/custom.conf to fix these issues.

# /etc/multipath/conf.d/custom.conf defaults { user_friendly_names yes } multipaths { multipath { wwid "your_device_wwid_here" alias "truenas_iscsi" path_selector "round-robin 0" path_grouping_policy multibus path_checker tur prio const failback immediate } } devices { device { vendor "TrueNAS" product "iSCSI" path_selector "round-robin 0" path_grouping_policy multibus hardware_handler "0" prio const failback immediate } }

Please replace "your_device_wwid_here" with the WWID of the device on your network.

The issue is there's a VDI that's not in the right map. It's hard to tell why without having a deeper look.

@McHenry @nick-lloyd With todays release of Xen Orchestra (XOA) version 5.100 there's now support for custom ACLs based around tags. These will prove really useful when your setting up the XOA with its ACL for your clients to access self service, while ensuring that they can't access the other's pools and VMs etc.

@Danp

The file is getting removed every time, that's why I was questioning the behavior of the command (whether it is grabbing all records or cached records).

We can do that, but if the user is deleted, that user entry would be gone.

@nikade This is what is currently have:

[16:39 xc-ng-hv1-fi ~]# sysctl net.ipv4.ip_forward net.ipv4.ip_forward = 0

Is setting the value to 1 all O need to do? net.ipv4.ip_forward = 1 in /etc/sysctl.conf

@Danp Thank you, trying now.

Since it was somewhat critical (urgent migration from other pool), I had to switch the pool masters and had to restart the xcp028.

But I downloaded the system log. Maybe you find the cause of the problem there?

BTW, before restarting the host, I was not able to download these logs (failed).

Yeah I think that's the best approach in your case 🙂

Just going to XO / Home / Pools / pool-1 and pressing "Add hosts" button, selecting host-2 worked OK this time. So no detaching host from a pool and attaching to new pool ... just a button 🙂

That's what it was. For whatever reason, ubuntu defaults to installing these versions for node and npm respectively:
v12.22.9
8.5.1

Following the steps here fixed it. As always, thanks!!

@stevewest15 Thx for SMlog. I don't see anything suspicious 😞

@McHenry Check the contents of the VM's blocked-operations parameter. This is from one of my VMs --

# xe vm-param-get param-name=blocked-operations uuid=e764e6fb-5e18-35dd-cfb6-ddf83d32e1fd start_on: Start operation for this vm is blocked, clone it if you want to use it.; start: Start operation for this vm is blocked, clone it if you want to use it.

Both the start and start_on operations should be blocked on CR created replicas.