Bug 850740
Summary: | win2008 guest BSOD when host has stress | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Shaolong Hu <shu> |
Component: | kvm | Assignee: | Virtualization Maintenance <virt-maint> |
Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 5.9 | CC: | chayang, juzhang, michen, mkenneth, rhod, virt-maint |
Target Milestone: | rc | Keywords: | TestBlocker |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-08-23 11:15:22 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: | |
Embargoed: |
Description
Shaolong Hu
2012-08-22 09:43:34 UTC
we have met this before: Bug 717882 - BSOD occurs when start 4 128GB windows guest on 512 GB host it happens when there is memory overcommit, but this one happens when there is enough memory. I am testing timer device on rhel5.9 host with win2008 guest, add stress to host is a basic step, so this is a test blocker. guest is win2008 64 sp2 with latest virtio-win-1.0.3-1.52454.el5 btw, BSOD happens even do not add stress in guest with Heavyload, same BSOD code. (In reply to comment #1) > we have met this before: > > Bug 717882 - BSOD occurs when start 4 128GB windows guest on 512 GB host > > it happens when there is memory overcommit, but this one happens when there > is enough memory. > > > I am testing timer device on rhel5.9 host with win2008 guest, add stress to > host is a basic step, so this is a test blocker. We know that RHEL5 host scheduler is inferior to RHEL6 scheduler, and this is not going to change. As a result processes (VCPUs) are not scheduled to run, and the guest BSOD. I believe that you will run into the same issue with previous RHEL versions. It will probably happen with RHEL6 at some stress level. Would it be possible to lower the stress level for the time-keeping test? Thanks, Ronen. (In reply to comment #5) > We know that RHEL5 host scheduler is inferior to RHEL6 scheduler, and this > is not going to change. As a result processes (VCPUs) are not scheduled to > run, and the guest BSOD. > I believe that you will run into the same issue with previous RHEL versions. > It will probably happen with RHEL6 at some stress level. > Would it be possible to lower the stress level for the time-keeping test? > > Thanks, Ronen. I did a little more test: when use the tool "stress": --cpu only add user space stress --io and --vm only add kernel space stress single user space or kernel space stress won't cause BSOD no matter how large the parameter is, only when there is high stress on both kernel and user space, causing frequent user/kernel space switching, BSOD happens: single "--vm 1 --vm-bytes 128M" will give 99% system cpu usage on a 4 cores host, when add --cpu X, BSOD happens until the X up to 4. I think in our RHEV-M product, we may want to warn users about this situation, some advice will be like save one or certain portion of physical cpu in host, or do not bind qemu-kvm process and vcpu to same pcpu, if i understand it correctly. I will use some thing like "--cpu 3 --vm 4 --vm-bytes 128M" to do my test, i think it works for the run, thanks for specification and feel free to close this one. Shaolong Shaolong, Thanks for the additional tests and interesting results. I am hesitant about adding specific instructions about how to avoid stress situations, since there are too many possible setups of VMs running on a single host doing all kind of things. Since the issue is not new, and it is no more a test-blocker, I am closing this bug. Ronen. Just a FYI, test suggest this situation exists in latest 5.8.z, so this is not regression. Test with: 2.6.18-308.14.1.el5 kvm-83-249.el5_8.5 |