First time I succeed in launching the VM, I got the following
message:
VT-x/AMD-V hardware acceleration is not available on your system.
Your 64-bit guest will fail to detect a 64-bit CPU and will not
be able to boot.
It seem that the problem is indeed related to the hardware
virtualization feature in the bios that should be activated.
This is important for running a 64 bits guest on a 32 bits host.
However my 32 bit satellite machine does not support this option.
The only possible solution would be to generate 32 bits VMs instead.
I tried changing the os type to Linux (meaning 32 bit linux) but unfortunately,
there is currently no prebuilt i686-linux nixops image on the nixos web site.
Only the 64 bits version is available and I assume, hence the hack.
First time I succeed in launching the VM, I got the following message:
It seem that the problem is indeed related to the hardware virtualization feature in the bios that should be activated. This is important for running a 64 bits guest on a 32 bits host.
However my 32 bit satellite machine does not support this option.
The only possible solution would be to generate 32 bits VMs instead.
I validated and indeed in https://github.com/NixOS/nixops/blob/master/nixops/backends/virtualbox.py in the
create
function (about ln206), nixops systematically create a 64 bits machine with the instruction["VBoxManage", "createvm", "--name", vm_id, "--ostype", "Linux26_64", "--register"]
.I tried changing the os type to
Linux
(meaning 32 bit linux) but unfortunately, there is currently no prebuilt i686-linux nixops image on the nixos web site. Only the 64 bits version is available and I assume, hence the hack.At http://nixos.org/releases/nixos/virtualbox-nixops-images/, one can see there effectively isn't any up to date nixops VMs for i686.