Am 18.11.2022 um 22:37 schrieb John W. Himpel
<john(a)jlhimpel.net>:
All,
I am following the instructions found at:
https://docs.fedoraproject.org/en-US/fedora-server/virtualization/vm-inst...
I have found what I believe is a typo in the provided example in the
documentation:
[…]# wget
https://download.fedoraproject.org/pub/fedora/linux/releases/37/Server/x8...
s/b
[…]# wget
https://download.fedoraproject.org/pub/fedora/linux/releases/37/Server/x8...
Indeed, wrong link. The korrekt link is obviously :
https://download.fedoraproject.org/pub/fedora/linux/releases/37/Server/x8...
and it gives you the file Fedora-Server-KVM-37-1.7.x86_64.qcow2
But at least the link for the checksum is correct.
Unfortunately the KVM image was missing on getfedora in the beginning and it is a bit
different now than during the rc phase. The devil is in the details and you can't test
every little thing enough :-).
When I attempted to install the custom.qcow2 image, fedora37 is not
currently found as an acceptable --os-variant (The osinfo-query os
command hasn't been updated yet). So I tried fedora36 and fedora-
unknown, neither one changed the results described below.
When I made the above changes, I ran the virt-install script. It
starts and outputs the following:
Starting install...
Creating domain... | 0 B
00:00
Running text console command: virsh --connect qemu:///system console
testFedora
Connected to domain 'testFedora'
Escape character is ^] (Ctrl + ])
At this point the shell script hangs. virt-manager shows the vm has
been created and is running, but the boot process seems to not have
started. I can use the spice protocol in virt-manager to open a
console to the vm, but the console shows no activity and seems
unresponsive.
If I hit <enter> in the shell or inside virt-manager nothing happens.
Or if if enter the escape character inside the shell or inside virt-
manager, nothing happens.
Has anyone successfully tried this documented procedure with the G/A
release of Fedora Server?
I tested it with the latest rc. I have already 'mothballed' my test environment
until the next release testing. I need to rebuild it 'just now' and test the
current image.
Peter