Tired of fiddling with guest XML files and virtual DJing with ISO images? Then
our latest entry in our Knowledge Series might come handy! Plus it also offers
access to further Linux distributions on IBM Z!
Read more on how virt-install can help at
http://kvmonz.blogspot.com/2018/07/knowledge-use
Both are after the successful install. I didn't capture the failed install
command.
>>> On 8/5/2017 at 11:52 AM, Neale Ferguson wrote:
> This is using both mechanisms to create working guests -
The first one doesn't look like it's for the actual install, but after that. I
don't see anything pointing to your installation kernel, initrd, or ISO image
(or otherwise).
Mark Pos
-msg timestamp=on
It would be interesting to see what qemu command gets generated via
virt-manager versus virt-install.
--
For LINUX-390 subscribe / signoff / archive access instructions
enerated via
virt-manager versus virt-install.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/ht
I found the problem disappeared when I changed location from the
loop-mounted ISO image to the URL of the ClefOS download site. Things are
installing as expected.
Neale
--
For LINUX-390 subscribe / signoff / archive access instru
Hard to tell from afar ... could you try to run virt-install with
>"--print-step all" (not sure which one to use in this case) and post the
>resulting domain XML?
>What versions of qemu and libvirt are you using?
---
tiple times and then giving up:
>
> Starting Switch Root...
> [FAILED] Failed to start Switch Root.
> See 'systemctl status initrd-switch-root.service' for details.
>
> Is there something I should have specified in the vert-install:
>
> vir
nitrd-switch-root.service' for details.
Is there something I should have specified in the vert-install:
virt-install\
--name=itzgeekguest \
--connect=qemu:///system\
