This bug was fixed in the package linux - 3.2.0-92.130
---------------
linux (3.2.0-92.130) precise; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1500854
[ dan.street...@canonical.com ]
* [Config] HOTPLUG_PCI_ACPI=y
- LP: #1479031
[ John Johansen ]
* SAUCE: (no-up) apparmor: fix mount not handling disconnected paths
- LP: #1496430
[ Upstream Kernel Changes ]
* RDS: verify the underlying transport exists before creating a
connection
- LP: #1496232
- CVE-2015-6937
* virtio-net: drop NETIF_F_FRAGLIST
- LP: #1484793
- CVE-2015-5156
-- Brad Figg <brad.f...@canonical.com> Mon, 05 Oct 2015 13:50:43 -0700
** Changed in: linux (Ubuntu Precise)
Status: Fix Committed => Fix Released
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-5156
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-6937
** Changed in: linux (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1479031
Title:
attached block devices not showing up
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Precise:
Fix Released
Bug description:
I have Ubuntu Precise guests running in kvm to which I attach volumes
immediately after boot. Sometimes I notice that the devices do not
show up in the guest e.g. they are not visible in /proc/partitions and
dmesg boot log shows no sign of then being noticed. Qemu itself shows
that the devices are attached and if I do a rescan within the guest
the devices appear. A reboot also cause the devices to appear. So, it
feels like there is enough evidence to suggest that the devices were
properly attached by qemu/seabios but they just didn't get noticed by
the guest.
This issue is reproducible with Precise running 3.2, 3.5 (lts-quantal)
and 3.8 (lts-raring) kernels but not as of 3.11 (lts-saucy) so it
would appear that something changed between 3.8 and 3.11 that resolved
this issue and if we can identify it we should backport to 3.2.
I am able to reproduce this issue using Openstack to spin up vms and
attach volumes using the following script:
http://pastebin.ubuntu.com/11954253/
I hit this issue with 1/2 instances.
As a workaround one can rescan and the device shows up:
echo 1 | sudo tee /sys/bus/pci/rescan
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
