December 2015 - Libguestfs - Libguestfs List Archives

Which ISO format/layout does virt-builder expect?

by Scott Gorton

I'm running into a bit of trouble using virt-builder and I'm hoping that someone might be able to point in the right direction. My build process creates a custom ISO image which is subsequently used to kickstart an Oracle X4-2 server using PXE. The ISO is a minimal install and contains a suite of packages and customization scripts to properly configure our box during first boot. The process works great for kickstarting baremetal machines as well as VMs created with virt-manager or vsphere. I'd like to be able to use virt-builder to build virtual images automatically (i.e., take our .ISO and generate a qcow2 of a properly installed system). Unfortunately, virt-builder doesn't seem to like the format of my ISO image. The tool dies during the "Setting passwords" step because it's attempting to create a temp file in /etc and my ISO doesn't have an /etc directory at this point. Here's a snippet that shows the error message: [ 16.0] Setting passwords libguestfs: trace: mktemp "/etc/shadow.guestfsXXXXXX" libguestfs: trace: mktemp = NULL (error) virt-builder: error: libguestfs error: mktemp: /etc/shadow.guestfsyU5Zwo: No such file or directory Is there a particular ISO format that virt-builder expects? As a test, I used virt-builder to successfully create a centos-6 image. I looked in my .cache/virt-builder directory, unxz'd the image and then mounted the partitions. It appears that the sanitized centos-6 image is fully complete (i.e., contains a typical filesystem, has an /etc, an /etc/passwd...etc.) whereas mine seems more like a linux image that is in a ready-to-be-installed state. virt-inspector on my ISO shows: <?xml version="1.0"?> <operatingsystems> <operatingsystem> <root>/dev/sda</root> <name>linux</name> <arch>x86_64</arch> <distro>oraclelinux</distro> <major_version>6</major_version> <minor_version>0</minor_version> <package_format>rpm</package_format> <package_management>yum</package_management> <format>installer</format> <mountpoints> <mountpoint dev="/dev/sda">/</mountpoint> </mountpoints> <filesystems> <filesystem dev="/dev/sda"> <type>iso9660</type> <label>iDVA 4.95.0 x86_64</label> <uuid>2015-11-20-19-50-52-00</uuid> </filesystem> </filesystems> <applications/> </operatingsystem> </operatingsystems> Likewise, if I mount my ISO I have a filesystem that looks like: drwxrwxr-x 3 test test 4096 Nov 19 18:03 images drwxrwxr-x 11 test test 4096 Nov 19 18:05 iqcustom -rw-rw-r-- 1 test test 966785078 Nov 19 18:08 iqcustom.tar.gz drwxrwxr-x 2 test test 4096 Nov 19 18:03 isolinux -rw-rw-r-- 1 test test 2368 Nov 19 18:03 ks-dell.cfg -rw-rw-r-- 1 test test 15158 Nov 19 18:03 ks-oracle.cfg -rw-rw-r-- 1 test test 15985 Nov 19 18:03 ks-pxe.cfg -rw-rw-r-- 1 test test 3061 Nov 19 18:03 ks-pxe-oracle-vm.cfg -rw-rw-r-- 1 test test 2176 Nov 19 18:03 ks-vm.cfg drwxrwxr-x 2 test test 36864 Nov 19 18:04 Packages drwxrwxr-x 2 test test 4096 Nov 19 18:04 repodata -r--r--r-- 1 test test 3106 Nov 19 18:05 TRANS.TBL drwxrwxr-x 3 test test 4096 Nov 19 18:05 In contrast, mounting one of the partitions in the centos-6 image shows: dr-xr-xr-x. 2 root root 4096 Oct 31 2014 bin drwxr-xr-x. 2 root root 4096 Oct 31 2014 boot drwxr-xr-x. 2 root root 4096 Oct 31 2014 dev drwxr-xr-x. 73 root root 4096 Dec 9 16:26 etc drwxr-xr-x. 2 root root 4096 Sep 23 2011 home dr-xr-xr-x. 10 root root 4096 Oct 31 2014 lib dr-xr-xr-x. 9 root root 12288 Oct 31 2014 lib64 drwx------. 2 root root 16384 Oct 31 2014 lost+found drwxr-xr-x. 2 root root 4096 Sep 23 2011 media drwxr-xr-x. 2 root root 4096 Sep 23 2011 mnt drwxr-xr-x. 3 root root 4096 Oct 31 2014 opt drwxr-xr-x. 2 root root 4096 Oct 31 2014 proc dr-xr-x---. 2 root root 4096 Oct 31 2014 root dr-xr-xr-x. 2 root root 12288 Oct 31 2014 sbin drwxr-xr-x. 2 root root 4096 Oct 31 2014 selinux drwxr-xr-x. 2 root root 4096 Sep 23 2011 srv drwxr-xr-x. 2 root root 4096 Oct 31 2014 sys drwxrwxrwt. 2 root root 4096 Oct 31 2014 tmp drwxr-xr-x. 13 root root 4096 Oct 31 2014 usr drwxr-xr-x. 19 root root 4096 Oct 31 2014 var Note: we build our ISO using mkisofs. Is there some other tool/process that we should use to generate ISOs that satisfy virt-builder? Should I be starting from a Live CD format? Cheers! ________________________________ NOTICE: This communication and any attachments may contain confidential and/or privileged information of IneoQuest Technologies, Inc. ("IneoQuest"). This communication is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this communication, you are hereby notified that any dissemination, distribution, copying or other use of this communication or the information it contains is strictly prohibited and may be unlawful. If you have received this communication in error, please notify the sender immediately by reply e-mail and destroy all copies of this communication (including attachments), electronic or otherwise. If you are a party to a written Non-Disclosure Agreement ("NDA") with IneoQuest, you should maintain the contents of this communication (including attachments) in confidence to the full extent specified in the NDA.

