XCP-ng 8.3 betas and RCs feedback 🚀
-
@marvine said in XCP-ng 8.3 betas and RCs feedback :
giving error code 43
This error is a driver issue on Windows side.
It says that the card is "virtualised" Nvidia is very strong in blocking this, if it's not allowed.
If you google for it there should be plenty of workarounds.
-
@Houbsi yeah i did try it with the nvcleaninstall but gives me the same error and also tried the HV value to hide windows is virtualised.
Will try again to remove everything and start over
-
@marvine I am using two Nvidia P40 with passthrough to Debian VMs with XCP-ng 8.3 RC1. I had no issues with passthrough, installing and runing the P40. For Windows VMs, this older post might give some more information.
-
@CJ said in XCP-ng 8.3 betas and RCs feedback :
@stormi wait init shows exited with a success status. stunnel shows active and running.
I disabled the server and enabled it again and this time it connected without an error. However, it lists as unknown pool and doesn't show in any of the host/pool/vm pages.
Also, when I go on the console, it states that the host is already in maintenance mode. Selecting Enter/Exit Maint Mode results in the following.
(''NoneType' object has no attribute 'opaqueRef'')
Have you tried to reboot the server once again? If the issue persists, can you share
/var/log/xensource.log
somewhere (might contain sensitive information, so better share privately). -
@stormi I have not rebooted the server at all. I told it to apply patches and then this all happened.
I didn't want to reboot it in case it was in the middle of something or if there were things you wanted me to check.
I'll try rebooting it and see what happens. Hopefully the other pools and nodes won't have this issue.
-
This will be fun. The console keeps losing connectivity with the VMs so I wasn't able to suspend them before rebooting the server.
Oh, that's not good. No change after rebooting. It's still borked. What's the best way to reach out to you, @stormi ?
-
@CJ You can send me a PM here.
-
@stormi Uh, how do I do that?
Also, I think the problem may be due to when I was attempting to set up a private network. I had deleted all of that but it seems to be stuck in a loop trying to find sdn-controller-ca.pem. Therefore the update never completes and it just tries again.
-
@CJ Then this would not be directly related to the update, but maybe just to the reboot that was performed by XOA after it?
-
Problem solved on chat. Our last update doesn't like it at all when a certificate was manually removed from the system without letting XAPI know.
So we had to:
- revert the update and restart the toolstack - XAPI works again
touch /etc/stunnel/certs/sdn-controller-ca.pem
to create back a dummy file for the missing cert, so thatxe
will accept to remove it from database (it fails if it can't find the file for which you're trying to remove the database entry )xe pool-certificate-uninstall name=sdn-controller-ca.pem
- update again
- perform the update of the rest of the pool hosts
I added a comment in the issue related to the patches we included in this update to fix certificate fingerprints: https://github.com/xapi-project/xen-api/issues/5955