KVM does not start following the instructions in Fedora Server Documentation

[John W. Himpel]

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...


Also, the current image that I found was for version 37-1.7 not 37 (I
could not find a version 37).

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?

John Himpel

[Peter Boy]

>  Am 18.11.2022 um 22:37 schrieb John W. Himpel
> <john(a)jlhimpel.net&gt;:
>  
>  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

[Peter Boy]

>  Am 18.11.2022 um 22:37 schrieb John W. Himpel
> <john(a)jlhimpel.net&gt;:
>  
>  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. 
I followed the instructions of the doc as follows:

>  - - - - - - - - - - - - - - - - -  - — - - - - - - - - - - - - <
[root@zbox images]# virt-install  --name zvm01 \
     --memory 4096  --cpu host --vcpus 2 --graphics none \
     --os-variant fedora-unknown \
     --import  \
     --disk /var/lib/libvirt/images/zvm01.qcow2,format=qcow2,bus=virtio \
     --network type=direct,source=enp1s0,source_mode=bridge,model=virtio \
     --network bridge=virbr0,model=virtio

Installation wird gestartet …
Domain wird erstellt...                                                                   
                                       |    0 B  00:00:00     
Running text console command: virsh --connect qemu:///system console zvm01
Connected to domain 'zvm01'
Escape character is ^] (Ctrl + ])


== Longer pause, several seconds, less than 1 minute ==


[    0.000000] Linux version 6.0.7-301.fc37.x86_64
(mockbuild(a)bkernel01.iad2.fedoraproject.org) (gcc (GCC) 12.2.1 20220819 (Red Hat
12.2.1-2), GNU ld version 2.38-24.fc37) #1 SMP PREEMPT_DYNAMIC Fri Nov 4 18:35:48 UTC
2022
[    0.000000] Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.0.7-301.fc37.x86_64
root=/dev/mapper/sysvg-root ro console=tty1 console=ttyS0,115200n8 rd.lvm.lv=sysvg/root
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point
registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using
'standard' format.
[    0.000000] signal: max sigframe size: 1776

== (a lot of messages) ==

[  OK  ] Reached target nss-user-lo…[0m - User and Group Name Lookups.
         Starting systemd-logind.se…ice - User Login Management...
[  OK  ] Started rsyslog.service - System Logging Service.
[  OK  ] Started chronyd.service - NTP client/server.
[  OK  ] Finished dracut-shutdown.s…estore /run/initramfs on shutdown.
[   13.627422] NET: Registered PF_QIPCRTR protocol family
================================================================================
================================================================================

1) [x] Language settings                 2) [x] Time settings
       (English (United States))                (Etc/UTC timezone)
3) [x] Network configuration             4) [x] Root password
       (Connected: enp2s0, enp1s0)              (Root account is disabled)
5) [ ] User creation
       (No user will be created)


Please make a selection from the above ['c' to continue, 'q' to quit,
'r' to
refresh]: 
>  - - - - - - - - - - - - - - - - -  - — - - - - - - - - - - - - <

If after the line "Escape character is ^] (Ctrl + ])“ the systems seems to hang, it
is often an issue with the terminal. The system uses some kind of graphics display that
virt-install resp. virus can not use / show. But in the Background everything works.

Did you include the  „ --graphics none " option?

Can you ping the VM (of course, DHCP needs to be active, at least the internal net virbr0
should work)? 


Peter