OVMF not starting if logical host CPUs current allocation is more than 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
edk2 (Ubuntu) |
Incomplete
|
Medium
|
Unassigned | ||
virt-manager (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
After creating VM through virt-manager with OVMF booting only black screen I can see when starting it.
The reason is that if in VM parameters to choose "1" for logical host CPUs current allocation, it starts good, but if to choose "2" or higher OVMF doesn't starts - only black screen and nothing.
Host: Kubuntu 16.04 x86_64
ovmf: 0~20160408.
virt-manager: 1.3.2-3ubuntu1
Please, ask for any additional info.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: virt-manager 1:1.3.2-3ubuntu1
Uname: Linux 4.6.0-040600-
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Thu May 19 21:00:52 2016
InstallationDate: Installed on 2014-06-08 (711 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
PackageArchitec
SourcePackage: virt-manager
UpgradeStatus: Upgraded to xenial on 2016-02-04 (104 days ago)
summary: |
- OVMF not starting on newly created windows VM + OVMF not starting if logical host CPUs current allocation is more than 1 |
description: | updated |
description: | updated |
description: | updated |
Changed in edk2 (Ubuntu): | |
importance: | Undecided → Medium |
Changed in virt-manager (Ubuntu): | |
importance: | Undecided → Medium |
Status changed to 'Confirmed' because the bug affects multiple users.