On Mon, Aug 22, 2016 at 05:49:30PM -, 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
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 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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:
** Changed in: edk2 (Ubuntu)
Importance: Undecided => Medium
** Changed in: virt-manager (Ubuntu)
Importance: Undecided => Medium
--
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:
** Description changed:
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" the VM
- doesn't starts -
** 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.
** Summary changed:
- OVMF not starting on newly created windows VM
+ OVMF not starting if logical host CPUs current allocation is more than 1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583728
