| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2023-03-05 | debvm-create: extend examples in the manual page | Helmut Grohne | |
| 2023-03-05 | debvm-run: always use virtio input devices for graphical mode | Helmut Grohne | |
| These clearly benefit the amd64 case as well. Experience with the virtio gpu is not as clear cut as it may crash qemu. | |||
| 2023-03-02 | debvm-run: be more explicit about graphics and cloud kernels | Helmut Grohne | |
| Reported-by: Arnd Bergmann <arnd@arndb.de> | |||
| 2023-03-02 | debvm-run: improve graphical experience on !x86 | Arnd Bergmann | |
| 2023-02-28 | upload 0.2.9 to unstable | Helmut Grohne | |
| 2023-02-23 | debvm-create: also support --initsystem=busybox | Helmut Grohne | |
| Reported-by: Johannes Schauer Marin Rodrigues <josch@debian.org> | |||
| 2023-02-23 | debvm-create: also support --initsystem=runit | Helmut Grohne | |
| 2023-02-23 | debvm-create: do not fsck | Helmut Grohne | |
| Asking for a fsck pass in fstab is not what we want. Requiring fsck makes sysvinit fail when fsck.ext4 is missing. Without that pass, it happily boots without e2fsprogs. Link: https://bugs.debian.org/1028267 Thanks: Thorsten Glaster <t.glaser@tarent.de> | |||
| 2023-02-20 | debvm-create: add --initsystem option | Helmut Grohne | |
| This option allows changing the init system. The notable addition is sysv. | |||
| 2023-02-20 | debvm-create: fix graphical sysv autologin | Helmut Grohne | |
| 2023-02-20 | debvm-create: extend autologin hook to work with sysvinit | Helmut Grohne | |
| 2023-02-20 | debvm-create: avoid failing when we install no passwd | Helmut Grohne | |
| 2023-02-10 | upload 0.2.8 to unstable: more autopkgtest fixing | Helmut Grohne | |
| 2023-02-09 | autopkgtest: improve unprivieleged unshare condition | Helmut Grohne | |
| Thanks to Johannes Schauer for trying it on debci and seeing that it properly tests the environment. | |||
| 2023-02-08 | autopkgtests: drop versioned qemu dependency | Helmut Grohne | |
| Since qemu-kvm is virtual, it doesn't have a version and we cannot depend on it like that. Rather than revert back to qemu-system-misc (which would defeat the purpose), just drop the dependency as testing has a fixed version now. Thanks to Jochen Sprickerhof for explaining the cause of badpkg. | |||
| 2023-02-05 | upload 0.2.7 to unstable: autopkgtest without fakechroot | Helmut Grohne | |
| 2023-02-05 | debvm-create: fix resizing of output image | Helmut Grohne | |
| resize2fs -b will not actually perform a resize. Rather, it will truncate the file to the filesystem length, reversing the earlier truncate call. Thus we need second resize2fs call to change the size of the filesystem. Fixes: 09bcaa8fe901 ("debvm-create: make the ext4 look more like ext4") | |||
| 2023-02-05 | debvm-create: add --skip=initsystem | Helmut Grohne | |
| Closes: #1030254 | |||
| 2023-02-05 | debvm-create: install systemd-sysv rather than init | Helmut Grohne | |
| We actually expect systemd in the network configuration. Be more honest about this. | |||
| 2023-02-05 | debian: autopkgtest: do away with fakeroot | Helmut Grohne | |
| Use two tests. One in --mode=root and another skippable one in --mode=unshare. The latter will likely be skipped on Debian infrastructure. | |||
| 2023-02-03 | Merge branch tar-output into main | Helmut Grohne | |
| Closes: !29 | |||
| 2023-02-03 | debvm-create: update documentation for --skip=ext4 | Helmut Grohne | |
| 2023-02-02 | debvm-create: Output image in tar format if step "ext4" is skipped | Gioele Barabucci | |
| Outputting the image in tar format breaks interoperability with `debvm-run`, but makes it easier to inspect, convert or perform additional modifications of the generated image. | |||
| 2023-02-02 | debvm-run: deal with arbitrary disk labels | Helmut Grohne | |
| Reported-by: Gioele Barabucci <gioele@svario.it> Closes: #1030255 | |||
| 2023-02-02 | debvm-create: make the ext4 look more like ext4 | Helmut Grohne | |
| One notable difference remains. metadata_csum keeps missing as tune2fs insists on doing this interactively only. Reported-by: Gioele Barabucci <gioele@svario.it> Closes: #1030252 | |||
| 2023-02-01 | debian: add qemu as test trigger | Helmut Grohne | |
| It's only a trigger for s390x yet, due to being a dependency of debvm otherwise. | |||
| 2023-01-27 | upload as 0.2.6 to unstable in another attempt at autopkgtests | Helmut Grohne | |
| 2023-01-27 | debian: autopkgtest: disable on armel and armhf as they're too slow | Helmut Grohne | |
| 2023-01-27 | debian: autopkgtest: stop triggering on unused 686-pae kernel image | Helmut Grohne | |
| 2023-01-27 | debian: autopkgtests: depend on suitably recent fakechroot | Helmut Grohne | |
| 2023-01-26 | debian: autopkgtest needs file on i386 to refine arch guess | Helmut Grohne | |
| 2023-01-26 | debvm-run: be a bit more verbose about detected architecture | Helmut Grohne | |
| 2023-01-25 | upload as 0.2.5 to unstable | Helmut Grohne | |
| 2023-01-25 | Merge branch 'multiarch' into 'main' | Helmut Grohne | |
| install and use multiarch kernels for sibling architectures See merge request helmutg/debvm!28 | |||
| 2023-01-25 | debvm-run: always pass gic-version=max for arm64 | Helmut Grohne | |
| We already pass it in the kvm case where it should become host and all should be fine. However in the non-kvm case, the default gic can only support 8 cores. If we want to go beyond that, we need a higher gic-version. We couldn't measure a performance difference between max and unset, so we'll just always pass max. Thanks: Arnd Bergmann <arnd@arndb.de> Thanks: Johannes Schauer Marin Rodrigues <josch@debian.org> | |||
| 2023-01-25 | debvm-run: disable kvm for armhf -> arm64 when the cpu cannot run it | Helmut Grohne | |
| Reported-by: Arnd Bergmann <arnd@arndb.de> | |||
| 2023-01-25 | debvm-run: internally differentiate between VMARCH and KERNELARCH | Helmut Grohne | |
| In a multiarch setting, VMARCH shall describe the contained userland and KERNELARCH shall describe the architecture of the contained kernel. | |||
| 2023-01-25 | debvm-run: make shellcheck happy | Helmut Grohne | |
| Fixes: 66b9374cc19c ("debvm-run: extract kernel image before inspecting it") | |||
| 2023-01-25 | debvm-run: also handle upgrading arm | Helmut Grohne | |
| elf-arch may report armel and armhf as arm. | |||
| 2023-01-25 | debvm-run: extract kernel image before inspecting it | Helmut Grohne | |
| Reported-by: Arnd Bergmann <arnd@arndb.de> | |||
| 2023-01-25 | tests: use an amd64 kernel on i386 | Helmut Grohne | |
| 2023-01-25 | debvm-create: handle multiarch kernel for 32bit+64bit arm | Helmut Grohne | |
| 2023-01-25 | debvm-run: handle some multiarch kernels | Helmut Grohne | |
| We completely treat all 32bit arm as armhf now. Booting the rpi kernel installed by debvm-create for armel will not work at all. The only sane way to boot armel is to enable a multiarch kernel. Refine the VMARCH guess from /bin/true using the file output for the kernel image for the common cases of i386+amd64 and armel/armhf+arm64. | |||
| 2023-01-24 | debvm-run: do not pass -smp on unicore systems | Helmut Grohne | |
| 2023-01-24 | tests: add armel with an armhf kernel | Helmut Grohne | |
| 2023-01-24 | debvm-create: install better kernels in multiarch case | Helmut Grohne | |
| While this works for armel+armhf by sheer luck, debvm-run fails for i386+amd64 as it selects qemu-system-i386. | |||
| 2023-01-24 | debvm-create: fix parsing dpkg architecture in multiarch case | Helmut Grohne | |
| 2023-01-24 | tests: bump up timeout for create-and-run.sh | Helmut Grohne | |
| Timeouts were hit on salsa-ci for arm64 occasionally. The armhf autopkgtest also runs into this timeout. | |||
| 2023-01-23 | upload debvm/0.2.4 to unstable | Helmut Grohne | |
| 2023-01-23 | debian: fix placement of general mmdebstrap hooks | Helmut Grohne | |
 |
index : ~helmut/debvm.git | |
| A tool for creating and running Debian-based VMs | Helmut Grohne |
| summaryrefslogtreecommitdiff |