| Summary: | Fedora 25 x686 on the top of VirtualBox, on the top of VMWorkstation | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | niemand <nobodyless> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | extras-qa, gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, nobodyless |
| Target Milestone: | --- | Flags: | nobodyless:
needinfo?
(extras-qa) |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-10-20 11:44:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
niemand
2016-10-16 06:39:58 UTC
Here is the update on this bug. Four use cases: [1] With kernel 4.8.1-1.fc25.i686, this bug is present when number of virtual CPUs is 1. [2] With kernel 4.8.1-1.fc25.i686, this bug is NOT present when number of virtual CPUs are 4. [3] With kernel 4.8.2-300.fc25.i686, this bug is NOT present when number of virtual CPUs is 1. [4] With kernel 4.8.2-300.fc25.i686, this bug is NOT present when number of virtual CPUs are 4. This issue is (magically) solved. I need the following: (1) Root Cause of the problem (what was wrong with use case [1])? (2) Solution for (1)! Thank you! _nobody_ To be perfectly honest, nobody is going to look at this bug. The combination of multiple virtualization technologies that are not KVM combined with a 32-bit kernel means this is literally the lowest bug on the priority list. We appreciate the report, but we wanted to set expectations accordingly. We are glad you have found a workaround. Hello Josh (Boyer), I do agree on what you have wrote here. I also declare Case Closed. But in this regards, I wrote the new bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1387361 Good luck on this one (you'll need it)! ;-) _nobody_ |