Re: [Libguestfs] virt-customize networking question

On Thu, Nov 23, 2017 at 06:26:37PM +, ANDRES POZO MUNOZ wrote: > Hi, > > A quick question about a problem I’m facing. > > I want to customize some image running a customization script with > virt-customize. > > Everything works fine, except the fact that I don’t have a DHCP > server in the net

Re: [Libguestfs] [PATCH 0/1] RFC: switch from YAJL to Jansson

On Thu, Nov 23, 2017 at 02:23:51PM +0100, Pino Toscano wrote: > What do you think? A quick reply is: yes, we should do this. But I think we might want to wait until after 1.38 is released (just a few more weeks), because it is quite a big change so close to the stable release. Rich. -- Richard

[Libguestfs] virt-customize networking question

Hi, A quick question about a problem I’m facing. I want to customize some image running a customization script with virt-customize. Everything works fine, except the fact that I don’t have a DHCP server in the network (virt-customize relies on DHCP to assign the IP when it boots the image, ri

Re: [Libguestfs] [PATCH 1/1] Switch from YAJL to Jansson

On Thursday, 23 November 2017 15:00:12 CET Martin Kletzander wrote: > On Thu, Nov 23, 2017 at 02:23:52PM +0100, Pino Toscano wrote: > >While YAJL mostly works fine, it did not see any active development in > >the latest 3 years. OTOH, Jansson is another JSON C implementation, > >with a very libera

Re: [Libguestfs] [PATCH 1/1] Switch from YAJL to Jansson

On Thursday, 23 November 2017 17:07:34 CET Eric Blake wrote: > On 11/23/2017 07:23 AM, Pino Toscano wrote: > > While YAJL mostly works fine, it did not see any active development in > > the latest 3 years. OTOH, Jansson is another JSON C implementation, > > with a very liberal license, and a much

Re: [Libguestfs] [PATCH 1/1] Switch from YAJL to Jansson

On 11/23/2017 07:23 AM, Pino Toscano wrote: > While YAJL mostly works fine, it did not see any active development in > the latest 3 years. OTOH, Jansson is another JSON C implementation, > with a very liberal license, and a much nicer API. > > Hence, switch all of libguestfs from YAJL to Jansson:

Re: [Libguestfs] failure to virt-sysprep (FC27?)

On Thu, Nov 23, 2017 at 4:05 PM, Richard W.M. Jones wrote: > On Thu, Nov 23, 2017 at 03:00:45PM +0200, Yaniv Kaul wrote: > > On Thu, Nov 23, 2017 at 10:57 AM, Richard W.M. Jones > > wrote: > > > > > On Tue, Nov 21, 2017 at 11:43:54PM +0200, Yaniv Kaul wrote: > > > > Since I upgrading to FC27, I

Re: [Libguestfs] failure to virt-sysprep (FC27?)

On Thu, Nov 23, 2017 at 03:00:45PM +0200, Yaniv Kaul wrote: > On Thu, Nov 23, 2017 at 10:57 AM, Richard W.M. Jones > wrote: > > > On Tue, Nov 21, 2017 at 11:43:54PM +0200, Yaniv Kaul wrote: > > > Since I upgrading to FC27, I *sometimes* fail to virt-sysprep. > > > The debug messages: > > > libgue

Re: [Libguestfs] [PATCH 1/1] Switch from YAJL to Jansson

On Thu, Nov 23, 2017 at 02:23:52PM +0100, Pino Toscano wrote: While YAJL mostly works fine, it did not see any active development in the latest 3 years. OTOH, Jansson is another JSON C implementation, with a very liberal license, and a much nicer API. Hence, switch all of libguestfs from YAJL t

[Libguestfs] [PATCH 0/1] RFC: switch from YAJL to Jansson

Hi, recently, there was a discussion in the development list of libvirt on switching to a different JSON library than YAJL [1]. Since we use YAJL, and the points there IMHO apply to libguestfs as well, I decided to give a try in switching to Jansson [2]. The result IMHO is nice, with the additio

[Libguestfs] [PATCH 1/1] Switch from YAJL to Jansson

While YAJL mostly works fine, it did not see any active development in the latest 3 years. OTOH, Jansson is another JSON C implementation, with a very liberal license, and a much nicer API. Hence, switch all of libguestfs from YAJL to Jansson: - configure checks, and buildsystem in general - pack

Re: [Libguestfs] failure to virt-sysprep (FC27?)

On Thu, Nov 23, 2017 at 10:57 AM, Richard W.M. Jones wrote: > On Tue, Nov 21, 2017 at 11:43:54PM +0200, Yaniv Kaul wrote: > > Since I upgrading to FC27, I *sometimes* fail to virt-sysprep. > > The debug messages: > > libguestfs: trace: set_verbose true > > libguestfs: trace: set_verbose = 0 > > l

Re: [Libguestfs] RFE: ctime byte-for-byte reproducible qcow2 ext2/3/4 FS

On Wed, Nov 22, 2017 at 11:06:36PM -0500, Marc Pawlowsky wrote: > Problem: Want to be able to produce a qcow2 file with multiple ext4 > File Systems. > Days later want to reproduce the production of the qcow2 and have the > exact same byte-for-byte file, to prove my build is reproducible. > Curren

Re: [Libguestfs] failure to virt-sysprep (FC27?)

On Tue, Nov 21, 2017 at 11:43:54PM +0200, Yaniv Kaul wrote: > Since I upgrading to FC27, I *sometimes* fail to virt-sysprep. > The debug messages: > libguestfs: trace: set_verbose true > libguestfs: trace: set_verbose = 0 > libguestfs: create: flags = 0, handle = 0x7f465dd0, program = python2 >

[Libguestfs] [PATCH] launch: direct: Omit locking option for non-file disks (RHBZ#1516094)

QEMU does not accept options unrecognized by the block driver in use. Disable locking only for read-only disks that are file-backed, as that's the only block driver it is supported with. Signed-off-by: Lars Seipel --- lib/launch-direct.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-)

[Libguestfs] RFE: ctime byte-for-byte reproducible qcow2 ext2/3/4 FS

Problem: Want to be able to produce a qcow2 file with multiple ext4 File Systems. Days later want to reproduce the production of the qcow2 and have the exact same byte-for-byte file, to prove my build is reproducible. Currently the ctime attributes of the inodes will differ and thus the qcow2 file