This makes it a bit more similar to Guix system configurations that
separate bootloaders and filesystem/block devices.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
I forgot to remove the trisquel-netinst_11.0_amd64.iso.asc file in the
commit fed7db636e
("trisquel-automatic-netinstall-qemu: Update to Trisquel 11.0.1.").
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
I forgot to update the README as well in the commit
fed7db636e
("trisquel-automatic-netinstall-qemu: Update to Trisquel 11.0.1.").
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
The commit b264ddedb1
("trisquel-automatic-netinstall-qemu: Fix -cpu host without KVM.")
only contained part of the fix.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Without that fix, when KVM is disabled, we have the following:
qemu-system-x86_64: CPU model 'host' requires KVM or HVF
and since HVF is only available on MacOS[1], and that MacOS is nonfree
we won't be using it when KVM isn't available.
[1]https://www.qemu.org/docs/master/system/introduction.html
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
This should improve the performances a bit as this mostly pass through
the host CPU, and so the VM can benefit from some of the more advanced
CPU features. Depending on the CPU and host configuration, it can also
enable other features as well like nested KVM.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Some 'string' were aligned with the di-question. In addition I also
separated the response type and values in a different column to make
it easier to detect this kind of mistakes.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
