OVMF not starting if logical host CPUs current allocation is more than 1

Bug #1583728 reported by Gannet
12
This bug affects 2 people
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.ffea0a2c-2
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-generic x86_64
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)
PackageArchitecture: all
SourcePackage: virt-manager
UpgradeStatus: Upgraded to xenial on 2016-02-04 (104 days ago)

Revision history for this message
Gannet (ken20001) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in edk2 (Ubuntu):
status: New → Confirmed
Changed in virt-manager (Ubuntu):
status: New → Confirmed
Gannet (ken20001)
summary: - OVMF not starting on newly created windows VM
+ OVMF not starting if logical host CPUs current allocation is more than 1
Gannet (ken20001)
description: updated
Gannet (ken20001)
description: updated
description: updated
Changed in edk2 (Ubuntu):
importance: Undecided → Medium
Changed in virt-manager (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Steve Langasek (vorlon) wrote :

I can't reproduce this failure with the indicated version of edk2 and version 1:1.3.2-3ubuntu1.16.04.2 of virt-manager (the current version in xenial as of this writing). Please provide a complete libvirt xml that can be used to reproduce the problem.

Changed in edk2 (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Gannet (ken20001) wrote :

After libvirt was updated to 2.0 this issue is gone.

> Please provide a complete libvirt xml that can be used to reproduce the problem.
What exactly xml-file do you need, vm_name.xml ?

Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 1583728] Re: OVMF not starting if logical host CPUs current allocation is more than 1

On Mon, Aug 22, 2016 at 05:49:30PM -0000, Gannet wrote:
> After libvirt was updated to 2.0 this issue is gone.

> > Please provide a complete libvirt xml that can be used to reproduce the problem.
> What exactly xml-file do you need, vm_name.xml ?

The one that would be output by 'virsh dumpxml <domain>'. On the
filesystem, this is normally stored under /etc/libvirt/qemu.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.