Guix from qcow2 image refuses to boot after reconfigure

  • Open
  • quality assurance status badge
Details
One participant
  • Jonathan Brielmaier
Owner
unassigned
Submitted by
Jonathan Brielmaier
Severity
normal
J
J
Jonathan Brielmaier wrote on 18 Oct 2021 12:38
(name . bug-guix)(address . bug-guix@gnu.org)
1b267c1b-4f48-c6f7-d122-189c1deed992@web.de
Imagine follow scenario:

wget

Boot the VM:
qemu-system-x86_64 -enable-kvm -m 4G -device e1000,netdev=net0 \
-netdev user,id=net0,hostfwd=tcp::5522-:22 \
-drive
file=guix-system-vm-image-1.3.0.x86_64-linux.qcow2,if=virtio,cache=writeback,werror=report

Inside the VM do a:
sudo su
guix system reconfigure /run/current-system/configuration.scm
reboot

Boot fails (see attached image: failed_boot.png).

Its the same if I do:
sudo su
guix pull
GUIX_PROFILE="$HOME/.config/guix/current"
. "$GUIX_PROFILE/etc/profile"
hash guix
guix system reconfigure /run/current-system/configuration.scm
reboot

~Jonathan
Attachment: failed_boot.png
J
J
Jonathan Brielmaier wrote on 18 Oct 2021 18:10
(address . 51261@debbugs.gnu.org)
d11e40f2-65e5-3443-6126-755bcf471f73@web.de
It's because `/dev/vda1` is mounted to `/`. If I change that to
`/dev/vda2` it works again :)
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 51261@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 51261
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch