| 2015-07-28 15:57:05 |
Edward Hope-Morley |
bug |
|
|
added bug |
| 2015-07-28 15:57:39 |
Chris J Arges |
nominated for series |
|
Ubuntu Precise |
|
| 2015-07-28 15:57:39 |
Chris J Arges |
bug task added |
|
linux (Ubuntu Precise) |
|
| 2015-07-28 15:58:13 |
Edward Hope-Morley |
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 currently 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 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. |
|
| 2015-07-28 15:58:22 |
Chris J Arges |
linux (Ubuntu): status |
New |
Fix Released |
|
| 2015-07-28 15:58:26 |
Chris J Arges |
linux (Ubuntu Precise): assignee |
|
Chris J Arges (arges) |
|
| 2015-07-29 10:09:01 |
Michael Cunningham |
bug |
|
|
added subscriber Michael Cunningham |
| 2015-07-29 13:31:29 |
Launchpad Janitor |
linux (Ubuntu Precise): status |
New |
Confirmed |
|
| 2015-07-29 18:38:41 |
Chris J Arges |
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. |
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 |
|
| 2015-08-06 12:41:30 |
Rafael David Tinoco |
linux (Ubuntu Precise): assignee |
Chris J Arges (arges) |
Rafael David Tinoco (inaddy) |
|
| 2015-08-06 13:59:59 |
Rafael David Tinoco |
bug |
|
|
added subscriber Rafael David Tinoco |
| 2015-08-06 20:43:40 |
Rafael David Tinoco |
linux (Ubuntu Precise): assignee |
Rafael David Tinoco (inaddy) |
|
|
| 2015-08-06 20:55:25 |
Chris J Arges |
linux (Ubuntu Precise): importance |
Undecided |
High |
|
| 2015-08-07 17:02:48 |
Rafael David Tinoco |
linux (Ubuntu Precise): assignee |
|
Rafael David Tinoco (inaddy) |
|
| 2015-08-11 11:09:03 |
Rafael David Tinoco |
linux (Ubuntu Precise): status |
Confirmed |
In Progress |
|
| 2015-08-11 17:32:38 |
Rafael David Tinoco |
attachment added |
|
diskNUM.xml https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+attachment/4443003/+files/diskNUM.xml |
|
| 2015-08-11 17:33:59 |
Rafael David Tinoco |
attachment added |
|
precise.xml https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+attachment/4443004/+files/precise.xml |
|
| 2015-08-11 17:35:01 |
Rafael David Tinoco |
attachment added |
|
teste.sh https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+attachment/4443005/+files/teste.sh |
|
| 2015-08-11 17:36:46 |
Rafael David Tinoco |
attachment removed |
precise.xml https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+attachment/4443004/+files/precise.xml |
|
|
| 2015-08-11 17:37:55 |
Rafael David Tinoco |
attachment added |
|
precise.xml https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+attachment/4443012/+files/precise.xml |
|
| 2015-08-11 17:45:54 |
Rafael David Tinoco |
linux (Ubuntu Precise): assignee |
Rafael David Tinoco (inaddy) |
|
|
| 2015-08-11 17:49:06 |
Dan Streetman |
linux (Ubuntu Precise): assignee |
|
Dan Streetman (ddstreet) |
|
| 2015-08-11 17:49:32 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2015-08-28 14:02:40 |
Rafael David Tinoco |
tags |
|
sts |
|
| 2015-09-25 16:18:31 |
Brad Figg |
linux (Ubuntu Precise): status |
In Progress |
Fix Committed |
|
| 2015-09-25 16:18:50 |
Brad Figg |
linux (Ubuntu): status |
Fix Released |
Invalid |
|
| 2015-10-08 14:38:14 |
Luis Henriques |
tags |
sts |
sts verification-needed-precise |
|
| 2015-10-09 14:45:47 |
Rafael David Tinoco |
tags |
sts verification-needed-precise |
sts verification-done |
|
| 2015-10-19 16:06:43 |
Launchpad Janitor |
linux (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
| 2015-10-19 16:06:43 |
Launchpad Janitor |
cve linked |
|
2015-5156 |
|
| 2015-10-19 16:06:43 |
Launchpad Janitor |
cve linked |
|
2015-6937 |
|
| 2015-10-19 16:06:42 |
Launchpad Janitor |
linux (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
