Control domain of Xcp-ng

[Darkbeldin]

@sumansaha Not forget the control domain but yes you can remove the VDI attached to it.

[sumansahabd]

@Darkbeldin There is no other to remove VDI. Do you mean to remove the VM.

[Darkbeldin]

@sumansahabd No what you are seeing in Dashboard > Health are VDI attached to your dom0 not dom0 himself so yes click on the item there and remove them it's ok.

[sumansaha]

@Darkbeldin

Actually I didn't get you . But the two control domain snapshot has two base copies and consumed storage space. Please suggest how we can remove the control domain snapshots.

[olivierlambert]

It's not a control domain snapshot, it's a VM snapshot (Porta web) MOUNTED on the dom0.

Having a snap mounted to the dom0 is OK during the backup phase, but if it's still attached after, it's not normal.

So if it's outside a backup, you can disconnected the snapshots from the control domain, remove the VM snapshot, and then it should be coalesced automatically

[sumansaha]

@olivierlambert

I've disconnected the snapshots and after that should I go for to Destroy VDI' .

[olivierlambert]

Check if your VM with porta web doesn't have a snapshot, that will automatically remove all the snapshot disks

[sumansaha]

@olivierlambert

There is no snapshot actually. Should I run "Destroy VDI" on the snapshots from the disk.

[olivierlambert]

Yes, destroy the VDI snapshot in the SR/disk view

[sumansaha]

@olivierlambert

Thanks for your response.After 'Destory VDI' from Disk currently there is only one base copy. And no coalesced process running now. Is there any way to remove current base copy.

[olivierlambert]

No. If it's not coalesced automatically, there's a reason

[sumansaha]

@olivierlambert How we can troubleshoot that.

[olivierlambert]

https://xcp-ng.org/docs/troubleshooting.html is a good start to read.

In your case, it's likely inside /var/log/SMlog