<Elephant454>I'm a little bit confused on the concept of creating a vm using Guix. What is the difference between "guix system vm example.scm" and "guix system vm-image"? What do the "boot-loader" and "file-system" fields to in the context of these?
<Elephant454>I'm trying to create a clean throw-away environment for testing Emacs, StumpWM, etc configs (on a clean install with a clean home directory), and I'm trying to figure out the best Guix faculty to go about doing that. 🙂
<brendyyn>Elephant454: vm creates all the required packages in the store, and an .sh script ready to launch the qemu vm, where it uses all the files in your host /gnu/store.
<brendyyn>Elephant454: vm-image creates an actual image that could be put on to a thumb drive with `cat' and booted in to
<brendyyn>... but could also be booted with qemu, but in that case all it's packages are embedded in that image file, rather than being a in the /gnu/store file system.
<Elephant454>brendyyn: That makes sense. 🙂 I'm still a little confused, on a couple other related things, though. I'm trying to think how to best combine questions so as to ask the least necessary...
<Elephant454>brendyyn: Is the vm-image mutable? Does it contain a filesystem that gets modified if it is on a medium that allows that (like if it's being booted with QEMU from the guix store)?
<brendyyn>Elephant454: IRC is not so formal, you can just ask what you want. Sometimes I just talk to myself in here when I'm trying to solve something that is stressing me, and maybe someone else chooses to help me
<brendyyn>Elephant454: I'm not sure, I guess you could copy the image out of the store and that would be the case. It is a qcow2 image with an ext4 file system by default, So I think you could
<Elephant454>My only real consistent IRC experience is in the Arch Linux channel asking for help, and there you essentially have to have the question you have so well researched you essentially answer it yourself. 😅
<Elephant454>Alright, that makes sense. That's consistent with the bits and pieces I've seen. I wasn't sure if the image was immutable, because I've seen other QEMU images need to be layered on top of in order to save changes, but I guess that isn't the case with qcow?
<Elephant454>The main thing that was tripping me up was what the "file-systems" and "bootloader" entries in the "operating-system" function should be in this context. Are these actual locations of where the bootloader and some form of persistent storage should be, or are these virtual and created inside a virtual filesystem made for the vm? I was wondering if I have to find a place to store for myself, or if a virtual place is created by "guix
<archetyp>rekado: yes, Hurd is already in a usable state, but not v1.0
<brendyyn>That's why I think there is a pragmatic aspect and humanistic aspect to IRC. I will try to do as much as I can on my own before asking questions, but sometimes i just want to talk to another person. I think in the last several years I've met only 1 person in meatspace that has heard of GNU, and 0 people that actually run GNU/Linux, so the internet is my only source of interaction when I'm hacking and learning
<espectalll[m]>I'm getting it to work, however, by using Rufus' (please forgive me Stallman) ISO mode with MBR partitioning... where I can only get to the GRUB boot mode but using BIOS compatibility mode
<roptat>for instance "val foo = <bar></bar>" is a valid scala expression
<plasma41>rekado: I just burned the x86_64 ISO to a DVD and tried to install using it on the same hardware. I face the exact same issue as with the i686 version. The hardware is an old dual-core x86_64 box.
<taylan>hmm, guix gc freed about 24G of space, hope I didn't delete one symlink too many :D
<taylan>quite possible that I had several outdated whole systems there though
<lfam>If they span multiple 'core-updates' cycles they can be quite large
<espectalll[m]>Guys, it's the UUID duplication thing that makes my Mac unable to boot
<espectalll[m]>Why is that used? Should I just report it through the mailing list?
<rekado>espectalll[m]: feel free to send mail to guix-devel to discuss this. I don’t know why there would be UUID duplication.
<plasma41>espectalll[m]: I'm experiencing the exact same 'waiting for partition "31393730-3031-3031-3139-313631383738"' problem as you. I tried both i686 and x86_64 versions of the 0.16.0 install ISO. Problem is present in both.
<Laalf>hello. does someone have a config for cuirass for me? i dont have a lot of space and i am scared it would fill my ssd in no time. cuirass-service-type says nothing about autoclean if i see that right