Posts made by SchaffnerOnline

@julien-f Wanted to check on this as the fix didn't correct the issue.

Thanks
Mike

@julien-f Hi Julien, I updated my XO this morning and tested, unfortunately, the same issue still exists. I've attached the log file.

2024-03-27T14_56_50.270Z - XO.txt

@julien-f, I think I might have figured out the issue. I run my entire system on a 1Gbps network. When copying the template to a new VM, it takes about 10-12 minutes for the base Windows 10 VM to copy. We are getting a timeout, it appears based on some testing I did, that if it takes longer than 5 minutes, it times out and thus the template that is created doesn't get the final steps and turned into a VM. Here is the log when I tried to create a new VM from a Debian template I created, but I had put a large file (10 GB) which made the template to VM creation take about 7 minutes. I happened to see an error box pop-up in the upper-right corner and pulled the log:

vm.create
{
  "clone": false,
  "existingDisks": {
    "0": {
      "name_label": "Deb-12-Template-20G",
      "name_description": "",
      "size": 107374182400,
      "$SR": "7b7c9d36-6410-ca59-16c6-84e4922d00ee"
    }
  },
  "name_label": "Deb 12 Template 20G",
  "template": "56901d17-0bc8-f48f-9055-9103c303d381",
  "VDIs": [],
  "VIFs": [
    {
      "network": "c89c9d93-c08e-6b51-1ba7-cddfc1a85a0e",
      "allowedIpv4Addresses": [],
      "allowedIpv6Addresses": []
    }
  ],
  "CPUs": 2,
  "cpusMax": 2,
  "cpuWeight": null,
  "cpuCap": null,
  "name_description": "",
  "memory": 4294967296,
  "bootAfterCreate": true,
  "copyHostBiosStrings": false,
  "createVtpm": false,
  "destroyCloudConfigVdiAfterBoot": false,
  "secureBoot": false,
  "share": false,
  "coreOs": false,
  "tags": [],
  "hvmBootFirmware": "bios"
}
{
  "name": "HeadersTimeoutError",
  "code": "UND_ERR_HEADERS_TIMEOUT",
  "message": "Headers Timeout Error",
  "call": {
    "method": "VM.copy",
    "params": [
      "OpaqueRef:5c4b2c34-c7b6-fa8b-b855-2b9664e11ad5",
      "Deb 12 Template 20G",
      ""
    ]
  },
  "stack": "HeadersTimeoutError: Headers Timeout Error
    at Timeout.onParserTimeout [as callback] (/root/xen-orchestra/node_modules/undici/lib/dispatcher/client-h1.js:635:28)
    at Timeout.onTimeout [as _onTimeout] (/root/xen-orchestra/node_modules/undici/lib/util/timers.js:20:13)
    at listOnTimeout (node:internal/timers:569:17)
    at processTimers (node:internal/timers:512:7)"
}

@julien-f I created a new VM to build XO from scratch and when I went to create a new VM from my Windows 10 Template, it just created another template. But I also deployed an XOA (Version 5.91.2), and then asked it to create the VM from my Windows 10 Template, it worked correctly. I upgrade the XOA to the latest channel build (Version 5.92.1) and it worked correctly there as well.

So I've been doing some more work to see if I can figure out this issue. And so far no luck.

I'm running a 3 Host environment, that all 3 hosts are identical, HP EliteDesk 800 G3 SFF, Intel i7-7700 CPUs, 64GB memory in each. There is QNAP NAS that is providing NFS storage for the VMs and an NFS ISO storage location. My XCP-NG hosts are running version 8.3 Beta 2

My XO is running on a Mini PC, XO is compiled from sources, and updated today to commit 1b515.

When I create any Windows VM and then convert it to a template. When I then try to create a new VM from that template, instead of creating a VM, it creates another template. What I have found interesting, is that when I try to create this new VM and I give the Disk a new name, when it completes and has created template instead, the name of the disk is the same as the source template and not the new disk name that I gave it when I was filling out the info for the new VM.

When I create a Windows VM from the template I made, but using the "Fast Clone", then it seems to be working correctly. Its creating a VM and the disk name is the new disk name I wanted for the new VM.

I think, but I can't confirm that I think this issue may have started with the changes from this issue:
https://github.com/vatesfr/xen-orchestra/pull/7388

If someone can confirm using the same XCP-NG version and an updated XO from sources, or some guidance on where to look in logs that may tell me why instead of a VM being created from the template, its creating another template.

julien-f opened this pull request in vatesfr/xen-orchestra

closed Fix clone #7388

@Bub When you created the VM from your template, was "Fast Clone" enabled or disabled. Sounds like fast clone was enabled, as that works for me too and it only takes a few seconds to create. When you turn "Fast Clone" off, it will take a few minutes to create the VM and that's when it fails.

@DustinB I do have that load-balance plugin activated. Though I wouldn't think that doing a VM creation would cause to become a template instead of a VM. I have 3 identical hosts with XO running on a separate mini PC.

@DustinB So I just confirmed, that when I try and create the VM from the template I created with Fast Clone turned off, its creating another template and not a VM.

@DustinB Yep, that's what is has been doing. I'm running another test, because I had it work when I did a fast clone, but I'm trying it without fast clone to see. I also did a VM creation using XCP-NG Center, just to see and it worked properly on that one.

@DustinB Im running XO from sources, currently on commit b8177

I am creating the new VM from the template, but it creates a template instead of a VM. I'm running another test I've rebooted my XO box.

Created a Windows 10 system to be used as a template for creating other Windows 10 VMs. After building the VM and getting Windows 10 to where I want it for a template. I shutdown that VM and did a "Convert to Template". All good to this point.

When I go to create a VM from that template, after giving the VM a different name than the template and a different disk name. XenOrchestra goes through the process of creating the new VM.

When the process completes, there isn't a VM in the listing. It has created another template with the new name, and when looking into the storage and the disks in the SR, there is a disk that has the original name from the template and not the new name that I gave it for the VM. There are now 2 disk with the same name, one attached to the template that I created and another that is attached to the new template that was created, that was supposed to be a VM.

This is something that has happened recently, I haven't been able to pin down when it exactly stopped working correctly. As I was able to create VMs from this Windows template before. I have also deleted my original template and built a new Windows 10 template, but that hasn't corrected the issue either.