Skip to content

Releases: reindertpelsma/nvkvm-pv

nvkvm v0.2.5

Choose a tag to compare

@github-actions github-actions released this 05 Sep 18:22

Both artifacts below were built from this tag by
.github/workflows/release.yml
on a GitHub-hosted runner and carry a build-provenance attestation.
Verify before you run either — an attestation nobody checks is decoration.

Container (the quick way in)

gh attestation verify oci://ghcr.io/reindertpelsma/nvkvm-pv:v0.2.5 --repo reindertpelsma/nvkvm-pv
docker run --rm -it --device /dev/kvm --gpus all \
    -e NVIDIA_DRIVER_CAPABILITIES=compute,utility,graphics,display,video \
    -p 127.0.0.1:2222:2222 -v nvkvm-guest:/opt/nvkvm-guest \
    ghcr.io/reindertpelsma/nvkvm-pv:v0.2.5

Needs /dev/kvm and, for the GPU, the NVIDIA container runtime. Note
that in a container the isolate falls back to UID separation, which is
weaker than the namespaced sandbox — see SECURITY.md.

Prebuilt tarball (bare host)

gh attestation verify nvkvm-v0.2.5-linux-x86_64.tar.gz --repo reindertpelsma/nvkvm-pv
tar xzf nvkvm-v0.2.5-linux-x86_64.tar.gz && cd nvkvm-v0.2.5
sudo cp -a qemu-nvkvm /opt/qemu-nvkvm
sudo install -Dm755 src/stub/nvkvm_stub /usr/lib/nvkvm/nvkvm_stub

x86-64 only, headless QEMU, glibc floor and the full contents are in
RELEASE.md inside the tarball. The guest kernel module is not
prebuilt — it is compiled against your guest's kernel from
src/guest/, which is why the sources ship with it.


Full Changelog: v0.2.4...v0.2.5

nvkvm v0.2.4

Choose a tag to compare

@github-actions github-actions released this 04 Sep 12:27

Both artifacts below were built from this tag by
.github/workflows/release.yml
on a GitHub-hosted runner and carry a build-provenance attestation.
Verify before you run either — an attestation nobody checks is decoration.

Container (the quick way in)

gh attestation verify oci://ghcr.io/reindertpelsma/nvkvm-pv:v0.2.4 --repo reindertpelsma/nvkvm-pv
docker run --rm -it --device /dev/kvm --gpus all \
    -e NVIDIA_DRIVER_CAPABILITIES=compute,utility,graphics,display,video \
    -p 127.0.0.1:2222:2222 -v nvkvm-guest:/opt/nvkvm-guest \
    ghcr.io/reindertpelsma/nvkvm-pv:v0.2.4

Needs /dev/kvm and, for the GPU, the NVIDIA container runtime. Note
that in a container the isolate falls back to UID separation, which is
weaker than the namespaced sandbox — see SECURITY.md.

Prebuilt tarball (bare host)

gh attestation verify nvkvm-v0.2.4-linux-x86_64.tar.gz --repo reindertpelsma/nvkvm-pv
tar xzf nvkvm-v0.2.4-linux-x86_64.tar.gz && cd nvkvm-v0.2.4
sudo cp -a qemu-nvkvm /opt/qemu-nvkvm
sudo install -Dm755 src/stub/nvkvm_stub /usr/lib/nvkvm/nvkvm_stub

x86-64 only, headless QEMU, glibc floor and the full contents are in
RELEASE.md inside the tarball. The guest kernel module is not
prebuilt — it is compiled against your guest's kernel from
src/guest/, which is why the sources ship with it.


Full Changelog: v0.2.3...v0.2.4

nvkvm v0.2.3

Choose a tag to compare

@github-actions github-actions released this 04 Sep 06:07

Both artifacts below were built from this tag by
.github/workflows/release.yml
on a GitHub-hosted runner and carry a build-provenance attestation.
Verify before you run either — an attestation nobody checks is decoration.

Container (the quick way in)

gh attestation verify oci://ghcr.io/reindertpelsma/nvkvm-pv:v0.2.3 --repo reindertpelsma/nvkvm-pv
docker run --rm -it --device /dev/kvm --gpus all \
    -e NVIDIA_DRIVER_CAPABILITIES=compute,utility,graphics,display,video \
    -p 127.0.0.1:2222:2222 -v nvkvm-guest:/opt/nvkvm-guest \
    ghcr.io/reindertpelsma/nvkvm-pv:v0.2.3

Needs /dev/kvm and, for the GPU, the NVIDIA container runtime. Note
that in a container the isolate falls back to UID separation, which is
weaker than the namespaced sandbox — see SECURITY.md.

Prebuilt tarball (bare host)

