similar to: Bringing up a guest with network disabled

On Tue, 01 Oct 2013 06:10:46 -0600 Eric Blake <eblake@redhat.com> wrote: > On 10/01/2013 06:04 AM, James Gibbon wrote: > > > > > > Hello all, > > > > I have a KVM guest VM which is a clone of a production machine > > running on a different physical server, incarnated from an > > image backup. > > Careful. You need to scrub more than

On 10/01/2013 06:04 AM, James Gibbon wrote: > > > Hello all, > > I have a KVM guest VM which is a clone of a production machine > running on a different physical server, incarnated from an > image backup. Careful. You need to scrub more than just the IP address for a clone and it's parent to safely run at the same time. For example, if you don't scrub the

On 10/01/2013 09:29 AM, James Gibbon wrote: > Would be grateful if someone could suggest a way to disable the networking in the > cloned VM within the XML, if that's possible. I have no idea if it's possible to "disable" the NIC on the VM definition but you could boot into runlevel 1 (where there is no network) and perform the changes there. You may do this by passing a

2013/10/2 Jorge Fábregas <jorge.fabregas@gmail.com> > On 10/01/2013 09:29 AM, James Gibbon wrote: > > Would be grateful if someone could suggest a way to disable the > networking in the > > cloned VM within the XML, if that's possible. > > I have no idea if it's possible to "disable" the NIC on the VM > definition but you could boot into

This patch is incomplete but it illustrates the idea. virt-sysprep is rewritten as a modular tool in OCaml. Only the 'utmp' and 'hostname' operations are implemented at the moment. Rich.

There's not going to be an easy way to present this patch. It's huge and interconnected. Anyway, what it does is lay the groundwork for a new tool which I'm calling 'virt-customize'. virt-customize is virt-builder, but without the part where it downloads a template from a respository. Just the part where it customizes the template, that is, installing packages, editing

Remove the db and log of sssd. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- sysprep/Makefile.am | 2 ++ sysprep/sysprep_operation_sssd_db_log.ml | 50 ++++++++++++++++++++++++++++++ 2 files changed, 52 insertions(+) create mode 100644 sysprep/sysprep_operation_sssd_db_log.ml diff --git a/sysprep/Makefile.am b/sysprep/Makefile.am index

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.

Help the OCaml compiler by expliciting Guestfs.guestfs as type for 'g' in some functions. --- get-kernel/get_kernel.ml | 2 +- sysprep/sysprep_operation_abrt_data.ml | 2 +- sysprep/sysprep_operation_bash_history.ml | 2 +- sysprep/sysprep_operation_ca_certificates.ml | 2 +- sysprep/sysprep_operation_crash_data.ml

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

Remove the ca certificates. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- sysprep/Makefile.am | 2 + sysprep/sysprep_operation_ca_certificates.ml | 62 ++++++++++++++++++++++++++ 2 files changed, 64 insertions(+) create mode 100644 sysprep/sysprep_operation_ca_certificates.ml diff --git a/sysprep/Makefile.am b/sysprep/Makefile.am index

Remove the generated kerberos data in the guest. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- sysprep/Makefile.am | 2 ++ sysprep/sysprep_operation_kerberos_data.ml | 52 ++++++++++++++++++++++++++++ 2 files changed, 54 insertions(+) create mode 100644 sysprep/sysprep_operation_kerberos_data.ml diff --git a/sysprep/Makefile.am

V1->V2: add the documentation. V2->V3: change the split sign from ":" to "@" for IPv6. Add the the ipconfig for vir-prep. Usage like below: [root at Allen ~]# virt-sysprep --ipconfig="eth0:192.168.1.2,255.255.255.0,192.168.1.1" --enable=ipconfig -d clone-6u1 OR [root at Allen ~]# virt-sysprep -d clone-6u1 Signed-off-by: Wanlong Gao <gaowanlong at

On Mon, 27 Feb 2023, Nico Kadel-Garcia wrote: >> > does any one of you have a best practice on renewing ssh host keys on cloned >> > machines? >> >> Yes: not cloning machines. > >Good luck with *that*. Building VM's from media is a far, far too >lengthy process for production deployment, especially for auto-scaling >clusters. (It?s ?VMs?, no genitive

Hello, I'm having a problem when trying to use virt-sysprep against vms that have rbd disk images. When I run virt-sysprep I get the following error: >> root@kitt:~/libguestfs-1.22.4# virt-sysprep -d server-clone-test --firstboot firstboot.sh >> Examining the guest ... >> Fatal error: exception Guestfs.Error("rbd: image name must begin with a '/'") My

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

Hi Rich: I just send a patch to request for your comments, then will do further work about this. things like this: [root at Allen ~]# virt-sysprep --ipconfig="eth0:192.168.1.2,255.255.255.0,192.168.1.1" --enable=ipconfig -d clone-6u1 OR [root at Allen ~]# virt-sysprep -d clone-6u1 Please comments. Thanks -Wanlong Gao Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com>

In the TODO file there's a discussion of perhaps writing a new 'virt-customize' tool. I think it's probably better (or at any rate, easier) to just add this functionality into virt-sysprep. That is what this small series of patches aims to achieve. Note these are not very well tested at the moment. The first patch adds a generic and useful '--firstboot' flag. The

Hi, My use case involves creating duplicates of saved virtual machines. Tried with virt-manager and with virsh but so far it seems like this case is not supported by these tools. Does anyone know how I could achieve the above? Thanks, Michael