raymac46 Posted November 23, 2024 Posted November 23, 2024 (edited) I'm starting a new thread as I have now installed Manjaro on VirtualBox on Windows. As Josh pointed out in the EOS thread, Manjaro is quite a different beast from Arch and its derivatives. It does share the AUR and similar package management but has its own repos and does not update as often. The idea is to see if Manjaro causes issues in VBox. If it does, I think we can rule out the distro as a source of corruption. HJ has had a stable Manjaro install for years but he is using a Linux-based VMM, Not VBox. VBox has more layers of abstraction and hardware simulation than a "normal" VMM does - hence more things to go wrong. Preliminary observations: Very fast download on a wired system, fast install in VBox. Initial boot on virtual disk did not give a GUI - had to change to VBoxSVGA video to get it to show up. Manjaro Xfce has quite an Industrial Strength appearance - EOS is much more attractive. Manjaro uses pamac to update and access AUR - can be a GUI or terminal app. Both seem to work OK. No problems so far but it's early days. Edited November 23, 2024 by raymac46 Quote
abarbarian Posted November 24, 2024 Posted November 24, 2024 Neat adventure your undertaking with the VBox it is certainly much better than endless sudoku puzzles. You will have to keep your guard up now that you have stepped into the dark side. 1 Quote
raymac46 Posted December 1, 2024 Author Posted December 1, 2024 Just updated 338 packages in Manjaro (1.3 GB.) Rebooted and everything looks OK. System: Kernel: 6.11.10-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1 Desktop: Xfce v: 4.18.1 Distro: Manjaro base: Arch Linux Machine: Type: Virtualbox System: innotek GmbH product: VirtualBox v: 1.2 serial: <superuser required> Mobo: Oracle model: VirtualBox v: 1.2 serial: <superuser required> BIOS: innotek GmbH v: VirtualBox date: 12/01/2006 CPU: Info: dual core model: 11th Gen Intel Core i7-11700 bits: 64 type: MCP arch: Rocket Lake rev: 1 cache: L1: 160 KiB L2: 1024 KiB L3: 32 MiB Speed (MHz): avg: 2496 min/max: N/A cores: 1: 2496 2: 2496 bogomips: 9986 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter vendor: VMware driver: vboxvideo v: kernel bus-ID: 00:02.0 Display: x11 server: X.org v: 1.21.1.14 driver: X: loaded: modesetting gpu: vboxvideo resolution: 1920x974~60Hz API: EGL v: 1.5 drivers: swrast platforms: active: x11,surfaceless,device inactive: gbm,wayland API: OpenGL v: 4.5 vendor: mesa v: 24.2.7-arch1.1 glx-v: 1.4 direct-render: yes renderer: llvmpipe (LLVM 18.1.8 256 bits) Audio: Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel bus-ID: 00:05.0 API: ALSA v: k6.11.10-2-MANJARO status: kernel-api Server-1: JACK v: 1.9.22 status: off Server-2: PipeWire v: 1.2.7 status: active Network: Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 bus-ID: 00:03.0 IF: enp0s3 state: up speed: 1000 Mbps duplex: full mac: <filter> Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus v: N/A port: N/A bus-ID: 00:07.0 Drives: Local Storage: total: 20.15 GiB used: 11.16 GiB (55.4%) ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 20.15 GiB Partition: ID-1: / size: 19.66 GiB used: 11.16 GiB (56.8%) fs: ext4 dev: /dev/sda1 Swap: Alert: No swap data was found. Sensors: Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors. Info: Memory: total: 6 GiB available: 5.77 GiB used: 1.46 GiB (25.3%) Processes: 197 Uptime: 2m Init: systemd Packages: 1087 Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.37 inxi: 3.3.36 [ray@ray-virtualbox ~]$ Quote
Hedon James Posted December 1, 2024 Posted December 1, 2024 4 hours ago, raymac46 said: Just updated 338 packages in Manjaro (1.3 GB.) Rebooted and everything looks OK. System: Kernel: 6.11.10-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1 Desktop: Xfce v: 4.18.1 Distro: Manjaro base: Arch Linux Machine: Type: Virtualbox System: innotek GmbH product: VirtualBox v: 1.2 serial: <superuser required> Mobo: Oracle model: VirtualBox v: 1.2 serial: <superuser required> BIOS: innotek GmbH v: VirtualBox date: 12/01/2006 CPU: Info: dual core model: 11th Gen Intel Core i7-11700 bits: 64 type: MCP arch: Rocket Lake rev: 1 cache: L1: 160 KiB L2: 1024 KiB L3: 32 MiB Speed (MHz): avg: 2496 min/max: N/A cores: 1: 2496 2: 2496 bogomips: 9986 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter vendor: VMware driver: vboxvideo v: kernel bus-ID: 00:02.0 Display: x11 server: X.org v: 1.21.1.14 driver: X: loaded: modesetting gpu: vboxvideo resolution: 1920x974~60Hz API: EGL v: 1.5 drivers: swrast platforms: active: x11,surfaceless,device inactive: gbm,wayland API: OpenGL v: 4.5 vendor: mesa v: 24.2.7-arch1.1 glx-v: 1.4 direct-render: yes renderer: llvmpipe (LLVM 18.1.8 256 bits) Audio: Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel bus-ID: 00:05.0 API: ALSA v: k6.11.10-2-MANJARO status: kernel-api Server-1: JACK v: 1.9.22 status: off Server-2: PipeWire v: 1.2.7 status: active Network: Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 bus-ID: 00:03.0 IF: enp0s3 state: up speed: 1000 Mbps duplex: full mac: <filter> Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus v: N/A port: N/A bus-ID: 00:07.0 Drives: Local Storage: total: 20.15 GiB used: 11.16 GiB (55.4%) ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 20.15 GiB Partition: ID-1: / size: 19.66 GiB used: 11.16 GiB (56.8%) fs: ext4 dev: /dev/sda1 Swap: Alert: No swap data was found. Sensors: Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors. Info: Memory: total: 6 GiB available: 5.77 GiB used: 1.46 GiB (25.3%) Processes: 197 Uptime: 2m Init: systemd Packages: 1087 Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.37 inxi: 3.3.36 [ray@ray-virtualbox ~]$ Interesting that your Manjaro VM looks like it has the same graphics driver as Endeavour, and possibly the same kernel? Quote
raymac46 Posted December 10, 2024 Author Posted December 10, 2024 Another update on Manjaro without issues. I used Pamac to do the update. [ray@ray-virtualbox ~]$ inxi -Fxz System: Kernel: 6.11.10-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1 Desktop: Xfce v: 4.18.1 Distro: Manjaro base: Arch Linux Machine: Type: Virtualbox System: innotek GmbH product: VirtualBox v: 1.2 serial: <superuser required> Mobo: Oracle model: VirtualBox v: 1.2 serial: <superuser required> BIOS: innotek GmbH v: VirtualBox date: 12/01/2006 CPU: Info: dual core model: 11th Gen Intel Core i7-11700 bits: 64 type: MCP arch: Rocket Lake rev: 1 cache: L1: 160 KiB L2: 1024 KiB L3: 32 MiB Speed (MHz): avg: 2496 min/max: N/A cores: 1: 2496 2: 2496 bogomips: 9988 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter vendor: VMware driver: vboxvideo v: kernel bus-ID: 00:02.0 Display: x11 server: X.org v: 1.21.1.14 driver: X: loaded: modesetting gpu: vboxvideo resolution: 1920x974~60Hz API: EGL v: 1.5 drivers: swrast platforms: active: x11,surfaceless,device inactive: gbm,wayland API: OpenGL v: 4.5 vendor: mesa v: 24.2.8-arch1.1 glx-v: 1.4 direct-render: yes renderer: llvmpipe (LLVM 18.1.8 256 bits) Audio: Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel bus-ID: 00:05.0 API: ALSA v: k6.11.10-2-MANJARO status: kernel-api Server-1: JACK v: 1.9.22 status: off Server-2: PipeWire v: 1.2.7 status: active Network: Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: kernel port: d020 bus-ID: 00:03.0 IF: enp0s3 state: up speed: 1000 Mbps duplex: full mac: <filter> Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus v: N/A port: N/A bus-ID: 00:07.0 Drives: Local Storage: total: 20.15 GiB used: 12.04 GiB (59.8%) ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 20.15 GiB Partition: ID-1: / size: 19.66 GiB used: 12.04 GiB (61.3%) fs: ext4 dev: /dev/sda1 Swap: Alert: No swap data was found. Sensors: Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors. Info: Memory: total: 6 GiB available: 5.77 GiB used: 1.48 GiB (25.6%) Processes: 183 Uptime: 6m Init: systemd Packages: 1087 Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.37 inxi: 3.3.36 [ray@ray-virtualbox ~]$ Quote
raymac46 Posted January 2 Author Posted January 2 Now that I feel confident that I can keep Endeavour OS stable in VBox I am going to scrap Manjaro. I need only one Linux VM in Windows 11. Quote
Hedon James Posted January 2 Posted January 2 31 minutes ago, raymac46 said: Now that I feel confident that I can keep Endeavour OS stable in VBox I am going to scrap Manjaro. I need only one Linux VM in Windows 11. The one thing that I actually LIKE about Manjaro is the 2-week lag between Arch repos and Manjaro repos. I can understand why someone who wants a cutting-edge distro would be turned off by that. But for me, that is an extra layer of testing & fixes before it's released to Manjaro users. I don't need a 24 or 48-hour turnaround for a fix to a package. I'm absolutely willing to wait 2+/- weeks for the Arch users to get it sorted out and for Manjaro devs to ensure compatibility. JMO... OTOH....that IS an additional layer "away from" Arch. Endeavour reminds me a little of Manjaro, but a few steps closer and drawing from the (mostly) same repos. Quote
raymac46 Posted January 2 Author Posted January 2 It does seem that Manjaro is a tad more stable in VMs but if I want stability at all costs, I'll go with some form of Debian. Quote
Hedon James Posted January 3 Posted January 3 14 hours ago, raymac46 said: It does seem that Manjaro is a tad more stable in VMs but if I want stability at all costs, I'll go with some form of Debian. That's what I did on bare metal. Debian for the win. JMO. I was very interested in rolling release so I wouldn't have to reinstall OS on my small network every 2-5 years. But the constant flow of update packages from rolling release (Arch, Debian Testing, Siduction, etc...) is just too much, and rolling out across a small network of non-homogeneous hardware is just daring the gods with my hubris. If all I had was my own computer to administer, rolling releases would be VERY appealing to me. And that extra 2 week delay between Arch repos and Manjaro repos as actually an attractive feature for me, despite Manjaro's other quirks. Side note....if quirks become "normal" and expected behavior, do they cease to become quirks? LOL! Quote
raymac46 Posted January 4 Author Posted January 4 Generally two types of Linux appeal to me. Neither is really mission critical. I want a stable, easy to use variant for family to operate - either on an old piece of hardware at home, or on something I have here when they visit. For me, that's Linux Mint. I also want something that's fun and engages my mind - something to keep me interested in learning. That can be a bit more unstable as long as I am not constantly borking it. In this situation Arch or EOS is perfect. I also like Debian testing. This fun distro is what I would want to virtualize on Windows. Nobody else will use it but me. This problem of EOS in a VM was a perfect case of situation 2 - fun, challenging, no worry about destroying anything critical. Quote
Hedon James Posted January 4 Posted January 4 12 hours ago, raymac46 said: Generally two types of Linux appeal to me. Neither is really mission critical. I want a stable, easy to use variant for family to operate - either on an old piece of hardware at home, or on something I have here when they visit. For me, that's Linux Mint. I also want something that's fun and engages my mind - something to keep me interested in learning. That can be a bit more unstable as long as I am not constantly borking it. In this situation Arch or EOS is perfect. I also like Debian testing. This fun distro is what I would want to virtualize on Windows. Nobody else will use it but me. This problem of EOS in a VM was a perfect case of situation 2 - fun, challenging, no worry about destroying anything critical. You just described the IDEAL use of a VM, at least the way I see it. A way to learn about an OS with no fear of messing up a mission critical system. And if you do bork something beyond the state of repair, nuke it, reinstall and try again. In probably 5-10 minutes or less?! It's a learning lab/test bed! Quote
raymac46 Posted January 4 Author Posted January 4 In your case, you have to run mission-critical applications in Windows on a VM in Linux. With such high stakes, I can see how stability must be top of mind for you. Quote
Hedon James Posted January 5 Posted January 5 10 hours ago, raymac46 said: In your case, you have to run mission-critical applications in Windows on a VM in Linux. With such high stakes, I can see how stability must be top of mind for you. Right on...bullseye. Not a fan of bleeding edge, for that reason. I prefer leading edge, but can't sacrifice reliable stability for it. I think Debian is the right fit for me, as my main driver. I get my bleeding & leading edge "fixes" in my VM choices. Quote
raymac46 Posted January 5 Author Posted January 5 I guess my only mission-critical need is for a Linux distro that won't crash and frustrate my wife and family plus is familiar enough that my grandkids can hop on and run without any hand-holding. Hence Linux Mint. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.