XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • P

      active volcano eruption going on here =)

      Watching Ignoring Scheduled Pinned Locked Moved Off topic
      2
      5
      0 Votes
      2 Posts
      30 Views
      nikadeN
      @Pilow damn thats super scary! I hope everyone is OK.
    • D

      XCP-ng Windows PV tools announcements

      Watching Ignoring Scheduled Pinned Locked Moved News
      83
      0 Votes
      83 Posts
      10k Views
      A
      @dinhngtu You rock - thank you!
    • kruessK

      XenServer 7.1.2 to XCP-ng 8.3: INTERNAL_ERROR(Not_found)

      Watching Ignoring Scheduled Pinned Locked Moved Migrate to XCP-ng
      3
      0 Votes
      3 Posts
      39 Views
      kruessK
      @Danp Thanks for looking into this... Restart: Yes, Pool Master was restarted after applying the XCP patches VM start: Yes, I'm trying to start the VMs on the master (also, it would not allow me to start VMs on the slaves with XenServer on it during the migration phase) Upgrade Path: Yes, vrom XS 7.1.2 to XCP 8.3 Regarding the VM_HOST_INCOMPATIBLE_VERSION: I saw those, too, but cannot think of anything obvious, as the VMs which I was able to start on the Master were of the same kind (WinSrv2019, Ubuntu Server, Win10). Of course, there might be slight differences in the metadata, but I've compared two WinSrv2019 and they are pretty close. Only "RW/MRW" differences found: HVM-boot-params (MRW): order: dc; firmware: bios HVM-boot-params (MRW): order: dc platform (MRW): ...; secureboot: false platform (MRW): ... I've removed those two param keys from the failing VM but it did not change the behaviour.