This bug was fixed in the package virt-manager - 0.9.4-2ubuntu3
---
virt-manager (0.9.4-2ubuntu3) raring; urgency=low
* debian/patches/uefi_support.patch: ugly hack to add a UEFI firmware
option. (LP: #1074207)
-- Marc DeslauriersTue, 05 Mar 2013 17:43:17
-0500
** Changed
** Branch linked: lp:ubuntu/raring-proposed/virt-manager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074207
Title:
please add support for configuring ovmf via use of qemu -L option
To manage not
Ping: Marc, I'm still using the ppa build of virt-manager here, are
there any remaining blockers in the underlying packages to having this
included in raring?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
edk2/ovmf is now available in raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074207
Title:
please add support for configuring ovmf via use of qemu -L option
To manage notifications about th
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: virt-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074207
Title:
This bug was fixed in the package qemu - 1.3.0+dfsg-1~exp3ubuntu8
---
qemu (1.3.0+dfsg-1~exp3ubuntu8) raring; urgency=low
* qemu-system.links:
- Add link to usr/share/ovmf/OVMF.fd (LP: #1074207)
- Fix target of /etc/kvm/kvm-if{up,down} links
-- Serge HallynTue, 29 Jan 2
This bug was fixed in the package libvirt - 1.0.1-0ubuntu3
---
libvirt (1.0.1-0ubuntu3) raring; urgency=low
* debian/apparmor/libvirt-qemu: add /usr/share/ovmf/** r (LP: #1074207)
-- Serge HallynTue, 29 Jan 2013 11:55:19 -0600
** Changed in: libvirt (Ubuntu)
Status: Con
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074207
Title:
please add support for configuring ovmf via use of qemu -L opt
On Fri, Jan 18, 2013 at 10:07:10PM -, Serge Hallyn wrote:
> @Jamie,
> do you think we should whitelist /**/OVMF.Fd, whitelist
> /usr/share/qemu/**, or are you suggesting something different (in
> comments #16 and #8)?
At present we have the following in
/etc/apparmor.d/abstractions/libvirt-qe
@Jamie,
do you think we should whitelist /**/OVMF.Fd, whitelist
/usr/share/qemu/**, or are you suggesting something different (in
comments #16 and #8)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/10
The path doesn't*need to be specified (as mentioned). What I am saying
is that I found a bug that shows there is a problem with virt-aa-helper
if you do specify it. This isn't OVMF.Fd specific. Using the at
all with an absolute path will result in a very lowlevel error that is
hard to diagnose and
Why would this need to be specified as an absolute path? I think the
existing model of passing different video bios types, and linking
everything into the common qemu directory, seems applicable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Actually, libvirt will likely want to be adjusted too-- Marc used
'OVMF.fd' which is fine and let's qemu find it and
virt-aa-helper happens to think that is ok, cause the path is relative.
However, if an absolute path is used (eg
'/usr/share/qemu/OVMF.fd'), then the guest will not
boot for the reas
Thanks Marc. This works well here. When using UEFI it adds the
OVMF.fd line to the xml and it doesn't when using the
default. Booting with UEFI I see the OVMF.fd firmware screen and without
UEFI I do not. Also, the way Marc implemented this, no changes are
needed to libvirt.
Small nit: I've only e
The first stab is a hack, as for it to be done properly: 1- qemu needs
to be able to report what firmware it locates and supports, 2- the
libvirt qemu driver needs to report that as capabilities, 3- libvirt
needs to be able to report loaders as capabilities, 4- virtinst needs to
support loader capa
OK, I've uploaded an ugly first stab at adding this to virt-manager in
the following PPA:
https://launchpad.net/~mdeslaur/+archive/testing/+packages
Make sure the firmware file is called "OVMF.fd" and is in the
hypervisor's default firmware directory. For qemu, this would be in
/usr/share/qemu.
On Fri, Nov 16, 2012 at 01:46:30PM -, Marc Deslauriers wrote:
> Since it will now be a single firmware file, I will probably use the
> -bios option via , so the ovmf firmware will need to go in
> the same directory as the other qemu firmware.
The other qemu firmware is all located in different
FYI, I compiled my own OVMF.Fd (http://people.canonical.com/~jamie/ovmf/). To
use immediately, do something like:
$ mkdir ~/vms/ovmf
$ cp bios.bin ~/vms/ovmf
Adjust /etc/apparmor.d/abstractions/libvirt-qemu to have:
# until libvirt is patched
@{HOME}/vms/ovmf/** r,
Then use in libvirt xml so
libvirt's virt-aa-helper valid_path() will also need to be updated. If
the OVMF.Fd (aka bios.bin) is in /usr/share, then specifying
'/usr/share//bios.bin' causes virt-
aa-helper to fail because files in /usr/share are currently considered
restricted. This can be fixed by adding "/usr/share/" to
"ov
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Since it will now be a single firmware file, I will probably use the
-bios option via , so the ovmf firmware will need to go in
the same directory as the other qemu firmware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Probably goes without saying, but libvirt will need to be updated such that
/etc/apparmor.d/abstractions/libvirt-qemu will need to have the following line:
/usr/share/ovmf/** r,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
(1) Re #3:
OVMF.fd includes OvmfVideo.rom starting with SVN rev 13520. A single
-bios option suffices.
(2) Re Bug Description:
Can you please tell me more about the package to be shipped in Raring
Ringtail? Is it available somewhere online (work in progress or
otherwise)? I'm especially interest
15:19 < mdeslaur> the ovmf package could ship the qemu-system-x86_64-uefi and
qemu-system-i386-uefi scripts, which
would just be a shell file that adds the appropriate option
for the alternate directory
15:20 < mdeslaur> and a trivial distro patch could be added to libvirt to g
OVMF includes its own implementation of the VGA BIOS which must be used
together with the BIOS image. So the override of the VGA BIOS path is
quite deliberate; there doesn't seem to be a way to point at an
arbitrary VGA BIOS file with libvirt. The override of the keymaps path
is less deliberate,
The -L option probably wouldn't be appropriate because it will also
change the default path for the VGA bios and keymaps.
Would the -bios option work for this firmware? If so, I believe libvirt
already supports settings this via in , in which case
adding it to virt-manager would be a lot more ele
26 matches
Mail list logo
