[Nix-dev] Nixops on headless server

[Marco Maggesi]

Hi, there seems to be again a problem with nixops with virtualbox headless
nodes.

$ nixops deploy -d minicloud
webserver> creating VirtualBox VM...
webserver> Virtual machine
'nixops-24856f59-ba5b-11e3-a2e6-2d15dd5fa0ff-webserver' is created and
registered.
webserver> UUID: d6ea884c-3173-4e12-bada-aeff1112c39c
webserver> Settings file: '/home/maggesi/VirtualBox
VMs/nixops-24856f59-ba5b-11e3-a2e6-2d15dd5fa0ff-webserver/nixops-24856f59-ba5b-11e3-a2e6-2d15dd5fa0ff-webserver.vbox'
webserver> creating disk 'disk1'...
webserver> 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
webserver> Clone hard disk created in format 'VDI'. UUID:
ad027933-92f8-4655-8f63-a3bf582122b8
webserver> attaching disk 'disk1'...
webserver> VBoxManage: error: The virtual machine
'nixops-24856f59-ba5b-11e3-a2e6-2d15dd5fa0ff-webserver' has terminated
unexpectedly during startup with exit code 1
webserver> VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005),
component Machine, interface IMachine
webserver> Waiting for VM
"nixops-24856f59-ba5b-11e3-a2e6-2d15dd5fa0ff-webserver" to power on...
webserver> waiting for IP address...........

Can you test and confirm the problem.

My setup:

# nix-channel --list
nixops http://hydra.nixos.org/project/nixops/channel/latest
nixos http://nixos.org/channels/nixos-unstable
hydra http://hydra.nixos.org/project/hydra/channel/latest

Thank you in advance,
M.



2014-01-16 21:13 GMT+01:00 Patrick Wheeler <patrick.john.wheeler at gmail.com>:

> @Marco Good to hear thanks for let everyone know.
>
>
> On Tue, Jan 14, 2014 at 12:08 PM, Marco Maggesi <maggesi at math.unifi.it>wrote:
>
>> Hi,
>>
>> just a quick note to let you know that I gave an other try to nixops
>> today and now everything works as expected!
>> (I deleted the old attempt and I updated nixops to version 1.2, no
>> modification of my configuration).
>>
>> Thank you for your support,
>> Marco
>>
>>
>> 2013/12/25 Oliver Charles <ollie at ocharles.org.uk>
>>
>>>  On 23/12/13 20:06, Marco Maggesi wrote:
>>>
>>>  I started from scratch.  This is the interaction.
>>> Thanks a lot,
>>> M.
>>>
>>>  [maggesi at o0dom0:~/Devel/nixconfs/minicloud]$ nixops create
>>> ./logical.nix ./physical-vbox.nix --name minicloud
>>> created deployment 'aa84379e-6c0c-11e3-8dd5-bfd6a9bb84eb'
>>>  aa84379e-6c0c-11e3-8dd5-bfd6a9bb84eb
>>>
>>>  [maggesi at o0dom0:~/Devel/nixconfs/minicloud]$ nixops deploy -d minicloud
>>>  webserver> creating VirtualBox VM...
>>> webserver> Virtual machine
>>> 'nixops-aa84379e-6c0c-11e3-8dd5-bfd6a9bb84eb-webserver' is created and
>>> registered.
>>> webserver> UUID: eda5fa7f-8141-40df-a9cf-9e13265d7e1f
>>>  webserver> Settings file: '/home/maggesi/VirtualBox
>>> VMs/nixops-aa84379e-6c0c-11e3-8dd5-bfd6a9bb84eb-webserver/nixops-aa84379e-6c0c-11e3-8dd5-bfd6a9bb84eb-webserver.vbox'
>>>  webserver> creating disk 'disk1'...
>>> webserver>
>>> 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
>>>  webserver> Clone hard disk created in format 'VDI'. UUID:
>>> d9b38107-e2fe-440c-86e4-335711704dbf
>>> webserver> attaching disk 'disk1'...
>>> webserver> VBoxManage: error: The virtual machine
>>> 'nixops-aa84379e-6c0c-11e3-8dd5-bfd6a9bb84eb-webserver' has terminated
>>> unexpectedly during startup with exit code 1
>>> webserver> VBoxManage: error: Details: code NS_ERROR_FAILURE
>>> (0x80004005), component Machine, interface IMachine
>>>  webserver> Waiting for VM
>>> "nixops-aa84379e-6c0c-11e3-8dd5-bfd6a9bb84eb-webserver" to power on...
>>> webserver> waiting for IP
>>> address.....................................................................................................................................................................................................................................................................................^Cerror:
>>> interrupted
>>>
>>>  [maggesi at o0dom0:~/Devel/nixconfs/minicloud]$ VBoxManage startvm
>>> nixops-aa84379e-6c0c-11e3-8dd5-bfd6a9bb84eb-webserver --type headless
>>> Waiting for VM "nixops-aa84379e-6c0c-11e3-8dd5-bfd6a9bb84eb-webserver"
>>> to power on...
>>> VBoxManage: error: The virtual machine
>>> 'nixops-aa84379e-6c0c-11e3-8dd5-bfd6a9bb84eb-webserver' has terminated
>>> unexpectedly during startup with exit code 1
>>> VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005),
>>> component Machine, interface IMachine
>>>
>>>   [maggesi at o0dom0:~/Devel/nixconfs/minicloud]$ VBoxManage startvm
>>> nixops-aa84379e-6c0c-11e3-8dd5-bfd6a9bb84eb-webserver
>>> Waiting for VM "nixops-aa84379e-6c0c-11e3-8dd5-bfd6a9bb84eb-webserver"
>>> to power on...
>>> VBoxManage: error: The virtual machine
>>> 'nixops-aa84379e-6c0c-11e3-8dd5-bfd6a9bb84eb-webserver' has terminated
>>> unexpectedly during startup with exit code 1
>>> VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005),
>>> component Machine, interface IMachine
>>>
>>>
>>>
>>>
>>> I think I had similar behaviour with VirtualBox, and it turned out the
>>> internal DHCP server for VirtualBox wasn't running. I forget the specific
>>> details, but if you Google around you should be able to find the
>>> instructions. Could be a red herring - but worth looking into!
>>>
>>> - ocharles
>>>
>>
>>
>> _______________________________________________
>> nix-dev mailing list
>> nix-dev at lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
>>
>
>
> --
> Patrick Wheeler
> Patrick.John.Wheeler at gmail.com
> Patrick.J.Wheeler at rice.edu
> Patrick.Wheeler at colorado.edu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20140402/859c1090/attachment-0001.html