kernel-packages team mailing list archive

[Rafael David Tinoco <rafael.tinoco@xxxxxxxxxxxxx>]

#
# Precise latest kernel
#
# CONFIG_HOTPLUG_PCI_ACPI=y
#

inaddy@sf00068947precise:boot$ uname -a
Linux sf00068947precise 3.2.0-92-generic #130-Ubuntu SMP Mon Oct 5 21:43:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

inaddy@alien:teste$ ./teste.sh
% RUN: 1
+ Creating disk 0: /dev/vdb
+ Creating disk 1: /dev/vdc
! Starting virtual machine
! Adding disk 0: /dev/vdb
! Adding disk 1: /dev/vdc
! Waiting virtual machine network to be up
! Checking if disk is online:
* Found 2 extra disks online
! Destroying virtual machine
...
...
% RUN: 16
+ Creating disk 0: /dev/vdb
+ Creating disk 1: /dev/vdc
! Starting virtual machine
! Adding disk 0: /dev/vdb
! Adding disk 1: /dev/vdc
! Waiting virtual machine network to be up
! Checking if disk is online:
* Found 2 extra disks online
! Destroying virtual machine
...

-> verification done

** Tags removed: verification-needed-precise
** Tags added: verification-done

-- 
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 Committed

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