** Description changed: - After creating VM through virt-manager for windows choosing windows 8.1 - option and OVMF for booting only black screen I can see when starting it - first time. + After creating VM through virt-manager with OVMF booting only black + screen I can see when starting it. - Interesting, but if create VM for ubuntu16.04 tianocore starts well. So - it seems windows 8.1 created configuration conflicts with ovmf for some - reason. + 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" the VM + 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)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583728 Title: OVMF not starting if logical host CPUs current allocation is more than 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1583728/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
