On a fully-updated system, as of today, I am no longer seeing this
issue. Therefore, I am closing this ticket.
** Attachment removed: "Dependencies.txt"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1559801/+attachment/4606074/+files/Dependencies.txt
** Attachment removed: "SSHDCon
Based on the upstream bug closure, it sounds like importing the fixed
version from upstream (or at least the fix patch) is probably the
solution here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launc
I think it is important to realize that this bug causes Ubuntu 16.04 to
be unusable in many high security environments, since the stock SSH
installation does not function with GSSAPI and the installation of a
non-vendor-supported SSH will be unacceptable by policy in many of those
same environments
Public bug reported:
OpenSSH server GSSAPI authentication appears to be broken in Ubuntu
16.04 Xenial. Ticket #1558576 details some other issues regarding
breakage in Ubuntu 16.04 pertaining to OpenSSH, but this ticket is
specifically for the fact that GSSAPI authentication is no longer
working,
Public bug reported:
SSH was working fine for years, until I upgraded to Ubuntu 16.04. When
I upgraded to Ubuntu 16.04, the openssh-server stopped accepting
connections from Ubuntu 14.04 LTS clients, with the following error:
Disconnecting: Hash's MIC didn't verify
The error above sho
It did, indeed, have an autodev script configured:
---
# Template used to create this container: /usr/share/lxc/templates/lxc-download
# Parameters passed to the template:
# For additional config options, please look at lxc.container.conf(5)
# Distribution configuration
lxc.include = /usr/share/l
I haven't experienced this issue in a long time, so I'm just changing
this ticket to "invalid" status to cancel it.
** Changed in: krb5 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5
I am seeing this here as well. After seeing the comment by Serge above,
I took a look at this. Here is what I did, and I propose that anyone
who is experiencing this problem should probably do the same:
rm /etc/ufw/applications.d/dovecot-common
The reason is that you already have these rules in
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/985727
Title:
krb5-admin-server falsely claiming clock skew errors
To manage notifications about this bug go to:
https://bugs.launchpad.n
Public bug reported:
I installed a Kerberos KDC and Admin Server onto an Ubuntu 12.04 64-bit
VM. I created a test realm, and added principals.
When I kinit, it works, and I get a ticket back. However, when I try to
use kadmin, kadmin is extremely slow to respond, then eventually gives
an "unspe
Hi Serge,
Yes, this kernel does fix the problem! Thank you!! I was able to boot
successfully into the kernel with SMP enabled on the systems that
couldn't do this before.
Let me know if there is additional testing I can do to help you get this
into the Lucid stream.
Thanks again for all of you
@Serge,
Thanks for the work on these patches. I did look at the PPA and all I
see are the 2.6.38 packages, and since the 2.6.32-29 kernel isn't in the
mainstream repository yet I am unsure of where to get it. Could you
please point me to where I can get this new kernel with the fixes, so I
can t
Hi Serge,
Yes, that PPA kernel does indeed fix it. I used the PPA kernel in the
guest and it made everything work perfectly. So I'm thinking one of
those fixes you mentioned solves the problem.
Note that I am still using the standard Lucid kernel in the host, but I
don't think that's relevant s
It ended up being "apt-get install linux-image-server-backport-natty"
after doing an update. But you told me what I needed to get it working.
I'll try it out and let you know how it works. Thanks for all the help!
--
You received this bug notification because you are a member of Ubuntu
Server T
What is the fastest and easiest way for me to add these Natty backports
packages to test them on my affected machines? I went to the PPA you
mentioned but I see a very large list of packages. I would prefer to
add some repo to my apt sources list and get them that way, but I'm not
100% certain ex
I also want to mention that in my last comment, Launchpad turned the
upstream bug number into a hyperlink and referenced an Ubuntu bug of the
same number; that link is not correct, but I can't edit it because I
don't have access. Please follow the first link in post #11 (the one on
SourceForge) fo
Okay, I have done some more research and testing and I now think the
following upstream KVM bug is the problem:
http://sourceforge.net/tracker/?func=detail&aid=2968899&group_id=180599&atid=893831
Upstream KVM bug 2968899 describes a bug which causes the SMP guest to
lock up when setting the time.
I also want to add that I am not 100% clear where the bug is at this
point. My best guess, based on the information we have available in
this ticket, is that there is an upstream bug in the Linux kernel
itself, with regard to the way it handles AMD64 processors when running
under KVM. If that's t
Someone else has confirmed the same bug so I am changing the status to
"Confirmed".
** Changed in: qemu-kvm (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bug
Thank you, Serge. Please let me know how I can help. I am wiling to
test packages and help however I can. Thanks again for looking into
this!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.
Thank you for your response. I did try the backported Maverick qemu-kvm
packages from the PPA you mentioned, and they did not help the problem
at all. Actually, they seem to have made it much worse. Now, instead
of SMP VMs failing about 50% of the time on my AMD-based machines, it
fails 100% of
** Tags added: kvm qemu-kvm virtualization
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/714335
Title:
KVM SMP Linux Guests Hang
--
Ubuntu-server-bugs mailing list
Ubuntu-server
I also want to mention that the guests are fully-updated 64-bit Ubuntu
Lucid Server VMs.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/714335
Title:
KVM SMP Linux Guests Hang
--
Thanks for the tip. I tried that over here and it didn't help, but I
think I have a different bug over here (mine is related to SMP guests),
so I just filed bug 714335 to track mine.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm
** Description changed:
Binary package hint: qemu-kvm
SMP Linux guests are hanging under KVM. This does not happen always,
but at least 50% of the time or so.
If I start the guests with "-smp 1" or just completely omit the "-smp"
parameter this doesn't happen.
I can also say
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
https://bugs.launchpad.net/bugs/714335
Title:
KVM SMP Linux Guests Hang
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or
Public bug reported:
Binary package hint: qemu-kvm
SMP Linux guests are hanging under KVM. This does not happen always,
but at least 50% of the time or so.
If I start the guests with "-smp 1" or just completely omit the "-smp"
parameter this doesn't happen.
I can also say that it doesn't seem
Okay, thank you for the information. Earlier I had wondered if maybe
you had shortened the cpuinfo you posted, just to keep things more
compact in your bug report (which is why I asked, because the cpuinfo
obviously shows single-cpu), but since that isn't the case and they
really are single-CPU VM
Could you please tell us if the VMs that won't boot are SMP VMs? I know
it's the SMP kernel but what I mean is, is KVM giving the VM more than
one CPU? If they are SMP VMs, could you please try to make them single-
CPU and try to boot them, then let us know what happens? I am seeing a
bug with L
I am curious as to what you're running into, as I've run into a problem
myself trying to build the package for all of the targets.
The problem I've run into when trying to build the package from source
is that it doesn't seem to build all of the targets that the old
(0.11.x) package did. So I end
** Summary changed:
- qemu-kvm 0.12.1.1 needed for KSM support (key virtualization feature)
+ qemu-kvm 0.12.1.1 needed for KSM support (key KVM virtualization feature)
** Description changed:
Binary package hint: qemu-kvm
- KSM is supported by the current Lucid kernel. However, the current
** Summary changed:
- qemu-kvm 0.12.1.1 needed (KSM not available in current 0.11 version)
+ qemu-kvm 0.12.1.1 needed for KSM support (key virtualization feature)
--
qemu-kvm 0.12.1.1 needed for KSM support (key KVM virtualization feature)
https://bugs.launchpad.net/bugs/500272
You received this
Public bug reported:
Binary package hint: qemu-kvm
KSM is supported by the current Lucid kernel. However, the current
version of the qemu-kvm package, 0.11, does not support KSM. Therefore,
memory usage will be suboptimal, as this key feature is disabled for KVM
VM guests unless a high enough v
33 matches
Mail list logo