toce's Posts

Just to confirm that the first official release of Debian 12 (bookworm) 12.0.0 runs fine for me in Fusion 13.0.2 on Apple Silicon. Also verified that the WirePlumber stuttering audio fix as proposed by gnttz79xro is working great as well.

Here's one for the Tips and Techniques manual. Recently an updated Debian 11 backport kernel has been released. Existing kernel in my Debian 11 VM: linux-image-5.18.0-0.deb11.4-4-arm64 Upgraded to: linux-image-5.19.0-0.deb11.2-arm64 After the upgrade the VM boots and everything I checked so far seems to be in proper working order. And that includes dynamic resizing. apt-get install linux-image-5.19.0-0.deb11.2-arm64/bullseye-backports Enjoy! 

I have a Debian 11 VM with backported kernel 5.18.0-0.deb11.4-arm64 and backported open-vm-tools and open-vm-tools-desktop packages. Under certain circumstances in this VM I lose the cursor not only in the VM itself but also MacOS wide. What's the scenario: Have all your VM's shutdown properly. No VM is in suspended state. Reboot your Mac and start VMware Fusion. Boot the offending Debian 11 VM (with backported kernel and open-vm-tools pkgs) and logon. Open a Nautilus file browser (so we have an active window) After a minute or so suspend the VM. Close VMware Fusion. Reboot your Mac. Restart VMware Fusion and revive the suspended VM. Click in the VM on the desktop. At that point the cursor will disappear not only in the VM but also outside of the VM. How to recover the cursor: Attempt to blindly place the hidden cursor in the MacOS dock. Keypress option-command-esc (this will bring up the task manager). Your cursor should appear somewhere together with the task manager. Try to navigate the cursor to the dock, preferably avoiding the VM area, and scrub over the dock. In the process you may lose your cursor but it will become visible again when meeting the dock. Click the Finder icon. Your cursor is now restored. If step 3+4 did not work (my experience is it'll take a few attempts), press Esc to quit the task manager and go back to 2. Next to the Debian 11 VM I also have another Debian 11 VM without a backported kernel and no open-vm tools. With this VM I have no problem suspending and reviving the VM in the scenario described above.

I have two Debian 11 VM's in my library. For the first VM the reported VM HD size shows a healthy 5.6 GB. This is correct. For the second VM the reported VM HD size shows a meager 2.6 MB (yes, MB, not GB), which is of course way off. What could be the difference between the two VM's? The only thing I can think of is that the first VM was created as a custom VM whereas the second one was created by dropping the iso on the "install from disc or image". Ref attached screendump "vm-info-220906.png" showing the 2.6 MB VM HD size. Ref attached dirdump "vm-220906.txt" showing the files of the second VM.

In the Tech Preview 22H2 Apple Silicon Tips and Techniques v2 document, instructions are provided to upgrade the Debian 11 kernel with a 5.18.0 backport. For this, ref section 4.2 "Obtaining newer kernel versions for Debian 11". Unfortunately, with the instructions provided I do not seem to be able to upgrade the kernel. I installed Debian 11 using a fresh copy of the "debian-11.4.0-arm64-netinst.iso", and configured the installation with GNOME and only the standard utilities. Ref attached "backport-220905.txt" for the actual command used and the (alas, disappointing result. Basically the failure boils down to "Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming." Several messages in the attached log refer to kernel "5.18.2-1~bpo11+1", but attempting to install that using name "linux-image-5.18.2-1~bpo11+1" tells me its name could not be located. Any help is appreciated.