Hi,
Did anyone succeed in virt-install'ing F24 beta using kickstart (on CentOS 6 host, if that matters)?
I see lots of warnings (dracut-initqueue), then the console goes into a slowly filling bar at the bottom (plymouthd!?), then I see lots of "No space left on device" errors, then a dracut emergency shell is started.
The generated rdsosreport.txt contains 34284 lines...
FWIW, when *not* using kickstart I can install F24 beta on the same system with virt-install fine.
Thx,
-- -- Jos Vos jos@xos.nl -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204
On Sat, 2016-05-14 at 17:44 +0200, Jos Vos wrote:
Hi,
Did anyone succeed in virt-install'ing F24 beta using kickstart (on CentOS 6 host, if that matters)?
I see lots of warnings (dracut-initqueue), then the console goes into a slowly filling bar at the bottom (plymouthd!?), then I see lots of "No space left on device" errors, then a dracut emergency shell is started.
The generated rdsosreport.txt contains 34284 lines...
FWIW, when *not* using kickstart I can install F24 beta on the same system with virt-install fine.
I don't use virt-install, but we've done many kickstart installs of F24 both manually and in openQA and they work fine.
On Fri May 20 2016 15:02:17 GMT-0600 (MDT) Adam Williamson adamwill@fedoraproject.org wrote:
I don't use virt-install, but we've done many kickstart installs of F24 both manually and in openQA and they work fine.
"No space left on device" may hint to wrong partitioning or disk allocation. Jos can you try with a very basic ks file first and post it here?
Hi,
On Fri, May 20, 2016 at 03:48:50PM -0600, Viorel Tabara wrote:
"No space left on device" may hint to wrong partitioning or disk allocation. Jos can you try with a very basic ks file first and post it here?
See the attached ks-file. Simpler I can't make it...
This is the virt-install command (on CentOS 6.6):
virt-install -n f24t2016b -r 1024 --arch=x86_64 --vcpus=2 -l f24beta-x86_64/images/boot.iso --os-type=Linux --os-variant=fedora18 --disk /var/lib/libvirt/images/f24test.img,format=qcow2,size=50 --extra-args=ks=http://192.168.180.20:8888/f24beta-x86_64/ks/ks-f24test.cfg --network bridge=br0,mac=52:54:00:00:18:02,model=virtio
Note that it *does* pick up the ks-file correctly.
Using another mirror (this one is the closest to me) doesn't help, enabling the updates repo doesn't help, explicitly using a big size for / (i.s.o. --grow) doesn't help, etc...
Thanks,
"No space left on device" may hint to wrong partitioning or disk allocation. Jos can you try with a very basic ks file first and post it here?
See the attached ks-file. Simpler I can't make it...
I tested your ks in virt-manager with F24 Beta Server netinst and it worked without problems.
Try virt-manager, give it more RAM (this is quite likely, the requirements increased recently), don't set it as Fedora 18, make sure you have a vda disk. Please report back if you find out what the problem was. Thanks.
Hi,
On Mon, May 23, 2016 at 09:36:50AM -0400, Kamil Paral wrote:
I tested your ks in virt-manager with F24 Beta Server netinst and it worked without problems.
Try virt-manager, give it more RAM (this is quite likely, the requirements increased recently), don't set it as Fedora 18, make sure you have a vda disk. Please report back if you find out what the problem was. Thanks.
OK, my 1GB RAM was the problem, sigh... I guess the RAM-disk it creates isn't big enough then. I changed RAM from 1024 to 2048 and now it works.
Thanks for your help, I'm still from the time we could run Linux (with X11 !) on a 386 in 8 MB RAM... ;-). Still doubting whether assuming "enough" RAM for temporary storage is such a good idea...
Some other remarks:
- My "virt-install --os-variant=list" shows "fedora18" (described as "Fedora 18 or later") as the highest choice in Fedora-land. Should I better choose something else?
- There are zillions of "dracut-initqueue" warnings of deprecated Python stuff during the install. This won't be fixed before GA?
Cheers,
On Mon, 2016-05-23 at 16:04 +0200, Jos Vos wrote:
Hi,
On Mon, May 23, 2016 at 09:36:50AM -0400, Kamil Paral wrote:
I tested your ks in virt-manager with F24 Beta Server netinst and it worked without problems.
Try virt-manager, give it more RAM (this is quite likely, the requirements increased recently), don't set it as Fedora 18, make sure you have a vda disk. Please report back if you find out what the problem was. Thanks.
OK, my 1GB RAM was the problem, sigh... I guess the RAM-disk it creates isn't big enough then. I changed RAM from 1024 to 2048 and now it works.
Thanks for your help, I'm still from the time we could run Linux (with X11 !) on a 386 in 8 MB RAM... ;-). Still doubting whether assuming "enough" RAM for temporary storage is such a good idea...
You can *run* Fedora with very little RAM, but you can't *install* it with as little, due to memory usage by dnf during install when there is no swap partition. Exactly how much is needed varies a bit depending on whether you're doing a live install, what installer interface you're using, how many packages you're installing, whether it's a full moon, etc...I've seen it work with 512MB and fail with 1.5.
This was my problem too, finally finding this thread moved me past this blocker. THANK YOU.
-
Adam Williamson -
Jos Vos -
Kamil Paral -
Michael Tippie -
Viorel Tabara