similar to: Re: [Bug 1046905] New: RFE: add argument to virt-sysprep to disable individual default operations

On Tuesday 07 January 2014 12:12:43 Richard W.M. Jones wrote: > On Tue, Jan 07, 2014 at 11:16:08AM +0100, Pino Toscano wrote: > > On Friday 27 December 2013 10:58:15 you wrote: > > > virt-sysprep either runs with all default operations or a selected > > > list of operations with the --enable argument. A few times I've > > > found I'd like to use the

On Tue, Jan 07, 2014 at 11:16:08AM +0100, Pino Toscano wrote: > On Friday 27 December 2013 10:58:15 you wrote: > > virt-sysprep either runs with all default operations or a selected > > list of operations with the --enable argument. A few times I've > > found I'd like to use the default list, but minus one or two > > operations in particular, however there's

On Tuesday 07 January 2014 15:24:51 Pino Toscano wrote: > On Tuesday 07 January 2014 12:12:43 Richard W.M. Jones wrote: > > On Tue, Jan 07, 2014 at 11:16:08AM +0100, Pino Toscano wrote: > > > On Friday 27 December 2013 10:58:15 you wrote: > > > > virt-sysprep either runs with all default operations or a > > > > selected > > > > list of

On Thu, Jan 09, 2014 at 03:45:54PM +0000, Richard W.M. Jones wrote: > On Thu, Jan 09, 2014 at 04:21:10PM +0100, Pino Toscano wrote: > > + and set_operations op_string = > > + let currentopset = > > + match (!operations) with > > No need for parentheses around !operations. > > > + let n = ref op_name in > > + let remove =

On Thu, Jan 09, 2014 at 04:21:10PM +0100, Pino Toscano wrote: > + and set_operations op_string = > + let currentopset = > + match (!operations) with No need for parentheses around !operations. > + let n = ref op_name in > + let remove = string_prefix op_name "-" in > + if remove then > + n := String.sub op_name 1

On Friday 10 January 2014 10:09:19 Richard W.M. Jones wrote: > On Thu, Jan 09, 2014 at 03:45:54PM +0000, Richard W.M. Jones wrote: > > On Thu, Jan 09, 2014 at 04:21:10PM +0100, Pino Toscano wrote: > > > + and set_operations op_string = > > > + let currentopset = > > > + match (!operations) with > > > > No need for parentheses around

Setting timezone is easy. It turns out to be almost impossible to set keyboard layout in virt-builder sanely, so I have added some examples instead. Coming up next, setting languages in virt-builder (clue: very very very hard). Rich.

This is just one possible way to fix this bug, but the simplest. Others I considered: - Keeping the network disabled by default. Options like --install wouldn't work and there would be no actionable error message telling users what to do to fix it. - Modifying virt-customize to warn/error/suggest if operations like --install were used but the network was disabled. However

On Wed, Aug 23, 2017 at 06:25:17AM +0000, Tang, Alan (NSB - CN/Qingdao) wrote: > [ 0.000000] Linux version 3.10.101 (root@ci092133) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Mon Apr 11 16:22:43 ULAT 2016 ... > commandrvf: mount -o ro /dev/sda1 /sysroot/ > [ 2.333550] SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled > [

In commit ae6f726ecc3bc1b67fd76e51a7b1e1a33d4dcfc0 we started to use the virt-customize code to replace various virt-sysprep operations. This had the effect of adding many more possible operationg to virt-sysprep, but some of them (specifically --install) did not work unless the appliance network is enabled. It was not enabled in virt-sysprep, so these operations never worked. This change

Add a new --operation parameter which, similarly to --enable, can be used to enable operations, but also to remove them, and to add/remove the default operations and all the available ones. --- sysprep/main.ml | 36 +++++++++++++++++++++++++++ sysprep/sysprep_operation.ml | 24 ++++++++++++++++++ sysprep/sysprep_operation.mli | 21 ++++++++++++++++ sysprep/virt-sysprep.pod |

Fixes RHBZ#845234. v3 changes: Drive letters works if inspection is enabled (-m is not given) v2 changes: Ammended so it doesn't do inspection for every dir to list. Maros Zatko (3): virt-ls: support drive letters on Windows virt-ls: update usage for win drive letters docs: amend virt-ls manpage with win drive letters cat/ls.c | 41 +++++++++++++++++++++++++++++++++++++----

I'm setting up a system to run LXC containers with ZFS on Linux (Ubuntu 14.04). I intend to set up a base image which I'd like to clone to create other containers from. virt-sysprep and virt-customize seem ideal for the task: I obviously could mount and work with the rootfs from each container directly, but the libguestfs tools have a bunch of pre-existing recipes that would surely be much

Add the support for rhel. Change the hostname and delete the HWADDR for rhel. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- clone/virt-sysprep.in | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/clone/virt-sysprep.in b/clone/virt-sysprep.in index 833a31d..d505532 100644 --- a/clone/virt-sysprep.in +++ b/clone/virt-sysprep.in @@ -273,7 +273,7 @@ fi

On Tue, Jan 07, 2014 at 10:06:16AM +0000, Graeme Lambert wrote: > Hi, > > I'm trying to run virt-sysprep against a disk in Ceph RBD storage > but I appear to be unable to do so. > > The commands (bold) and outputs I've had are: > > On Ceph node: > *virt-sysprep -a rbd://localhost/libvirt-pool/ubuntu-12-04-beanstalk001* > libguestfs: new guestfs handle

On Tue, 21 Jan 2014, Richard W.M. Jones wrote: > A common problem that people have with virt-builder and virt-sysprep > is which guests that use SELinux, like Fedora and RHEL. In both cases > we touch /.autorelabel in the guest, which means the guest has to > reboot once during its first boot. ... snip much analysis ... > (4) It can touch '/.autorelabel' which causes an

On Fri, Oct 07, 2016 at 04:42:21PM -0400, Charlie Drage wrote: > I apologize if this is not the appropriate place to contact you.. Adding the mailing list. > Got a weird issue! > > So when I use --firstboot via virt-sysprep on a host, it's totally fine. > > However.. > > In this scenario: > 1. virt-sysprep an offline image > 2. transfer said image from one

On Tue, 21 Jan 2014, Richard W.M. Jones wrote: > This could be because the kernel of the libguestfs appliance doesn't > match the kernel of the guest. We also encounter such problems when re-labelling images not matching the dom0 kernel distribution, and just accept the relabel delay (slow and linear) and second boot (boots are fast) -- but I had hoped you had a solution ;) -- Russ

In data martedì 29 dicembre 2015 17:58:18, Richard W.M. Jones ha scritto: > On Mon, Dec 28, 2015 at 03:51:51PM -0800, Ryan Sawhill Aroha wrote: > > The `virt-builder --notes <TEMPLATE>` command is nice, but I really wish it printed the full template definition, eg, something like this: > > > > ``` > > $ virt-builder --notes centos-70 > > > >

18:07 < _ng> What is the proper way to break mult lines when using virt-sysprep --write option, with --commands-from-file? (I don't mean escaping, but actually writing new lines to the file) You can use \ as a continuation character, as it mentions in the manual. Using virt-builder (just because it's a bit easier to demonstrate, but