Applying http://article.gmane.org/gmane.comp.emulators.kvm.devel/45983
(also applied upstream, see http://git.kernel.org/?p=virt/kvm/qemu-
kvm.git;a=commit;h=e2a305fb13ff0f5cf6ff80aaa90a5ed5954c) on top of
0.12.3-0ubuntu11 fixes this problem for me.
This patch is also referenced in the above
Public bug reported:
Binary package hint: qemu-kvm
qemu-kvm has a faster method of doing I/O on Linux called Linux AIO.
According to my tests and the upstream maintainer
(http://news.gmane.org/gmane.comp.emulators.kvm.devel/cutoff=48050) it
is faster and should not cause any problems.
It is
Works in recent versions, most likely due to the dropped patch in
0.11.0-0ubuntu1
** Changed in: qemu-kvm (Ubuntu)
Status: Triaged = Fix Released
--
--daemonize option broken
https://bugs.launchpad.net/bugs/437389
You received this bug notification because you are a member of Ubuntu
ii qemu-kvm 0.11.0~rc2-0ubuntu12
Full virtualization on i386 and amd64 hardware
Ubuntu Karmic, up to date
--
--daemonize option broken
https://bugs.launchpad.net/bugs/437389
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
Binary package hint: qemu-kvm
The kvm --daemonize option is broken
be...@pest:~$ sudo kvm --daemonize
kvm_create_vcpu: Input/output error
create_userspace_phys_mem: Input/output error
kvm_cpu_register_physical_memory: failed
(yes this also happens with a complete option
Please find attached the two patches I use. commit-b0e62dc removes the
deletion of pc-bios/*.bin, because they are shipped upstream and git-
buildpackage is unhappy when they are deleted in the clean target.
With those patches applied cleaning without dependencies works fine, but
I'm not sure
** Attachment added: commit-b0e62dc
http://launchpadlibrarian.net/32501120/commit-b0e62dc
--
Unable to clean package without having all build-dep
https://bugs.launchpad.net/bugs/427876
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
bind9 from intrepid-proposed works fine for me on amd64
--
[intrepid] IPv6 unusable
https://bugs.launchpad.net/bugs/249824
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
--
Ubuntu-server-bugs mailing list
Please reopen this bug, this is NOT fixed.
[EMAIL PROTECTED]:~$ dig www.heise.de @2001:a60:f001:1::69
dig: couldn't get address for '2001:a60:f001:1::69': address family not
supported
[EMAIL PROTECTED]:~$ apt-cache show dnsutils | grep Version
Version: 1:9.5.0.dfsg.P2-1ubuntu2
** Changed in:
Not fixed in 1:9.5.0.dfsg.P2-1ubuntu2 (which should be based on
1:9.5.0.dfsg.P2-1, no?)
--
[intrepid] IPv6 unusable
https://bugs.launchpad.net/bugs/249824
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
--
This bug is still there with 1:9.5.0.dfsg.P2-1ubuntu1. Rebuilding the
source package on an IPv6 enabled box did not fix it.
In the buildlog at http://launchpadlibrarian.net/17069359
/buildlog_ubuntu-
intrepid-i386.bind9_1%3A9.5.0.dfsg.P2-1ubuntu1_FULLYBUILT.txt.gz you can
see
checking for
*** This bug is a duplicate of bug 249824 ***
https://bugs.launchpad.net/bugs/249824
** This bug has been marked a duplicate of bug 249824
[intrepid] IPv6 unusable
--
DNS: not able to use IPv6 Resolvers
https://bugs.launchpad.net/bugs/259740
You received this bug notification because you
*** This bug is a duplicate of bug 249824 ***
https://bugs.launchpad.net/bugs/249824
** This bug has been marked a duplicate of bug 249824
[intrepid] IPv6 unusable
--
bind9 doesn't bind to IPv6 interfaces
https://bugs.launchpad.net/bugs/257909
You received this bug notification because
Public bug reported:
Binary package hint: bind9
dig (from dnsutils 1:9.5.0.dfsg.P1-2~build1) in intrepid cannot use IPv6
transport apparently
[EMAIL PROTECTED]:~$ dig -6 -t lrz-muenchen.de @dns1.lrz-muenchen.de
dig: can't find IPv6 networking
The machine has working IPv6 connectivity
14 matches
Mail list logo