@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

We don't have any feedback on that, so I can't tell

That's weird, but OK. Maybe it's because even when you update, the old/existing RRDs data won't be "replaced".

@DustinB Guest tools simply don't support the system I'm running.

Question for @pdonias

@Danp said in Advanced VM settings Logs: Hi Dustin, Yes... these types of actions are recorded in the Audit log (Settings > Audit) if you have access to this feature and have enabled it. Dan Perfect, thanks!

I see your point. Thank you!

@blackliner said in Sdn controller and physical network: @nikade How do you "pair" the XCP-ng SDN with your routing setup? You cant/dont, you'll have to setup each private network on the vyos router and then have the vm private network routed through it manually. For example if you have private network 1 with subnet 192.168.1.0/24 you'd have to add this network to the vyos router and assign 192.168.1.1/24 on the router. Then set 192.168.1.1 as default gateway in your vm's which uses this network. Then you'll setup ospf or bgp on the vyos router manually with your upstream border/core-router or firewall. If the subnet is a private subnet you'll need to setup NAT as well somewhere before it reaches internet to NAT traffic from 192.168.1.0/24.

@olivierlambert I’ve got a few VM’s that lock up from time to time. There is no rhyme nor reason (different hosts, different storage, etc). As a result, I just have a job that restarts them at 5:30 am every day. I’d like to have the software tool software restart them but, in the occasion wher the VM is locked up tight as Fort Knox, I’d like the hard reset to happen. Make sense ?

@cocoon hello! For now we are on reflexion on a refactoring to move towards a system more RBAK based, IAM type. We will inform the whole community when we are sure of the direction the new ACL system will take. Stay tuned

Pinging @stormi about it

@jkatz Thanks for that. I actually did something different but it worked. I don't know how but it is working. I used this in XO in Cloud Config [image: 1747138648336-a5f1ca37-802a-4ff4-bc4f-6c8ccaa3dc97-image.png] It worked [image: 1747138770858-e2666c29-8a03-41e1-879b-b6559b7f0bf2-image.png] Don't know if does it matter or not ( probably does) that I also entered this plugin into both files : cloudbaseinit.plugins.common.sethostname.SetHostNamePlugin @jkatz said in Cloudbase-init on Windows: You don't. That is lame. Wonder if domain join is possible with that...

These two bugs have been fixed in the latest release

Don't worry it's for you

@piotrlotr1 I think my original mini-lab did this, I had mistakenly joined these hosts to the big lab pool, found out is was wrong and detached them to make a mini-lab pool. There were some oddities when I did this, but I just worked past them and created their own pool and did my warm migrations. Wish I had taken better notes of this when I did it. I wiped and rebuilt my mini-lab now, so no going back.

Thanks for fixing this!

@Bastien-Nollet Thanks for the update. In my community edition instance at my church, I just updated it to Master, commit 37fbb so I'll test over the weekend and provide an update. For my XOA (Airgapped) instance at work, I did receive an updated appliance about two weeks ago, so I'll test and see if the problem persists. If it does, then I'll just wait until the official release of XO and then I'll request an updated appliance.

Problem solved with update of XOCE

@ecoutinho Thanks for chiming in. I managed to figure out the math, but thanks nonetheless.