LinuxQuestions.org - VirtualBox for Slackware Users

Page 10 of 12

Show 50 post(s) from this thread on one page

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - VirtualBox for Slackware Users (https://www.linuxquestions.org/questions/slackware-14/virtualbox-for-slackware-users-4175689027/)

FTIO	12-09-2022 10:29 AM

I tried to use the run file of 7.0.4 today, and installed it as root, but as it was installing I got several lines of this:

Code:

./routines.sh: line 249: systemctl: command not found

in the dialogue, yet at the end it said it was installed.

Then I tried to run it as user doing:

Code:

/opt/VirtualBox/VirtualBox

VBox starts, but shows a small window telling me 'can't enumerate USB devices'. I x out that small window and click on the appliance to use it blinks on for a split second and then gives a small window with 'AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED)'. I checked my BIOS, and it *IS* enabled.

I then uninstall virtualbox and even during the uninstall I get one line telling me

Code:

./routines.sh: line 249: systemctl: command not found

but uninstalls nonetheless.

Any ideas what the heck I'm doing wrong?

fourtysixandtwo

12-10-2022 02:11 AM

Quote:

Originally Posted by FTIO (Post 6396883)

<snip>
Then I tried to run it as user doing:

Code:

/opt/VirtualBox/VirtualBox

Code:

./routines.sh: line 249: systemctl: command not found

but uninstalls nonetheless.

Any ideas what the heck I'm doing wrong?

You can ignore the the systemctl errors, and just use "virtualbox" to launch, which is a link to /opt/VirtualBox/VirtualBox.

Is this a first time install or an upgrade? If the former, there are a few setup steps required. What groups does your user belong to? Does it launch as root?

FTIO	12-10-2022 04:19 AM

Quote:

Originally Posted by fourtysixandtwo (Post 6397008)

Okay, I tried just 'virtualbox', that worked, thank you for that, but it still does the same thing exactly.

This is a first time install on this up-to-date 15.0 x64 system (updated every few days with slackpkg). I'm using the .run version of virtualbox, in case that makes any difference, as it used to work pretty well in my 14.2 x64 system.

Since KDE doesn't have the kuser thing anymore, I've lost my way in figuring out groups and such and don't know how to do that (sorry, but my memory just isn't what it used to be and trying to remember commands is too frustrating, unfortunately).

It starts the same as with user when trying it as root, with a bunch of lines of 'Qt WARNING: Numeric mode unsupported in the posix collation implementation' and 'Qt WARNING: QSortFilterProxyModel: index from wrong model passed to mapToSource', but when I try to start the appliance, it does exactly the same thing as with user - a window for a second, then the same thing about the AMD-V thing.

**edit: After looking things up on the internet, I found out how to add myself to the vboxusers group. After that, I did an

Code:

id

command and it shows me '999(vboxusers)'. I then tried to start virtualbox again (after logging out and back in) and still get the same exact problem with the AMD-V thing.

FTIO	12-10-2022 08:33 AM

Bleh...I went back into the BIOS in the hopes that it was something simple, and found that my BIOS has a search function. I found the SRV thing that I couldn't find spending an hour in there looking for such things.

Anyway, I 'enebled' it, and viola!...VBox now works like a charm.

Sorry for all the garbage added to this thread, and thanks to fourtysixandtwo for trying to help.

Daedra

12-10-2022 10:55 AM

Is anyone else finding Virtualbox 7.0 not ready for prime time? It is understandable since it is a new major version so there is bound to be bugs that need to be worked out. I almost immediately dropped back down to 6.1.40 after trying it, but I thought I would see how you guys are doing with it?

TSquaredF

12-10-2022 01:10 PM

Quote:

Originally Posted by Daedra (Post 6397073)

My Win10 installation will lock up when booting on any version of Virtualbox 7.0. My Slackware-15 installation boots OK. I, also, am back to 6.1.40.

rizitis

12-10-2022 01:17 PM

I m using VBox 7.0.4 last 2 days for Gnome building. I have on my VBox one installation of slackware 15 stable and 2 installation of slack current everything works fine so far. 2 days about 30 hours of hard use...

FTIO	12-10-2022 03:23 PM

