XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Shares 0
    • Posts 18
    • Groups 0
    R Offline
    1. Home
    2. robertblissitt
    3. Best

    Posts

    Recent Best Controversial
    • RE: XO Community edition backups dont work as of build 6b263

      Yes, you will always see those "cleanVm: incorrect backup size in metadata" warnings, and Vates has said that it's OK to ignore them. You won't see them if you "Store backup as multiple data blocks instead of a whole VHD file," but your storage will need to support the required 500-1000 files per backed up GB (and of course you'll need to evaluate whether you wish to use multiple data blocks instead of VHD files in the first place).

      I re-ran my backups and the three VMs that failed backup previously have now succeeded.

      posted in Backup
      R
      robertblissitt
    • RE: XCP-ng 8.3 updates announcements and testing

      @vxgmichel I may have found our problem. Looks like an XCP-ng update may have slipped an unwanted site back into our /etc/yum.repos.d/xcp-ng.repo. When I first deployed XCP-ng, I had to remove the "http://mirrors.xcp-ng.org/8/8.3/base/x86_64/" entry for updates to work as it was too troublesome to get it working through our outbound proxy managed by another team. I have re-removed that site and things are working again. It was not fun trying to figure that out in the midst of a vulnerability.

      diff /etc/yum.repos.d/xcp-ng.repo /etc/yum.repos.d/xcp-ng.repo.orig
      <- baseurl=http://updates.xcp-ng.org/8/8.3/base/x86_64/
      -> baseurl=http://mirrors.xcp-ng.org/8/8.3/base/x86_64/ http://updates.xcp-ng.org/8/8.3/base/x86_64/

      <- baseurl=http://updates.xcp-ng.org/8/8.3/updates/x86_64/
      -> baseurl=http://mirrors.xcp-ng.org/8/8.3/updates/x86_64/ http://updates.xcp-ng.org/8/8.3/updates/x86_64/

      posted in News
      R
      robertblissitt
    • RE: XO Community edition backups dont work as of build 6b263

      I've updated to the latest master as well (1a7b5) and my metadata/config backups completed successfully, as did my smaller test backup. However, only 16 of 19 VMs in my main backup job completed. I am re-running the main backup now and will report back if the error recurs.

      Update: The job is still running, but here is the error from the three VMs that failed previously: "Error: invalid HTTP header in response body"

      posted in Backup
      R
      robertblissitt
    • RE: Error: Can't init vhd directory without using alias

      I am seeing similar behavior, and only on my backup Remote with "Store backup as multiple data blocks" enabled. I've fallen back to a previous build from two days ago and rerunning backup now. 🙂

      posted in Backup
      R
      robertblissitt
    • RE: VMware migration tool: we need your feedback!

      @florent Hi there, and thank you for your reply. I did a file compare of the .VMX and .VMSD files and found only one difference between when the VM was configured for Native Snapshots and not configured for Native Snapshots. Note that snapshot.alwaysAllowNative = "FALSE" is the default afaik, so a .VMX file without this line in it has Native Snapshots disabled.

      C:\Downloads>fc stem2p19_files-snap-false\stem2p19.vmx stem2p19_files-snap-true\stem2p19.vmx
      Comparing files STEM2P19_FILES-SNAP-FALSE\stem2p19.vmx and STEM2P19_FILES-SNAP-TRUE\STEM2P19.VMX
      ***** STEM2P19_FILES-SNAP-FALSE\stem2p19.vmx
      usb_xhci:4.parent = "-1"
      snapshot.alwaysAllowNative = "FALSE"
      ***** STEM2P19_FILES-SNAP-TRUE\STEM2P19.VMX
      usb_xhci:4.parent = "-1"
      snapshot.alwaysAllowNative = "TRUE"


      C:\Downloads>fc stem2p19_files-snap-false\stem2p19.vmsd stem2p19_files-snap-true\stem2p19.vmsd
      Comparing files STEM2P19_FILES-SNAP-FALSE\stem2p19.vmsd and STEM2P19_FILES-SNAP-TRUE\STEM2P19.VMSD
      FC: no differences encountered

      I tested several scenarios for fun:

      Windows VM with Native Snapshots enabled:
      With VM powered down and no snapshot taken, can I still import it successfully?
      Yes.
      What about powered down and with a (native) snapshot taken?
      Yes, with or without "Stop the Source VM" enabled.
      What about with VM powered on, snapshot taken, and Stop the Source VM enabled, can I import VM successfully?
      No, at the end of the import, both imported disks and the imported VM disappear.
      What about with VM powered on, native snapshot enabled, no snapshot taken, and Stop the Source VM enabled, can I import VM successfully?
      Yes.

      Windows VM with Native Snapshots not enabled (just one single test scenario):
      What about with VM powered on, snapshot taken, and Stop the Source VM enabled, can I import VM successfully?
      Yes

      So the problem seems to be when the VM is powered on and there's a native snapshot present.

      The warm migration capability is very cool. I likely won't use it because a reboot would be required to remove VMware Tools anyway. Also, my VMs are not huge and should migrate fast.

      I see what you mean by Fast Clone. That is very fast.. I'll try to get that to work with Citrix MCS. I think it may only be useful for our single-sessions hosts, not our RDSH-type hosts, but that would still be helpful.

      One last thing: NetApp offers a very good ONTAP simulator for free. Now that ESXi is also free once again (LOL), you may be able to test the above scenario on your end if you like. 🙂

      Please let me know if you have any questions. Cheers!

      posted in Migrate to XCP-ng
      R
      robertblissitt
    • RE: XCP-ng 8.3 updates announcements and testing

      Thank you, @stormi , I'm happy to know that xcp-ng.repo is not touched. These three hosts haven't been rebuilt or restored recently, no hosts have been added, and I did have to make the above modification on each one of them to get them to work. I suppose it's possible I missed the step to remove "mirrors.xcp-ng.org" from xcp-ng.repo during the initial pool build about a year ago and it's just somehow been working with our outbound Internet proxy. 🙂 In any event, having "mirrors.xcp-ng.org" in our xcp-ng.repo file has definitely caused us problems in the past with our proxy setup.

      TGIF/DMCV!

      posted in News
      R
      robertblissitt
    • RE: XCP-ng 8.3 updates announcements and testing

      I did a RPR early this morning just to start fresh and then kicked off an RPU 15 minutes ago. The RPU evacuated all the VMs from the master successfully but the RPU is stuck at 0% (as seen in Pool Tasks). I will allow the process to time out (or restart XO if the wait is too long), promote another node to master, and retry the RPU.

      posted in News
      R
      robertblissitt
    • RE: XCP-ng 8.3 updates announcements and testing

      @gduperrey Absolutely understand. 🙂 I didn't now about the Escape key as Manilx mentioned. Next time, I will press Esc to see if there is any useful information and report it here. This was just new behavior and wanted to report it informally.

      posted in News
      R
      robertblissitt
    • RE: XCP-ng 8.3 updates announcements and testing

      @Pilow I've been wondering lately if I should do a Rolling Pool Reboot before any Rolling Pool Update. This might allow me to identify problems in advance and I would also be installing the patches on freshly-rebooted hosts.

      posted in News
      R
      robertblissitt
    • RE: Unable to fetch latest master commit.

      Greetings! I have been seeing the same since yesterday and it is happening every time. I rolled back to a previous version yesterday and the failure notice was no longer displayed. I ran the XenOrchestraInstallerUpdater script again this morning, and while it did update successfully, the failure notice has returned.

      c0806919-7bc2-402a-b7e7-235c99507ba1-image.jpeg

      posted in Xen Orchestra
      R
      robertblissitt