9 years, 1 month

2
1
0 / 0

rpm scriptlet failed

by Alexandre Freire da Silva Osorio

Hello, While trying to install a rpm package in a Linux image under guestifish, the following error message is returned: sh "rpm -ivh --nodeps sympl.rpm" error: install: %pre scriptlet failed (2), skipping sympl If I boot the same image in QEMU and run the same command, no error message is returned and the package is correctly installed. The script contents is only a single "exit 0". I don't what could be the cause of this error. Please I would like to know whether any of you have face such a problem before. Thanks in advance. Regards, Alexandre

9 years, 1 month

1
0
0 / 0

SELinux relabel API

by Richard W.M. Jones

[ I realized that we were discussing adding this feature, in various private email, IRC, and this long bugzilla thread: https://bugzilla.redhat.com/show_bug.cgi?id=1060423 That's not how we should do things. Let's discuss it on the mailing list. ] One thing that virt-customize/virt-sysprep/virt-builder have to do is relabel SELinux guests. What we do at the moment is run: if load_policy && fixfiles restore; then rm -f /.autorelabel else touch /.autorelabel echo '%s: SELinux relabelling failed, will relabel at boot instead.' fi while chrooted into the guest (using the 'guestfs_sh' API). This has a number of problems: - It has to load the policy using 'load_policy', but this doesn't work sometimes: * RHEL 5 load_policy takes a parameter. * Doesn't work if appliance kernel is significantly different from guest kernel version, because the binary policy format changes irregularly and is not backwards compatible. * Requires the appliance [host] kernel to be compiled with LSM/SELinux support. - Touching /.autorelabel is often broken, eg. it's broken in Fedora 20 because of systemd (RHBZ#1049656). - /etc/resolv.conf will not be relabelled if guestfs network is on, because of resolv.conf shenanigans in libguestfs.git/daemon/command.c - It requires running guest code, which we'd like to avoid. What would be nice would be to have an API to just do this relabelling. Libguestfs could change this API as required to handle different guests. Dan Walsh helpfully pointed out to us that we've been doing it wrong all along :-) A much better way to relabel is to run: setfiles /etc/selinux/targeted/contexts/files/file_contexts DIR where 'file_contexts' is a file which contains the default labels for files (a set of regexps), and 'DIR' is the directory at which relabelling starts. Note that 'setfiles' would be the libguestfs appliance binary, so no guest binary needs to be run. A simple API could just look like this: guestfs_selinux_relabel (g); which would always use the 'targeted' policy from the guest, and always start relabelling at the root. This would work fine for virt-builder. For Colin's requirements for Project Atomic, I suspect he will want to be able to set the file_contexts file and the root directory, but I'll leave him to describe what would be useful. A couple of notes: - I'd like to avoid baking in assumptions from the 'setfiles' command as far as possible. libguestfs APIs last for many years and some have caused us many years of regret (but that's our job) :-/ - Is it a good idea to tie this into inspection in some way -- for example, inspection could provide us with the path to the current or default SELinux policy. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top

9 years, 1 month

5
10
0 / 0

Virt-v2v alignement check

by Kevin COUSIN

Hi list, Is virt-v2v make any alignement check on partitions when copying VM ? Thanks, Regards Kevin C

9 years, 1 month

2
1
0 / 0

Virt-v2v Import Issue

by Budur Nagaraju

Hi I have converted win2k3 which was deployed in vmware esxi to oVirt by using "v2v" tool ,imported successfully after powering on unable to get the login prompt getting stuck at "windows is starting". can someone help me in this issue ? pls help me to know the commands to get the virt2v logs Thanks, Nagaraju

9 years, 1 month

2
1
0 / 0

Cannot compile 1.31.29

by jean-christophe Manciot

1.31.28 issue regarding some packages that cannot be authenticated is gone, but there's a new issue while building 1.31.29: /bin/mkdir -p '/usr/share/man/man3' /usr/bin/install -c -m 644 ./guestfs-perl.3 '/usr/share/man/man3' /usr/bin/install: cannot stat './guestfs-perl.3': No such file or directory Makefile:1531: recipe for target 'install-man3' failed make[3]: *** [install-man3] Error 1 make[3]: Leaving directory '/home/actionmystique/Program-Files/Ubuntu/Libguestfs/git-libguestfs/perl/examples' Makefile:1623: recipe for target 'install-am' failed make[2]: *** [install-am] Error 2 make[2]: Leaving directory '/home/actionmystique/Program-Files/Ubuntu/Libguestfs/git-libguestfs/perl/examples' Makefile:1843: recipe for target 'install-recursive' failed make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory '/home/actionmystique/Program-Files/Ubuntu/Libguestfs/git-libguestfs' Makefile:2307: recipe for target 'install' failed make: *** [install] Error 2 **** Installation failed. Aborting package creation. Whole log is attached. -- *Jean-Christophe Manciot* * [image: Architecte réseaux et Sécurité] <https://learningnetwork.cisco.com/people/manciot.jeanchristophe/content> *[image: Network & Security Architect] <http://fr.linkedin.com/in/jeanchristophemanciot> <https://plus.google.com/u/0/+jeanchristopheManciot-IT/posts> <https://twitter.com/jc_manciot>

9 years, 1 month

2
1
0 / 0

Bug report "WARNING: The following packages cannot be authenticated!"

by Richard W.M. Jones

No idea why this happens, but it was reported to me ... Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW

9 years, 1 month

1
0
0 / 0

[PATCH 0/6 v2] [FOR COMMENTS ONLY] Rework inspection.

by Richard W.M. Jones

This is a more working version. Inspection (partially) succeeds on a real guest this time :-) You can test it out on a real guest (in this case, a CentOS disk image located at /tmp/centos-6.img) by doing: $ ./run guestfish -v -x -a /tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection --verbose" which will print lots of debugging, and at the end the list of facts from inspecting the image. Rich.

