TheDarkTrumpet's Posts

Good afternoon everyone, I'm running into a weird issue that I'm unsure what to do.  There's plenty of information about accessing a service that's running on a guest (e.g. ssh), but not the other w... See more...
Good afternoon everyone, I'm running into a weird issue that I'm unsure what to do.  There's plenty of information about accessing a service that's running on a guest (e.g. ssh), but not the other way around. Host: OSX Senoma Guest: Ubuntu (Server + ARM) On the host, I have a service that's running on port 7860, and I'd like to access it on the guest.  I'd like to avoid accessing it via a more "public" url.  For example, if my IP address, internal to my network, is 192.168.1.5, I don't want to access it via http://192.168.1.5:7860.  What I'd like to do, instead, is access it over the private host-only network. For example, on my mac I have the. following IP address bound to 172.16.126.1.  In the guest, that IP address is 172.16.126.1228.  I'd like to access the service via http://172.16.126.1:7860 I've verified the service I'm running is listening on all hosts (0.0.0.0), and I can access the URL via http://172.16.126.1:7860 on my mac.  I just can't access that URL via my virtual machine.  I've tried with/out firewall and little snitch on. I should also add that I have multiple NICs in the VM.  I tried with disabling all but one of them, and that didn't work either.  Ping, though, does work fine. Thanks
Sorry for the late reply.  From when you helped me earlier on that.   I'm using Ubuntu 22.04.2 LTS, using the 5.19.0-46-generic kernel (based off the linux-image-generic-hwe-22.04 package)
Good morning, I'm noticing a bit of a "weird behavior" of sorts, well - 2 of them actually.  They're not super big deals, but figured it's worth asking about anyways incase it's some bug in the driv... See more...
Good morning, I'm noticing a bit of a "weird behavior" of sorts, well - 2 of them actually.  They're not super big deals, but figured it's worth asking about anyways incase it's some bug in the driver. Case 1: Copy/Select in Kitty (terminal) I use the terminal, Kitty, fairly often on multiple machines.  Machines with graphical acceleration (which is what Kitty utilizes).  I noticed that with graphic acceleration turned off, the terminal allows functionality pretty much exactly as it is on my mac.  Copy text, paste, etc.  On my linux box (physical), Kitty also operates as expected.  The configuration is no different between the two executions (graphical acceleration and non).  But, at least on the M2, selecting text doesn't work properly.  In the background, it's selecting the text, but there's no visual indication of it. The only thing different is graphics acceleration - same conflig/etc. and the behavior is different. Case 2: Jetbrains Tools and window "refresh" Another weird issue is some of the Jetbrains tools.  What can happen while running it is that the entire IDE will turn black, and segments of the GUI will show back to normal.  Usually when highlighting or trying to interact with the section turned black.  So far, only PHPStorm has had this issue. I noticed too that refresh of certain elements can be incredibly slow, much more than the same app on OSX proper - but that may be a Jetbrains thing more than anything else. Specs/Setup: - M2 with 64Gb of RAM - Ubuntu has 32Gb of RAM allocated to it, and 2Gb of virtual memory for graphics. I haven't found any error showing up in dmesg, nor anything online about either of these issues so far.
@Technogeezer wrote: 5.15 kernels don't meet prerequisites for 3D acceleration for Fusion on arm64. You need a 5.19 kernel (containing an updated vmwgfx driver that supports 3D on arm64) and Mesa... See more...
@Technogeezer wrote: 5.15 kernels don't meet prerequisites for 3D acceleration for Fusion on arm64. You need a 5.19 kernel (containing an updated vmwgfx driver that supports 3D on arm64) and Mesa 22.1.1 or later. You might want to try the HWE kernel in that Jammy VM. The HWE kernel package linux-image-genreic-hwe-22.10 contains a 5.19 series kernel. You also need to ensure that the Mesa 3D version is 22.1.1 or later. 22.10 and 23.04 both contain these pre-requisites. You may have better luck with them. I've run the glxgears and glmark2 demos on those releases and they both get the acceleration for 3D.  Thanks for taking the time to reply and put this here as well.  I see this in the guide as well (14.5 - https://communities.vmware.com/t5/VMware-Fusion-Documents/The-Unofficial-Fusion-13-for-Apple-Silicon-Companion-Guide/ta-p/2939907?attachment-id=113215 for those that need it). I applied that change and it works great.  I may also change the network as well, since I need to setup a way to selectively change the name server on some conditions via script, and it'll likely be easier (using sed) than systemctl or using netplan apply and moving files around. Thanks again.
@Technogeezer wrote: @TheDarkTrumpet wrote: I haven't tested it fully, but as I was trying to look up an error with OpenGL acceleration with an Ubuntu guest (on an M2 with 64Gb of RAM), I get... See more...
@Technogeezer wrote: @TheDarkTrumpet wrote: I haven't tested it fully, but as I was trying to look up an error with OpenGL acceleration with an Ubuntu guest (on an M2 with 64Gb of RAM), I get the following error, in dmesg (viewable through ssh, the GUI doesn't work at all): [drm:vmw_cotable_resize [vmwgfx]] *ERROR* Failed waiting for cotable unbind. I tried increasing the video ram allocated (4Gb) with no real effect. I've verified opengl-related libraries are installed: dpkg -s libglu1-mesa Package: libglu1-mesa Status: install ok installed Priority: optional Section: libs Installed-Size: 314 Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Architecture: arm64 Multi-Arch: same Source: libglu Version: 9.0.2-1 Replaces: libglu1 Provides: libglu1 Depends: libc6 (>= 2.17), libgcc-s1 (>= 3.3.1), libopengl0, libstdc++6 (>= 5) Conflicts: libglu1, mesag3 (<< 5.0.0-1), xlibmesa3 What version of Ubuntu and what kernel version? Kernel is: Linux ubuntu-miami 5.15.0-76-generic Version is: Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy   One thing mentioned was the unofficial guide, I forgot about that.  I installed everything myself without really any guide, so still using systemd for networking (which works fine for me), but the video information may be there - so will check it out just to be sure I didn't miss something there.
Personally, I wouldn't try any of the graphical live-cds when installing Ubuntu.   I start with Ubuntu server, install there, then install `sudo apt install ubuntu-desktop`, with open-vm-tools/desk... See more...
Personally, I wouldn't try any of the graphical live-cds when installing Ubuntu.   I start with Ubuntu server, install there, then install `sudo apt install ubuntu-desktop`, with open-vm-tools/desktop, and it's working pretty well. Well, minus graphical acceleration, which I responded below on.
I haven't tested it fully, but as I was trying to look up an error with OpenGL acceleration with an Ubuntu guest (on an M2 with 64Gb of RAM), I get the following error, in dmesg (viewable through ssh... See more...
I haven't tested it fully, but as I was trying to look up an error with OpenGL acceleration with an Ubuntu guest (on an M2 with 64Gb of RAM), I get the following error, in dmesg (viewable through ssh, the GUI doesn't work at all): [drm:vmw_cotable_resize [vmwgfx]] *ERROR* Failed waiting for cotable unbind. I tried increasing the video ram allocated (4Gb) with no real effect. I've verified opengl-related libraries are installed: dpkg -s libglu1-mesa Package: libglu1-mesa Status: install ok installed Priority: optional Section: libs Installed-Size: 314 Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Architecture: arm64 Multi-Arch: same Source: libglu Version: 9.0.2-1 Replaces: libglu1 Provides: libglu1 Depends: libc6 (>= 2.17), libgcc-s1 (>= 3.3.1), libopengl0, libstdc++6 (>= 5) Conflicts: libglu1, mesag3 (<< 5.0.0-1), xlibmesa3   On a side note - I want to thank you for the tech preview.  I was worried with the lack of updates to the core product that it was dying on a vine, so to speak, and wasn't going to get further updates.  But the tech preview proved me wrong.