Posts made by splastunov

Maybe netdata will cover everything?

There are no default alerts, but you can easily create them by yourself.

Also it is very easy to deploy "parent" netdata node and stream metrics to it from all hosts (maybe this part could be integrated to XOA free version? ).
You do not need netdata cloud account for this solution

@RS sorry, I have no idea how to fix it

You can always try to use XAPI, or xe cli tool

@RS Few years ago I faced the same errors on all xva backups and after that switch to vdi backups.
I did not find the root of problem, but I know how to "repair" broken backup.

Check xva backup with command vhd-util check -n name_of_backup.xva.
If you got something like Checksum : 0x0|0xffffffff (Bad!), the solution is:

1. Create VM or get server with modern Ubuntu. You will need x3 space of your backup size.
2. Copy broken backup
3. Install xva-img https://github.com/eriklax/xva-img

apt-get install libssl-dev g++ cmake
add-apt-repository ppa:ubuntu-toolchain-r/test && apt-get update && apt-get install -y gcc-7

#To compile execute following commands in xva-img folder

cmake ./
make install

4. Unpack backup

mkdir my-virtual-machine
tar -xf name_of_backup.xva.xva -C my-virtual-machine
chmod -R 755 my-virtual-machine

5. Create RAW disk. Replace Ref\:1 with your digits

xva-img -p disk-export my-virtual-machine/Ref\:1/ disk.raw

6. Install qemu-utils from standard repos apt install qemu-utils
7. Convert RAW to VHD qemu-img convert -f raw -O vpc disk.raw resotred.vhd
8. Copy VHD to xcp-ng SR cp resotred.vhd /run/sr-mount/{sr-uuid}/
9. Get UUID of your restored VHD. This command should be executed on xcp-ng server. vhd-util read -p -n resotred.vhd
10. Rename vhd
11. Rescan SR, rename VHD with empty name

@KPS said in Simulating network cable disconnect:

This is an old thread, but to keep it in one place: is there any option to start a VM with disconnected vif?

as workaround/trick you can use locking mode.
Set it to "locked" and do not allow any IP, so all traffic will be dropped on this VIF. It will be like "disabled". After that you can set locking mode to "unlocked" to allow any traffic.

@mohammadm
I'm talking now about vGPU not passthrough

1. old drivers
2. no way to monitor GPU load
3. Sometimes the GPU on Dom0 stops responding and the only thing that can be done to solve this problem is to reboot the entire server with all the virtual machines on it.
   and etc.... do not remember all troubles I had with it

@austinw no licenses, but a lot of troubles.....

Instructions
Set the "other-config:auto_poweron=true" parameter on both target VM and resource pool：

#xe pool-param-set uuid=<pool_UUID> other-config:auto_poweron=true
#xe vm-param-set uuid=<vm_UUID> other-config:auto_poweron=true

great news! Thank you @michael-manley

Just use official AMD drivers

https://www.amd.com/en/support/professional-graphics/firepro/firepro-s-series/firepro-s7150-x2

It works fine, but sometime Dom-0 "lose" graphic adapter and you should restart whole server....
I did find solution and AMD stopped supporting it....

Some time later I faced with problem that VMs (Linux and Windows) can't correctly start GPU (ADM MxGPU).
In windows device manager there was error #43.
I have solved this error without host reboot by reloading gim module.

Hope this will help somebody else.

rmmod gim gim_api
modprobe gim gim_api

In my case problem was in bad connection.
I have reassembled server, cleaned PCI-e (GPU) contacts and now it is stable.

But it will be nice to have some tool to control and monitor AMD GPUs.

@hani it began asking for license after one day but without throttling.

I have switched to AMD GPUs

@Dani Strange. Is it executable? Did you tried to follow step by step my instruction to make vGPU work?

Do you have vgpu binary file at /usr/lib64/xen/bin/vgpu?

Why it is not working?

Did you read my post about how to run Nvidia vGPU on XCP-ng?
https://xcp-ng.org/forum/post/55774

But in any case you will need Nvidia license sever

That's good sign.

On host you can check to which pci-e controller drives are connected by command
ls -al /sys/block/sd*

You will see something like this

Before ata... you will find pci-e address

Check if you passthrough correct SATA controller.
I thing you have 2 SATA controllers because your MB have M.2 connector.

Can you see drives on the host if disable pass through?

Recently I have some troubles with OCulink to NVMe cables.
That was Supermicro server and they have different cables for SATA/SAS and NVMe.
The difference is in wire resistance - for SATA/SAS you should use cables with 100Ohm resistance and for NVM with 85Ohm.
In such way motherboard detects what type of drives are connected to hybrid port.

It is just my ideas what happens.

First you should check if host can see drives without pass through.

Live migration is not possible in this case, because of lack of free space.

You have to shutdown VM, then click this button and chose another host

Hello!

Are all VMs on this host belongs to you and you certainly know what processes running on them?

I had same issue with Dell R630.
The solution was to update to latest BIOS.
I think that some clients ran some software that triggered some bug and host rebooted.

XCP-ng security updates does not helped.
In my case only BIOS update fixed suddenly crushes.

So the work around will be to move VMs one by one to another host and check if it will solve the problem.