Re: [VBox-users] Hardware available features: will vbox use them automatically?

[Alexey Eromenko]

On Sun, Sep 22, 2019, 03:36 Dedeco Balaco via VBox-users-community <
vbox-users-community@lists.sourceforge.net> wrote:

> So, with the context i showed in my Debian, it will use only something
> my hardware has?
>
> KVM is something that VB will never use?
>
>
>
> --
>
> VirtualBox has it's own CPU hardware acceleration module, 'vboxdrv', that
> like KVM does acceleration.
___
VBox-users-community mailing list
VBox-users-community@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
___
Unsubscribe:  
mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe

Re: [VBox-users] Hardware available features: will vbox use them automatically?

[Dedeco Balaco via VBox-users-community]

So, with the context i showed in my Debian, it will use only something
my hardware has?

KVM is something that VB will never use?


Em 18-09-2019 05:22, Alexey Eromenko escreveu:
> VirtualBox uses CPU hardware acceleration for Virtualization, similar to
> Linux-KVM. 
> 
> 
> On Wed, Sep 18, 2019, 06:39 Dedeco Balaco via VBox-users-community
>  > wrote:
> 
> Hello,
> 
> i have this small computer since not too long ago, and i never run a
> virtual machine in it. Now, i am thinking about running one. I use
> Debian in it, but eventually i want to test things without it affecting
> my every day environment. And the virtual machines could perfectly
> fit this.
> 
> Searching around a bit, i see that some computers may have hardware
> features to do virtual machines. My question here is about that, i could
> not find the answer in VirtualBox (VB) documentation: will it use,
> automatically, all the features my hardware has to make the virtual
> machines as fast as possible, within the limits i impose for them?
> 
> After this question, i have discovered two commands to show me that, but
> i do not know how to interpret the meanings of their output. May you
> tell me how do i use that with VB?
> 
> Output from my terminal:
> 
> ===
> # check-bios-nx --verbose
> ok: the NX bit is operational on this CPU.
> 
> # kvm-ok
> INFO: /dev/kvm exists
> KVM acceleration can be used
> ===
> 
> Thank you
> 
> 
> ___
> VBox-users-community mailing list
> VBox-users-community@lists.sourceforge.net
> 
> https://lists.sourceforge.net/lists/listinfo/vbox-users-community
> ___
> Unsubscribe: 
> mailto:vbox-users-community-requ...@lists.sourceforge.net
> 
> ?subject=unsubscribe
> 


___
VBox-users-community mailing list
VBox-users-community@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
___
Unsubscribe:  
mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe

[VBox-users] Linux 5.3 Guest - no vboxsf [was Re: 5.2.32 Modules Fail to Build against Linux 5.3 w/dkms]

[David C. Rankin]

On 09/20/2019 01:40 AM, David C. Rankin wrote:
> All,
> 
>   Arch updated to Linux 5.3 kernel tonight and the update failed to build the
> kernel modules with several errors. I have opened bug:
> 
> https://www.virtualbox.org/ticket/18949
> 
>   I've attached to make.log here in case anyone can think of any workarounds
> to try. This is with gcc 9.1.0.
> 
>   Thanks for any help you can offer.
> 
> 
> (the 6.X version is not an option due the my use of headless windows guests
> that are unusably slow under the 6.X version -- see long thread beginning
> 1/9/19 - Virtualbox 6.0.0 - Marked Slowdown for Window7 Guests? Linux Guests 
> OK​)

I have patched the Archlinux Virtualbox 5.2.32 in AUR for Linux 5.3, however
when updating the Archlinux Guest to Linux 5.3 shared folders are no longer
available and the vboxsf module is not found. Is something else required when
the guest is running Linux 5.3?

I ask because I have Win7 guests, openSUSE 15.0 and 15.1 guests and they all
have no issue accessing the shared folder on the host. It is only the
Archlinux guest that cant use the shared folders.

All guests are access --headless over the LAN. Checking the guest modules, the
only ones loaded are vboxvideo (X works fine, but the share clipboard isn't)
and vboxgues, e.g.

6:37 vl1:~> lsmod | grep vbox
vboxvideo  40960  2
drm_vram_helper20480  1 vboxvideo
drm_kms_helper212992  1 vboxvideo
drm   516096  6 drm_kms_helper,drm_vram_helper,vboxvideo,ttm
vboxguest  45056  5

With the 5.2 kernel, there were no problems with the shared folders on the
guest. mount -t vboxsf fails as well. However, the permanent mount point is
still there:

16:46 vl1:~> l /media/
total 12
drwxr-xr-x  3 root root   4096 May 27 14:09 .
drwxr-xr-x 18 root root   4096 May 28 16:30 ..
drwxrwx---  2 root vboxsf 4096 May 27 14:09 sf_davidvl

but it is empty. The Archlinux 5.3 host shows the shared folder active:

$ VBoxManage showvminfo arch_1_64

Shared folders:

Name: 'davidvl', Host path: '/home/david' (machine mapping), writable

The host modules running are:

lsmod | grep vbox
vboxnetflt 32768  0
vboxnetadp 28672  0
vboxpci28672  0
vboxdrv   487424  4 vboxpci,vboxnetadp,vboxnetflt


What else (and where else) would I check to see why the vboxsf isn't working
on the Linux-5.3 guest?


-- 
David C. Rankin, J.D.,P.E.


___
VBox-users-community mailing list
VBox-users-community@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
___
Unsubscribe:  
mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe