Subcategories

  • All Xen related stuff

    627 Topics
    6k Posts
    D
    @hrvojer Ever since 2012 R2 went out of support, there have been multiple compatibility breaks in the drivers and guest agents since they now target Server 2016+. It might be possible to get the drivers working on 2012 R2 in a testing environment, but bringing that to production is another topic.
  • The integrated web UI to manage XCP-ng

    29 Topics
    367 Posts
    olivierlambertO
    The same as @john.c and also XO Lite tends to be less a priority because less critical than the full fledged XO (the priority is to replace entirely XO 5 in the next releases). Why you would need XO Lite outside basic actions? It's mostly meant to bootstrap XO itself and do basic operations (which is already the case, at least with many basic features already). Initially, the goal hasn't moved: replacing XenCenter. We are moving in that direction, but again, I think it's more important to get XO 6 finished first. I'm curious to understand more the use case of XO Lite in your context @unreal-shizzle ?
  • Section dedicated to migrations from VMWare, HyperV, Proxmox etc. to XCP-ng

    132 Topics
    1k Posts
    J
    @mpiton Thanks for a fantasticly quick answer, and detailed as well. I will test this immediately! Update: I can confirm that this was indeed the problem!
  • Hardware related section

    178 Topics
    2k Posts
    S
    lspci -nn -s fra dom0 21:15 xcp-ng-test ~]# lspci -n -vvv -s 0f:00.0 0f:00.0 0300: 1002:13c0 (rev c1) (prog-if 00 [VGA controller]) Subsystem: 1002:13c0 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 42 Region 0: Memory at fc10000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at fc200000 (64-bit, prefetchable) [size=2M] Region 4: I/O ports at e000 [size=256] Region 5: Memory at fc700000 (32-bit, non-prefetchable) [size=512K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [64] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 16GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 16GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, EqualizationPhase1+ EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable- Count=1/4 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [c0] MSI-X: Enable+ Count=4 Masked- Vector table: BAR=5 offset=00042000 PBA: BAR=5 offset=00043000 Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270 v1] #19 Capabilities: [2a0 v1] Access Control Services ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans- ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans- Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 00000100, Page Request Allocation: 00000000 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec+ Priv+, Max PASID Width: 10 PASIDCtl: Enable- Exec- Priv- Capabilities: [410 v1] #26 Capabilities: [450 v1] #27 Kernel driver in use: pciback
  • The place to discuss new additions into XCP-ng

    255 Topics
    3k Posts
    dicode-nlD
    New version: https://github.com/dicode-nl/xcp-ng-ceph-rbd/releases/tag/v20260903 This one includes native Ceph rbd SXM over SMAPIv3! GitHub updated with the latest commits and changes. As always, use with caution. I did run a lot of test scenario's but please do test yourself and let me know your findings!
  • Openstack vs xcp-ng (XO)

    3
    0 Votes
    3 Posts
    974 Views
    I
    @olivierlambert got it.
  • XCP-ng host - Power management

    11
    2
    0 Votes
    11 Posts
    4k Views
    A
    @tjkreidl We don't need performance, but we do need to test how XCP-ng pools, networking, migration, live migration, backup, import from VMware and so on work. It's just a playground where we can have relatively many XCP-ng hosts, but it's not about performance, it's about efficiency and low requirements, because it's just a playground where we learn, validate how things work, and prepare the process for the final migration from VMware to XCP-ng. We originally had two R630s ready for this, then 4, but that would have been unnecessary, given the power consumption, to have physical hypervisors, so in the end we decided to virtualize it all. Well, on ESXi it's because XCP-ng works seamlessly there in nested virtualization.
  • 1 Votes
    8 Posts
    3k Views
    S
    @spcmediaco FYI, I never figured out how to fix. I am doing backup recovery now.
  • 0 Votes
    8 Posts
    2k Views
    julien-fJ
    @Bambos A timeout error means that the host did not reply in the expected delay, which, if I'm remembering correctly is 5 minutes. I suspect a problem on your host but we will take a look further on your support ticket.
  • GRUB waits for confirmation

    8
    0 Votes
    8 Posts
    2k Views
    J
    @techknowbabble said in GRUB waits for confirmation: What did finally work was re-installing with the 'no serial' option and everything seems to be working as expected now. I only have a handful of XCP-NG installations under my belt but I wonder if this is a known bug or if anyone else has had a similar experience. It's not something I've ever seen before and I've done quite a few installations but I can think of some possibilities as to why something like that might fix the problem. My best guess is that there's something built into, connected to, or otherwise in your system that looks like a serial port (maybe even a real serial port) that spits out a character or two into the system at boot time, confusing GRUB and stopping the normal boot process. The bad KVM I mentioned before was doing something like that, throwing a bogus keypress into the system at boot time.
  • Wide VMs on XCP-ng

    13
    0 Votes
    13 Posts
    4k Views
    planedropP
    @plaidypus Ah gotcha, this makes sense. I second scaling out instead of up. If you're getting new hosts, I'd also keep in mind newer CPUs do have much higher per core performance (not sure what your current stuff is), so you also might be able to get away with less vCPUs and lower likelihood of NUMA spanning. Either way though I think scaling out is the better direction to go.
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    4 Views
    No one has replied
  • VM cannot be migrated after NICs of one host died

    Solved
    5
    0 Votes
    5 Posts
    1k Views
    DanpD
    @hansve You're welcome.
  • block tdc: sector-size: 512/512 capacity: 20938752

    3
    0 Votes
    3 Posts
    725 Views
    K
    @apz I see. Thanks.
  • 0 Votes
    21 Posts
    9k Views
    daveD
    @R2rho yeah, there are Supermicro systems with AM5 which can handle a decent amount of load, like based on the h13sae-mf, like: https://www.supermicro.com/de/products/system/mainstream/1u/as-1015a-mt (with less depth) Seem to be stable, but we have a small issue regarding onboard graphics ATM: https://xcp-ng.org/forum/topic/9976/black-screen-after-install-on-supermicro-h13sae-mf-with-ryzen-9950x/3?_=1734419502978
  • VM not booting after attaching GPU

    2
    0 Votes
    2 Posts
    490 Views
    DanpD
    You should start by checking the logs. https://docs.xcp-ng.org/troubleshooting/log-files/
  • XCP-ng v8.3 Host Crashing Upon Console Login and Performing Any Action

    Solved
    6
    1
    0 Votes
    6 Posts
    1k Views
    bleaderB
    Thanks for letting us know, and I'm happy you have thing working nicely now. I think to mark this as resolved you need to convert your original post as a question, and it can then be marked as resolved. I actually cannot do it myself, I think only a few people have the permission to do it for others at Vates.
  • Change VM RAM

    Solved
    6
    0 Votes
    6 Posts
    1k Views
    olivierlambertO
    Enjoy XO & XCP-ng then
  • host time and xoa time are not consistent with each other

    Solved
    4
    1
    0 Votes
    4 Posts
    3k Views
    C
    @olivierlambert I resolved it, logged in the XCP-ng console and set the NTP servers to default. All good now. Thanks [image: xcp-ntp2.png]
  • Cloning Windows VMs

    5
    0 Votes
    5 Posts
    1k Views
    D
    Preferably after, since the PV drivers contain some VM-specific settings that may be wiped by Sysprep.
  • 1 Votes
    6 Posts
    2k Views
    W
    @dinhngtu said in Issues with XCP-ng Windows PV Tools 9.0.9000.0 Testsign Pre-release: With 9.0.9000.0, you could sometimes run into this issue if you reboot too early after installing. This will also be fixed in the next release. I just did two more tests and the boot-up failure happened both times. On the last test I waited some time (like 30 to 60 sec) after the driver installation before rebooting (using Windows restart from the start menu). Even though I waited before rebooting I still encountered the boot-up problem: Windows is spinning on this screen and doesn't finish booting: [image: ef30a370-5897-41e6-a0f1-41fa3720dacb-image.png]
  • 0 Votes
    5 Posts
    1k Views
    olivierlambertO
    I wasn't aware of this plugin even existing (thanks for the discovery). I'm not sure it's really maintained, but we have a clear goal of getting one officially maintained anyway.
  • Windows Admin Center extensions for XCP?

    4
    0 Votes
    4 Posts
    1k Views
    G
    @olivierlambert Which one, powershell or WAC. They are kind of one in the same when you look at how WAC makes the calls to do the work, there's a button to reveal the powershell behind the button clicks so you might be able to get both at once. But WAC draws nice graphs and gives us a GUI to get the work done. Yes I know, real Admins don't use GUI. Whatever, AI will eat our jobs anyway, just trying to stick it out another 9 years at this point. When I get time, I'll still probably take a swing at this task for WAC, because to me this would be valuable. Big learning curve though. Now if MS would finally add Group Policy to WAC and fix some of the DHCP and DNS features that are still in preview...
  • xenserver - net 9.1.7.65 issues

    3
    0 Votes
    3 Posts
    1k Views
    D
    @dinhngtu Ah thank you! Idk why I couldn't find that on my own, I searched for a while.
  • Xapi service missing

    6
    0 Votes
    6 Posts
    2k Views
    DanpD
    According to the documentation, you only need xfsprogs.