gh attestation verify nvkvm-v0.2.3-linux-x86_64.tar.gz --repo reindertpelsma/nvkvm-pv
tar xzf nvkvm-v0.2.3-linux-x86_64.tar.gz && cd nvkvm-v0.2.3
sudo cp -a qemu-nvkvm /opt/qemu-nvkvm
sudo install -Dm755 src/stub/nvkvm_stub /usr/lib/nvkvm/nvkvm_stub

x86-64 only, headless QEMU, glibc floor and the full contents are in
RELEASE.md inside the tarball. The guest kernel module is not
prebuilt — it is compiled against your guest's kernel from
src/guest/, which is why the sources ship with it.


Full Changelog: v0.2.2...v0.2.3

nvkvm v0.2.2

Choose a tag to compare

@github-actions github-actions released this 03 Sep 21:43

Both artifacts below were built from this tag by
.github/workflows/release.yml
on a GitHub-hosted runner and carry a build-provenance attestation.
Verify before you run either — an attestation nobody checks is decoration.

Container (the quick way in)

gh attestation verify oci://ghcr.io/reindertpelsma/nvkvm-pv:v0.2.2 --repo reindertpelsma/nvkvm-pv
docker run --rm -it --device /dev/kvm --gpus all \
    -e NVIDIA_DRIVER_CAPABILITIES=compute,utility,graphics,display,video \
    -p 127.0.0.1:2222:2222 -v nvkvm-guest:/opt/nvkvm-guest \
    ghcr.io/reindertpelsma/nvkvm-pv:v0.2.2

Needs /dev/kvm and, for the GPU, the NVIDIA container runtime. Note
that in a container the isolate falls back to UID separation, which is
weaker than the namespaced sandbox — see SECURITY.md.

Prebuilt tarball (bare host)

gh attestation verify nvkvm-v0.2.2-linux-x86_64.tar.gz --repo reindertpelsma/nvkvm-pv
tar xzf nvkvm-v0.2.2-linux-x86_64.tar.gz && cd nvkvm-v0.2.2
sudo cp -a qemu-nvkvm /opt/qemu-nvkvm
sudo install -Dm755 src/stub/nvkvm_stub /usr/lib/nvkvm/nvkvm_stub

x86-64 only, headless QEMU, glibc floor and the full contents are in
RELEASE.md inside the tarball. The guest kernel module is not
prebuilt — it is compiled against your guest's kernel from
src/guest/, which is why the sources ship with it.


Full Changelog: v0.2.1...v0.2.2

nvkvm v0.2.1

Choose a tag to compare

@github-actions github-actions released this 03 Sep 12:07

Both artifacts below were built from this tag by
.github/workflows/release.yml
on a GitHub-hosted runner and carry a build-provenance attestation.
Verify before you run either — an attestation nobody checks is decoration.

Container (the quick way in)

gh attestation verify oci://ghcr.io/reindertpelsma/nvkvm-pv:v0.2.1 --repo reindertpelsma/nvkvm-pv
docker run --rm -it --device /dev/kvm --gpus all \
    -e NVIDIA_DRIVER_CAPABILITIES=compute,utility,graphics,display,video \
    -p 127.0.0.1:2222:2222 -v nvkvm-guest:/opt/nvkvm-guest \
    ghcr.io/reindertpelsma/nvkvm-pv:v0.2.1

Needs /dev/kvm and, for the GPU, the NVIDIA container runtime. Note
that in a container the isolate falls back to UID separation, which is
weaker than the namespaced sandbox — see SECURITY.md.

Prebuilt tarball (bare host)

gh attestation verify nvkvm-v0.2.1-linux-x86_64.tar.gz --repo reindertpelsma/nvkvm-pv
tar xzf nvkvm-v0.2.1-linux-x86_64.tar.gz && cd nvkvm-v0.2.1
sudo cp -a qemu-nvkvm /opt/qemu-nvkvm
sudo install -Dm755 src/stub/nvkvm_stub /usr/lib/nvkvm/nvkvm_stub

x86-64 only, headless QEMU, glibc floor and the full contents are in
RELEASE.md inside the tarball. The guest kernel module is not
prebuilt — it is compiled against your guest's kernel from
src/guest/, which is why the sources ship with it.


Full Changelog: v0.2.0...v0.2.1

nvkvm v0.2.0

Choose a tag to compare

@github-actions github-actions released this 02 Sep 20:07

Both artifacts below were built from this tag by
.github/workflows/release.yml
on a GitHub-hosted runner and carry a build-provenance attestation.
Verify before you run either — an attestation nobody checks is decoration.

Container (the quick way in)

gh attestation verify oci://ghcr.io/reindertpelsma/nvkvm-pv:v0.2.0 --repo reindertpelsma/nvkvm-pv
docker run --rm -it --device /dev/kvm --gpus all \
    -e NVIDIA_DRIVER_CAPABILITIES=compute,utility,graphics,display,video \
    -p 127.0.0.1:2222:2222 -v nvkvm-guest:/opt/nvkvm-guest \
    ghcr.io/reindertpelsma/nvkvm-pv:v0.2.0

