VirtualBox 6.1.28 / 6.1.29 on Fedora 35/34/33, CentOS/RHEL 8/7 - Comment Page: 7

Oracle VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. VirtualBox is a general-purpose full virtualizer for x86 hardware. Targeted at server, desktop and embedded use, it is now the only professional-quality virtualization solution that is also Open Source Software. Check video guide howto install VirtualBox 6.1.28/6.1.29 on Fedora 35/34/33 using .run installer: Check video guide howto install VirtualBox 6.1.28 on Fedora 34/33 using Oracle's own dnf repo: Watch More Videos and Subscribe to if-not-true-then-false.com Youtube Channel VirtualBox supports a large number of guest operating...

809 comments on “VirtualBox 6.1.28 / 6.1.29 on Fedora 35/34/33, CentOS/RHEL 8/7 - Comment Page: 7

1 5 6 7 8 9 27
    1. Thanks for this guide. Works perfectly.

      Reply
    2. [[email protected] ~]# /etc/init.d/vboxdrv setup
      Stopping VirtualBox kernel modules [ OK ]
      Uninstalling old VirtualBox DKMS kernel modules [ OK ]
      Trying to register the VirtualBox kernel modules using DKMS[FALHOU]
      (Failed, trying without DKMS)
      Recompiling VirtualBox kernel modules [FALHOU]
      (Look at /var/log/vbox-install.log to find out what went wrong)

      I’m using Fedora 16 64x.
      I’ve tried using the tips above but still have the problem.

      Thx.

      Reply
      • Hi!

        Could you post output of following command:

        
        rpm -qa binutils gcc make patch libgomp glibc\* kernel\* dkms |sort
        

        And could you also post your /var/log/vbox-install.log content?

        Reply
    3. thanks you, for you help, it was very important, until I made your instruccions I can do work with my virtualbox.

      Reply
    4. Dear JR

      I followed you exactly and got the error as below, I was trying to install VitualBox in CentOS 5.7( (in an openvz vps server).

      Stopping VirtualBox kernel modules [ OK ]
      Uninstalling old VirtualBox DKMS kernel modules [ OK ]
      Trying to register the VirtualBox kernel modules using DKMSError! echo
      Your kernel headers for kernel 2.6.18-274.7.1.el5.028stab095.1 cannot be found a
      t
      /lib/modules/2.6.18-274.7.1.el5.028stab095.1/build or /lib/modules/2.6.18-274.7.
      1.el5.028stab095.1/source.
      [FAILED]
      (Failed, trying without DKMS)
      Recompiling VirtualBox kernel modules [FAILED]
      (Look at /var/log/vbox-install.log to find out what went wrong)

      vbox-install.log shows
      Uninstalling modules from DKMS
      removing old DKMS module vboxhost version 4.1.8

      ——————————
      Deleting module version: 4.1.8
      completely from the DKMS tree.
      ——————————
      Done.
      Attempting to install using DKMS

      Creating symlink /var/lib/dkms/vboxhost/4.1.8/source ->
      /usr/src/vboxhost-4.1.8

      DKMS: add completed.
      Failed to install using DKMS, attempting to install without
      Makefile:201: *** Unable to find the folder to install the support driver to. S
      top.

      ====================
      rpm -qa kernel* // returns
      kernel-devel-2.6.18-274.18.1.el5
      kernel-headers-2.6.18-274.18.1.el5

      locate amd_iommu.h //returns
      /usr/src/kernels/2.6.18-274.18.1.el5-i686/include/asm-x86_64/amd_iommu.h

      And I already tried
      KERN_DIR=/usr/src/kernels/2.6.18-274.18.1.el5-i686
      export KERN_DIR
      /etc/init.d/vboxdrv setup

      Please help, thank you very much in advance.

      Reply
    5. In addition

      rpm -qa binutils gcc make patch libgomp glibc\* kernel\* dkms |sort //returns

      binutils-2.17.50.0.6-14.el5
      dkms-2.2.0.3-1.el5
      gcc-4.1.2-51.el5
      glibc-2.5-65.el5_7.3
      glibc-common-2.5-65.el5_7.3
      glibc-devel-2.5-65.el5_7.3
      glibc-headers-2.5-65.el5_7.3
      kernel-devel-2.6.18-274.18.1.el5
      kernel-headers-2.6.18-274.18.1.el5
      libgomp-4.4.4-13.el5
      make-3.81-3.el5
      patch-2.5.4-31.el5

      Reply
      • Hi YoungX,

        Your rpm -qa binutils gcc make patch libgomp glibc\* kernel\* dkms |sort command output looks like you have not any kernels installed?

        Please post output of following commands:

        
        rpm -qa kernel
        
        uname -a
        
        Reply
    6. During the installation of Red hat 6.0 in virtulabox…Error was

      This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot – please use a kernel appropriate for your CPU

      Reply
      • Hi prakash,

        Did you create 64-bit virtual machine?

        Reply
      • Hi elaslink,

        So you have problems to boot Linux distros on VirtualBox?

        Reply
        • no jr.. in this case of my video i install virtualbox inside my fedora 16 vm i dont know if possible run another machine

          Reply
          • So you run Fedora 16 on virtual machine (as guest system) top of some host OS? And installed VirtualBox on Fedora 16 and try to run some another Linux distro (virtual machine/guest)?

            I think that, even this should be possible, but it’s more efficient if you run that other Linux distro on your host OS…

            Reply
            • yeah jr u right.. but i trye just for testing.. the host Os win7
              ;)

              Reply
              • Okay! I think that, it should be possible to test, if you have enough RAM. :)

                Reply
    7. the following attempt to share a directory between fc15(host) and vBox fails.

      mount -t vboxsf vbClient /zdm_vBox -> mount: unknown filesystem type ‘vboxsf’

      Your install guide worked just fine. Hopefully you can point to the fix for this issue
      Thanks – Don

      Reply
    8. JR how does one go about doing that plus I was under the opinion that since my VM (client) was the windows mach that was not needed

      Reply
      • Are you trying to use mount command in Windows guest? Mount command works only in Linux guest, not Windows.

        With Windows you have to use something like following command:

        
        net use x: \\vboxsvr\ -p
        
        Reply
    9. JR – when i start the vBox i get a config panel with a “settings” option
      if I hit that settings button i get a drop down list and the last entry is “shared folder” clicking on this option i get a “net use x: \\vboxsrv\share” hint screen and above that hint i have the option to create or edit my folder to share entry
      The folder path seems correct “/” as it resides on “root” using a folder name of “zdm_willieServer” which does exist but i can not get it to showUp under the “myCOmputer” option all i see are “local disk C:” and “CD drive D:”

      Reply
      • Do you try to share your Fedora host entire root? I’m not sure, it is even possible, because then you need root permissions and you have very big chance mess up your whole Linux system.

        This net use x…command is Windows command line command, more info here. Or you can browse your “Network” on Windows and try to find your VBox shared folders.

        Reply
    10. good point
      here is what i am now trying
      created folder on root as /zdm_vBox with perms set to r-w-ex
      started vBox and went to settings -> shared folders where i entered path -> /zdm_vBox
      and folder as zdm_vBox set autoMount = on and saved the config
      started VM and went to myComputer – nothing so then went to netWorkPlaces nothing then tried to create z:\\zdm_vBox to no avail
      going bald from pulling my hair out

      Reply
      • Now it sounds much better :)

        Try to create z:\\vboxsvr\zdm_vBox or \\vboxsvr\zdm_vBox instead?

        Reply
    11. ran “Map Network Drive” from myComputer
      windows response – The network path \\vboxsrv\zdm_vBox could not be found

      Reply
      • So what happens if you open Windows command line (cmd) and write exactly following command (check spaces):

        
        net use x: \\vboxsvr\zdm_vBox
        

        Do you get some error or do you get X: drive?

        Reply
    12. Got same response – The network path \\vboxsrv\zdm_vBox could not be found

      Reply
      • I guess that the VirtualBox Guest Additions will solve this problem, but if you are absolutely sure that Guest Additions are not needed and you won’t install it, then I don’t have any other idea howto get it working…

        Reply
    13. JR – i am removing vBox and will attempt to reinstall again. when is the “Guest Additions” installed and are their any other additions i should be aware of. How do i get the common clipboard working and USB ports as example

      Thanks for your help – Don

      Reply
    14. thanks a lot, works great!

      Reply
1 5 6 7 8 9 27

Leave a Reply to mate Cancel reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Close