Some help please - virtualbox won't update to latest version

    • Offizieller Beitrag

    What model of i3? It makes a difference.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    That should support almost all the VT technologies and you would even be able to use a 64 bit guest on a 32 bit client. What error are you getting when trying to install 64 bit windows?

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • 1. The 64 bit is not available on the Virtualbox operating system drop down list.


    2. I got an error that said on syslog upon boot up that vbox is using a 32 bit os.
    I don't have an exact message to post right now.

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

  • So, check if VT-X is enabled in the OS :
    apt-get update
    apt-get install msr-tools
    modprobe msr
    rdmsr 0x3A


    It should return 5 if the extensions are enabled, and 1 if disabled.


    You can also try to update your bios, and check after that vt-x is still enabled.

  • You're right, tekkb.


    I shutdown my server a couple weeks ago to redo my cable management, and replace CMOS battery.
    I thought I enabled it back, but it wasn't. It's good now.


    Thanks guys.

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

  • I got Virtualbox issue again:
    I'm running OMV x64, VT-X is enabled in BIOS, but I'm getting vbox warning about 32-bit capabilities.
    OMV info:

    Code
    Linux nas 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u4~bpo70+1 (2015-09-22) x86_64 GNU/Linux




    Error Messages:

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    • Offizieller Beitrag

    Script and packages update to virtualbox 5.0.10 and phpvirtualbox 5.0-3. Old script (5.0.2) still available.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    Just run the script. It will install 5.0 even if 4.3 isn't installed.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Just to add a few comments about the script:


    1. It is for 64-bit OMV installations only by the look of things. I changed the line:
    wget http://download.virtualbox.org…1~Debian~wheezy_amd64.deb
    to the 32-bit version and it appears to work ok on a 32-bit OMV.


    2. I had issues with part of the script having run but not all. The script removes virtualbox-4.3 but not virtualbox-5.0. Maybe it should remove virtualbox-5.0 as well before it is re-added so that errors are not produced if there was a previous failure.


    3. I had to change permissions (chown -R vbox:vboxusers /media/xx/VMs share) once installed. Then re-set the box php admin user password and re-import the virtual box machines. The permission problem might have been due to fresh install of OMV 2.1 when disk was from an OMV 0.4 installation though.

    • Offizieller Beitrag

    1. Not many people run Virtualbox on a 32 bit machine. So, I didn't worry about it. This was only supposed to be a temporary solution.


    2. It was only meant to upgrade 4.3. Since it is hanging around longer than I thought, I will add 5.0.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!