Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-bugs

[Xen-bugs] [Bug 1078] New: domU crashed on ramdisk operations

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1078] New: domU crashed on ramdisk operations
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 5 Oct 2007 01:11:34 -0700
Delivery-date: Fri, 05 Oct 2007 01:12:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1078

           Summary: domU crashed on ramdisk operations
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: xensource.com@xxxxxxxxx


Set-up:
Hardware: XEN 3.1.0 on a 2 CPU (dual core XEON E5345 @ 2.33GHz) with 16 GB RAM
on Adaptec SAS Controller

Virtual Machine config:
--- snip ---
kernel = "/boot/vmlinuz-2.6.20-xen-r3-domU"
memory = 4096
name = "dbserver"
vcpus = 4
vif = [ '', 'bridge=xenbr1', 'bridge=xenbr3' ]
disk = [ 'phy:/dev/evms/domU_dbserver_swap,hda1,w',
'phy:/dev/evms/domU_dbserver_root,hda2,w' ]
root = "/dev/hda2 ro"
extra = "3 ramdisk_size=1048576"
--- snap ---

In this VM is no extra service running (no db or apache ....) just the plain
set-up. As you can see I created quite a large ramdisk with 1GB in size
(ramdisk_size=1048576).
I do the following on the cmd line:
dd if=/dev/zero of=/dev/ram1 bs=1k count=1048500 # Just a few k less than its
actual size
Which basically zero's out the ram disk.
This leads to a complete crash of the domU.

Alternatively you can delay the problem by making a filesystem on it and try to
fill it up with files: e.g
mkreiserfs /dev/ram1
mount /dev/ram1 /mnt/ramdisk
cp -av /home* /mnt/ramdisk # Home is more than 2 GB is my case


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs