If it's a lab and you can afford the time, at least we'll be on the safe side
Vates
People working at Vates
Posts
-
RE: VM Creation Failure | "Expected int64, got 'N'\"posted in Management
-
RE: Manual snapshots retentionposted in Management
Sure but it's all about discussing what would be the "best criteria"
-
RE: xcp-ng 8.3 not recognizing all host memoryposted in Hardware
So Xen can only see 12GiB RAM:
(XEN) [0000000d42938c09] System RAM: 12067MB (12357076kB)
I would double check BIOS settings, maybe 4GiB RAM reserved for video?
-
RE: Manual snapshots retentionposted in Management
Well, I'm not against that idea @flakpyro but we'd probably need some specification on what would be expected
-
RE: VM Creation Failure | "Expected int64, got 'N'\"posted in Management
@kagbasi-ngc Yes, top is executed from your Dom0, which is... a VM
When you run memtest, you run it on the entire host. And yes, ideally let it run entirely. -
RE: Intel iGPU passthoughposted in Hardware
@scawtydont Thanks for keeping us posted. Dummy plug is still a thing it seems
-
RE: xcp-ng 8.3 not recognizing all host memoryposted in Hardware
Indeed, @DustinB is right. In the meantime, you can show us the result of
xl dmesganddmesg. -
RE: VDI_COPY_FAILED: Failed to find parentposted in Management
Because it seems to be a leftover from a failed coalesce, at least it seems you have a problem with a chain. Maybe it's this chain and moving (not removing just in case) will make it right. The best solution would be to check which UUID reported in the error is in which chain to remove that broken chain and rescan the SR.
