Start the VM with xe vm-start uuid=<VM UUID> and see the error message there.

Well you both just made my Friday! I can follow directions after all!

@redakula First, thanks for chiming in. Second...I'll admit that I'm ignorant here. This is not an area that I have any real experience. The Intel doc reference (paraphrasing here) "magic lspci" options that will truly show you that the GPU isn't really running in Gen1x1 and that deeper down, its truly working as intended. I wish they would have just included the super-secret magic lspci options needed to show this is the case...But they didn't. The best I can see from lspci -vvxxxx is it still only shows Gen1x1 00:08.0 VGA compatible controller: Intel Corporation Battlemage G21 [Intel Graphics] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device 1114 Physical Slot: 8 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 Interrupt: pin ? routed to IRQ 79 Region 0: Memory at f1000000 (64-bit, prefetchable) [size=16M] Region 2: Memory at 400000000 (64-bit, prefetchable) [size=16G] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [40] Vendor Specific Information: Len=0c <?> Capabilities: [70] Express (v2) Endpoint, IntMsgNum 0 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 0W TEE-IO- DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1 TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range B, TimeoutDis+ NROPrPrP- LTR+ 10BitTagComp+ 10BitTagReq+ OBFF Not Supported, ExtFmt+ EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- TPHComp- ExtTPHComp- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- AtomicOpsCtl: ReqEn- IDOReq- IDOCompl- LTR- EmergencyPowerReductionReq- 10BitTagReq- OBFF Disabled, EETLPPrefixBlk- LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1- EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest- Retimer- 2Retimers- CrosslinkRes: unsupported Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000feed7000 Data: 0700 Capabilities: [d0] 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- Kernel driver in use: xe Kernel modules: xe 00: 86 80 12 e2 07 04 10 00 00 00 00 03 00 00 00 00 10: 0c 00 00 f1 00 00 00 00 0c 00 00 00 04 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 86 80 14 11 30: 00 00 00 f2 40 00 00 00 00 00 00 00 ff 00 00 00 40: 09 70 0c 01 0b 00 00 00 00 00 00 00 00 00 00 00 50: c0 f9 00 00 00 00 00 00 00 40 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 10 ac 02 00 e1 8f 00 00 10 29 00 00 11 0c 40 00 80: 00 00 11 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 12 08 13 00 00 00 00 00 02 00 00 00 a0: 01 00 00 00 00 00 00 00 00 00 00 00 05 d0 81 00 b0: 00 70 ed fe 00 00 00 00 00 07 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 01 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: c7 21 80 ff 03 00 00 00 00 00 00 00 00 00 00 00 When I ask the system what it thinks the capabilities are, again I get Gen1x1: cat /sys/bus/pci/devices/0000:00:08.0/current_link_speed 2.5 GT/s PCIe cat /sys/bus/pci/devices/0000:00:08.0/current_link_width 1 cat /sys/bus/pci/devices/0000:00:08.0/max_link_speed 2.5 GT/s PCIe cat /sys/bus/pci/devices/0000:00:08.0/max_link_width 1 I know I'm a bit out in uncharted territory here. I don't think XCP-ng supports ReBAR via pass-through (I think that's on the road-map for XenServer9 and maybe XCP-ng 9 as well), current gen GPUs all want ReBAR support, Intel GPU's are in a mostly experimental/developmental mode and might be having a murky future anyway... Anyway...From my completely uninformed and ignorant position, it doesn't look like it's negotiating PCIe properly through XCP-ng.

From what I can tell, the Netbox plugin in XO syncs VMs, interfaces and IPs, but it doesn't populate Netbox's separate Virtual Disks model yet, which is why you get the total disk space but an empty Virtual Disks tab. I don't think it's a permissions thing on your side, it looks more like a gap in what the plugin syncs today. There's already an open issue for disk-size sync (https://github.com/vatesfr/xen-orchestra/issues/7643), plus a few other Netbox requests in the tracker. If you want the per-disk sync added, the place it actually gets weighed is https://feedback.vates.tech, where the Netbox asks get prioritised together. It might also be worth a mention to @Team-XO-Backend, since they own the plugin and can say whether the newer Netbox virtual-disk model is on their radar. ecoutinho created this issue in vatesfr/xen-orchestra open Netbox plugin: Sync disk size error #7643

Evening @pierrebrunet My bad. I am now on commit b440f and the issue persist. I have written you a message with the link to the file. Regards, Marc

@yannsionneau Hi, is June still the target for the iso? Thanks

@niko thanks, that would help a ton!

mid 2026: you can't add a ipv6 address via XOA (XOA5) because the gui lacs the field for the v6 gateway-address XOA6 lacks feature to configure ips of the host the configuration of ipv6 (static) vie the "gui" on the host seems not be implemented yet (or i am missing something critical) command line configuration inside dom0 of the host is afaik not supported ? Some point looks like minor issues. it would be great to "address" pun intendet that as well

@Danp said: Smart Reboot option found on the host's Advanced tab does what you are asking Very nice!

Here is the log from when xen04 last crashed xen04-jun12-journalctl-crash-summary.txt

@Pilow pretty much

@olivierlambert said: I'm not sure it's a great idea, because even 64 hosts is huge in terms of VMs and fallout if you have a problem on your pool DB. Even if you drastically improve the current mechanism, the impact of a problem pool wide is far bigger with 64 hosts than 24 for example. It's more than purely tech, it's also a tech design/choice. Exactly, the failure domain just grows exponentially when going beyond a certain collective pool size. I was doing some more research and I found a few possible choices that Tesco may have moved too, but don't want to detract from this forum here.

@AlexanderK you could try to install perl-interpreter manually maybe? I happened to have a test host at hand that hasn't been updated since december, and the yum update went fine, perl interpreter was not installed before and yum update did install it on its own as a depency for openssl 3. Maybe others will have ideas as to why this would happen in your case.

@tuxen Doing some research, it doesn't look like the Xeon's I have are affected. But I'm willing to try the next time I need to reboot. Will report back after that.

Hello, Thanks for all !

@laszlobortel Hehe yeah, those are pretty old kernels. I'd say there's a good chance kernel upgrades will go a long way to alleviating the CPU hangs. I can't say it's exclusively a problem with lvmohba storage, that's just what we use because of our previous VMware infrastructure was block storage over fiber channel. We knew a physical infra overhaul wasn't in the cards for us for this migration so we stayed with our existing storage system. This bug bit us half way through the migration until we figured out upgrading the kernel generally fixed it.

@psafont Thanks for the quick response and clarification. I appreciate you opening a work item for this. Looking forward to seeing this improvement in a future release.