guix system vm-image ignores filesystem type

  • Open
  • quality assurance status badge
Details
One participant
  • Jack Hill
Owner
unassigned
Submitted by
Jack Hill
Severity
normal
Merged with
J
J
Jack Hill wrote on 19 Jan 2021 02:12
(address . bug-guix@gnu.org)
alpine.DEB.2.21.2101181955250.2314@marsh.hcoop.net
Hi Guix,

I believe that this is a feature request. I would like to create a Guix
qcow2 image to run as a VM. Additionally, I would like the root file
system to be btrfs. Therefore, I created an operating system definition
with the following file-systems:

```
(file-systems (cons (file-system
(mount-point "/")
(device "/dev/vda1")
(type "btrfs")
(flags '(no-atime))
(options "compress=zstd"))
%base-file-systems))
```

I then ran `guix system vm-image --image-size=10G --volatile config.scm`.
That successfully created a qcow2 image, but the root file system was ext4
instead of btrfs.

Ideally, I would get an image with a btrfs filesystem. I expect supporting
all combinations of filesystems and mapped devices might be challenging
for the image creation process, but some more options might be
interesting. At the very least, I think a warning or error when the
requested configuration is not supported would be appropriate.

What do you think about this feature?

Best,
Jack
J
J
Jack Hill wrote on 2 Feb 2021 18:17
Duplicate tickets for file system type in images
(address . control@debbugs.gnu.org)
alpine.DEB.2.21.2102021216590.11419@marsh.hcoop.net
merge 45974 42315

Thanks
?
Your comment

Commenting via the web interface is currently disabled.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 45974
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