Dev1 Galaxy Forum / Issues installing VirtualBox on Refracta

Re: Issues installing VirtualBox on Refracta

dummy@example.com (pcalvert) — Wed, 24 Mar 2021 15:13:36 +0000

fsmithred wrote:

I don't have any ideas for the usb. Yes I do. Not a fix; just a workaround. Someone I know used shared folders with a usb mounted on the host system.

Good idea. That might help some people. Unfortunately, that won't work for a printer or scanner.

Since version 5.2 worked just fine on Devuan ASCII, I figured I would go back to using that version even though it's no longer supported. Imagine my surprise when I encountered the same error messages when I tried to install version 5.2 on Beowulf-based Refracta.

This was my final attempt to get VirtualBox working:

$ wget https://download.virtualbox.org/virtualbox/6.1.18/VirtualBox-6.1.18-142142-Linux_amd64.run
$ wget https://www.virtualbox.org/download/hashes/6.1.18/SHA256SUMS
$ sha256sum VirtualBox-6.1.18-142142-Linux_amd64.run
[Then check to make sure that the sha256sum value is correct.]

$ su
[Enter root password.]

# chmod u+x VirtualBox-6.1.18-142142-Linux_amd64.run
# ./VirtualBox-6.1.18-142142-Linux_amd64.run install

I was quite surprised when those same error messages appeared again.

This is what I did to try to repair (complete) the installation:

# update-rc.d vboxdrv defaults
# rcvboxdrv setup

I then tested USB passthrough to see if it was working, and it was not. At this point I almost gave up. In fact, I did a minimal installation of QEMU and started researching the different utilities and GUI tools that are available for QEMU.

I then had a hunch that I should try rebooting the system. I didn't think it would help, but I went ahead and did it anyway. That worked -- USB passthrough is now working.

Re: Issues installing VirtualBox on Refracta

dummy@example.com (dice) — Wed, 24 Mar 2021 13:25:47 +0000

fsmithred wrote:

People use virtualbox because it's easy to figure out how to do things with it.
So how does one attach a usb drive in qemu? I saw two ways to do it and one way not to do it in the man page, but not really an explanation of how to do it. Anyone have a quick answer so I don't have to spend the time experimenting?

What head on a stick said. Ive only just started playing around with qemu, i installed a windows installation with qemu to update a garmin navman to the latest maps as garmin doesnt seem to care for linux and opensource. The only hard part was parting with 6GB of bandwidth downloading the win10 IS0. I followed head on a sticks tutorial and some notes from here: http://dev1galaxy.org/viewtopic.php?pid=26102#p26102

Head_on_a_Stick wrote:

I use this to launch a QEMU/KVM virtual machine along with virt-viewer and a shared directory (with the path to the disk image as the argument):

function vlaunch {
   qemu-system-x86_64 -enable-kvm \
                      -m 4G \
                      -cpu host \
                      -smp cores=4 \
                      -drive file="$1",format=raw,cache=none,if=virtio \
                      -soundhw hda \
                      -vga qxl \
                      -device virtio-serial-pci \
                      -device virtserialport,chardev=spicechannel0,name=com.redhat.spice.0 \
                      -chardev spicevmc,id=spicechannel0,name=vdagent \
                      -spice unix,addr=/tmp/vm_spice.socket,disable-ticketing \
                      -device nec-usb-xhci,id=usb \
                      -chardev spicevmc,name=usbredir,id=usbredirchardev1 \
                      -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 \
                      -chardev spicevmc,name=usbredir,id=usbredirchardev2 \
                      -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 \
                      -fsdev local,id=qemu_dev,path=/home/empty/Public,security_model=none \
                      -device virtio-9p-pci,fsdev=qemu_dev,mount_tag=qemu_mount &
   remote-viewer "spice+unix:///tmp/vm_spice.socket"
}

See http://forums.debian.net/viewtopic.php?f=16&t=144775 for more on this.

But that's in $ENV (~/.kshrc) because I use Korn Shell rather than bloaty old bash :-)

Re: Issues installing VirtualBox on Refracta

dummy@example.com (zapper) — Tue, 23 Mar 2021 23:13:54 +0000

Head_on_a_Stick wrote:

fsmithred wrote:
People use virtualbox because it's easy to figure out how to do things with it.
Have you tried gnome-boxes? It's easier to use than VirtualBox, and virt-manager isn't particularly difficult to use either.
fsmithred wrote:
how does one attach a usb drive in qemu?
See https://www.spice-space.org/usbredir.html ← that shows how to configure pass-through for the USB ports themselves. It works for any attached USB devices, including hard drives; gnome-boxes configures it automagically.
EDIT: my fdn guide shows a complete configuration from the command line, including shared folders and USB pass-through.

Virt-manager and gnome-boxes are both also good.

Virt-manager is the easier of the two.

But I think, redhat develops virt-manager, which makes me wary of them now.

