avocado-vt
avocado-vt copied to clipboard
avocado-framework
Add support to install and use Fedora rawhide guest
Add support to install and use Fedora rawhide guest image.
Signed-off-by: Satheesh Rajendran [email protected]
Tested on Powerpc:
06:53:23 INFO | Running libvirt command (reformatted):
06:53:23 INFO | /usr/bin/virt-install
06:53:23 INFO | --connect=qemu:///system
06:53:23 INFO | --hvm
06:53:23 INFO | --accelerate
06:53:23 INFO | --name 'virt-tests-vm1'
06:53:23 INFO | --machine pseries
06:53:23 INFO | --memory=32768
06:53:23 INFO | --vcpu=32,sockets=1,cores=4,threads=8
06:53:23 INFO | --location https://dl.fedoraproject.org/pub/fedora-secondary/development/rawhide/Server/ppc64le/os
06:53:23 INFO | --nographics
06:53:23 INFO | --serial pty
06:53:23 INFO | --memballoon model=virtio
06:53:23 INFO | --controller type=scsi,model=virtio-scsi
06:53:23 INFO | --disk path=/home/add_disk/tests/data/avocado-vt/images/fdevel-ppc64le.qcow2,bus=scsi,size=20,format=qcow2
06:53:23 INFO | --network=bridge=virbr0,model=virtio,mac=52:54:00:58:25:10
06:53:23 INFO | --mac=52:54:00:58:25:10
06:53:23 INFO | --extra-args 'console=hvc0 serial inst.repo=https://dl.fedoraproject.org/pub/fedora-secondary/development/rawhide/Server/ppc64le/os nicdelay=60 inst.sshd ip=dhcp inst.ks=http://192.168.124.1:8095/ks.cfg'
06:53:23 INFO | --noautoconsole
06:53:23 INFO | Running '/usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries --memory=32768 --vcpu=32,sockets=1,cores=4,threads=8 --location https://dl.fedoraproject.org/pub/fedora-secondary/development/rawhide/Server/ppc64le/os --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/home/add_disk/tests/data/avocado-vt/images/fdevel-ppc64le.qcow2,bus=scsi,size=20,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:58:25:10 --mac=52:54:00:58:25:10 --extra-args 'console=hvc0 serial inst.repo=https://dl.fedoraproject.org/pub/fedora-secondary/development/rawhide/Server/ppc64le/os nicdelay=60 inst.sshd ip=dhcp inst.ks=http://192.168.124.1:8095/ks.cfg' --noautoconsole'
06:53:28 DEBUG| [stdout]
06:53:28 DEBUG| [stdout] Starting install...
06:53:28 DEBUG| [stdout]
06:53:28 DEBUG| [stdout] Retrieving file vmlinuz... 1% [ ] 0 B/s | 496 kB --:-- ETA
06:53:28 DEBUG| [stdout]
06:53:28 DEBUG| [stdout] Retrieving file vmlinuz... 4% [- ] 1.4 MB/s | 1.4 MB 00:22 ETA
06:53:28 DEBUG| [stdout]
06:53:28 DEBUG| [stdout] Retrieving file vmlinuz... 8% [= ] 1.6 MB/s | 2.7 MB 00:19 ETA
06:53:28 DEBUG| [stdout]
06:53:28 DEBUG| [stdout] Retrieving file vmlinuz... 13% [== ] 1.9 MB/s | 4.5 MB 00:15 ETA
06:53:28 DEBUG| [stdout]
06:53:28 DEBUG| [stdout] Retrieving file vmlinuz... 20% [===- ] 2.3 MB/s | 7.1 MB 00:11 ETA
06:53:28 DEBUG| [stdout]
06:53:28 DEBUG| [stdout] Retrieving file vmlinuz... 31% [===== ] 2.8 MB/s | 11 MB 00:08 ETA
06:53:28 DEBUG| [stdout]
06:53:28 DEBUG| [stdout] Retrieving file vmlinuz... 46% [=======- ] 3.7 MB/s | 16 MB 00:04 ETA
06:53:28 DEBUG| [stdout]
06:53:28 DEBUG| [stdout] Retrieving file vmlinuz... 67% [===========- ] 4.9 MB/s | 23 MB 00:02 ETA
06:53:28 DEBUG| [stdout]
06:53:28 DEBUG| [stdout] Retrieving file vmlinuz... 97% [================-] 6.6 MB/s | 33 MB 00:00 ETA
06:53:28 DEBUG| [stdout]
06:53:28 DEBUG| [stdout] Retrieving file vmlinuz... | 34 MB 00:02
06:53:29 DEBUG| [stdout]
06:53:29 DEBUG| [stdout] Retrieving file initrd.img 20% [===- ] 0 B/s | 15 MB --:-- ETA
06:53:29 DEBUG| [stdout]
06:53:29 DEBUG| [stdout] Retrieving file initrd.img 44% [======= ] 27 MB/s | 31 MB 00:01 ETA
06:53:29 DEBUG| [stdout]
06:53:29 DEBUG| [stdout] Retrieving file initrd.img 70% [===========- ] 29 MB/s | 49 MB 00:00 ETA
06:53:29 DEBUG| [stdout]
06:53:29 DEBUG| [stdout] Retrieving file initrd.img 94% [================ ] 31 MB/s | 67 MB 00:00 ETA
06:53:29 DEBUG| [stdout]
06:53:29 DEBUG| [stdout] Retrieving file initrd.img... | 70 MB 00:01
06:53:30 DEBUG| [stdout] Domain installation still in progress. You can reconnect to
06:53:30 DEBUG| [stdout] the console to complete the installation process.
06:53:30 INFO | Command '/usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'virt-tests-vm1' --machine pseries --memory=32768 --vcpu=32,sockets=1,cores=4,threads=8 --location https://dl.fedoraproject.org/pub/fedora-secondary/development/rawhide/Server/ppc64le/os --nographics --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/home/add_disk/tests/data/avocado-vt/images/fdevel-ppc64le.qcow2,bus=scsi,size=20,format=qcow2 --network=bridge=virbr0,model=virtio,mac=52:54:00:58:25:10 --mac=52:54:00:58:25:10 --extra-args 'console=hvc0 serial inst.repo=https://dl.fedoraproject.org/pub/fedora-secondary/development/rawhide/Server/ppc64le/os nicdelay=60 inst.sshd ip=dhcp inst.ks=http://192.168.124.1:8095/ks.cfg' --noautoconsole' finished with 0 after 7.158175945281982s
06:53:30 DEBUG| waiting for domain virt-tests-vm1 to start (0.000009 secs)
06:53:30 DEBUG| Command used to create serial console: virsh -c qemu:///system console virt-tests-vm1 serial0
06:53:30 INFO | Waiting for installation to finish. Timeout set to 4800 s (80 min)
06:53:30 DEBUG| Monitoring serial console log for completion message: /home/add_disk/tests/results/job-2020-09-09T06.53-4aa34e2/test-results/1-guest_install.url.qemu.qcow2.virtio_scsi.smp2.virtio_net.Guest.Fedora.devel.ppc64le.io-github-autotest-qemu.unattended_install.url.http_ks.default_install.aio_native/serial-serial0-virt-tests-vm1-5o3w.log
06:53:32 DEBUG| virt-tests-vm1 alive now. Used to failed to get register info from guest 2 times
06:54:36 DEBUG| builtin http server handling request from 192.168.124.165: "GET /ks.cfg HTTP/1.1" 200 -
07:04:35 DEBUG| Message read from serial console log: Post set up finished
07:04:35 DEBUG| cleaning up threads and mounts that may be active
07:04:36 INFO | Guest reported successful installation after 665 s (11 min)
07:04:36 INFO | Wait for guest to shutdown cleanly
07:04:48 INFO | Guest managed to shutdown cleanly
@dzhengfy it's about installing, maybe we could ask qemu team to help review?
Do we need rename devel.cfg to more specific to Fedora rawhide, such as fedora_rawhide_devel.cfg?
Do we need rename devel.cfg to more specific to Fedora rawhide, such as fedora_rawhide_devel.cfg?
@chunfuwen devel.cfg would be simple, I feel, what say?