Needs /dev/kvm and, for the GPU, the NVIDIA container runtime. Note
that in a container the isolate falls back to UID separation, which is
weaker than the namespaced sandbox — see SECURITY.md.

Prebuilt tarball (bare host)

gh attestation verify nvkvm-v0.2.0-linux-x86_64.tar.gz --repo reindertpelsma/nvkvm-pv
tar xzf nvkvm-v0.2.0-linux-x86_64.tar.gz && cd nvkvm-v0.2.0
sudo cp -a qemu-nvkvm /opt/qemu-nvkvm
sudo install -Dm755 src/stub/nvkvm_stub /usr/lib/nvkvm/nvkvm_stub

x86-64 only, headless QEMU, glibc floor and the full contents are in
RELEASE.md inside the tarball. The guest kernel module is not
prebuilt — it is compiled against your guest's kernel from
src/guest/, which is why the sources ship with it.


Full Changelog: v0.1.0...v0.2.0

nvkvm v0.1.0

Choose a tag to compare

@github-actions github-actions released this 21 Aug 22:49

Both artifacts below were built from this tag by
.github/workflows/release.yml
on a GitHub-hosted runner and carry a build-provenance attestation.
Verify before you run either — an attestation nobody checks is decoration.

Container (the quick way in)

gh attestation verify oci://ghcr.io/reindertpelsma/nvkvm-pv:v0.1.0 --repo reindertpelsma/nvkvm-pv
docker run --rm -it --device /dev/kvm --gpus all \
    -e NVIDIA_DRIVER_CAPABILITIES=compute,utility,graphics,display,video \
    -p 127.0.0.1:2222:2222 -v nvkvm-guest:/opt/nvkvm-guest \
    ghcr.io/reindertpelsma/nvkvm-pv:v0.1.0

Needs /dev/kvm and, for the GPU, the NVIDIA container runtime. Note
that in a container the isolate falls back to UID separation, which is
weaker than the namespaced sandbox — see SECURITY.md.

Prebuilt tarball (bare host)

gh attestation verify nvkvm-v0.1.0-linux-x86_64.tar.gz --repo reindertpelsma/nvkvm-pv
tar xzf nvkvm-v0.1.0-linux-x86_64.tar.gz && cd nvkvm-v0.1.0
sudo cp -a qemu-nvkvm /opt/qemu-nvkvm
sudo install -Dm755 src/stub/nvkvm_stub /usr/lib/nvkvm/nvkvm_stub

x86-64 only, headless QEMU, glibc floor and the full contents are in
RELEASE.md inside the tarball. The guest kernel module is not
prebuilt — it is compiled against your guest's kernel from
src/guest/, which is why the sources ship with it.


Full Changelog: v0.0.1-rc2...v0.1.0

nvkvm v0.0.1-rc2

nvkvm v0.0.1-rc2 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 21 Aug 02:43

Both artifacts below were built from this tag by
.github/workflows/release.yml
on a GitHub-hosted runner and carry a build-provenance attestation.
Verify before you run either — an attestation nobody checks is decoration.

Container (the quick way in)

gh attestation verify oci://ghcr.io/reindertpelsma/nvkvm-pv:v0.0.1-rc2 --repo reindertpelsma/nvkvm-pv
docker run --rm -it --device /dev/kvm --gpus all \
    -e NVIDIA_DRIVER_CAPABILITIES=compute,utility,graphics,display,video \
    -p 127.0.0.1:2222:2222 -v nvkvm-guest:/opt/nvkvm-guest \
    ghcr.io/reindertpelsma/nvkvm-pv:v0.0.1-rc2

Needs /dev/kvm and, for the GPU, the NVIDIA container runtime. Note
that in a container the isolate falls back to UID separation, which is
weaker than the namespaced sandbox — see SECURITY.md.

Prebuilt tarball (bare host)

gh attestation verify nvkvm-v0.0.1-rc2-linux-x86_64.tar.gz --repo reindertpelsma/nvkvm-pv
tar xzf nvkvm-v0.0.1-rc2-linux-x86_64.tar.gz && cd nvkvm-v0.0.1-rc2
sudo cp -a qemu-nvkvm /opt/qemu-nvkvm
sudo install -Dm755 src/stub/nvkvm_stub /usr/lib/nvkvm/nvkvm_stub

x86-64 only, headless QEMU, glibc floor and the full contents are in
RELEASE.md inside the tarball. The guest kernel module is not
prebuilt — it is compiled against your guest's kernel from
src/guest/, which is why the sources ship with it.


Full Changelog: https://github.com/reindertpelsma/nvkvm-pv/commits/v0.0.1-rc2