Can also confirm that that fix works on trusty too, no regressions with
a pretty wide set of devices we're connecting to
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665565
Title:
python-paramiko
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1061665
Title:
Filter scheduler not respecting the force_hosts hint
To
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061665
Title:
Filter scheduler not respecting the force_hosts hint
To manage notifications
I'm having identical behavior - with more than one vcpu, I can't get a
32 bit CentOS system to boot. 64bit seems fine.
--
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/795717
Title:
I'm having identical behavior - with more than one vcpu, I can't get a
32 bit CentOS system to boot. 64bit seems fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/795717
Title:
32bit rhel and
Public bug reported:
Binary package hint: udev
$ lsb_release -rd
Description:Ubuntu 8.04.1
Release:8.04
udev:
Installed: 117-8
Candidate: 117-8
Version table:
*** 117-8 0
500 http://us.archive.ubuntu.com hardy/main Packages
100 /var/lib/dpkg/status
When
Bah - this is actually an issue with the initrd including the dm module.
Disregard.
** Changed in: udev (Ubuntu)
Assignee: (unassigned) = Adam Jacob (adam-hjksolutions)
Status: New = Invalid
--
udev events for lvm fail to trigger initialization on partitions shared with
root block
On newer versions of Ubuntu (fiesty and gutsy) you need a slightly
different /etc/event.d/runsvdir:
start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5
stop on shutdown
respawn
exec /usr/sbin/runsvdir-start
--
runsvdir does not use upstart
This can also be worked around by simply not logging to wtmp on a
successful pptp connection. Comment out the logwtmp line in
/etc/pptpd.conf, and things will be better.
This only occurred for us after applying updates to edgy; was it fixed
and then regressed again later?
--
pptpd on edgy
