Hi Francesco,

Quoting Francesco Poli (2022-02-26 00:35:01)
> At least, it completes without any error.
> And it generates a 'debian-unstable.qcow2' image that can boot, if I
> test it with:
> 
>   $ qemu-system-x86_64 -enable-kvm -m 512 -serial 
> unix:/tmp/ttyS0,server,nowait -drive  
> "file=./debian-unstable.qcow2,cache=unsafe,if=virtio,index=0"
> 
> I can even login as root (password-less!) in the graphical window that
> QEMU shows!
> 
> Now, I remember that you said I should test the serial console with
> minicom on the /tmp/ttyS0 socket.
> I typically use picocom for serial console connections.
> Is there a way to make picocom connect to a UNIX socket?
> 
> Maybe I should try after using socat, as suggested in this [howto].
> 
> [howto]: <https://www.schmut.com/cheat-sheets/unix-serial-howto>
> 
> Or is there a better way?

I don't know about picocom. Either of the following should work:

    $ minicom -D unix#/tmp/ttyS0
    $ nc -U /tmp/ttyS0
    $ socat - UNIX-CONNECT:/tmp/ttyS0

> However, it leaves a lot of "production scrap" within /dev/shm :
>
>  $ du --si -s /dev/shm/.guestfs-1000/
>  755M    /dev/shm/.guestfs-1000/
>
> More than 750 MB of "production scrap"!
>
> Why does guestfish do this?

I don't know and I don't have these files in my own $TMPDIR.

In any case, if it works for you now, maybe you can close this bug?

Thanks!

cheers, josch

Attachment: signature.asc
Description: signature

Reply via email to