Can I disable mouse integration/grab/seamless mode?

[nbolton]

I would like to disable the automatic mouse grab feature. I want the mouse to be fully captured by the VM (i.e. disable the automatic mouse transition from host to guest). You can do this in VirtualBox, for example, by disabling mouse pointer integration.

Is this possible in VirtualBuddy? If so, how can I do it?

[nbolton]

A bit of research...

I tried to make my own input class by inheriting VZPointingDeviceConfiguration but couldn't get past the first hurdle, as I got an error when creating an inheriting class.

diff --git a/VirtualCore/Source/Virtualization/Helpers/VirtualMachineConfigurationHelper.swift b/VirtualCore/Source/Virtualization/Helpers/VirtualMachineConfigurationHelper.swift
index 4917617..4d5e72b 100644
--- a/VirtualCore/Source/Virtualization/Helpers/VirtualMachineConfigurationHelper.swift
+++ b/VirtualCore/Source/Virtualization/Helpers/VirtualMachineConfigurationHelper.swift
@@ -134,6 +134,10 @@ extension VBNetworkDevice {
 
 }
 
+class VZUSBCapturePointingDeviceConfiguration: VZPointingDeviceConfiguration {
+    public init() {}
+}
+
 extension VBPointingDevice {
 
     var vzConfigurations: [VZPointingDeviceConfiguration] {
@@ -141,6 +145,7 @@ extension VBPointingDevice {
             switch kind {
             case .mouse:
                 //return [VZUSBScreenCoordinatePointingDeviceConfiguration()]
+                return [VZUSBCapturePointingDeviceConfiguration()]
             case .trackpad:
                 guard #available(macOS 13.0, *) else {
                     throw Failure("The trackpad pointing device is only available on macOS 13 and later")

[insidegui]

I think it would be easier to implement this by messing with event handling in VZVirtualMachineView, which could probably be done by wrapping it in a container view and overriding sendEvent: rather than subclassing VZVirtualMachineView itself. I haven't tried this yet, but in theory it should work (famous last words).

[nbolton]

And for what it's worth, Parallels has the same issue. But actually, you can't configure anything about M-series VMs in Parallels yet.