Skip to content

qemu: Update to 1.6.1#1175

Closed
rickynils wants to merge 1 commit intoNixOS:masterfrom
rickynils:qemu-161
Closed

qemu: Update to 1.6.1#1175
rickynils wants to merge 1 commit intoNixOS:masterfrom
rickynils:qemu-161

Conversation

@rickynils
Copy link
Member

qemu 1.5.2 no longer works for me. I get "Device or resource busy" when I try to create a qemu machine with libvirt (on Linux 3.11). qemu 1.6.1 works fine, though.

However, there was some problem last time I tried updating to 1.6.0. A lot of Hydra builds failed. @edolstra How can I verify that 1.6.1 isn't broken in the same way?

@edolstra
Copy link
Member

edolstra commented Nov 5, 2013

I think I tried 1.6.0 (maybe even 1.6.1) and it had the same problem, namely that the clock in the VM is set to the boot time, rather than current time, of the host. So many Autoconf builds will fail because the sources are in the future.

@rickynils
Copy link
Member Author

@edolstra OK. 1.6.0 was the first version with this problem. Is there a simple way to verify that is also happens in 1.6.1?

@edolstra
Copy link
Member

edolstra commented Nov 5, 2013

You can test it as follows:

$ echo 'with import ./. {}; vmTools.runInLinuxVM (runCommand "foo" {} "date; exit 1")' | nix-build -
Thu Oct 31 10:17:59 UTC 2013
[    0.400772] Power down.

This is with 1.6.1, so the problem still occurs. I'm using Linux 3.4.67 as the host kernel btw, that might matter.

@shlevy
Copy link
Member

shlevy commented Nov 5, 2013

Could we use builtins.currentTime in the runInLinuxVM function somehow?

@bjornfor
Copy link
Contributor

Why don't we set the timestamp of sources back to year 1970 at the end of unpackPhase? (I actually thought nix already did that.)

@rickynils
Copy link
Member Author

@edolstra It actually seems as if this is working correctly now. There must have been something other than qemu that caused the time issue. But now qemu 1.7.0 has been released, so I'll do a PR for that instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants