nix-community/nixos-anywhere

--vm-test does not complete

Lyndeno opened this issue · 3 comments

Lyndeno commented

It builds, and loads the vm.

I am unsure what the next steps are:

vm-test-run-disko-neo-disko> machine # + declare -a extraFormatArgs
vm-test-run-disko-neo-disko> machine # + extraOpenArgs=('--allow-discards')
vm-test-run-disko-neo-disko> machine # + declare -a extraOpenArgs
vm-test-run-disko-neo-disko> machine # + initrdUnlock=1
vm-test-run-disko-neo-disko> machine # + keyFile=
vm-test-run-disko-neo-disko> machine # [   10.272766] systemd[1]: Reached target Multi-User System.
vm-test-run-disko-neo-disko> machine # [   10.277736] dhcpcd[704]: eth0: adding default route via fe80::2
vm-test-run-disko-neo-disko> machine # [   10.279677] systemd[1]: Reached target Host and Network Name Lookups.
vm-test-run-disko-neo-disko> machine # + name=crypted
vm-test-run-disko-neo-disko> machine # + passwordFile=
vm-test-run-disko-neo-disko> machine # + settings=()
vm-test-run-disko-neo-disko> machine # + declare -A settings
vm-test-run-disko-neo-disko> machine # + type=luks
vm-test-run-disko-neo-disko> machine # [   10.286860] systemd[1]: Reached target User and Group Name Lookups.
vm-test-run-disko-neo-disko> machine # [   10.292906] systemd[1]: Startup finished in 2.951s (kernel) + 7.298s (userspace) = 10.250s.
vm-test-run-disko-neo-disko> machine # + set +x
vm-test-run-disko-neo-disko> machine # [  714.936330] systemd[1]: Started Logrotate Service.
vm-test-run-disko-neo-disko> machine # [  714.985572] systemd[1]: logrotate.service: Deactivated successfully.

This is the last output before it stops doing anything.

The command with vm-test does not complete. Is it supposed to do something or am I supposed to somehow log in to the vm to do testing myself?

phaer commented

Could you link your config for reproducibility?

From a quick glance, it looks like you are using luks and the test might be missing a key to unlock your disk?

Lyndeno commented

My config can be found here. I am testing this with the "neo" host.

I am using luks. I have tried putting a short password in a file and passing it through but I get the same result.

This pull #196 seems to indicate that these options do not work/not required for vm-test? But there is no description or reasoning for these changes on the pull so I cannot reallt understand what is going on.

Lyndeno commented

It seems by simply adding a settings.keyFile entry to the luks, it continues past that part in the test. Thus no bug.

I am now running into errors due to size contraints within the vm test. That should be a different issue I think.