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:
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:
#
# 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
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
** Changed in: linux (Ubuntu Precise)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu)
Status: Fix Released => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479031
Title:
attached block devices not showing up
To manage notifications about this bug go to:
Here is a PPA with a fix for this:
https://pad.lv/ppa/ddstreet/lp1479031
There was no code change required; the only change is the acpiphp driver
is built-in, instead of a module.
During boot, when the pci-acpi driver is loaded, it enumerates the bus.
Later when the acpiphp driver is loaded, it
Per Dan's request... second test is what he asked me to test - It
reasonably mitigates the issue:
#
# Precise latest -updates kernel
#
inaddy@sf00068947precise:~$ uname -a
Linux sf00068947precise 3.2.0-89-generic #127-Ubuntu SMP Tue Jul 28 09:28:15
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Per Dan's request... second test is what he asked me to test - It
reasonably mitigates the issue:
#
# Precise latest -updates kernel
#
inaddy@sf00068947precise:~$ uname -a
Linux sf00068947precise 3.2.0-89-generic #127-Ubuntu SMP Tue Jul 28 09:28:15
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
** Changed in: linux (Ubuntu Precise)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479031
Title:
attached block devices not showing up
To manage
Just out of curiosity, if I sleep in between starting the virtual
machine AND adding the disks (sleep 10, for example)... Then the disk
attachment works almost 100% of the times:
% RUN: 1
+ Creating disk 0: /dev/vdb
+ Creating disk 1: /dev/vdc
! Starting virtual machine
! Adding disk 0: /dev/vdb
** Changed in: linux (Ubuntu Precise)
Assignee: (unassigned) = Dan Streetman (ddstreet)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479031
Title:
attached block devices not showing up
To
Second reproducer for this bug (shell script attaching ceph volumes on kvm
machine).
Make sure to run this as 1st level guest (2nd level is slow and don't trigger
the issue).
** Attachment added: teste.sh
To be attached disk definition (using ceph)
** Attachment added: diskNUM.xml
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+attachment/4443003/+files/diskNUM.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Virtual machine definition (being used to attach/dettach ceph volumes)
OBS: ceph is being used just because original problem was using ceph
also
** Attachment added: precise.xml
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+attachment/4443012/+files/precise.xml
--
You
Okay, following instructions already provided by Chris Arges -
responsible for the kernel bisection so far - and Ed - working on the
case since its beginning - I was able to create another reproducer - not
openstack dependant - that fails close to 100% of times.
Output:
# running test
Virtual machine definition (being used to attach/dettach ceph volumes)
OBS: ceph is being used just because original problem was using ceph
also
** Attachment added: precise.xml
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+attachment/4443004/+files/precise.xml
--
You
** Changed in: linux (Ubuntu Precise)
Assignee: (unassigned) = Rafael David Tinoco (inaddy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479031
Title:
attached block devices not showing up
** Changed in: linux (Ubuntu Precise)
Assignee: Rafael David Tinoco (inaddy) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479031
Title:
attached block devices not showing up
** Changed in: linux (Ubuntu Precise)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479031
Title:
attached block devices not showing up
To manage notifications
This commit fixes the issue, whereas the previous commit results in failure.
3b63aaa70e1ccc4b66d60acc78da09700706a703
Need to figure out how to backport this into 3.2, since this is not a
clean cherry-pick and is a fairly large change.
--
You received this bug notification because you are a
** Changed in: linux (Ubuntu Precise)
Assignee: Chris J Arges (arges) = Rafael David Tinoco (inaddy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479031
Title:
attached block devices not
** 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
Problem exists between v3.9 and v3.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479031
Title:
attached block devices not showing up
To manage notifications about this bug go to:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479031
** Changed in: linux (Ubuntu)
Status: New = Fix Released
** Changed in: linux (Ubuntu Precise)
Assignee: (unassigned) = Chris J Arges (arges)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479031
Title:
attached block devices not showing up
To manage
28 matches
Mail list logo
