@dr4s1l-0 @Dr4s1l-0 you will not see the config drive mounted in your system, cloud-init only mounts it temporarily very early on in the boot process, copies the found config files off of it, and unmounts it. Mounting it manually will just cause more issues. You can probably see it being mounted early on in the logs in /var/log/cloud-init.log Cloud-init has introduced a ton of bugs this year and has no documentation regarding them, it has been a nightmare to try and track down these issues - I have a support customer with the same issue on recent versions of ubuntu and I've gotten nowhere. At this point I think it's best to take it up with the upstream project, cloud-init - from the XOA/XCP perspective we're doing everything we can, resulting in presenting a properly configured config drive - any issue after that is the cloud-init package

See also https://xcp-ng.org/forum/topic/4538/xoa-json-rpc-call-basic-exemple

Short answer: yes.

@olivierlambert Thanks. As always you guys are great. Thanks for this opensource project! Tasks have cleared up.

@marcungeschikts Yes, it's the third point of the GitHub issue

Cancel that. CTRL-F5 fixed it! Thanks again.

@jp13232 That wasn't what I asked. You mentioned Xenserver, so I wanted to know what version.

@darkbeldin Thanks it was his channel & what great info he provides! It was a 2018 "VM Backups, Disaster Recovery and Continuous Replication with Xen Orchestra Backup NG" Thanks very much Darkbeldin

@olivierlambert Sounds good, thank you!

What does the memory min/max settings look like in the advanced tab of those VM's? You could try to set the dynamic min/max to same values. Could very well be that your guest OS doesn't handle it properly when host is trying to dynamically adjust the available VM memory. Although this shouldn't happen (afaik) if there's plenty of memory available on the host, but worth a try at least.

Hi, The Docker container isn't coming from us, so there's no way to know where is the problem. Please contact the 3rd party provider for this Docker repo.

Yes, totally makes sense. Thanks! Consequently, best to accomplish the intended behavior from within the Windows VMs.

So another odd thing I'm seeing with this VDI, it's showing the size incorrectly. It shows 180GB of 180GB used up (on thin provisioned SR, both the old and new are), however the VM is only using 140GB of that 180GB. Something definitely went wrong with this VDI during transfer, just not sure what. I will say that I increased the VDI size again and now it displays more accurately, showing 180GB of 185GB used (both in XOA and with vhd-util). Almost behaving as if this was at one point on a thick provisioned SR or something. Just to avoid issues I'm maybe tempted to create a fresh VHD, copy data to that, then delete this one.

@olivierlambert OK perfect, thank you! I've got a S3 Delta test going, will come back and post my results for others to reference once my testing is done.

@ronivay that was it

@olivierlambert thanks for info I can wait for XO 6 version

It's not only this code. But in general, a good way to manage that is: "every message in CAPS is coming from the lower layer" (ie not XO).

@xcprocks said in Restoring a downed host ISNT easy: So, we had a host go down (OS drive failure). No big deal right? According to instructions, just reinstall XCP on a new drive, jump over into XOA and do a metadata restore. Well, not quite. First during installation, you really really must not select any of the disks to create an SR as you could potentially wipe out an SR. Second, you have to do the sr-probe and sr-introduce and pbd-create and pbd-plug to get the SRs back. Third, you then have to use XOA to restore the metadata which according to the directions is pretty simple looking. According to: https://xen-orchestra.com/docs/metadata_backup.html#performing-a-restore "To restore one, simply click the blue restore arrow, choose a backup date to restore, and click OK:" But this isn't quite true. When we did it, the restore threw an error: "message": "no such object d7b6f090-cd68-9dec-2e00-803fc90c3593", "name": "XoError", Panic mode sets in... It can't find the metadata? We try an earlier backup. Same error. We check the backup NFS share--no its there alright. After a couple of hours scouring the internet and not finding anything, it dawns on us... The object XOA is looking for is the OLD server not a backup directory. It is looking for the server that died and no longer exists. The problem is, when you install the new server, it gets a new ID. But the restore program is looking for the ID of the dead server. But how do you tell XOA, to copy the metadata over to the new server? It assumes that you want to restore it over an existing server. It does not provide a drop down list to pick where to deploy it. In an act of desperation, we copied the backup directory to a new location and named it with the ID number of the newly recreated server. Now XOA could restore the metadata and we were able to recover the VMs in the SRs without issue. This long story is really just a way to highlight the need for better host backup in three ways: A) The first idea would be to create better instructions. It ain't nowhere as easy as the documentation says it is and it's easy to mess up the first step so bad that you can wipe out the contents of an SR. The documentation should spell this out. B) The second idea is to add to the metadata backup something that reads the states of SR to PBD mappings and provides/saves a script to restore them. This would ease a lot of the difficulty in the actual restoring of a failed OS after a new OS can be installed. C) The third idea is provide a dropdown during the restoration of the metadata that allows the user to target a particular machine for the restore operation instead of blindly assuming you want to restore it over a machine that is dead and gone. I hope this helps out the next person trying to bring a host back from the dead, and I hope it also helps make XOA a better product. Thanks for a good description of the restore process. I was wary of the metadata-backup option. It sounds simple and good to have, but as you said it is in no way a comprehensive restore of a pool. I'd like to add my own oppinion here. A full pool restore, including network, re-attaching SRs and everything else that is needed to quickly get back up and running. Also a restore pool backup should be available on the boot media. It could look for a NFS/CIFS mount or a USB disk with the backup files on. This would avoid things like issues with bonded networks not working.

@danp Okay that's great. I was just making sure. Thanks for your reply. Jack

We did recently have a failed drive that finished rebuilding a few days ago.