syslog with successful KVM test on 5.8.0-53
** Attachment added: "arm64-kvm-5-8-0-53.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929925/+attachment/5500864/+files/arm64-kvm-5-8-0-53.log
** Description changed:
Issue found on 5.8.0-54-generic proposed ARM64 kernel with node "helo",
"wright"
This issue does not exist in 5.8.0-53.60 so this might be a regression.
Test case:
- Create a KVM with the following command:
- uvt-kvm create bjf-test release=groovy arch=arm64
- Or you can run the ubuntu_kvm_smoke_test with autotest:
- git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
-b master-next
- git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
- rm -fr autotest/client/tests
- ln -sf ~/autotest-client-tests autotest/client/tests
- sudo apt-get install git python-minimal -y || sudo apt install python2 -y
- AUTOTEST_PATH=/home/ubuntu/autotest sudo -E
autotest/client/autotest-local --verbose
autotest/client/tests/ubuntu_kvm_smoke_test/control
+ 1. Deploy Groovy on an ARM64 node
+ 2. Create a KVM with the following command:
+ uvt-kvm create bjf-test release=groovy arch=arm64
+ Or you can run the ubuntu_kvm_smoke_test with autotest:
+ git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
-b master-next
+ git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
+ rm -fr autotest/client/tests
+ ln -sf ~/autotest-client-tests autotest/client/tests
+ sudo apt-get install git python-minimal -y || sudo apt install python2 -y
+ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E
autotest/client/autotest-local --verbose
autotest/client/tests/ubuntu_kvm_smoke_test/control
+ 3. Install the proposed kernel and reboot
+ 4. Repeat step 2
This is 100% reproducible on ARM64, 4 out of 4 attempts (twice on each
nodes).
Test log:
- + SUT=bjf-test
- + SSH_KEY=/home/ubuntu/.ssh/id_rsa
- + SSH_OPTIONS='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
-o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
- ++ lsb_release -c
- ++ awk '{print$2}'
- + DISTRO=groovy
- + ARCHITECTURE=arm64
- + trap cleanup EXIT
- + '[' -z arm64 ']'
- + kvm-ok
- + '[' 0 '!=' 0 ']'
- + '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
- + '[' arm64 = ppc64el ']'
- ++ uvt-simplestreams-libvirt query
- ++ grep -P 'groovy.*arm64'
- + image='release=groovy arch=arm64 label=daily (20210527)'
- + '[' -z 'release=groovy arch=arm64 label=daily (20210527)' ']'
- + uvt-kvm create bjf-test release=groovy arch=arm64
- uvt-kvm: error: libvirt: unsupported configuration: Emulator
'/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'
+ + SUT=bjf-test
+ + SSH_KEY=/home/ubuntu/.ssh/id_rsa
+ + SSH_OPTIONS='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
-o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
+ ++ lsb_release -c
+ ++ awk '{print$2}'
+ + DISTRO=groovy
+ + ARCHITECTURE=arm64
+ + trap cleanup EXIT
+ + '[' -z arm64 ']'
+ + kvm-ok
+ + '[' 0 '!=' 0 ']'
+ + '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
+ + '[' arm64 = ppc64el ']'
+ ++ uvt-simplestreams-libvirt query
+ ++ grep -P 'groovy.*arm64'
+ + image='release=groovy arch=arm64 label=daily (20210527)'
+ + '[' -z 'release=groovy arch=arm64 label=daily (20210527)' ']'
+ + uvt-kvm create bjf-test release=groovy arch=arm64
+ uvt-kvm: error: libvirt: unsupported configuration: Emulator
'/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'
syslog:
May 28 07:08:13 helo-kernel kernel: [ 285.470965] qemu-system-aar using
unsupported default IPA limit, upgrade your VMM
May 28 07:08:13 helo-kernel libvirtd[3766]: libvirt version: 6.6.0, package:
1ubuntu3.5 (Christian Ehrhardt <christian.ehrha...@canonical.com> Wed, 07 Apr
2021 13:33:46 +0200)
May 28 07:08:13 helo-kernel libvirtd[3766]: hostname: helo-kernel
May 28 07:08:13 helo-kernel libvirtd[3766]: unsupported configuration:
Emulator '/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'
-
Please find attachment for the syslog on 5.8.0-53.60
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-54-generic 5.8.0-54.61
ProcVersionSignature: Ubuntu 5.8.0-54.61-generic 5.8.18
Uname: Linux 5.8.0-54-generic aarch64
AlsaDevices:
- total 0
- crw-rw---- 1 root audio 116, 1 May 28 07:04 seq
- crw-rw---- 1 root audio 116, 33 May 28 07:04 timer
+ total 0
+ crw-rw---- 1 root audio 116, 1 May 28 07:04 seq
+ crw-rw---- 1 root audio 116, 33 May 28 07:04 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu50.6
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDmesg:
-
+
Date: Fri May 28 07:10:15 2021
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: To be filled by O.E.M. Saber
PciMultimedia:
-
+
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-54-generic
root=UUID=6660a008-6d09-4dba-a6f8-0fb57ee2582f ro sysrq_always_enabled
RelatedPackageVersions:
- linux-restricted-modules-5.8.0-54-generic N/A
- linux-backports-modules-5.8.0-54-generic N/A
- linux-firmware 1.190.5
+ linux-restricted-modules-5.8.0-54-generic N/A
+ linux-backports-modules-5.8.0-54-generic N/A
+ linux-firmware 1.190.5
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2020
dmi.bios.release: 7.4
dmi.bios.vendor: EDK II
dmi.bios.version: 0ACKL030
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Saber
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 2
dmi.chassis.vendor: To be filled by O.E.M.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnEDKII:bvr0ACKL030:bd06/04/2020:br7.4:svnTobefilledbyO.E.M.:pnSaber:pvr1.0:rvnTobefilledbyO.E.M.:rnSaber:rvr1.0:cvnTobefilledbyO.E.M.:ct2:cvr1.0:
dmi.product.family: CN99XX
dmi.product.name: Saber
dmi.product.sku: SABER SKU
dmi.product.version: 1.0
dmi.sys.vendor: To be filled by O.E.M.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1929925
Title:
[Potential Regression] Unable to create KVM with uvtool on Groovy
ARM64
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Groovy:
New
Bug description:
Issue found on 5.8.0-54-generic proposed ARM64 kernel with node
"helo", "wright"
This issue does not exist in 5.8.0-53.60 so this might be a
regression.
Test case:
1. Deploy Groovy on an ARM64 node
2. Create a KVM with the following command:
uvt-kvm create bjf-test release=groovy arch=arm64
Or you can run the ubuntu_kvm_smoke_test with autotest:
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
-b master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
sudo apt-get install git python-minimal -y || sudo apt install python2 -y
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E
autotest/client/autotest-local --verbose
autotest/client/tests/ubuntu_kvm_smoke_test/control
3. Install the proposed kernel and reboot
4. Repeat step 2
This is 100% reproducible on ARM64, 4 out of 4 attempts (twice on each
nodes).
Test log:
+ SUT=bjf-test
+ SSH_KEY=/home/ubuntu/.ssh/id_rsa
+ SSH_OPTIONS='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
-o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
++ lsb_release -c
++ awk '{print$2}'
+ DISTRO=groovy
+ ARCHITECTURE=arm64
+ trap cleanup EXIT
+ '[' -z arm64 ']'
+ kvm-ok
+ '[' 0 '!=' 0 ']'
+ '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
+ '[' arm64 = ppc64el ']'
++ uvt-simplestreams-libvirt query
++ grep -P 'groovy.*arm64'
+ image='release=groovy arch=arm64 label=daily (20210527)'
+ '[' -z 'release=groovy arch=arm64 label=daily (20210527)' ']'
+ uvt-kvm create bjf-test release=groovy arch=arm64
uvt-kvm: error: libvirt: unsupported configuration: Emulator
'/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'
syslog:
May 28 07:08:13 helo-kernel kernel: [ 285.470965] qemu-system-aar using
unsupported default IPA limit, upgrade your VMM
May 28 07:08:13 helo-kernel libvirtd[3766]: libvirt version: 6.6.0, package:
1ubuntu3.5 (Christian Ehrhardt <christian.ehrha...@canonical.com> Wed, 07 Apr
2021 13:33:46 +0200)
May 28 07:08:13 helo-kernel libvirtd[3766]: hostname: helo-kernel
May 28 07:08:13 helo-kernel libvirtd[3766]: unsupported configuration:
Emulator '/usr/bin/qemu-system-aarch64' does not support virt type 'kvm'
Please find attachment for the syslog on 5.8.0-53.60
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-54-generic 5.8.0-54.61
ProcVersionSignature: Ubuntu 5.8.0-54.61-generic 5.8.18
Uname: Linux 5.8.0-54-generic aarch64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 May 28 07:04 seq
crw-rw---- 1 root audio 116, 33 May 28 07:04 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu50.6
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDmesg:
Date: Fri May 28 07:10:15 2021
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: To be filled by O.E.M. Saber
PciMultimedia:
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-54-generic
root=UUID=6660a008-6d09-4dba-a6f8-0fb57ee2582f ro sysrq_always_enabled
RelatedPackageVersions:
linux-restricted-modules-5.8.0-54-generic N/A
linux-backports-modules-5.8.0-54-generic N/A
linux-firmware 1.190.5
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2020
dmi.bios.release: 7.4
dmi.bios.vendor: EDK II
dmi.bios.version: 0ACKL030
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Saber
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 2
dmi.chassis.vendor: To be filled by O.E.M.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnEDKII:bvr0ACKL030:bd06/04/2020:br7.4:svnTobefilledbyO.E.M.:pnSaber:pvr1.0:rvnTobefilledbyO.E.M.:rnSaber:rvr1.0:cvnTobefilledbyO.E.M.:ct2:cvr1.0:
dmi.product.family: CN99XX
dmi.product.name: Saber
dmi.product.sku: SABER SKU
dmi.product.version: 1.0
dmi.sys.vendor: To be filled by O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1929925/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
