Failed to create kvm guest with uvt-kvm on Xenial/Zesty s390x zVM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
uvtool (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Steps:
1. Fetch the image with: uvt-simplestrea
2. Create the kvm: uvt-kvm create kvm-test release=xenial arch=s390x
Result:
* the uvt-kvm command returns "uvt-kvm: error: libvirt: XML error: No PCI buses available"
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.10.0-39-generic s390x
NonfreeKernelMo
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDmesg:
Date: Fri Nov 3 08:50:34 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=C
SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=/dev/
RelatedPackageV
linux-
linux-
linux-firmware 1.164.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
summary: |
- Failed to create kvm guest with uvt-kvm on Zesty s390x zVM + Failed to create kvm guest with uvt-kvm on Xenial/Zesty s390x zVM |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1729854
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.