Ubuntu 18.04 guest hangs during diskio stress
Bug #1778717 reported by
Sujith Pandel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| dellserver |
New
|
Undecided
|
Unassigned | ||
| linux (Ubuntu) |
Incomplete
|
High
|
Joseph Salisbury | ||
| Bionic |
Incomplete
|
High
|
Joseph Salisbury | ||
| Cosmic |
Incomplete
|
High
|
Joseph Salisbury | ||
Bug Description
Setup - A Dell EMC 14th Gen AMD server, with ESXi 6.7 as host and Ubuntu 18.04 (latest updates) guest.
Guest has 3 data disks apart from the boot disk. All these disks are exposed through "ParaVirtual SCSI controller" from the host ESXi 6.7.
Run diskio stress on all the 3 data disks for overnight.
Guest goes unresponsive (even ping fails) in between.
Only way to recover is to reset the guest.
Logs do not indicate much on this error.
Rarely we get a crash on the Guest-screen. Attaching 2 screenshots of different hits.
We have tried mainline kernel v4.18-rc-2 and have hit the issue there as well.
Changing the SCSI controller to "LSI Logic SAS adapter" helps and we have not seen any crash/hang here.
Revision history for this message
| Sujith Pandel (sujithpandel) wrote | #1 |
Revision history for this message
| Sujith Pandel (sujithpandel) wrote | #2 |
Revision history for this message
| Sujith Pandel (sujithpandel) wrote | #3 |
Revision history for this message
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote Missing required logs. | #4 |
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
| tags: | added: bionic |
Revision history for this message
| Sujith Pandel (sujithpandel) wrote | #5 |
Revision history for this message
| Sujith Pandel (sujithpandel) wrote | #6 |
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Confirmed |
Revision history for this message
| Joseph Salisbury (jsalisbury) wrote | #7 |
| Changed in linux (Ubuntu): | |
| importance: | Undecided → High |
| Changed in linux (Ubuntu Bionic): | |
| importance: | Undecided → High |
| status: | New → Incomplete |
| Changed in linux (Ubuntu Cosmic): | |
| status: | Confirmed → Incomplete |
| Changed in linux (Ubuntu Bionic): | |
| status: | Incomplete → Triaged |
| Changed in linux (Ubuntu Cosmic): | |
| status: | Incomplete → Triaged |
| Changed in linux (Ubuntu Bionic): | |
| assignee: | nobody → Joseph Salisbury (jsalisbury) |
| Changed in linux (Ubuntu Cosmic): | |
| assignee: | nobody → Joseph Salisbury (jsalisbury) |
| Changed in linux (Ubuntu Bionic): | |
| status: | Triaged → Incomplete |
| Changed in linux (Ubuntu Cosmic): | |
| status: | Triaged → Incomplete |
| tags: | added: cscc |
Revision history for this message
| Dustin Oprea (myselfasunder) wrote | #8 |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1778717
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.