I can confirm that the new libvirt packages fix the problem, my guest
vm's are again confined by apparmor.
Thanks.
--
virt-aa-helper fails when serial or console type is 'tcp'
https://bugs.launchpad.net/bugs/460271
You received this bug notification because you are a member of Ubuntu
Server
I can confirm that the new libvirt packages fix the problem, my guest
vm's are again confined by apparmor.
Thanks.
--
virt-aa-helper fails when serial or console type is 'tcp'
https://bugs.launchpad.net/bugs/460271
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
When serial and console devices are defined as follows:
...
serial type='tcp'
source mode='bind' host='127.0.0.1' service='1234'/
protocol type='telnet'/
target port='0'/
/serial
console type='tcp'
source mode='bind' host='127.0.0.1'
Public bug reported:
When serial and console devices are defined as follows:
...
serial type='tcp'
source mode='bind' host='127.0.0.1' service='1234'/
protocol type='telnet'/
target port='0'/
/serial
console type='tcp'
source mode='bind' host='127.0.0.1'
I'm seeing this too, clean up-to-date install of karmic alpha4 amd64
(netinst with mini.iso) on a physical machine.
This happens only when logged in via ssh, doing the test locally (over a
serial console) works. Definitely seems to be related to