Once I figured out my problem (my own fault, not VBox), I had it up for several hours earlier today playing an online RP game I've been on since 1997 (It started out as Gemstone III on AOL (UGH!), and is now Gemstone IV *not* on AOL). It didn't give one hiccup or burp or any kind of problems for me. Oh, using 7.0.4-154605.

fourtysixandtwo

12-10-2022 06:19 PM

Quote:

Originally Posted by FTIO (Post 6397050)

Glad you got it figured out.

Quote:

Originally Posted by Daedra (Post 6397073)

Other than the lilo bitmap issue I've had no issues with any of my 15.0 VMs. The -current one has had a couple of minor hiccups during shutdown and boot where a reset was necessary. But no adverse affects otherwise. (fsck was clean)

chrisretusn

12-11-2022 04:05 AM

Quote:

Originally Posted by Daedra (Post 6397073)

Working fine for me. Machines installed:
Boot-USB-sdc/
Slackware64/
Slackware64-racer/
Windows10/

cwizardone

12-17-2022 04:25 AM

A new test build-6.1.41-154912, with extension pack-6.1.41-154909,
and
a new development snapshot-7.0.5-154910, with extension pack-7.0.5-154905,
have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

glorsplitz

12-22-2022 09:08 PM

1 Attachment(s)

I've glanced at a couple pages here in this thread didn't see any comments regarding the sidebar/toolbox thingy when I open a vm.

I don't care for it, can't find anything in preferences, not sure what's it's called.

Anyone? Thanks

cwizardone

01-09-2023 12:03 PM

A new test build-6.1.41-155125, with a companion extension pack,
and
a new development snapshot-7.0.5-155126, with extension pack-7.0.5-155124,
have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

cwizardone

01-17-2023 02:18 PM

Quote:

New January 17th, 2023
VirtualBox 7.0.6 released!
Oracle today released a 7.0 maintenance release which improves stability and fixes regressions. See the Changelog for details.

The change log, https://www.virtualbox.org/wiki/Changelog-7.0#v6

Quote:

New January 17th, 2023
VirtualBox 6.1.42 released!
Oracle today released a 6.1 maintenance release which improves stability and fixes regressions. See the Changelog for details.

The change log, https://www.virtualbox.org/wiki/Changelog-6.1#v42

chrisretusn

01-19-2023 04:32 AM

Quote:

Originally Posted by glorsplitz (Post 6399734)

Guess you missed this post

As the post suggest you can switch to text interface in lilo. You will need to comment out the bitmap and bmp lines in lilo.conf

Code:

# ------ menu -------

# Boot BMP Image.

# Bitmap in BMP format: 640x480x8

#bitmap=/boot/124827-slack.bmp

# Menu colors (foreground, background, shadow, highlighted

# foreground, highlighted background, highlighted shadow):

#bmp-colors=255,0,255,0,255,0

# Location of the option table: location x, location y, number of

# columns, lines per column (max 15), "spill" (this is how many

# entries must be in the first column before the next begins to

# be used.  We don't specify it here, as there's just one column.

#bmp-table=60,6,1,16

# Timer location x, timer location y, foreground color,

# background color, shadow color.

#bmp-timer=65,27,0,255



# Standard menu.

# Or, you can comment out the bitmap menu above and 

# use a boot message with the standard menu:

message = /boot/boot_message.txt



# Basic text menu.

install = text

Another option is to just comment out the bmp entries, this will tell lilo to use the default menu interface (my choice).

Code:

# ------ menu -------

# Boot BMP Image.

# Bitmap in BMP format: 640x480x8

#bitmap=/boot/124827-slack.bmp

# Menu colors (foreground, background, shadow, highlighted

# foreground, highlighted background, highlighted shadow):

#bmp-colors=255,0,255,0,255,0

# Location of the option table: location x, location y, number of

# columns, lines per column (max 15), "spill" (this is how many

# entries must be in the first column before the next begins to

# be used.  We don't specify it here, as there's just one column.

#bmp-table=60,6,1,16

# Timer location x, timer location y, foreground color,

# background color, shadow color.

#bmp-timer=65,27,0,255

business_kid

01-19-2023 04:58 AM

Code:

Oracle today released a 7.0 maintenance release which improves stability and fixes regressions. See the Changelog for details.

I noticed this phrase coming up a few times. It reads like M$ speak

