kernel-packages team mailing list archive

[Edward Hope-Morley <edward.hope-morley@xxxxxxxxxxxxx>]

** Description changed:

  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 currently able to reproduce this issue using openstack to spin up
- vms and attach volumes using the following script:
+ 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 currently hit this issue with 1/2 instrances.
+ I hit this issue with 1/2 instances.

-- 
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:
  Fix Released
Status in linux source package in Precise:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+subscriptions