I used to like it, but I don't need it now that I know a bit more how to use qemu.

Re: Issues installing VirtualBox on Refracta

dummy@example.com (zapper) — Tue, 23 Mar 2021 23:09:50 +0000

fsmithred wrote:

People use virtualbox because it's easy to figure out how to do things with it.
So how does one attach a usb drive in qemu? I saw two ways to do it and one way not to do it in the man page, but not really an explanation of how to do it. Anyone have a quick answer so I don't have to spend the time experimenting?

Ah, you want to know how to use a usb drive in qemu?

I can tell you:

qemu-system-x86_64 ~/your.img -cpu kvm64,+nx -enable-kvm -hdb /dev/sdb -m 3072 -soundhw ac97

However, for some virtual machines, you need to do one other thing...

Switch on show tabs on your VM, and go to compat_monitor0

Then type in device_add usb-host or usb-storage...

That's always worked when I used to use winxp vms.

Obviously I keep those detached from the internet.

Quick note though, I don't remember whether its usb-host or usb-storage after device_add

my two cents. Hope this helps.

The extra step however isn't needed for Devuan images from what I remember. Same with Hyperbola, etc...

Re: Issues installing VirtualBox on Refracta

dummy@example.com (rolfie) — Tue, 23 Mar 2021 18:10:31 +0000

pcalvert wrote:

I ran into some problems when installing VirtualBox 6.1.18 on Beowulf-based Refracta.

Here's the relevant info:

$ cat /etc/apt/sources.list.d/virtualbox.list
deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian buster contrib

# aptitude install virtualbox-6.1 -r
The following NEW packages will be installed:
  libqt5opengl5{a} libqt5printsupport5{a} libsdl-ttf2.0-0{a} virtualbox-6.1 
0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/88.7 MB of archives. After unpacking 215 MB will be used.
Do you want to continue? [Y/n/?] y
Preconfiguring packages ...              
...
...snip...
...

Well, I have used a different way to install VBox on my stock Beowulf installations (with backports kernels). Loaded the Debian10 package down to /tmp, installed it with dpkg -i followed by a apt -f install to correct all dependencies. No trace of any dbus errors. My latest learning: maybe an apt install ./package.deb takes care for the dependencies too.

In addition, I added the vboxdrv, vboxnetadp and vboxnetflt to the /etc/modules file.

pcalvert wrote:

I believe that this may be a solution (or partial solution):
# update-rc.d vboxdrv defaults
Reference:
Instalando VirtualBox 6.0 en Devuan Beowulf
https://www.linuxito.com/cloud/1269-ins … an-beowulf
VirtualBox runs and appears to (mostly) work. However, at least one function (USB passthrough) does not. The extension pack and guest additions have been installed, so that isn't the problem.

I have not seen any need to fool around with update-rc.d. Maybe the modules did the job.

Besides the installation of the extension pack, the USB passthrough depends on that the user using the machine is member of the vboxusers group. Make sure you/the user are member of this group. The group is created automagically, but the user(s) needs to be added manually.

pcalvert wrote:

P.S. Don't tell me not to use VirtualBox. I'm not ready to switch just yet.

Full ACK from my side.

rolfie

Re: Issues installing VirtualBox on Refracta

dummy@example.com (Head_on_a_Stick) — Tue, 23 Mar 2021 17:03:27 +0000

fsmithred wrote:

People use virtualbox because it's easy to figure out how to do things with it.

Have you tried gnome-boxes? It's easier to use than VirtualBox, and virt-manager isn't particularly difficult to use either.

fsmithred wrote:

how does one attach a usb drive in qemu?

See https://www.spice-space.org/usbredir.html ← that shows how to configure pass-through for the USB ports themselves. It works for any attached USB devices, including hard drives; gnome-boxes configures it automagically.

EDIT: my fdn guide shows a complete configuration from the command line, including shared folders and USB pass-through.

Re: Issues installing VirtualBox on Refracta

dummy@example.com (fsmithred) — Tue, 23 Mar 2021 15:56:04 +0000

People use virtualbox because it's easy to figure out how to do things with it.

So how does one attach a usb drive in qemu? I saw two ways to do it and one way not to do it in the man page, but not really an explanation of how to do it. Anyone have a quick answer so I don't have to spend the time experimenting?

Re: Issues installing VirtualBox on Refracta

dummy@example.com (dice) — Tue, 23 Mar 2021 13:23:25 +0000

Forget virtualbox, use what is available and works within devuan, learn to use qemu.

Re: Issues installing VirtualBox on Refracta

dummy@example.com (zapper) — Sat, 20 Mar 2021 09:35:26 +0000

I am a bit confused why people use virtualbox still...

Qemu works fine for most things I thought...

just my two cents.

qemu-system-x86_64 ~/YOUR.img -cpu kvm64,+nx --enable-kvm -m 2048 -soundhw ac97

