Hello, thanks for the reply!
Sure, I use the default bootloader provided by live-build.
So default /boot and /EFI directories, but I use ISO loopback, loading the
system directly from the ISO into RAM.
grub.cfg
menuentry "debian-live.iso" {
set iso="/ISO/debian-live.iso"
set root=(hd0,5)
loopback loop $iso
linux (loop)/live/vmlinuz-4.19.0-6-amd64 boot=live components toram
findiso=$iso
initrd (loop)/live/initrd.img-4.19.0-6-amd64
}
Guest Images (x2):
qcow2
2.1GB
Compressed with
qemu-img convert -c
One more thing I noticed, if I copy the images to another location and THEN
chown them, no copies are created in /run/live/overlay/rw.
This confirms my suspicion that the problem is probably with the squashfs
filesystem.
On Tue, Nov 23, 2021, 5:30 PM Harshad Joshi <[email protected]> wrote:
> Hello.
>
> Can you share the settings of your live image esp including guest image
> using includes.chroot
>
> --sent from OnePlus device--
>
> Check out newly released Bufferstack.IO IIoT Gateway
>
> https://bufferstack.io
>
> On Tue, 23 Nov, 2021, 9:57 PM Elias Mobery, <[email protected]> wrote:
>
>> Hi everyone!
>>
>> I've built a Debian Live ISO with packages qemu and libvirt to run a VM
>> in the live environment.
>>
>> The guest images are added via includes.chroot. They are 2GB each and
>> placed in /var/lib/libvirt/images
>>
>> Everything works great, except for one issue.
>>
>> When starting a VM, libvirt automatically issues a chown command to the
>> images, to change ownership.
>>
>> This results in a copy of the images being created in
>> /run/live/overlay/rw/var/lib/libvirt/images
>> (It also happens when I manually chown them)
>>
>> I don't want these copies to be made but can't stop it.
>>
>> I noticed that this /run/live/overlay/rw directory only has the
>> folders and files that I added via includes.chroot EXCEPT for the images.
>> Those only appear there after using chown on them in the regular dir.
>>
>> Is this some kind filesystem error or squashfs issue?
>>
>>
