@Andrew said in Is it possible to convert a BIOS to UEFI and introduce vTPM into an existing VM?:

I have not converted windows as I normally started newer versions as UEFI and older version work better with BIOS

For peeps that stumble on this post looking for answers, the answer is yes you can for Windows.

You can use the built in Windows mbr2gpt program to do so. However, things to consider before attempting are?

• You can only have 3 partitions on the C driver. This is due to MBR only supporting 4.
  the 4th partition will be used during conversion

• it also has to shrink some space from the end of the drive

• You might have to move the recovery partition if it is at the end of the disk

Basic steps are, to first run the command below. This will tell you if conversion should works

mbr2gpt /validate /allowfullos

Then the following to start the conversion

mbr2gpt /convert /allowfullos

Hope it helps someone

GNS3 VM 2.2.43 on XCP-ng 8.2 seems to be working for me on HP G8 running 2 x Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz.

I havent really used GNS3 much so probably havent found what might be broken other than I cant load xen tools.

I just imported the OVA via XOA and pointed the windows GNS3 at the IP address it picked up.

@olivierlambert said in VM's going really slow after 3 - 4 weeks:

Oh wow. So something was wrong with the hardware, specifically the memory, and potentially more errors and error correction trying to keep up, slowing down everything. Is it a good recap?

To be honest I am not entirely sure.
I tested the memory my self in the early stages of this issue with memtest. In the past memtest has flagged memory issue that HP built in diags hasn't but it ran clean.

The server was rebooted prior to replacing the memory out of curiosity and everything came up OK no errors.

So we assume that something was wrong with the memory. And now we have are fingers crossed that that is the end if it

Hi Oliver,

My apologies I have wasted your time (though I did learn about the XOA so not totally wasted)

The old adage "If you want a job done properly. Do it yourself" is still very true.

Long story short when I looked into the issue myself, my colleague was using the wrong XO installation. This VPN isn't site to site so for now we have vmware running 2 nat'ed VMs, XO and a windows client. The windows client accesses XO and XO goes out over the hosts vpn connection to the remote site.

When using this correctly everything is OK

Case closed