9 years, 1 month

1
6
0 / 0

virt-builder is very slow in git master when building ubuntu 14.04 vm

by 阎淼

Hi All, I been using virt-builder to create testing VMs (most ubuntu) for a while, and it works great. But when I cloned the git repo today and found the process becoming extremely slow, please see the output below. log that produced by pre-installed vendor package: virt-builder ubuntu-14.04 --firstboot-command 'useradd -m -p "" myan; chage -d 0 myan; usermod -aG sudo myan;' [ 3.0] Downloading: http://libguestfs.org/download/builder/ubuntu-14.04.xz [ 4.0] Planning how to build this image [ 4.0] Uncompressing [ 6.0] Opening the new disk [ 11.0] Setting a random seed [ 11.0] Installing firstboot command: [1] useradd -m -p "" myan; chage -d 0 myan; usermod -aG sudo myan; [ 11.0] Setting passwords virt-builder: Setting random password of root to 5bRx9fpQ7kjPh0Dd [ 12.0] Finishing off Output file: ubuntu-14.04.img Output size: 4.0G Output format: raw Total usable space: 2.9G Free space: 2.0G (69%) log that produced by git master: ~/vm$../work/libguestfs/run virt-builder ubuntu-14.04 --firstboot-command 'useradd -m -p "" myan; chage -d 0 myan; usermod -aG sudo myan;' [ 0.4] Downloading: file:///home/myan/work/libguestfs/builder/website/ubuntu-14.04.xz [ 1.7] Planning how to build this image [ 1.7] Uncompressing [ 4.4] Opening the new disk [ 628.3] Setting a random seed [ 628.4] Installing firstboot command: useradd -m -p "" myan; chage -d 0 myan; usermod -aG sudo myan; [ 628.4] Setting passwords virt-builder: Setting random password of root to owA2CFqJeDYT92Sq [ 629.4] Finishing off Output file: ubuntu-14.04.img Output size: 4.0G Output format: raw Total usable space: 2.9G Free space: 2.0G (69%) Turning on debug shows that it spent most of time spinning here: [...] /sbin/dhclient-script: 31: /sbin/dhclient-script: cannot open /etc/fstab: No such file RTNETLINK answers: File exists [...] Any idea what's the problem or is it a known issue ? Thanks. Miao

9 years, 1 month

2
4
0 / 0

[PATCH] builder: create temporary images in the cachedir (RHBZ#1288201)

by Pino Toscano

Temporary images can be quite big, more than the space available in $TMPDIR when it's on a tmpfs; hence, place them in our cachedir instead. --- builder/builder.ml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/builder/builder.ml b/builder/builder.ml index 957bc37..3750e5f 100644 --- a/builder/builder.ml +++ b/builder/builder.ml @@ -378,6 +378,8 @@ let main () = goal_must, goal_must_not in + let cache_dir = (open_guestfs ())#get_cachedir () in + (* Planner: Transitions. *) let transitions itags = let is t = List.mem_assoc t itags in @@ -394,7 +396,7 @@ let main () = (* Since the final plan won't run in parallel, we don't only need * to choose unique tempfiles per transition, so this is OK: *) - let tempfile = Filename.temp_file "vb" ".img" in + let tempfile = Filename.temp_file ~temp_dir:cache_dir "vb" ".img" in unlink_on_exit tempfile; (* Always possible to copy from one place to another. The only -- 2.1.0

9 years, 1 month

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Libguestfs December 2015