I do this to make qemu work. It is the better option for many reasons...

Also, virtualbox is a security minefield I have heard.

And I wasn't talking about systemd either.

Re: Issues installing VirtualBox on Refracta

dummy@example.com (Head_on_a_Stick) — Fri, 19 Mar 2021 23:42:37 +0000

fsmithred wrote:

I just booted a live iso in qemu and installed vbox.

https://xkcd.com/1764/

(scnr)

Re: Issues installing VirtualBox on Refracta

dummy@example.com (fsmithred) — Fri, 19 Mar 2021 23:38:21 +0000

I just booted a live iso in qemu and installed vbox. I had to say those words in my head before I realized how weird it is. Anyway, I got the same error messages as you. Before I did it, I checked in sysv-rc-conf to see where dbus starts, and it starts in 2-5, not S. I checked beowulf, ascii, chimaera, jessie and wheezy. All the same.

There's no mention of dbus in /etc/init.d/vbox* or /var/lib/dpkg/info/virualbox-6.1.* so I don't know where that message is coming from.

I don't have any ideas for the usb. Yes I do. Not a fix; just a workaround. Someone I know used shared folders with a usb mounted on the host system.

Issues installing VirtualBox on Refracta

dummy@example.com (pcalvert) — Fri, 19 Mar 2021 21:00:01 +0000

I ran into some problems when installing VirtualBox 6.1.18 on Beowulf-based Refracta.

Here's the relevant info:

$ cat /etc/apt/sources.list.d/virtualbox.list
deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian buster contrib

# aptitude install virtualbox-6.1 -r
The following NEW packages will be installed:
  libqt5opengl5{a} libqt5printsupport5{a} libsdl-ttf2.0-0{a} virtualbox-6.1 
0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/88.7 MB of archives. After unpacking 215 MB will be used.
Do you want to continue? [Y/n/?] y
Preconfiguring packages ...              
Selecting previously unselected package libqt5opengl5:amd64.
(Reading database ... 158142 files and directories currently installed.)
Preparing to unpack .../libqt5opengl5_5.11.3+dfsg1-1+deb10u4_amd64.deb ...
Unpacking libqt5opengl5:amd64 (5.11.3+dfsg1-1+deb10u4) ...
Selecting previously unselected package libqt5printsupport5:amd64.
Preparing to unpack .../libqt5printsupport5_5.11.3+dfsg1-1+deb10u4_amd64.deb ...
Unpacking libqt5printsupport5:amd64 (5.11.3+dfsg1-1+deb10u4) ...
Preparing to unpack .../virtualbox-6.1_6.1.18-142142~Debian~buster_amd64.deb ...
Unpacking virtualbox-6.1 (6.1.18-142142~Debian~buster) ...
Selecting previously unselected package libsdl-ttf2.0-0:amd64.
Preparing to unpack .../libsdl-ttf2.0-0_2.0.11-6_amd64.deb ...
Unpacking libsdl-ttf2.0-0:amd64 (2.0.11-6) ...
Setting up libqt5printsupport5:amd64 (5.11.3+dfsg1-1+deb10u4) ...
Setting up libqt5opengl5:amd64 (5.11.3+dfsg1-1+deb10u4) ...
Setting up libsdl-ttf2.0-0:amd64 (2.0.11-6) ...
Setting up virtualbox-6.1 (6.1.18-142142~Debian~buster) ...
addgroup: The group `vboxusers' already exists as a system group. Exiting.
insserv: FATAL: service dbus is missed in the runlevels S to use service bluetooth
insserv: exiting now!
insserv: FATAL: service vboxdrv has to be enabled to use service vboxballoonctrl-service
insserv: FATAL: service dbus is missed in the runlevels S to use service bluetooth
insserv: exiting now!
insserv: FATAL: service vboxdrv has to be enabled to use service vboxautostart-service
insserv: FATAL: service dbus is missed in the runlevels S to use service bluetooth
insserv: exiting now!
insserv: FATAL: service vboxdrv has to be enabled to use service vboxweb-service
insserv: FATAL: service dbus is missed in the runlevels S to use service bluetooth
insserv: exiting now!
Processing triggers for mime-support (3.62) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for shared-mime-info (1.10-1) ...
Processing triggers for desktop-file-utils (0.23-4) ...

I believe that this may be a solution (or partial solution):

# update-rc.d vboxdrv defaults

Reference:
Instalando VirtualBox 6.0 en Devuan Beowulf
https://www.linuxito.com/cloud/1269-ins … an-beowulf

VirtualBox runs and appears to (mostly) work. However, at least one function (USB passthrough) does not. The extension pack and guest additions have been installed, so that isn't the problem.

Anyone have any ideas? And what about those error messages regarding dbus?

P.S. Don't tell me not to use VirtualBox. I'm not ready to switch just yet.