"Improves Stability" = we don't think this one crashes quite as much as the last one.
"Fixes regressions" Actually the last release was worse than the one before, but we hope we've fixed that.

They've gone up a major version number: 6.1.42 -->7.0.6 which should imply a break in compatibility or at least feature additions. :confused: :scratch:

drumz

01-19-2023 07:53 AM

Quote:

Originally Posted by business_kid (Post 6405397)

They've gone up a major version number: 6.1.42 -->7.0.6 which should imply a break in compatibility or at least feature additions. :confused: :scratch:

7.0 was released October 10th, 2022 (https://www.virtualbox.org/). They've continued to maintain the 6.1.y branch since then.

cwizardone

01-20-2023 03:10 AM

A new test build-6.1.43-155278, with extension pack-6.1.43-155246,
and
a new development snapshot-7.0.7-155289, with extension pack-7.0.7-155247,
have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

Daedra

01-20-2023 08:44 AM

6.1.42 running like a champ here on 15.0. I tried 7.0 on its initial release and found it not ready for prime time IMO. I'm keeping Virtualbox around for my Windows VM's, but finally made the switch to Qemu/Kvm via Virt-Manager for all my Linux/BSD VM's and I am so glad I did. It is superior in so many ways its absurd, but like all virtualization software there is not perfect solution and I still like Virtualbox for desktop Windows VM's.

cwizardone

02-02-2023 08:03 PM

A new test build-6.1.43-155609, with extension pack-6.1.43-155587,
and
a new development snapshot-7.0.7-155584, with extension pack-7.0.7-155601,
have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

cwizardone

02-03-2023 07:38 PM

A new development snapshot-7.0.97-155730, and extension pack-7.0.97-155728,
have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

cwizardone

02-23-2023 09:04 PM

A new development snapshot-7.0.97-155973, along with extension pack-7.0.97-155968,
have been posted at, https://www.virtualbox.org/wiki/Testbuilds

cwizardone

03-01-2023 07:53 PM

A new development snapshot-7.0.97-156054, along with extension pack-7.0.97-156053,
have been posted at, https://www.virtualbox.org/wiki/Testbuilds

astrogeek

03-05-2023 06:27 PM

Hello fellow Slackers and VBox users!

I have been troubleshooting recent problems running Firefox in a VBox VM.

VirtualBox is 6.1.32 running on a Slackware64-15.0 host.
The VM guest is also Slackware64-15.0.
The host is i7 8 core, 32GB RAM, Intel graphics.

Both the host and the VM had been updated via slackpkg Dec 21 2022 and have been trouble free since initial installation sometime after mid 2021, and since the December updates. Both were still running kernel 5.15.19.

I updated everything to the Slackware mirrors as of February 28, and also upgraded to kernel 5.15.94 at the same time, both host and guest. My trouble began shortly after this.

Since that upgrade Firefox in the guest has been unstable to the point of being unusable. I initially downgraded to Firefox 102.7.0 and that ran most of a full day, so I thought that was the problem, but then it folded up too. I am now back to 102.8.0 and still experiencing regular crashes. This VM is used almost exclusively for web browsing and has no notable software installed beyond the full Slackware installation.

From the most recent crash...

Code:

$ firefox

ATTENTION: default value of option mesa_glthread overridden by environment.

ATTENTION: default value of option mesa_glthread overridden by environment.

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D (t=6.71945) [GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D

Missing chrome or resource URL: resource://gre/modules/UpdateListener.jsm

Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs

Exiting due to channel error.

Exiting due to channel error.

Exiting due to channel error.

Exiting due to channel error.

Exiting due to channel error.

Exiting due to channel error.

Exiting due to channel error.

Segmentation fault

I have verified and even forced reinstall of the VB extension pack with the new kernel.

I have disabled hardware acceleration in Firefox and disabled GLX in Xorg, all without much effect (some modes seem to crash less frequently, but not sure if that means anything at all - it stil crashes). And I have experienced a similar crash in another VM on the same host, also updated at the same time to the same configuration, but without internet exposure.

I am now looking for non-Firefox causes.

I have used VBox for quite some time, but beyond setting it up I have not had to troubleshoot much with it and don't really know my way around it in any depth, but the manual is at hand.

So, two questions for those more familiar with these things:

1. I am attempting to upgrade to VBox 6.1.42, but after several downloads the checksum sum differs from that on the Oracle website... are Oracle known for neglecting to keep the builds and the sums in sync?

2. Any suggestions for how to most quickly decide whether it may be a VBox problem, or a pproblem with the OS update? I would have simply reinstalled by now except that I see the same problem on a second VM and think it worth getting to the actual cause.

Thanks for any and all suggestions!

After posting I realized this may not be the right place - if so please ask that it be moved to its own thread.

glorsplitz

03-05-2023 07:04 PM

I know this doesn't help but seems to be working here with the following, using ruario/latest-firefox.sh.

HOST:PRETTY_NAME="Slackware 15.0 x86_64" all up to date

using script from oracle
VirtualBox Graphical User Interface
Version 7.0.2 r154219 (Qt5.15.2)
Copyright © 2022 Oracle and/or its affiliates.

GUEST:PRETTY_NAME="Slackware 15.0 x86_64" all up to date
firefox 110.0.1 (64-bit) is up and running

fourtysixandtwo

03-06-2023 11:31 AM

Quote:

Originally Posted by astrogeek (Post 6415536)

Hello fellow Slackers and VBox users!
I am now looking for non-Firefox causes.

I have used VBox for quite some time, but beyond setting it up I have not had to troubleshoot much with it and don't really know my way around it in any depth, but the manual is at hand.

So, two questions for those more familiar with these things:

1. I am attempting to upgrade to VBox 6.1.42, but after several downloads the checksum sum differs from that on the Oracle website... are Oracle known for neglecting to keep the builds and the sums in sync?

2. Any suggestions for how to most quickly decide whether it may be a VBox problem, or a pproblem with the OS update? I would have simply reinstalled by now except that I see the same problem on a second VM and think it worth getting to the actual cause.

Thanks for any and all suggestions!

After posting I realized this may not be the right place - if so please ask that it be moved to its own thread.

Just tried downloading it and got the correct md5sum.

Code:

$ wget https://download.virtualbox.org/virtualbox/6.1.42/VirtualBox-6.1.42-155177-Linux_amd64.run



$ md5sum VirtualBox-6.1.42-155177-Linux_amd64.run 

ae5a18a205daedfd2dc65f36e0e4101b  VirtualBox-6.1.42-155177-Linux_amd64.run

astrogeek

03-07-2023 12:00 AM

Not sure what the checksum difference resulted from, but later yesterday I downloaded and verified Virtualbox-6.1.42 (with wget as fortysixandtwo).

I uninstalled the 6.1.32 then installed 6.1.42, then installed the extpack with VBoxManage extpack install --replace, reboot host and all my VMs are fine. Mounted guest additions ISO and updated them after booting the VM.

At the point I reinstalled VBox I had reverted one guest to the 5.15.19 kernel and another with 5.15.94, and both appeared to work well. I watched a few videos and scrolled around like a crazy person (scroll gestures had been noted to trigger the crash), and saw no crashes for the remainder of the night. Notably, scrolling and video controls were smoother than they had been which I take as a good sign also.

I have had both open with video playing continuously when not otherwise in use through the day, and have seen no more crashes, now more than 24 hours. I do still see a few messages when started from a terminal, but no segfaults.

Code:

$ firefox

ATTENTION: default value of option mesa_glthread overridden by environment.

ATTENTION: default value of option mesa_glthread overridden by environment.

Missing chrome or resource URL: resource://gre/modules/UpdateListener.jsm

Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D (t=8.81224) [GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D

One additional quirk, but for now I can live with it. The most important VM was the one I had reverted to 5.15.19 kernel, and was using about 80% of root partition, so I enlarged the virtual disk and restored everything to 64-15.0 current state with 5.15.94 kernel and 102.8.0 Firefox... after which video from some, but not all sources now plays just slightly slower than normal. I had experienced slow sound during playback recently not associated with any change on my end so I attributed it to changes on the source... annoying but I'll sort that out later, or live with it.

So, for the moment, the crashes appear to have been related in some way to the 6.1.32 VBox in combination with my hardware and configs, and were fixed by update to 6.1.42.

Thanks for the replies above!

@glorsplitz: I am tempted to continue to the 7.0.x VBox, but in reading through the thread I see a few posts by early adopters as late as January saying they had reverted to 6.1.4x due to problems encountered... so another day! I'll follow this thread more closely now!

cwizardone

03-14-2023 09:39 AM

A new test build-6.1.43-156228, with matching extension pack,
and
a new development snapshot-7.0.7-155262, with matching extension pack,
have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

cwizardone

03-17-2023 09:15 AM

They have added a category, so it is now:
"Latest 6.1.x test builds," "Latest 7.0.x test builds" and "Development snapshots."
As of the moment we have,
Latest 6.1.x test build-6.1.43-156228,
and
Latest 7.0.x test build-7.0.7-156262,
and
Development snapshot-7.0.97-156271.

All available at, https://www.virtualbox.org/wiki/Testbuilds

cwizardone

03-29-2023 10:28 AM

A new test build-6.1.43-156565, and a matching extension pack have been posted at,
https://www.virtualbox.org/wiki/Testbuilds

cwizardone

04-10-2023 09:18 AM

A new test build and a new development snapshot with matching extension packs, have been posted at, https://www.virtualbox.org/wiki/Testbuilds.

test build-7.0.7-156678.

development snapshot-7.0.97-156683.

cwizardone

04-18-2023 05:51 PM

Quote:

New April 18th, 2023
VirtualBox 7.0.8 released!
Oracle today released a 7.0 maintenance release which improves stability and fixes regressions. See the Changelog for details.

https://www.virtualbox.org/wiki/Changelog-7.0#v8

Quote:

New April 18th, 2023
VirtualBox 6.1.44 released!
Oracle today released a 6.1 maintenance release which improves stability and fixes regressions. See the Changelog for details.

https://www.virtualbox.org/wiki/Changelog-6.1#v44

cwizardone

04-21-2023 12:48 PM

New test builds and a new development snapshot have been made available for testing.

Latest 6.1.x test build-6.1.45-156947,
and
Latest 7.0.x test build-7.0.9-156993,
and
Development snapshot-7.0.97-156983.

All available at, https://www.virtualbox.org/wiki/Testbuilds

cwizardone

05-02-2023 08:20 AM

One new test build and a new development snapshot have been made available for testing.

Test build-7.0.9-157071,
and
Development snapshot-7.0.97-157070,

are available at, https://www.virtualbox.org/wiki/Testbuilds

cwizardone

05-12-2023 09:00 AM

A new test build-7.0.9-157345, is available at,

https://www.virtualbox.org/wiki/Testbuilds

cwizardone

05-22-2023 11:15 AM

New test build-7.0.9-157502, and a companion extension pack are available at,

https://www.virtualbox.org/wiki/Testbuilds

M440	05-31-2023 10:32 AM

If i want to try newer virtualbox (7.0.8) i just build it using slackbuilds?

https://slackbuilds.org/repository/1...em/virtualbox/
https://slackbuilds.org/repository/1...ualbox-kernel/

I've been using 6.1.40 from SBO so far.

cwizardone

05-31-2023 12:21 PM

New test builds and a new development snapshot have been made available for testing.

Latest 6.1.x test build-6.1.45-157688,
and
Latest 7.0.x test build-7.0.9-157689,
and
Development snapshot-7.0.97-157682.

All available at, https://www.virtualbox.org/wiki/Testbuilds

M440	06-01-2023 08:19 AM

Quote:

Originally Posted by M440 (Post 6433907)

FYI i wanted to try virtualbox 7.0.8 on kernel 6.3.5, slackware-current (because 6.1.40 was not compiling a kernel module on 6.3.5)

i tried to build from sources, according to instructions below, but it was failing - i was able to compile and install kernel module tho.

Code:

https://www.virtualbox.org/wiki/Linux%20build%20instructions

so than i installed binaries from link below and it updated and works fine (except display 3D acceleration it seams).

I thought I lost virtualbox for kernel 6.1.29, but no - it compiled a kernel module at boot time and works with 7.0.8

Code:

https://download.virtualbox.org/virtualbox/7.0.8/VirtualBox-7.0.8-156879-Linux_amd64.run

cwizardone

06-13-2023 06:28 PM

New test builds and a new development snapshot have been made available for testing.

Latest 6.1.x test build-6.1.45-157777,
and
Latest 7.0.x test build-7.0.9-157775,
and
Development snapshot-7.0.97-157803.

All available at, https://www.virtualbox.org/wiki/Testbuilds

cwizardone

07-05-2023 11:02 AM

Two new test builds and a new development snapshot are ready for testing.
The latest 6.1.x test build-6.1.45-158079,
and the latest 7.0.x test build-7.0.9-158070,
and
development snapshot-7.0.97-158092,
are all available at, https://www.virtualbox.org/wiki/Testbuilds

cwizardone

07-13-2023 06:43 PM

Two new test builds and a new development snapshot are ready for testing.
The latest 6.1.x test build-6.1.45-158243,
and the latest 7.0.x test build-7.0.9-158223,
and
development snapshot-7.0.97-158251,
are all available at, https://www.virtualbox.org/wiki/Testbuilds

cwizardone

07-18-2023 08:30 PM

Two new stable releases. Both can be found at, https://www.virtualbox.org/

Quote:

VirtualBox 7.0.10 released!
Oracle today released a 7.0 maintenance release which improves stability and fixes regressions.

The change log. https://www.virtualbox.org/wiki/Changelog-7.0#v10

Quote:

VirtualBox 6.1.46 released!
Oracle today released a 6.1 maintenance release which improves stability and fixes regressions.

The change log, https://www.virtualbox.org/wiki/Changelog-6.1#v46

cwizardone

07-21-2023 10:25 AM

A new development snapshot, version 7.0.97-158510,
is now available at, https://www.virtualbox.org/wiki/Testbuilds

glorsplitz

07-23-2023 02:48 PM

1 Attachment(s)

@cwizardone, since this seems to your thread, maybe you know.

What happened to virtualbox download page just recently? Used to be download linux for all distributions, can't seem to find it now, I found this by accident.

Like if I click the link you provided in #493, click Download VirtualBox 7.0, where is the download?

In the attachment, last several versions of vbox, I've been getting that bar thing on the right, can't see lilo menu, I've just ignored as it's either bug or feature and my vm's are fine.

Anyone else getting this, what is it. I keep thinking with each vbox release it might go away but hasn't.

Daedra

07-23-2023 02:53 PM

Quote:

Originally Posted by glorsplitz (Post 6443841)

@cwizardone, since this seems to your thread, maybe you know.

What happened to virtualbox download page just recently? Used to be download linux for all distributions, can't seem to find it now, I found this by accident.

In the attachment, last several versions of vbox, I've been getting that bar thing on the right, can't see lilo menu, I've just ignored as it's either bug or feature and my vm's are fine.

Anyone else getting this, what is it. I keep thinking with each vbox release it might go away but hasn't.

I had this problem in Virtualbox 7.0.x which is why I stuck with the 6.1.x branch for the time being. I mostly use Qemu/KVM anymore so I hadn't bothered to check if this had been fixed in the 7.x branch.

cwizardone

07-23-2023 03:06 PM

Someone has been tinkering with the web site the last few weeks.
One time everything is in order, the next time something is missing.
Your are correct, i.e., when the page is working properly, you click on
"downloads" and then you want the last on the list, "All Linux..." or
whatever it is called. Doesn't come to mind at the moment. You right click on
it and pick "save link as."
I first noticed the trouble on the test build page. Sometimes there are no test builds or development snapshots listed. At the moment there are two test builds listed, but no development snapshots. The heading is there, but nothing listed beneath it.
All we can do, is keep checking back.
For what it worth, the 7 series test build works well on this box.
BTW, of the test builds and developement snapshos you want the one
labeled, Linux 64-bit, for Slackware.

ChuangTzu

07-23-2023 06:18 PM

Quite strange, have noticed the same for quite some time---past two weeks perhaps.

glorsplitz

07-23-2023 07:17 PM

Quote:

Originally Posted by Daedra (Post 6443843)

yea I did qemu, I guess I'm a little lazy using vbox

Daedra

07-23-2023 07:42 PM

Quote:

Originally Posted by glorsplitz (Post 6443882)

yea I did qemu, I guess I'm a little lazy using vbox

If it wasn't for virt-manager I probably would still be using Virtualbox for most things. I still use and really like Virtualbox, but once you get a taste of near bare metal performance you get with Qemu/KVM its hard to go back to Virtualbox.

All times are GMT -5. The time now is 03:30 AM.

Page 10 of 12

« First

Show 50 post(s) from this thread on one page