Categories

  • All news regarding Xen and XCP-ng ecosystem

    136 Topics
    4k Posts
    G
    @TeddyAstie @olivierlambert Thank you sooo much for your prompt response ! FYI a function-level-reset is systematically performed by Xen when doing PCI passthrough, thus your device should be reset before entering another guest (aside reset bugs like you may have). This is exactly what the problem is. The Dom0 is unable to perform FLR when I also pass vUSB to the Guest. However, if USB is not passed (i mean if it is not attached; even though USB passthrough is enabled in host), the FLR seems to be performed correctly and I am able to restart the guest without problems. If the FLR is not performed, the Guest (even if it is the same one being restarted) is unable to detect the pass-through cards and also waits for about 136 seconds (about 65.5 seconds for each card) after which it continues without adding the card. This wait time is the kernel default wait time which cannot be changed without rebuilding the kernel I think. I am trying to find out where the conflict is. (Basically I am unable to understand if this is a driver problem or a Xen problem; since the FLR is being performed correctly when there is no usb being passed through) Ideally passing USB should not have in impact on PCI-pass through. Current XAPI uses the approach of having a set of "passthrough-able" devices at boot time by modifying the xen-pciback.hide kernel parameter, which does the same but at boot time. Will this still work with XCP-ng 8.3 ? /opt/xensource/libexec/xen-cmdline --set-dom0 "xen-pciback.hide=(0000:07:00.0)" I am unable to use xe pci-disable-dom0-access uuid=<pci uuid> since UUID for the above pci is not generated (and not visible in xe pci-list)
  • Everything related to the virtualization platform

    1k Topics
    13k Posts
    D
    @bberndt said in Migrating from XCP-ng Windows guest tools to Citrix: XenServer PV Bus 9.19.105 (old) Could you confirm which driver/device this was? It didn't look right. Also, are you pulling updates through WSUS or something similar? Normally Windows should be able to update all the PV drivers on its own. Otherwise, in a fresh Windows installation the drivers gotten from Windows Update are as following: Bus 9.1.11.115 Interface 9.1.12.94 Network Class 9.1.13.107 Network Device 9.1.7.65 (old, but normal; there's been no updates to this driver since) Storage 9.1.9.82 Rolling back to older drivers then running Windows Update got me the newest drivers as expected.
  • 3k Topics
    24k Posts
    H
    Hey @Danp , I can keep my cluster without this node up to Monday, do you have an idea / do you want to investigate on this case ?
  • Our hyperconverged storage solution

    30 Topics
    653 Posts
    H
    @olivierlambert No, For once, i followed the installation step carefully ^^'
  • 30 Topics
    85 Posts
    GlitchG
    @Davidj-0 Merci pour le retour, j'utilisais aussi une Debian pour mon test ^^