Bug 986364 - Kernel crashes when deprived of memory using virtio_balloon
Summary: Kernel crashes when deprived of memory using virtio_balloon
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-19 14:45 UTC by Martin Sivák
Modified: 2013-10-08 16:51 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-10-08 16:51:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Dmesg of the machine during my balloon testing (252.12 KB, text/plain)
2013-07-19 14:45 UTC, Martin Sivák
no flags Details

Description Martin Sivák 2013-07-19 14:45:14 UTC
Created attachment 775837 [details]
Dmesg of the machine during my balloon testing

Description of problem:

I booted virtualized x86_64 LiveCD of Fedora 19 (1GB of RAM), connected to it using virsh console and then used virsh setmem to deprive it of memory.

It crashed :)


Version-Release number of selected component (if applicable):

F19 LiveCD x86_64

How reproducible:

I haven't tried it again, but virsh setmem <name> 1000 should do the trick.

Steps to Reproduce:
1. Boot the VM in the current ovirt setup (3.3, but it is probably not necessary)
2. use virsh to deprive it of memory
3. watch the spectacle in dmesg

Actual results:

Kernel tracebacks and crashes (it actually killed the VM at the end)

Expected results:

Something graceful... virtio_balloon should not reclaim so much memory it kills the system I guess.

Comment 1 Josh Boyer 2013-09-18 20:24:24 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.11.1-200.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 2 Josh Boyer 2013-10-08 16:51:50 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.