@McHenry Oh, I didn't see you are doing continuous replication.
This tab is only to restore VM from a remote
Posts
-
RE: Missing backups
-
RE: Missing backups
@McHenry Hi
You can click on the "Refresh backup list" to see your backups
-
RE: Issue installing latest pfSense Plus (24.03 release)
@Affonso Hi !
Are you using XCP-ng 8.2.1 or 8.3 ?
I can't find the 24.03 iso, is this the paid version ? -
RE: Unable to clone my template's disk
@bvivi57 Ah yes, good catch, I didn't think of that !
-
RE: Unable to clone my template's disk
@bvivi57 Hum, weird.
From what i see, i can't tell you why is not working.
For the disk part, I did:
disk { sr_id = data.xenorchestra_sr.local_storage.id name_label = var.name size = var.disk_size * 1024 * 1024 * 1024 }
You can check my old project (I used it a couple month ago, so it should work correctly), and check if you can find some differences: https://git.ataxya.net/ataxya/Tsunami
I'll try to find some time to test your file
-
RE: Unable to clone my template's disk
@bvivi57 Hi !
What's the value of
var.xoa_template
in your file ? -
RE: Recovery-boot Linux Live CD - Windows VM - no graphics
@KPS I don't know why my brain has decided to index all the xcp-ng forum, so when I read your post, I immediately remember the post with the clonezilla issue
-
RE: XOA Pricing Concerns
@someone2b Hi !
You'll have more information here: https://vates.tech/blog/introducing-vates-virtualization-management-stack/
-
RE: Terraform create VyOS from ISO
@SethNY Hi !
I'm working since a few weeks to have a VyOS packer build working with the XCP-ng packer provider. The link you provided is only for qemu build, so it needs some work to be able to adapt it to XCP-ng.
I'll tell you when I have something working, but for now, I have some small difficulty to resolve (install the tools, and other small things).If you want to use terraform, you can do this:
- Prepare a VM manually, with the bare minimum
- Convert the VM to a template.
- And use this template with terraform
I don't know if cloudinit is supported out of the box or if you need to activate some things (I'm not here yet), but if you have something working, I'll think it will be helpful for the community
-
RE: Feedback in regards to upcoming XO update
@john-c The plugin I wrote send all data available to XO, and XO is doing the parsing and display.
As we only work currently with the Mona model, we are not concerned by liquid cooling and other things like this.
To have some history, I recommend using the Netdata plugin and plug it into a Prometheus to have long-term data. For now, XO is displaying real-time value directly from the BMC, with no history.
If you have some values you think are nice to have (in fact, the PSU status was not my idea, but feedback from my community), don't hesitate to tell us !
It's still a work in progress, nothing is set in stone -
RE: is there a way (cli) to get the current health (lifetime) of an internal host ssd?
@manilx Try:
xe host-call-plugin host-uuid=<uuid> plugin=smartctl.py fn=information xe host-call-plugin host-uuid=<uuid> plugin=smartctl.py fn=health
We changed the name between my test and the real plugin on xcp-ng
-
RE: is there a way (cli) to get the current health (lifetime) of an internal host ssd?
@manilx Hi !
I wrote a XAPI plugin for smartctl a while ago. You can use it like this:# Get all the info [18:06 Chouffe plugins]# xe host-call-plugin host-uuid=8b80bcc2-d31c-4f7d-85a7-e921f67c4ec5 plugin=smartctl.py fn=check_smartctl {"/dev/sdf": {"power_on_time": {"hours": 9147}, "ata_version": {"minor_value": 94, "string": "ACS-4 T13/BSR INCITS 529 revision 5", "major_value": 2556}, "form_factor": {"ata_value": 3, "name": "2.5 inches"}, "firmware_version": "SVQ02B6Q", "wwn": {"oui": 9528, "naa": 5, "id": 65536604056}, "smart_status": {"passed": true}, "smartctl": {"build_info": "(local build)", "exit_status": 0, "argv": ["smartctl", "-j", "-a", "/dev/sdf"], "version": [7, 0], "svn_revision": "4883", "platform_info": "x86_64-linux-4.19.0+1"}, "temperature": {"current": 32}, "rotation_rate": 0, [...]} # get health status [18:06 Chouffe plugins]# xe host-call-plugin host-uuid=8b80bcc2-d31c-4f7d-85a7-e921f67c4ec5 plugin=smartctl.py fn=check_health {"/dev/sdf": "PASSED", "/dev/sdg": "PASSED", "/dev/sdd": "PASSED", "/dev/sde": "PASSED", "/dev/sdb": "PASSED", "/dev/sdc": "PASSED", "/dev/sda": "PASSED"} ``
-
RE: Import Centos VM from VMware fails with must have required property
@jkissane Hi !
Did you select a template in the XO's UI ? -
RE: Importing ovf appliance question
@456Q No problem !
Let me export the .vhd and upload it somewhere. I'll give you the link in private, with the password of the applianceI already start to write the blog post
-
RE: Importing ovf appliance question
@456Q I'll do a blog post since it will be a little long to explain here
TLDR: Dell remove entirely the Xen driver, which is needed to be able to use the disk and the network. Had to install an other SUSE (yeah, OME is an SLES) to get the driver and insert it in the OME VM via a rescue box
-
RE: Importing ovf appliance question
It's working !
Let me write a small tutorial to explain how i make it boot, i'll post it ASAP.
Or if you prefer, I can send the .vhd with the patch directly