On Tue, Oct 02, 2018 at 06:21:01AM -0700, femi adegoke wrote: > Yes, Pavel that is correct, as in not wanting the guest to get started. > > I was hoping I could use virt-manager to "create" templates by "creating" a > guest vm that is ready to be powered on whenever it's needed. > I could do this in Hyper-V & was hoping for similar functionality.
As a workaround you can create and start the guest and shut it down right after the creation is done. But I guess that for the import method it would make sense to add an option to just define the guest without starting it. Pavel > > On Oct 2 2018, at 5:28 am, Pavel Hrdina <phrd...@redhat.com> wrote: > > > > On Tue, Oct 02, 2018 at 04:34:22AM -0700, femi adegoke wrote: > > > I just tried using the "import" function. > > > This does not work, it still wants to start the installation. > > > > > > So we need to agree on terminology: > > If you are creating new guest using virt-manager GUI there are four > > options: Local install media, Network install, Network Boot and Import. > > > > From virt-manager/virt-install point of view the first three options > > has two phases, install phase and final phase. The install phase > > usually uses a different domain definition that the final phase. > > During the install phase user usually installs the OS inside the guest > > and once the installation is completed the definition is changed and it > > starts again to the final phase. > > > > In case of 'Import' installation there is no install phase, there is > > only final phase. > > > > With virt-manager GUI the guest is always started no matter which > > installation method is selected. > > > > From your description I'm guessing that you don't want the guest to be > > started after it's created, that is not possible with virt-manager. > > > > Pavel
signature.asc
Description: PGP signature
_______________________________________________ virt-tools-list mailing list virt-tools-list@redhat.com https://www.redhat.com/mailman/listinfo/virt-tools-list
