Hi All. Yes, this is a very annoying problem that I've also experienced after a fresh Windows 11-24H2 install on XCP-ng 8.3 fully production-patched to date. I am accessing my Windows 11 VM console via a Windows 11-24H2 physical client PC using latest Firefox browser. The keyboard and mouse attached to my laptop via a Dell DisplayLink D3100 USB3 dock are a standard wired Logitech mouse with scroll and a wired Logitech keyboard. The XCP-ng 8.3 host is managed via XO from source (XOS) on the latest commit (66e67) as of yesterday 2/16/2025. XOS lives in an AlmaLinux 8.10 VM built with @ronivay 's superb installation script. After some Googling around, this frozen mouse issue appears to have occurred in other hypervisors too. It looks to be a Windows problem rather than an XCP-ng 8.3/XO/QEMU problem. (I see you smiling @olivierlambert ). I can't guarantee this technique will work for everyone, but after a day, I am no longer experiencing the mouse failure. What appears to be happening is that the Windows Plug-and-Play (PNP) mouse driver configuration is getting borked due to multiple triggerings of PNP. During the first-boot of the VM post-installation, it finds the original emulated hardware. Following the installation of the Citrix management agent 9.4, it performs additional device configuration that doesn't always go well. In the device manager, click view, show hidden devices to see any phantom devices that I generally remove so as to keep everything as clean and pristine as possible. This Windows registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4D36E96F-E325-11CE-BFC1-08002BE10318} is your friend. You must make sure that the value mouclass is the only value in the UpperFilters key of the above device class hive. As a general preventative against Windows oddities, I changed the value and then changed it back to mouclass to force the registry editor to rewrite the hive. You should also delete the mouse instance details folders 0000, 0001 etc. These should get deleted for you when you remove the mouse devices from the device manager. Windows will recreate those during the reboot. Random aside: another thing I like to do is to change the VM's UEFI OVMF display settings to 1280x960 in the Tiano UEFI firmware. This allows me to see the entire VM on my 1920x1080 HD monitor when Firefox is in full-screen mode, XO console scale set to 100%, and the Windows VM display resolution also set to 1280x960. This is intended to prevent weird visual scaling anomalies. The following image is my device manager after the fix. When the mouse was malfunctioning, the system had only created the PS/2 mouse device. The HID-compliant mouse was created after deleting the original PS/2 mouse device and the failed USB Universal Host Controller devices in device manager. Following this, scan for new devices to recreate what is missing and reboot the VM so that those devices get registered and initialized correctly. [image: 1739815845180-6d5087aa-9f38-4c6a-9cbd-c2aef55f5c33-image.png] Some additional screenshots of the mouse instance registry hive values: [image: 1739817060406-16002cf2-1e88-4874-83d4-c769691103c4-image.png] [image: 1739817089195-89518b7c-38bb-4fe1-94e8-d0575eee39b2-image.png] [image: 1739817104459-ae8a2d0e-041a-40cb-bbda-9278aa320c65-image.png]

@olivierlambert said in Feedback in regards to upcoming XO update: I'm not sure to get what you said. Right now, we have a specific partnership with 2CRSi, having access to their engineers who design the case and integrate the components inside. This helps us to give exclusive insight on the hardware, and on their side, providing XCP-ng pre-installed. I'm not against having other partners, but you can imagine that Dell or HPE are taking more time to provide XCP-ng pre-installed on it. I never heard of NovaTech before, I'll be happy to work with them if they want to work with us I have dropped a message to Novatech with a link to your website letting them know about you. They're currently closed for today but when their people come in tomorrow they'll get my message, be ready during that day onwards for possible contact from them! Your already got a French municipality as a customer providing their servers with your Virtualisation software stack. Well if you manage to partner with Novatech you'll also have the capacity to gain MBDA along with Thales as customers through them! They're a solutions producer and provider partnering with them would allow both of you to benefit, as well as incorporate XCP-ng, XOA and/or XOSTOR into the Novatech solutions. Each of the solutions provided by Novatech is bespoke to a specific customer, built using off the shelf commercial components. Pay attention to their video "Our Story #3 About Us" as they provide worry free computing to the companies working to change the world we live in. All of their people enable their customers to do remarkable things. What's more worry free than not having to worry about, a business's product policy of their closed source proprietary software? Partnering with them would enable their products and solutions to have Vates VMS as a component to them and reduce the worries of the Novatech customers!

