@Andrew All virtualisation options are enabled. It is an HPE DL360 Gen11, my first of that gen. Never had setup issues with Gen10. I'm focussing on the Intel network card - the NICs are not visible to XCP-ng. I have installed the Intel hardware driver for Redhat, installed with no issues. That made no difference.
Has this issue happened before?
Latest posts made by 2planks
-
RE: NIC not working on new HPE DL360 Gen11
-
NIC not working on new HPE DL360 Gen11
XCP-ng 8.2 and 8.3 both do not see the Network ports (Intel adapter 1350T4 ocpv3)
I am able to update the adapter firmware through XCP, so the hardware is visible. Intel has Linux drivers for this card, for SLES and Redhat - which is more suitable for XCP? -
RE: New server pool not showing in XOA
@Andrew all that was okay. The proxy string was incorrect, now working. Thanks
-
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.