That happens a lot with me. The solution is just there when I wake.
Try with qemu instead of virt- manager. There may be more options
Is BOOTSYSTEM.img rw?
Does virt-manager have a logfile… it may give more info
Thinking may be useful after all.
Hi all, 
thanks so much for your latest input and for not giving up on me. 
I´m sorry to say I didn´t dream up a solution. Well, it was worth a shot. 
I looked around on the internet and found out (A.6. Virtualization Logs | Red Hat Product Documentation ) there are indeed logs:
I just fired up the EasyOS install from yesterday. It hangs as already described and I found a single entry referring to that event (at least I guess so):
env LANG=en_US.UTF-8 journalctl _SYSTEMD_UNIT=libvirtd.service | grep "Sep 17"
Sep 17 12:12:55 rosika-10159 libvirtd[1005]: operation failed: pool 'default' already exists with uuid e6bdbf3b-512f-4340-a80b-1af3bc2d147d
Hmm, I wonder what that brought up… 
O.K. I still have to try that. Thanks for the suggestion.
.rw-r--r-- 865M rosika rosika 16 Sep 17:55 BOOTSYSTEM.img
For me as user … yes.
Hmm, I fear I don´t quite understand.
Do you mean I should dd the EasyOs installation which I had successfully installed on my USB-stick to the BOOTSYSTEM.img 
In this case I would need something bigger than a small partition I guess … as I would need 825 MB for the installation…
Many thanks and many greetings.
Rosika 
I would use dd to ssd but I do not know the dd command. It may indeed dd to a partition, and run in dual boot, but I am not sure I would. I have booted this usb on four different PC’s, one is running W11.
1 Like
Do you know what that uuid is?
It seems to say something is present that should not be?
rw-r--r-- 865M rosika rosika 16 Sep 17:55 BOOTSYSTEM.img
For me as user yes.
I assume qemu does not use some special user?
Does it need to be rwx?
You might try rwxrwxrwx just to be sure
Regards
Neville
1 Like
Hi again, 
Thanks.
I tested dd thus:
-
created a new container:
qemu-img create 2BOOTSYSTEM.img 10G -
plugged in the USB stick on which EasyOS is successfully installed (/dev/sdg)
-
/dev/sdg has two partitions:
1.) /dev/sdg1: EFI (FAT-12/16/32) (Bootable): 7,3 MB
2.) Linux ext4 : 63 GB (61 GB free) -
sudo dd if=/dev/sdg1 of=./2BOOTSYSTEM.img# went well
That left me with the 2nd partition. Hmm 
…
I decided to try another path by:
sudo dd if=/dev/sdg of=./2BOOTSYSTEM.img
… hopig it would take care of the two partitions. Well, I guess it would have but I created a 10 GB virtual drive and the stick has got a size of 64 GB.
dd copies every sector, so the emply ones as well.
I would need a command that only copies used sectors.
ls -Al /dev/disk/by-uuid | grep e6bdbf3b
returned nothing. Strange…
Changes it with chmod 777 BOOTSYSTEM.img but the outcome was the same. 
Thanks a lot and many greetings from Rosika 
Then that uuid must be inside the container?
We arent any wiser.
1 Like
SUCCESS, SUCCESS, SUCCESS 
I´ve done it. 
I found the solution on Ventoy: easy.sfs cp: write error: No space left on device - Puppy Linux Discussion Forum
As easy is made to write to a partition on an usb drive that is grown at first start.
The initial partition in the .img file is very small and easy is not made to grow the image file .
You could make the image bigger ( something like dd if=/dev/zero bs=1M count=2048 >> easy-3.4.7-amd64.img )
Then I think easy would be able to grow the partition in the image and run!
(bold by me)
So I did that.
dd if=/dev/zero bs=1M count=2048 >> easy-4.3.4-amd64.img
Now the img file has a size of 2.8 GB instead of the over 800 MB.
And that´s the solution.
I applied that new img as an existing drive image in virt-manger and the installation succeeeded.
EasyOS is running and I even have an running internet connection.
Thanks so much, really: so much for your kind help. All of you.
It´s very much apreciated 
… and indeed I´ve learned a lot. 
Many greetings from Rosika
1 Like
So I did that.
dd if=/dev/zero bs=1M count=2048 >> easy-4.3.4-amd64.img
Now the img file has a size of 2.8 GB instead of the over 800 MB.
And that´s the solution.
Hi Rosika,
Congratulations. You did it all on your own.
As I understand it now, You added 2Mb of space to the .img file.
, and that gave it the room it needed to be able to be able to have writes… and I assume permanence.
So to celebrate, let me give a quote from one of my favourite saints… it happens to be her feast day today
. “We cannot live in a world that is not our own, in a world that is interpreted for us by others. An interpreted world is not a home.”
-Hildegard of Bingen.
It is about music, but it is quite relevant… one ultimately has to solve ones own computer issues
Regards
Neville
1 Like
Thanks a lot, Neville.
Thanks indeed for congratulating me. BUT: I certainly didn´t do it on my own. 
Without your kind help and the help of all the other kind members I certainly would´ve given up at a much earlier pont. That´s for sure.
You kept me going and indeed kept up my spirit. That´s something to be held up high.
Plus: as I´ve already mentioned - I´ve learned quite a lot just by discussing the facts and all the possible scenarios.
That´s really quite something.
So thanks again - so much - you´re all so kind.
Many greetings and have a nice weekend
Rosika
Yes , we have all learnt a lot.
In my opinion your post has been one of the best ever.
I wonder, when we all finish celebrating, could we end this off with a summary of all the things learned?
It would seem that when you write the .img file to a usb drive, the extra space is there, but when you clone it to an HDD it is not.
Regards
Neville
1 Like
That’s the better and more understandable version of what I was trying to say earlier. One needs resizefs or something to enlarge what is there, because the img obviously doesn’t want to hold unnecessary empty space.
The same process needs to be done in a classical Raspbian installation. The partition needs to be enlarged, before first use. However, I think there is no problem booting it up to do that, so it’s less painful.
1 Like
Congratulations!!!
1 Like
Hi all,
Thanks a lot, Daniel
But the important thing is you said it earlier and that´s very insightful. It was surely me who didn´t recognize the full potential of your statement. Sorry. 
resizefs … I certainly didn´t think of that as I never had occasion to deal with that command. Thanks for mentioning it.
That´s certainly the background of it all.
Oh, that´s good to know … in case I might want to deal with such a project in the future.
Wow, that´s really kind of you. I almost feel a bit embarassed.
It seems that way, although How to install EasyOS on a new SSD states
This page describes how to install EasyOS on an entire drive, completely replacing what was on it before. This can be any drive; SSD or magnetic-platter HDD, internal or external. Also USB flash-sticks or SD-cards.
But perhaps dealing with a virtual drive is a bit different…
Well, that´s a good idea, Neville. But I certainly cannot do it on my own as despite all the learning I don´t feel confident enough to be something of a “teacher”… 
But I´ll be glad to help.
Many greetings from Rosika
1 Like
Someone explain to me as to why Mr Barry Kauler departed from .iso’s to .img’s?
Why don’t you ask him directly, yourself?
@Akito
I have already read what he has to say!!! I do not buy it!!! What about your thoughts!!!
Sounds like a break/away from Puppy Linux, like Daniel Robbins and Funtoo.
That link does not work, at least not with Gentoo and FF.
Indeed.
Fatal error: Uncaught Error: Call to a member function AddAddress() on null in
/webroot/b/k/bkauler001/bkhome.org/www/contact/contact-form/include/fgcontactform.php:68
Stack trace:
#0 /webroot/b/k/bkauler001/bkhome.org/www/contact/contact-form/contactform.php(19): FGContactForm->AddRecipient()
#1 {main} thrown in /webroot/b/k/bkauler001/bkhome.org/www/contact/contact-form/include/fgcontactform.php on line 68
That guy should be contacted to tell him he should repair his contact page. 
2 Likes
Doing what you were proposing… copy the usb drive to a disk… would have worked, according to what Rosika and Akito have found, as long as you cloned the whole 64Gb
But we may not have understood why it worked.
1 Like