@Andrew all that was okay. The proxy string was incorrect, now working. Thanks
Latest posts made by 2planks
-
RE: New server pool not showing in XOA
-
New server pool not showing in XOA
A new pool has been added with new servers, all functioning in XCP-ng Center. The pool master has been added to XOA, but does not show in the list of hosts, and the pool is not added to list of pools. Any advice please!
-
XOA cannot see 4 pools
Running XOA Enterprise, have just added a fourth host pool. Only 3 pools can be seen at any time: if I restart XOA appliance, it will still be 3, but not necessarily the same ones.
XCP-ng sees all the pools - is there a limit on XOA Enterprise? -
RE: Migrate all VHDs from SR
@akurzawa thanks, I have been doing that. I was looking for a lazy way to move 20+ VMs out of a partition.
-
RE: Migrate all VHDs from SR
Good to know that's on the way. Yes, have been using VM view
-
Migrate all VHDs from SR
I hope there is a way to migrate all virtual disks from a partition. There is 3TB of data to move, it would be great to queue it up and let it run.
-
RE: no object with UUID or opaque ref
I think this is what happens when you ask XOA to move a disk into a different resource pool, and that pool can't see the storage. Discovered that by accident
-
RE: Moving VMs in a multi-pool setup
Olivier - the destination storage was attached to the wrong pool. It was behaving correctly, but not doing what I wanted.
-
Moving VMs in a multi-pool setup
I am moving some VMs to different storage, into a large NFS partition. My hosts are grouped into 2 pools, which have different purposes, so I run different VMs in each pool.
I am copying the VM, then deleting the original, as there is a problem with the existing storage. Every copy I make from pool1 is ending up in pool2. That is surprising since I never added the destination storage to pool2, but XOA can see it all and just makes it happen.
Is there a way I can make XOA copy into the original pool? -
RE: no object with UUID or opaque ref
@borzel I am moving some VMs out of a storage pool, by moving the disks. For each VM in that storage, I get the error above.
The VMs are healthy, and I am able to copy them instead, then remove the original copy.
Pretty sure the problem is on the storage side, which is why I am migrating out of there.