The package was removed due to its SRU bug(s) not being verified in a
timely fashion.
** Changed in: libvirt (Ubuntu Wily)
Status: Fix Committed => Won't Fix
** Tags removed: removal-candidate verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bu
I'm sorry but I have no trusty VM machines anymore to check it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To manage notifications about this bug g
** Changed in: libvirt (Ubuntu Trusty)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To manage notifications about th
Hello Gannet, or anyone else affected,
Accepted libvirt into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/1.2.2-0ubuntu13.1.18 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
Hello. Sorry, I can't check in Wily. I'm using Xenial already and
finally it works in it! Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To man
Hello Gannet, or anyone else affected,
Accepted libvirt into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/1.2.16-2ubuntu11.15.10.4 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
Should be in the next version that gets SRUd, but that likely won't
happen until after the 16.04 feature freeze (in 8 days).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creati
In what libvirt version it will be fixed ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To manage notifications about this bug go to:
https://bugs.la
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu Wily)
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/1483071
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu Trusty)
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/1483071
Titl
** Also affects: libvirt (Ubuntu Trusty)
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/1483071
Title:
Error creating new VM with OVMF
To manage notificat
Since trusty is LTS, I think this wouldn't be superfluous.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To manage notifications about this bug go to
** Description changed:
+ =
+ SRU Justification
+ Impact: cannot start VMs with UEFI
+ Test case:
+ Regression potential: virt-aa-helper is modified to add the nvram files to
the allowed list, there should be no regressions.
+ =
+
The patch to fix this should be 91fdcefa7f145c1c39acc8e9a44fbfbf11568e54
upstream. It is in the xenial package. So I'm marking this fix
released and SRUing for wily.
Do we need this SRU'd to trusty too?
** Also affects: libvirt (Ubuntu Wily)
Importance: Undecided
Status: New
** Chan
Ran into this bug trying to test running under UEFI.
I was able to get the VM booting (but it dropped into the EFI shell, no
quite sure, but possible related to the use of the two files versus the
single-combined file). Here's how I reproduced the issue:
On xenial amd64 host,
- sudo add-apt-rep
Reproduced the issue(*) with Xenial / 1.2.21-2ubuntu4.
Following Zycorax's line of thinking(**), binary-patched virt-aa-helper to get
rid of the error.
$ perl -pi -e s/ovmf/OVMF/ virt-aa-helper
*: selecting UEFI when creating vm with virt-manager fails to create vm and
giving the apparmor profi
Thnak you @zycorax-0. That solved the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To manage notifications about this bug go to:
http
@jpvr,
The patch for virt-aa-helper to handle the nvram files is upstream, and
should hit xenial with the next merge. Then you shouldn't need the
template workaround.
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a memb
Adding this line
> /var/lib/libvirt/qemu/nvram/*_VARS.fd rw,
into
/etc/apparmor.d/libvirt/TEMPLATE.qemu
didn't helped.
Interesting things: error messages says it can't load AppArmor profile
"libvirt-203121ff-6933-4707-a851-3de158af5968". But it is really absent
in
/etc/apparmor.d/libvirt
So
A work-arround is to (ab)use the template file
/etc/apparmor.d/libvirt/TEMPLATE.qemu
---
profile LIBVIRT_TEMPLATE {
#include
/var/lib/libvirt/qemu/nvram/*_VARS.fd rw,
}
---
I'm not too familiar with AppArmour, nor kvm/libvirt's security model,
but I assume the whole point of virt-aa-helper i
I have encoutered a similar bug related to the libvirt per guest
AppArmor profile helper, libvirt-aa-helper
Virtual Machine Manager GUI reports
---
Error starting domain: internal error: process exited while connecting to
monitor: 2015-11-16T09:39:50.572025Z qemu-system-x86_64: -drive
file=/var
Also I wanna note again that I did:
systemctl stop apparmor.service
But it didn't helped.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To manage no
Hi Seth,
Quoting Seth Arnold (1483...@bugs.launchpad.net):
> Thanks Gannet; all your error messages mentioned AppArmor, so I expected
> to see some DENIED lines from AppArmor preventing libvirt access to
> files or resources.
Actually I'm not sure. The error comes in the loading of the apparmor
Thanks Gannet; all your error messages mentioned AppArmor, so I expected
to see some DENIED lines from AppArmor preventing libvirt access to
files or resources.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Note, that previous audit.log I've got after installing auditd and tried
to create an VM with OVMF and recieved an arror that noted in comment
#11. Then I looked into /var/log/audit/audit.log file and here it is
content in comment #15.
--
You received this bug notification because you are a membe
Also, here is /var/log/audit/audit.log contents after I tried to create
VM with OVMF:
type=DAEMON_START msg=audit(1444934142.375:5639): auditd start, ver=2.4.2
format=raw kernel=4.3.0-040300rc5-generic auid=4294967295 pid=12344
subj=unconfined res=success
type=USER_END msg=audit(1444934148.419:
/usr/share/virt-manager/virtManager/asyncjob.py:
def cb_wrapper(callback, asyncjob, *args, **kwargs):
try:
callback(asyncjob, *args, **kwargs)
What do you mean under "DENIED lines"? Do you mean asking me to show
line 89 of asyncjob.py file etc?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To
Gannet, can you include the new DENIED lines?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To manage notifications about this bug go to:
http
I'm stil having this issue, even with apparmor stopped (through
systemctl stop apparmor):
Не вдалося завершити встановлення: «внутрішня помилка: не вдалося
завантажити профіль AppArmor «libvirt-656c15f3-4203-45df-bfcf-
261421c96962»»
Traceback (most recent call last):
File "/usr/share/virt-mana
https://www.redhat.com/archives/libvir-list/2015-August/msg00761.html
Might also be required for UEFI under libvirt with AppArmor enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Yes, each time I'm checking by creating a new VM. Recently checked again
and againe have got the same:
Не вдалося завершити встановлення: «внутрішня помилка: не вдалося
завантажити профіль AppArmor «libvirt-a05215eb-12ea-
498b-a168-45708c63e8bc»»
Traceback (most recent call last):
File "/usr/sh
Hi,
Is the failure exactly the same as before? Does it persist if you try
with a newly defined VM?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To
** Changed in: libvirt (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To manage notifications about t
Oh, I ment:
'systemctl restart libvirt-bin.service'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To manage notifications about this bug go to:
https:
I tried it yesterday:
'systemctl service libvirt-bin.service'
but not helped. Today my machine newly booted but the same massage still
appears:
Не вдалося завершити встановлення: «внутрішня помилка: не вдалося
завантажити профіль AppArmor «libvirt-75ecf2fe-fc4e-
448d-a278-61fabcaf1851»»
Traceba
Gannet, this feels like it might be influenced by restarting the
libvirt-bin service; try this:
sudo service libvirt-bin restart
Then try recreating the new virtual machine.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
I've already 1.2.16-2ubuntu8 but error still appears:
Не вдалося завершити встановлення: «внутрішня помилка: не вдалося
завантажити профіль AppArmor «libvirt-ba2976da-97bc-
4f63-a9f6-66a8f1b23f38»»
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 8
This bug was fixed in the package libvirt - 1.2.16-2ubuntu8
---
libvirt (1.2.16-2ubuntu8) wily; urgency=medium
* Support OVMF images in virt-aa-helper. (LP: #1483071)
* Fix the libvirt-bin.preinst to not stop libvirt-bin on upgrade
from 1.2.16-2ubuntu7.
-- Serge Hallyn Fr
So we need to wait for new libvirt bugfixed version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483071
Title:
Error creating new VM with OVMF
To manage notifications about this bug go to:
https
This is a problem with virt-aa-helper.c. Basically, in valid_path()
this:
/* override the above with these */
const char * const override[] = {
"/sys/devices/pci", /* for hostdev pci devices */
"/etc/libvirt-sandbox/services/" /* for virt-sandbox service config
41 matches
Mail list logo
