Unfortunately, I no longer have that particular configuration available
for testing. (It's now in production, and I can no longer risk destroying
the data on the disks.)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
I didn't see a debug log appear; is there something special I need to do
to get it? Are you unable to duplicate this bug? What options are you
using that are different from mine?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
On 2010-06-24 22:24 - (Thu), Steven Wagner wrote:
As mentioned in comment #3, could this be related to a specific SATA
chipset?...Ive noticed no difference for if the guest is using virtio
or ide mode.
For me the guests work fine in IDE mode; it's only virtio that has a
problem. So, in a
masc, the bug you pointed out appears to be when using a particular
hardware SATA chipset; KVM isn't mentioned anywhere there. Are you
saying that this happens with KVM guests when running on hosts without
this problem?
Using dd, I wrote new 60GB file (writing zeros) on a guest using the KVM
IDE
Public bug reported:
Binary package hint: qemu-kvm
See this bug:
http://sourceforge.net/tracker/index.php?func=detailaid=2933400group_id=180599atid=893831
I have confirmed that this happens with 10.04 host and guest. Giving kvm
a logical virtio volume of 1024 GB works; a logical volume of 1048
Public bug reported:
Using the following command:
{{{
vmbuilder kvm ubuntu -v --debug \
--overwrite \
--raw=/dev/mapper/xxx --part=priv.partition \
--user=xxx --name=xxx --uid=1234 --gid=1234 \
--pass=xxx --ssh-user-key=/home/xxx/.ssh/authorized_keys \
--arch=amd64
Actually, come to think of it, I would be perfectly happy if you'd
change vmbuilder to take no command line options whatsoever, except
perhaps to turn on debug output, and just take a config file with the
myriad details necessary for setting up a new VM.
--
vmbuilder sometimes ignores --raw
I'm glad to hear you had good success with this with OpenBSD. It's also
been working on NetBSD for many, many years now.
--
Bind9 (8.04) not returning 'ad' flag when dnssec is enabled
https://bugs.launchpad.net/bugs/242956
You received this bug notification because you are a member of Ubuntu
As related in the original ticket description, all this stuff is working
fine under NetBSD; the issue is not with the data, but with Ubuntu. In
particular, there's certainly an issue with Ubuntu glibc that will
simply not allow it to check the AD bit.
While we only reported this recently, I'm
Note also that the definition of RES_USE_DNSSEC (defined to be
0x0020) must be added to /usr/include/resolv.h in order for
OpenSSH's openbsd-compat/getrrsetbyname.c to be able to set that bit
when edns0 is set.
--
Bind9 (8.04) not returning 'ad' flag when dnssec is enabled
It gets worse; I tried the above, and getrrsetbyname still doesn't get
back a record with the AD bit set. (I verified that RES_USE_DNSSEC was
set in the options passed to res_query.) Is the resolver broken?
--
Bind9 (8.04) not returning 'ad' flag when dnssec is enabled
11 matches
Mail list logo