Hi, I am currently looking for exactly this function. If there is a solution here, I am very interested.

@olivierlambert Bringing this back up because I'm thinking of retiring old servers in exchange for new mini-PC. Looking around in XO, I don't see anywhere to click to promote a server in a pool to controller (master), am I missing something? My plan would be to join all new mini-pc to the existing pool, migrate VMs to these new servers, then take controller (master) onto one of the mini-pc. After that I would remove the older servers from the pool and shut them down. Is the proper way to use the above command, or go to the local console and just force promote one of the new mini-pc to be the new controller? [edit] found it, been a while since I've set up a pool. Click where the arrow is and you get choices on which server in the pool you want to control things. [image: 1737994794797-xcp_commander.png]

@Danp said in Patching and trying to Pool Hosts after they've been in production: Warm migration should work in this case because the VM is halted then restarted as part of the process. See here for more details. Sweet, I'll setup something small on the old host for testing and use the Warm Migration process.

@pdonias said in Xen Orchestra & XO Lite PWA Manifest: Thank you @john-c! We need to make a few changes first, we'll take care of your PR right after that As a result of taking such a long time to get around to reviewing and merging my PR. The base for my contribution got really out of sync so I had to discard the changes and rebase. This meant the PR got closed a new one was needed. The Old PR with branch was really out of sync and with several lots of conflicts. https://github.com/vatesfr/xen-orchestra/pull/7445 So please do this new one during today or tomorrow so that the rebasing isn't needed again! MrGrymReaper opened this pull request in vatesfr/xen-orchestra closed xo-web Initial PWA manifest for Xen Orchestra 6 #7445

That's on VMware side then, double check you have all the emulated NICs setup in VMware

@felipefonsecabh You need to check the specific checkbox: https://xen-orchestra.com/docs/full_backups.html#backup-without-snapshot

@hannes Full backup interval (and Force full backup in the schedule settings) forces the job to do a full export of the disk and not a delta based on a previous one. It is not impacted by the retention as XO will always makes sure every chain has at least a full export at the beginning so that all backups are viable. Which means you will have multiple full backups, always one at the beginning, and, those that have been triggered by the settings above.

The issue is within pools: XCP-ng isn't meant to have pool members down (for various reasons), so the scenario is only limited to pools with one host only

You can't login to our servers with your source version (from Git), you must download the virtual appliance. If you can't access https://xen-orchestra.com internally, then, indeed, you won't be able to register it in the end. But if you managed to clone it from Github, you have some access to outside

Happy to do baby steps If / when you guys add some kind of "register" option to get a count on things I'd add my instance(s), as long as it doesn't break the existing install / upgrade scripts at least! Generally I have no issues with just clicking it away since I'm the only one that sees it. If it were a viable option sometime in the future, those would be my ideal "features". I've really enjoyed using XO coming from ESXi / vCenter at work and formerly running my home lab. Your vision of support is similar to Nutanix's which is partially why we went their route for our server overhaul and I think it's excellent. I'm hoping by the time we're due for a refresh the hyper-converged offering is fleshed out and production ready. Though I would miss my integrated firmware upgrades.

I did for sure. But I noticed that a new commit(886ff2cd7) was made literally in about the last hour and after updating again to that version all is good!

@rjt yes exactly.

@w21froster Did you ever come up with a solution here?

AFAIK, you have to do manual passthrough for USB so if you want to attach ethernet dongle to a VM, you plug it in the host and turn off the VM, passthrough the USB to the VM, start the VM, never do snapshot of this VM as it will fail.