Hi,
>> # virt-install --name demo --hvm --memory 1024 --virt-type kvm \
>> -x "ks=/var/lib/libvirt/images/anaconda-ks.cfg" \
>
>
> https://rhinstaller.github.io/anaconda/boot-options.html#inst-repo
>
> The kickstart location is read by the operating system inside the VM. It
> doesn't hav
On 07/22/2015 04:12 PM, Alex wrote:
# virt-install --name demo --hvm --memory 1024 --virt-type kvm \
-x "ks=/var/lib/libvirt/images/anaconda-ks.cfg" \
https://rhinstaller.github.io/anaconda/boot-options.html#inst-repo
The kickstart location is read by the operating system inside the V
Hi,
>> I'm aware of kickstart, but have never used it. Is that the best
>> option, or is something like chef or puppet easier?
>> ...
>> I've experimented with virt-install, but that apparently doesn't
>> provide the ability to select all of the install config options
>
> It might help to picture
On 07/22/2015 07:39 AM, Alex wrote:
I'm aware of kickstart, but have never used it. Is that the best
option, or is something like chef or puppet easier?
...
I've experimented with virt-install, but that apparently doesn't
provide the ability to select all of the install config options
It might
On Wed, Jul 22, 2015 at 10:39:15AM -0400, Alex wrote:
> I have a fedora22 server with libvirt/kvm/qemu installed and would
> like to use it to create a number of kvm virtual instances remotely,
> non-interactively, according to my parameters (memory, disk layout,
> package options, etc).
> I'm awar
Hi,
I have a fedora22 server with libvirt/kvm/qemu installed and would
like to use it to create a number of kvm virtual instances remotely,
non-interactively, according to my parameters (memory, disk layout,
package options, etc).
I'm aware of kickstart, but have never used it. Is that the best
op