Jump to content

Mark Syms

Members
  • Posts

    296
  • Joined

  • Last visited

  • Days Won

    8

Posts posted by Mark Syms

  1. These can't and should not be deleted as they are the read-only parents of delta VDIs that will have been created by your backup software taking snapshots of the VMs. Asuming nothing else untoward they will be cleaned up and merged with the leaf VDIs at some point after the snapshots are deleted, if the snapshots are still present they will not be removed until such time as the snapshots are removed and the background housekeeping tasks have an opportunity to merge the data in the parent and child VDIs.

    • Like 2
  2. This is not a problem with the hypervisor but an issue with your network service provider.

    The only thing you could do is create a separate VM as a "router" VM and route the traffic from the other VMs through that with a NAT firewall. The VMs each need to have a unique MAC address as that is what is used to ensure that network traffic for the VMs is sent to the correct place.

  3. On 12/2/2021 at 2:12 PM, Tobias Kreidl said:

    Might be easier to install 7.6 on the new servers (if even possible), join them to the existing pool, and then consider an upgrade. On the other hand, you also want to make sure all your servers will be compatible with 8.2 before you even think about upgrading. As you already pointed out, there is no direct migration from 7.6 to 8.2, anyway.

     

    -=Tobias

    Upgrade from 7.6 to any version is not supported as the versions to which 7.6 was supported to upgrade to are themselves no longer in support.

  4. 34 minutes ago, Mike Maggio1709162854 said:

    I though you could go from 7.2 to 8 and then to 8.2.

    no, it was only ever supported to upgrade from N-2 to N, i.e. 7.5/7.6 -> 8.0. Long Term Support releases, i.e. XenServer 7.1 CU2 are expected to be upgradable to the next LTSR release, i.e Citrix Hypervisor 8.2.

    Currently there are only the two LTSRs in support, i.e XenServer 7.1 LTSR CU2 (until August 2022) and Citrix Hypervisor 8.2 LTSR

  5. You can look in the /var/log/SMlog file after running the "Rescan" operation from XenCenter. If the garbage collector finds any coaleascable nodes it will print a tree of them in the log and if it can't perform the coalesce for any reason it will report why in there as well.

  6. It's probably both, something went wrong and then the code is not handling the failure. As XS 7.6 is long EOL (as is Citrix Hypervisor 8.0) there is now no supported upgrade path that doesn't involve re-installing from scratch.

  7. Both of those features require virtualisation support in the operating system and as this is a VM that means nested virtualisation support in the hypervisor. This is not a feature supported by Citrix Hypervisor and it is not on any roadmap although it is something that both the product and engineering teams are aware of being necessary for supporting certain features of Windows. 

×
×
  • Create New...