Commit graph

1247 commits

Author SHA1 Message Date
Florian Klink fa6c93abe5
linuxPackages.virtualboxGuestAdditions: don't install VBoxOGL for now (#61944)
linuxPackages.virtualboxGuestAdditions: don't install VBoxOGL for now
2019-05-26 12:30:28 +02:00
Ambroz Bizjak 1430e10892 virtualbox: 6.0.6 -> 6.0.8 2019-05-25 21:39:55 +02:00
Florian Klink 8b34ec423c linuxPackages.virtualboxGuestAdditions: don't install VBoxOGL for now
It seems to be broken upstream too, and fixing it is far down the
priority list:
https://www.virtualbox.org/pipermail/vbox-dev/2017-June/014561.html
Additionally, 3d support seems to rely on VBoxOGL.so being symlinked
from libGL.so (which we can't), and Oracle doesn't plan on supporting
libglvnd either. (#18457)
2019-05-23 14:27:05 +02:00
Austin Seipp 99c8680f49 podman: 1.2.0 -> 1.3.1
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-05-23 12:05:48 +02:00
Austin Seipp a86c178a58 conmon: unstable-2019-03-19 -> 0.0.1pre52_6905a4d
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-05-23 12:05:48 +02:00
Tim Steinbach d35692126f
docker: 18.09.5 -> 18.09.6 2019-05-22 09:15:36 -04:00
Sascha Grunert 9b43c29047 cri-o: init at version v1.14.1
This commits adds the CRI-O package, which includes the `crio` binary as
well as `conmon` and `pause`. The configuration is not part of this
package because it would be included in a service.

Signed-off-by: Sascha Grunert <mail@saschagrunert.de>
2019-05-20 11:12:11 +01:00
Spencer Baugh 4b8803dae6 switch users of "gnupg1" to plain "gnupg"
gnupg is gnupg 2.2. gnupg1 is also gnupg 2.2, just with a few extra
symlinks in the bin directory. None of these packages need those
symlinks, and it's confusing for them to say they're depending on
"gnupg1", so switch their dep to plain "gnupg".
2019-05-12 20:08:50 +02:00
Florian Klink 7495a761cc
virtualbox: python2 -> python3 (#61100)
virtualbox: python2 -> python3
2019-05-10 14:54:56 +02:00
Ambroz Bizjak 5bec9dc65b virtualbox: 5.2.28 -> 6.0.6
Quite some fixing was needed to get this to work.

Changes in VirtualBox and additions:

- VirtualBox is no longer officially supported on 32-bit hosts so i686-linux is removed from platforms
  for VirtualBox and the extension pack. 32-bit additions still work.

- There was a refactoring of kernel module makefiles and two resulting bugs affected us which had to be patched.
  These bugs were reported to the bug tracker (see comments near patches).

- The Qt5X11Extras makefile patch broke. Fixed it to apply again, making the libraries logic simpler
  and more correct (it just uses a different base path instead of always linking to Qt5X11Extras).

- Added a patch to remove "test1" and "test2" kernel messages due to forgotten debugging code.

- virtualbox-host NixOS module: the VirtualBoxVM executable should be setuid not VirtualBox.
  This matches how the official installer sets it up.

- Additions: replaced a for loop for installing kernel modules with just a "make install",
  which seems to work without any of the things done in the previous code.

- Additions: The package defined buildCommand which resulted in phases not running, including RUNPATH
  stripping in fixupPhase, and installPhase was defined which was not even run. Fixed this by
  refactoring using phases. Had to set dontStrip otherwise binaries were broken by stripping.
  The libdbus path had to be added later in fixupPhase because it is used via dlopen not directly linked.

- Additions: Added zlib and libc to patchelf, otherwise runtime library errors result from some binaries.
  For some reason the missing libc only manifested itself for mount.vboxsf when included in the initrd.

Changes in nixos/tests/virtualbox:

- Update the simple-gui test to send the right keys to start the VM. With VirtualBox 5
  it was enough to just send "return", but with 6 the Tools thing may be selected by
  default. Send "home" to reliably select Tools, "down" to move to the VM and "return"
  to start it.

- Disable the VirtualBox UART by default because it causes a crash due to a regression
  in VirtualBox (specific to software virtualization and serial port usage). It can
  still be enabled using an option but there is an assert that KVM nested virtualization
  is enabled, which works around the problem (see below).

- Add an option to enable nested KVM virtualization, allowing VirtualBox to use hardware
  virtualization. This works around the UART problem and also allows using 64-bit
  guests, but requires a kernel module parameter.

- Add an option to run 64-bit guests. Tested that the tests pass with that. As mentioned
  this requires KVM nested virtualization.
2019-05-09 23:36:57 +02:00
Graham Christensen e2f6e36401
virtualbox: python2 -> python3 2019-05-07 14:54:39 -04:00
lewo cbb0a0c108
Merge pull request #60466 from vdemeester/update-runc
runc: 1.0.0-rc7 -> 1.0.0-rc8
2019-05-05 09:22:06 +02:00
Mario Rodas 6e90393ead
looking-glass-client: fix build
spice-protocol removed the spice/error_codes.h header file [1], which
looking-glass-client was still using.

[1] 334cef51d0
2019-05-02 22:06:56 -05:00
Vincent Demeester c64087b4a3
runc: 1.0.0-rc7 -> 1.0.0-rc8
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-04-30 10:56:50 +02:00
Artemis Tosini ea29d811b5
virtualbox: 5.2.26 → 5.2.28 2019-04-28 23:07:55 +00:00
Neil Mayhew 48415a20b9 docker: 18.09.2 -> 18.09.5 2019-04-27 17:48:50 -04:00
Neil Mayhew f100ec7939 docker: make overridable 2019-04-27 17:48:50 -04:00
volth 56b25e7034 qemu: fix cross (#60261) 2019-04-27 09:19:06 +02:00
Austin Seipp d3fad881d6
firecracker: 0.15.0 -> 0.15.2
Signed-off-by: Austin Seipp <aseipp@pobox.com>
2019-04-22 11:52:40 -05:00
Vincent Demeester 6adf0f3e9a
containerd: 1.2.5 -> 1.2.6
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-04-09 20:05:38 +02:00
Vladimír Čunát a6dd84a126
Merge #57951: qemu: apply CVE-2019-3812 patch 2019-04-07 11:23:20 +02:00
lewo 79016d9f40
Merge pull request #58732 from r-ryantm/auto-update/open-vm-tools
open-vm-tools: 10.3.5 -> 10.3.10
2019-04-06 19:29:35 +02:00
Vincent Demeester 91fc821cc1
podman: 1.1.2 -> 1.2.0
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-04-05 16:56:37 +02:00
markuskowa 3eecb297bc
Merge pull request #58936 from bzizou/charliecloud
charliecloud: init at 0.9.8
2019-04-04 14:43:36 +02:00
Bruno Bzeznik 8a298f8d5a charliecloud: init at 0.9.8 2019-04-04 14:16:48 +02:00
R. RyanTM 475ea05064 open-vm-tools: 10.3.5 -> 10.3.10
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/open-vm-tools/versions
2019-04-01 21:24:10 -07:00
Vincent Demeester 28a2dd8024
runc: 1.0.0-rc6 -> 1.0.0-rc7
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-03-29 11:12:04 +01:00
Andreas Rammhold c7d7c6fc41
qemu: apply CVE-2019-3812 patch 2019-03-20 11:15:41 +01:00
aszlig 12efcc2dee
Merge overlayfs fix, LTS kernel bump and test
In Linux 4.19 there has been a major rework of the overlayfs
implementation and it now opens files in lowerdir with O_NOATIME, which
in turn caused issues in our VM tests because the process owner of QEMU
doesn't match the file owner of the lowerdir.

The crux here is that 9p propagates the O_NOATIME flag to the host and
the guest kernel has no way of verifying whether that flag will lead to
any problems beforehand.

There is ongoing work to possibly fix this in the kernel, but it will
take a while until there is a working patch and consensus.

So in order to bring our default kernel back to 4.19 and of course make
it possible to run newer kernels in VM tests, I'm merging a small QEMU
patch as an interim solution, which we can drop once we have a working
fix in the next round of stable kernels.

Now we already had Linux 4.19 set as the default kernel, but that was
subsequently reverted in 048c36ccaa
because the patch we have used was the revert of the commit I bisected a
while ago.

This patch broke overlayfs in other ways, so I'm also merging in a VM
test by @bachp, which only tests whether overlayfs is working, just to
be on the safe side that something like this won't happen in the future.

Even though this change could be considered a moderate mass-rebuild at
least for GNU/Linux, I'm merging this to master, mainly to give us some
time to get it into the current 19.03 release branch (and subsequent
testing window) once we got no new breaking builds from Hydra.

Cc: @samueldr, @lheckemann

Fixes: https://github.com/NixOS/nixpkgs/issues/54509
Fixes: https://github.com/NixOS/nixpkgs/issues/48828
Merges: https://github.com/NixOS/nixpkgs/pull/57641
Merges: https://github.com/NixOS/nixpkgs/pull/54508
2019-03-19 00:15:51 +01:00
Jason Samsa a7147c868f update xhyve to tip of master 2019-03-18 17:39:18 -05:00
aszlig 4c1ddb3a57
qemu: Apply interim fix for overlayfs + O_NOATIME
Our VM tests and everything related to our virtualisation infrastructure
is currently broken if used with kernel 4.19 or later.

The reason for this is that since 4.19, overlayfs uses the O_NOATIME
flag when opening files in lowerdir and this doesn't play nice with the
way we pass the Nix store to our QEMU guests.

On a NixOS system, paths in the Nix store are typically owned by root
but the QEMU process is usually run by an ordinary user. Using O_NOATIME
on a file where you're not the owner (or superuser) will return with
EPERM (Operation not permitted).

This is exactly what happens in our VM tests, because we're using
overlayfs in the guests to allow writes to the store.

Another implication of this is that the default kernel version for NixOS
19.03 has been reverted to Linux 4.14.

Work on getting this upstream is still ongoing and the patch I posted
previously was incomplete, needs rework and also some more review from
upstream maintainers - in summary: This will take a while.

So instead of rushing in a kernel patch to nixpkgs, which will affect
all users of overlayfs, not just NixOS VM tests, I opted to patch QEMU
for now to ignore the O_NOATIME flag in 9p.

I think this is also the least impacting change, because even if you
care about whether access times are written or not, you get the same
behaviour as with Linux 4.19 in conjunction with QEMU.

Signed-off-by: aszlig <aszlig@nix.build>
Fixes: https://github.com/NixOS/nixpkgs/issues/54509
2019-03-18 13:34:30 +01:00
Vincent Demeester 115dde6d33
containerd: 1.2.4 -> 1.2.5
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-03-14 17:05:29 +01:00
Jascha Geerds ffedc3e4a9 misc: Remove myself from list of maintainers
Unfortunately I don't have the time anymore to maintain those
packages.
2019-03-12 23:50:52 +01:00
Florian Franzen 871c1d5bb1 virtmanager: Fix gobject-introspection (#57385) 2019-03-12 22:29:45 +01:00
Michael Raskin fdeb864cc8
Merge pull request #57498 from r-ryantm/auto-update/virt-viewer
virt-viewer: 7.0 -> 8.0
2019-03-12 15:28:30 +00:00
R. RyanTM 8f92b77ab4 virt-viewer: 7.0 -> 8.0
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/virt-viewer/versions
2019-03-12 02:09:33 -07:00
Wael M. Nasreddine eee09b103c
docker: export GOCACHE for all platforms 2019-03-11 09:59:10 -07:00
Vincent Demeester 54cf5b4bbf containerd: 1.2.2 -> 1.2.4 (#56947)
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-03-08 22:56:00 +01:00
Vincent Demeester 1bd0655e6d podman: 1.1.0 -> 1.1.2 (#56945)
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-03-08 22:31:58 +01:00
lewo f5462b19d5
Merge pull request #56513 from vdemeester/update-podman
Update podman
2019-03-05 21:12:51 +01:00
Jörg Thalheim 27cb0669c6
Merge pull request #56500 from kalbasit/nixpkgs_add-support-go-1-12
go_1_12: init at go 1.12
2019-03-04 14:22:27 +00:00
jD91mZM2 4901af69c5 x11docker: v5.4.1 -> v5.4.4 (#56570) 2019-03-04 13:38:19 +01:00
Wael M. Nasreddine 6ef04cabd4
go_1_12: init at go 1.12 2019-03-02 14:24:17 -08:00
R. RyanTM d047e1e397 docker-compose: 1.23.1 -> 1.23.2
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/docker-compose/versions
2019-03-01 18:16:02 -08:00
Frederik Rietdijk 2fcb11a244 Merge staging-next into master 2019-03-01 09:06:20 +01:00
Vincent Demeester 42a79f7bc2
podman: 1.0.0 -> 1.1.0
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-02-28 11:54:53 +01:00
Vincent Demeester e8a4d2a2be
conmon: unstable-2018-11-28 -> unstable-2019-02-15
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
2019-02-28 11:25:24 +01:00
Averell Dalton d6c2fe76ed nvidia-docker: init at 2.0.3
nvidia_x11 and persistenced were modified to provide binaries which can be
mounted inside a docker-container to be executed there.

most ldconfig-based discovery of bundled nvidia libraries is patched out

ldconfig itself is patched to be able to deal with patchelf'ed libraries
See https://sourceware.org/bugzilla/show_bug.cgi?id=23964
2019-02-27 09:56:03 +01:00
Frederik Rietdijk c2eac6741b Merge master into staging-next 2019-02-24 09:19:12 +01:00
Florian Klink 29d7e7a0c6 virtualbox: 5.2.22 -> 5.2.26 (#56210) 2019-02-22 17:55:47 -08:00