On Thu, 2016-09-29 at 15:34 -0300, Sergio Belkin wrote: > Hi, > > I've tried to create a Live ISO using livemedia-creator, and followed the > steps from > https://fedoraproject.org/wiki/Livemedia-creator-_How_to_create_and_use_a_Live_CD > . > > But I cannot do it, these is the errors: > > sudo livemedia-creator --ks > /home/sergio/Descargas/Pagure/flat-fedora-live-base.ks --no-virt > --resultdir /home/lmc --project Fedora-Rescate-Silicon --make-iso --volid > Fedora24-Rescate-Silicon --iso-only --iso-name F24-R-R-Silicon.iso > /usr/lib64/python3.5/optparse.py:999: PendingDeprecationWarning: The > KSOption class is deprecated and will be removed in pykickstart-3. Use the > argparse module instead. > option = self.option_class(*args, **kwargs) > 2016-09-29 15:23:19,900: disk_img = /home/lmc/lmc-disk-flpdk287.img > 2016-09-29 15:23:19,901: Using disk size of 5122MiB > 2016-09-29 15:23:22,380: Running anaconda. > 2016-09-29 15:23:24,103: Processing logs from ('127.0.0.1', 51634) > 2016-09-29 15:23:27,388: The 'logging' function is not a part of DNF API > and will be removed in the upcoming DNF release. Please use only officially > supported API functions. DNF API documentation is available at > https://dnf.readthedocs.org/en/latest/api.html. > 2016-09-29 15:23:27,388: Starting installer, one moment... > 2016-09-29 15:23:27,389: terminal size detection failed, using default width > 2016-09-29 15:23:27,389: anaconda 24.13.7-1 for Fedora-Rescate-Silicon 24 > (pre-release) started. > 2016-09-29 15:23:27,389: The 'logging' function is not a part of DNF API > and will be removed in the upcoming DNF release. Please use only officially > supported API functions. DNF API documentation is available at > https://dnf.readthedocs.org/en/latest/api.html. > 2016-09-29 15:23:29,478: Running anaconda failed: process '['anaconda', > '--kickstart', '/home/sergio/Descargas/Pagure/flat-fedora-live-base.ks', > '--cmdline', '--dirinstall', '--remotelog', '127.0.0.1:46181']' exited with > status 1 > 2016-09-29 15:23:29,478: Shutting down log processing > 2016-09-29 15:23:29,650: Install failed: novirt_install failed > 2016-09-29 15:23:29,652: Removing bad disk image > 2016-09-29 15:23:29,684: ERROR: Image creation failed: novirt_install failed > > Am I doing something wrong? That error means the anaconda install failed. The way livemedia_creator works is that it actually runs an anaconda install using the kickstart specified - using its 'install to a directory' method if you pass --no- virt, otherwise in a VM - then creates an image file from the resulting installation. You'd need to look at the generated log files, probably anaconda.log , to see what exactly went wrong. I'd probably advise against running livemedia-creator with the --no- virt option in your actual production environment, it could potentially cause problems. The way I've found to make lmc fly (though it's a bit awkward, and I need to get around to writing some scripts to make it more convenient) is to mimic what Koji does for production builds, and run it in a mock chroot. Basically, set up a clean mock chroot of the release you actually want to create a live image for, install the creation tools into the mock root with 'mock -r (whatever) --install livemedia-creator' (and whatever other packages are needed, I forget) then run 'mock -r (whatever) --shell' and do the live image creation inside the shell. It's been a few weeks since I did this so I forget a few annoying twiddly details you run into along the way, but that basically worked for me. I actually just steal the kickstarts from Koji - you can just grab a kickstart from a completed official live image task, and customize it if you want. I find that easier than trying to generate the flattened kickstarts lmc wants... Hope that helps a bit, anyway... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
