@Andrew but I suppose that even without the udev rules, the device was still working with just the code compilation. I made it compile too, changing just a #if definition that was looking for kernel source version < 4.19.10 and mine is 4.19.0 but existing and was conflicting. Was there another code modification?

@Andrew but just to understand: did you do something else apart recompiling the r8152 project?

@FilHarr and @Andrew instead I had the driver compiled and loading. I am setting my USB 2.5 device with echo 1 > /sys/bus/usb/devices/2-5/bConfigurationValue to use r8152 but it stays always disconnected

@ronan-a I was in the bad assumptions that all the things that has been installed in this guide where new packages for RunX.

So when it began to give problems I went for the remove option. My bad!

Everything popped out from the fact that after that I could make the vms start again updating the packages as soon as I was starting the dockerd I was loosing connectivity in the host.

So I wanted to remove it.

@ronan-a I could make it start again doing a yum update.

Then I think I did an error, because I tried to run the following line:

yum remove --enablerepo=epel -y qemu-dp xenopsd xenopsd-cli xenopsd-xc xcp-ng-xapi-storage runx

This killed my xapi.service. Not starting anymore. If you will tell me how to find the log I can give to you the trace

Hello all! After testing this and following the guidelines now my XCP-NG is no more able to run VMs.

When I restart the host and try to run a VM it complains that HVM is needed. I just checked the Bios and VT-d is enabled as all the other settings that were there before testing this out.

What can I do?