i3.
Some help please - virtualbox won't update to latest version
-
- OMV 2.x
- gelöst
- phoebus
-
-
What model of i3? It makes a difference.
-
i3-4370
LGA1150Based on the Intel specs, it's supported.
I'm currently using VirtualBox 4.3.32
-
-
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?
-
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. -
Are you sure that your OMV install is 64 Bit ?
In a console, run this command : uname -a, there should be x86_64 at the end. -
-
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
-
So, check if VT-X is enabled in the OS :
apt-get update
apt-get install msr-tools
modprobe msr
rdmsr 0x3AIt 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.
-
I think the bios is the key. He probably does not have it 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.
-
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:CodeLinux 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
Code
Alles anzeigenArchitecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Stepping: 3 CPU MHz: 897.007 BogoMIPS: 7600.10 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 4096K NUMA node0 CPU(s): 0-3
Error Messages:
Code
Alles anzeigenACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140424/hwxface-580) ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140424/hwxface-580) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff88043f083860), AE_NOT_FOUND (20140424/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88043f0838d8), AE_NOT_FOUND (20140424/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88043f0838d8), AE_NOT_FOUND (20140424/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff88043f083860), AE_NOT_FOUND (20140424/psparse-536) EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro aufs: module is from the staging directory, the quality is unknown, you have been warned. ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff88043f083860), AE_NOT_FOUND (20140424/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff88043f083860), AE_NOT_FOUND (20140424/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88043f0838d8), AE_NOT_FOUND (20140424/psparse-536) ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20140424/psargs-359) ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88043f0838d8), AE_NOT_FOUND (20140424/psparse-536) capability: warning: `VBoxHeadless' uses 32-bit capabilities (legacy support in use)
-
-
-
Where do I save this script to ?
-
Normally you can download the script in any folder you are using on the system drive. The data drives are normally noexec and scripts will not run on a drive mounted as noexec.
-
my work installing vb5 from scratch ( no previosly vb4 installed)
-
-
Just run the script. It will install 5.0 even if 4.3 isn't installed.
-
The script worked great.
Thanks. -
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.
-
-
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.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!