This bug was fixed in the package libvirt - 0.8.3-1ubuntu1
---
libvirt (0.8.3-1ubuntu1) maverick; urgency=low
* Merge from debian unstable with security fixes
* Fixes:
- LP: #588369
- LP: #585964
* Remaining changes:
- debian/control:
+ Build-Depends on qemu-kv
** Changed in: libvirt (Ubuntu)
Status: Confirmed => In Progress
--
problems with using parallel port
https://bugs.launchpad.net/bugs/609055
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs
now I've changed the rights for /dev/parport0 with chmod to 777 and run
qemu out of the terminal, and now it works fine
--
problems with using parallel port
https://bugs.launchpad.net/bugs/609055
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribe
What do you mean with "confirmed"?
Maybe the problem with the parallel port is configuration problem, but that I
can't boot the vm (as I've written in post #4) is at least quite strange. :(
Can you help me, please? ;)
--
problems with using parallel port
https://bugs.launchpad.net/bugs/609055
Yo
This appears to be related to the apparmor profile in libvirt.
** Package changed: virt-manager (Ubuntu) => libvirt (Ubuntu)
** Tags added: apparmor
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Changed in: libvirt (Ubuntu)
Status: Incomple
