Hi,

reply to myself:

Giovanni Biscuolo <g@xelera.eu> writes:

[...]

> 7. start the VM, connect via SPICE and see the VM does not boot due to
> an error in procedure mount, falling back to the guile REPL; the backtrace
> is:
>
> --8<---------------cut here---------------start------------->8---
> In gnu/build/linux-boot.scm:
>    516:13  2 (_)
>     367:8  1 (mount-root-file-system "/dev/vda1" "ext4" # _)
> In unknown file:
>            0 (mount "/dev/vda1" "/real-root" "ext4" 1 #<undefined>)
> --8<---------------cut here---------------end--------------->8---

OK I solved this, it was "virsh domxml-from-native" that missed to detect
the correct disk type of the vda disk, so I changed this part of the XML
domain definition:

--8<---------------cut here---------------start------------->8---
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='writeback' error_policy='report'/>
      <source file='/gnu/store/4mz1qqv7h5g5885q1aq0izlmy01knf1g-qemu-image'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </disk>
--8<---------------cut here---------------end--------------->8---

type='raw' changed to type='qcow2'

but now I've a problem with the /gnu/store mount in guest

"9pnet_virtio: no channels available for device TAGjoptajej2oynju6yvboauz7pl6uj"

...still missimg someting

any hint please?

Thanks!