pinging @nhanlon

@olivierlambert Dont know why the screenshots were not loading, posting that again

With no snapshots and coalesce completed, very very little space used.

Captura de pantalla (233).png

@julien-f That explains it. Thanks!

@maxcerny You shouldn't have any diff, no.

@ruskofd is right. You should be able to use the cloud_network_config attribute to achieve this.

The following code is untested but should launch a vm with a static IP. Please see the xenorchestra_vm resource docs and the cloud-init networking v1 docs for more details.

resource "xenorchestra_vm" "static_ip_vm" { .... cloud_network_config = <<EOF network: version: 1 config: - type: physical name: eth0 subnets: - type: static address: STATIC_IP/24 gateway: GATEWAY_IP dns_nameservers: - 8.8.8.8 EOF }

Let me know if you have any questions or issues using cloud_network_config,

As for the blog post, the VM would have been assigned an ip address via dhcp (assuming the guest OS had cloud-init installed which was true for the VM template in the blog post).

I agree it makes sense.

Ping @pdonias

@jedimarcus said in Clarification on an Advanced setting:

@eangulus With MaxCPU you can do the increase WITHOUT shutting down...

I'll complete this with an example:

create a VM with 4 vCPUs and Max vCPU = 8. you can now change the number of vCPUs from anything between 1 and 8 without shutting the VM down

It's also explained very clearly here: https://xen-orchestra.com/docs/community.html (in the first point)

Always update to latest code available before reporting a problem 🙂

@danp i couldnt get the log from command line, sorry

But i was able to complete the backup to another remote, so i think the main problem is the remote im using

@harajukakei I dont use it but it does work for me (XO build from Source), although not from my android phone (the hosts don't move across to the Available list), so could it be browser related?

@andy you're welcome!

@julien-f

Thank you for explaining your plans. I am very eager to see the new XO 6! Perhaps a Christmas present for all of us? 😉

I just realised I have one more "peeve" with XOA. That is the console view which does not work well with Swedish keyboard layout. For example pressing Alt-Gr+2 to get at-sign '@' doesn't work. It also crashes the keyboard input so it doesn't release the alt-key. This always works correctly in XCP-ng center. The problem is in both Linux and Windows guests.

Have you checked our guide to install Windows drivers? Check https://xcp-ng.org/docs/guests.html#windows

If you still have issues, with your current XOA account in trial, you can open support tickets already so we can take a look remotely (https://support.vates.fr)

Feature request oped 🤞

https://github.com/vatesfr/xen-orchestra/issues/5391

brezlord created this issue in vatesfr/xen-orchestra closed Set pool wide Xen Motion Network #5391

@naeemarsalan Good catch, It will be added to the cloudinit script creating the master and the nodes.

This will save one reboot to everyone. 🙂

It's a little different, but if in Xen Orchestra you go:
Home => Hosts => <host> => Network
there I can see my storage IP addresses comparable to that "IP Address Configuration" part.

Except that here, all the networks are listed in the same list.
Can you see if that's what you are looking for?

Is there a way to access your OVA so we can try to reproduce?

Existing HA level is at VM level. It means, if the VM is down (or the host on the VM is running is down), it will be booted on a working host in that pool.

For hyperconvergence, it's far from being a miracle solution. It costs a lot of thinking, planning and maintenance (and careful usage of it).

Like HA in the end.

So before asking for advanced features, it's good to think about what you really need.

He also said there's a fix coming for the next release.

@olivierlambert Thanks, I tried running fstrim but it returned "the discard operation is not supported" on this NFS SR mount. I also tried running on SSD mounts which do support TRIM and they all returned the same message about "discard...not supported."

The VM OS (CentOS 7.8) does support TRIM in kernel so not sure if xcp-ng or xenserver is the reason why the VM can't issue fstrim on the NFS SR mount or the SSD SR mounts.

85b94dd0-b129-45ec-9ee2-bc4b7dd92b5e-image.png