Public bug reported:
When installing the "xpra" package on Ubuntu 18.04 with the Hardware
Enablement Stack installed, the xpra package dependencies cause the
Hardware Enablement X server to be removed and replaced by the old, non-
Hardware-Enablement version of X.
ProblemType: Bug
DistroRelease:
me know how I can help.
Thank you,
Brian Knoll
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: light-locker 1.7.0-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sun Apr 16 20:01
I just wanted to add a quick note that this is Ubuntu 16.04 where I am
seeing this, although the problem has existed for some time now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1683205
Title:
Lucid is end-of-life. Closing ticket.
** Changed in: base-files (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/812874
Title:
package base-files
** Changed in: xfce4-volumed (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561260
Title:
xfce4-volumed causes volume popups frequently in XFCE
To manage
Public bug reported:
When I engage light-locker to lock my screen, it locks the screen and
disables power to the monitor, as it should. However, I can never get
video back again after that. Power to the monitor is never restored,
and the only way I can get my video back at that point is to
I should also add that I've tried disabling all of my power management
in my window manager settings, but the problem still occurs; that may or
may not be a bug in the window manager power management, but the net
effect appears to be that it is requesting the driver to cut the power
to the
Public bug reported:
I was having problems with frequent volume change popups in my XFCE
desktop. This was happening with Trusty 14.04 as well, and it is still
happening in 16.04 Xenial. I killed the xfce4-volumed process, and
disabled the autostart. Now I still see the volume control flash
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:
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:
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
Bugs, which is subscribed to Ubuntu.
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.
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
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
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:
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
I should also add, for clarification to anyone possibly unfamiliar with
Kerberos and, therefore, the impact of this bug, that the result of this
bug is that the incorrectly-named ticket cache is not visible to
applications searching for the ticket cache for the user, so the user
cannot (without
Public bug reported:
When unlocking an Ubuntu 16.04 system which is using light-locker as the
screen saver, Kerberos authentication works for a normal, unprivileged
user, except that the resulting ticket cache is incorrectly named.
Instead of the resulting ticket cache created as a result of such
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 =
Public bug reported:
System was previously running Ubuntu 14.04 LTS 64-bit and Linux
containers worked very well. Linux containers are unprivileged
containers started by the system using dedicated UID and GID mapped
ranges, not userns containers.
Upon upgrade-in-place to 16.04 LTS using
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 =
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
** Summary changed:
- cryptsetup: unknown fstype, bad password or options? error decrypting LUKS
volume at boot
+ cryptsetup: unknown fstype, bad password or options? error unlocking /
decrypting LUKS volume at boot
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- cryptsetup unknown fs type or options error decrypting LUKS volume at boot
+ cryptsetup: unknown fstype, bad password or options? error decrypting LUKS
volume at boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Since upgrading to cryptsetup-1.6.6-5ubuntu1 to replace
cryptsetup-1.6.1-1ubuntu7 today on my Ubuntu Wily 15.10 installation, I
have been receiving an error message at boot time after entering my
passphrase to unlock the LUKS partition. I noticed that at the same
time the
Public bug reported:
When the system enters sleep mode, Xorg appears to freeze. When the
system wakes back up, there is just a black screen. There is no
apparent way to get the system back once this happens. Interestingly,
the system does not appear to be completely frozen, in that it is still
Just a quick note that this problem still exists in Ubuntu 15.10 Wily.
As with the original reporter, if I turn off IOMMU support, the problem
does not occur.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just a note that I am seeing this problem as well, here on an AMD 8350
8-core system using Trusty 14.04 AMD64. The Xorg process takes about
20%-35% of one core, when the system is otherwise idle. I'm open to
suggestions regarding how I can dig deeper to determine the cause,
because obviously
Bug report was withdrawn by the original user, and over here it was a
driver issue, so I am marking this ticket invalid.
** Changed in: xorg (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just noticed what appears to be another problem:
-rw--- 1 myuser mygroup 504 May 12 21:21 krb5cc_0
-rw--- 1 myuser mygroup 504 May 12 21:16 krb5cc_1000_a8bk3j
While lightdm is renewing the tickets now when unlocking the screen
saver, and the ownership of the ticket is correct, the
I set the status back to new because that sounded correct given that
there is potentially additional work to be evaluated here, but if that's
not the right thing to do please let me know for future reference when
working with Launchpad tickets. I would normally just file a new
ticket, but in this
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 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
Bugs, which is subscribed to Ubuntu.
I applied this to a VM to test, and it does indeed appear to do the
right thing. I can confirm that this code does seem to have the
intended effect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment removed: Dependencies.txt
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1275380/+attachment/3965869/+files/Dependencies.txt
** Attachment removed: fstab.txt
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1275380/+attachment/3965870/+files/fstab.txt
**
To move this along, I've built a VM I can test this fix on, but to speed
things up, is there a PPA I can use? I don't mind building it but I am
concerned about building it differently than the official build, so if
there is a PPA I can use I will gladly install this onto my VM and I can
tell you
Public bug reported:
I am using the pam-krb5 module to log into a Kerberos realm using
lightdm. This works the initial time I log in, when I come in through
lightdm. However, once I am logged in, and I lock the screen using
light-locker, when I unlock the screen I no longer get renewed tickets.
Just a comment that I think this should probably have a fairly high
priority, as it severely affects the user experience for anyone using
Kerberos to authenticate via the libpam-krb5 module against Kerberos or
Active Directory, which I expect is a fairly large number of people.
Please let me know
Thank you, Russ, for the insightful explanation of what is happening
here. I can definitely confirm that xscreensaver does indeed work on my
system, as that is what I am using as a workaround to this issue. It
isn't as polished as using the lightdm screen saver would be, but it
certainly works
Public bug reported:
The SHA-1 hash has been, for years now, considered undesirable for new
installations. In Trusty, a new install using LUKS results in an
installation using SHA-1 hashing, as can be demonstrated by using the
following command:
cryptsetup luksDump encrypted partition
Please
I just want to add that an even better option, long-term, would probably
be to push back to upstream the idea that the installer should be
modified to present the user installing the system with the choice of
hash to be used. However, this does not change the fact that the
default hash should be
Public bug reported:
This message appeared in X while the system was up and operating.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: openafs-modules-dkms 1.6.1-1+ubuntu0.1
ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
Uname: Linux 3.2.0-38-generic x86_64
I am not sure this is the same bug as that mentioned in comment #2. For
example, after finding that my Canon MX870 would not function under
Ubuntu 12.04 64-bit, I purchased a cheap HP printer that uses the hplip
driver, and that works fine. I would like to have this Canon function,
however, so I
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
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
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
--
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:
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985727
Title:
krb5-admin-server falsely claiming clock skew errors
To manage notifications about this bug go to:
Public bug reported:
The Canon MX870 printer is connected via either wireless or wired
ethernet. It worked fine in Ubuntu 10.04 64-bit if one followed
workarounds available on various sites which basically involve
downloading Canon drivers from Canon, forcing the architecture on the
Canon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981290
Title:
Canon MX870 Printer Always Busy on Precise 12.04 64-Bit
To manage notifications about this bug go to:
I just performed a full update of all packages on my 12.04 installation,
rebooted, and tried again:
-
# lpq
WARNING: gnome-keyring:: no socket to connect to
mfc is ready
no entries
-
So the warning is still there. This installation was a regular install
with the Gnome 2 desktop
I want to mention that the workaround listed in comment #6, involving
commenting out the module, does indeed work over here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305
Title:
[12.04]
I also want to mention that this appears to be related to upstream
Debian bug #649408, and breaks both network services and applications.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914305
Title:
I think somebody who has access to do so should raise the priority of
this bug to a higher level. This bug has been known to break certain
network services, even services which have no apparent legitimate need
to be using gnome-keyring at all. It would be best if this bug were
fixed prior to the
I just wanted to add one example of a critical network service which is
broken by this bug, to demonstrate the broken functionality. CUPS
appears to be broken by this bug. I cannot print, and when I look in my
CUPS error log I see a bunch of messages about the daemon having
problems connecting
Hi Steve,
In Lucid and prior versions of Ubuntu, when using the Alternate
installer the user would be presented with three choices when installing
to a LUKS partition: AES, Blowfish, Serpent or Twofish. Of course,
additional options were also presented, but these four basic ciphers
were always
I meant to say that in prior versions the user would be presented with
_four_ choices, not three. Now they are only presented with three. I
apologize for the confusion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In the Ubuntu Alternate installer, the option for using Twofish appears
to have been removed around the Maverick or, possibly, Natty time frame.
The option to install using LUKS onto Twofish partitions was present in
Lucid, but some time around Maverick or Natty it was
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886483
Title:
Twofish LUKS Support in Alternate Installer
To manage notifications about this bug go to:
Public bug reported:
I received this error on two of my Lucid AMD64 systems today. Please
tell me if you want any other information.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: base-files 5.0.0ubuntu20.10.04.4
ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/812874
Title:
package base-files 5.0.0ubuntu20.10.04.4 failed to install/upgrade:
EOF on stdin at conffile prompt
To manage notifications about this
I see the same problem over here on a REV6 chip. I have had to resort
to completely disabling the onboard NIC (Realtek R8168B) and put in an
Intel PCI Express NIC so I can have functional connectivity.
** Changed in: linux (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug
I have tested this on the latest -server kernel and the problem is
indeed NOT fixed. It looks like the patch only made it into the
-generic kernel. It does work in the -generic kernel, but since only
the -generic kernel was patched, anyone using -server will still
experience this issue.
To
I am concerned that this patch possibly didn't make it into the -server
kernel (or possibly the -virtual kernel), only the -generic kernel:
-rw-r--r-- 1 root root 4052960 2011-02-28 18:37 vmlinuz-2.6.32-29-generic
-rw-r--r-- 1 root root 4110656 2011-02-11 16:52 vmlinuz-2.6.32-29-server
I think
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
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
@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
@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
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
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
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
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
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
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
Bugs,
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)
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=detailaid=2968899group_id=180599atid=893831
Upstream KVM bug 2968899 describes a bug which causes the SMP guest to
lock up when setting the time.
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=detailaid=2968899group_id=180599atid=893831
Upstream KVM bug 2968899 describes a bug which causes the SMP guest to
lock up when setting the time.
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)
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.
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
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
Bugs, which is subscribed to Ubuntu.
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
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.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/714335
** 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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/714335
Title:
KVM SMP Linux Guests Hang
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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
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
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 to
--
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
** 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
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
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
--
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/714335
Title:
KVM SMP Linux Guests Hang
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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 to
** 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
1 - 100 of 182 matches
Mail list logo
