@Etienne Goyer: I changed the timelimit and bind policy, installed
libnss-ldapd and now I don't get trouble with the gnome-session. However
I got other trouble like bug #672521.
I aggree with your analysis but I'm still looking for a paintless
solution. I'll probably write a shell script that
Try this that has been working for me when I added a name (in /etc/hosts
host's file) to the IP used by the guess: $ sudo kill -HUP `pidof
dnsmasq`
Howerver I get a different (related trouble): custom host definition is not
honor with my configuration (even after rebooting the host). dnsmasq
Ok in fact I founded why this was not working. I deleted and recreated
my VM but there still was an entry corresponding to the old one in
/var/lib/libvirt/dnsmasq/default.hostsfile. So I modified the MAC
address and now it is working like a charm (after using HUP signal).
--
libvirt can't add
** Attachment added: xsession-errors
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/654249/+attachment/1693837/+files/xsession-errors
--
libnss-ldap create troubles in gnome session when ldap server is unreacheable
https://bugs.launchpad.net/bugs/654249
You received this bug
** Attachment added: 0-slave.log
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/654249/+attachment/1693843/+files/0-slave.log
--
libnss-ldap create troubles in gnome session when ldap server is unreacheable
https://bugs.launchpad.net/bugs/654249
You received this bug
** Attachment added: 0.log
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/654249/+attachment/1693844/+files/0.log
--
libnss-ldap create troubles in gnome session when ldap server is unreacheable
https://bugs.launchpad.net/bugs/654249
You received this bug notification because
** Attachment added: 0-greeter.log
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/654249/+attachment/1693845/+files/0-greeter.log
--
libnss-ldap create troubles in gnome session when ldap server is unreacheable
https://bugs.launchpad.net/bugs/654249
You received this bug
$ egrep -v ^(#|$) /etc/ldap.conf | cat
base dc=local
uri ldap://ldap.tlse.lng/
ldap_version 3
rootbinddn cn=manager,dc=example,dc=net
timelimit 2
bind_timelimit 1
bind_policy soft
idle_timelimit 1
pam_password md5
nss_initgroups_ignoreusers
Public bug reported:
System : Ubuntu 10.10
Case : Multiple backing file
Result :
$ cat
/etc/apparmor.d/libvirt/libvirt-c05e04f2-fe2e-b8de-c129-bd074c908476.files
# DO NOT EDIT THIS FILE DIRECTLY. IT IS MANAGED BY LIBVIRT.
/var/log/libvirt/**/trifyl-obm23-lenny.log w,
A temporary workaround in my case is to:
1/ add the denied file in the Template /etc/apparmor.d/libvirt/TEMPLATE :
/U/libvirt-image/base/lenny_compressed.qcow2 r,
2/ Remove the generated file
/etc/apparmor.d/libvirt/libvirt-c05e04f2-fe2e-b8de-c129-bd074c908476*
3/ Reload apparmor and start the VM
Public bug reported:
Binary package hint: libnss-ldap
System : Maverick RC
Steps to reproduce:
- Install libnss-ldap and set it up correctly
= Gnome sessions should work normally for a local user
- Plug the computer in an other network or unplug it
= the ldap server should be unreacheable
-
Actually this change is responsible of an new trouble with apparmor.
Extract of /var/log/syslog:
Mar 23 14:19:13 kiwi kernel: [ 7025.583776] type=1503 audit(1269350353.212:49):
operation=open pid=17840 parent=1
profile=libvirt-f25941b5-8a0b-086a-888e-fe8570f0487d requested_mask=r::
** Patch added: Fix apparmor profil with new package seabios
http://launchpadlibrarian.net/41715543/apparmor_seabios.diff
--
BIOS shipped as binary blobs without source
https://bugs.launchpad.net/bugs/541524
You received this bug notification because you are a member of Ubuntu
Server Team,
I just update the packages that added libvirt-qemu to kqemu too but
doesn't solve the trouble. I still have to change the permissions of
/dev/kvm. Am I the only one that encountered this trouble ?
--
[PPA] VT is not used with libvirt 0.7.5
https://bugs.launchpad.net/bugs/503376
You received this
I changed the group bug it still doesn't use kvm.
$ groups libvirt-qemu
libvirt-qemu : libvirtd kvm
As strange as it can be, when I run the kvm same command as user libvirt-qemu
it appears that kvm is used (I can't remove the module), but not when using
virt-manager.
I checked euid et ruid of
I just installed the lucid's kernel.
I've got the following traceback when trying to launch a VM :
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 588, in run_domain
vm.startup()
File /usr/share/virt-manager/virtManager/domain.py, line 150, in
Public bug reported:
When starting a VM with the virtual manager, VT is not used and the VM
is slow.
System : Ubuntu 9.10
Hardware : CPU Intel with VT
Software : libvirt from dnjl's Virtualization PPA
I can see it because it's possible to remove kvm_intel module while the VM is
running.
The
17 matches
Mail list logo
