This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Linux-HVM, qemu, and xen-balloon.ko

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Linux-HVM, qemu, and xen-balloon.ko
From: "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx>
Date: Fri, 12 Dec 2008 17:24:32 +0000
Delivery-date: Fri, 12 Dec 2008 09:24:55 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:mime-version:content-type:content-transfer-encoding :content-disposition:x-google-sender-auth; bh=XbILyFVgaY7/o7Ty/6PP7GKDU4g1M2IXvo2ysMheOe0=; b=YzahJ2knR6oXomAKM5U+6t+AU5o1q2psXkxXl7Sxv3ENZ6D/N76KAoGcNoQF/8Y5Mx +rgSGUeJulAds70KfB8LFNd8Slcw9MM51K3MSKryPd8matEma8sr4AuB0mKGnAyshAK/ yDauKhZL7sRNlOLXwlaFKIb+MuO0j1WrwmDew=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition:x-google-sender-auth; b=M6/0fZwb2Y1CD2LO/G+J3EAbdAwbOn1AZeT3XrhjaqgY0NPGzrBDweCydWS8j42am/ 4BRe3mtAD+olMzeXMEoCevbseLo4XiIszwqDpufdtw3BXIcPyDc0SecaEB/dFkTNBO+V feRahhsNh+Y6SVOJnX2qUmVsxjkveA/v7rPsk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
There seems to be some sort of a bug when qemu interacts with the
balloon driver.  Stefano is trying to repro it, but I thought I'd
share it for people to look at.

+ Debian 4.0 host installation
+ Vanilla -unstable xen dom0 kernel, hypervisor, and qemu-dm (all
pulled this morning)
+ 4G of ram
+ Debian 4.0 Linux HVM, 2.6.18-6-i686 package
+ unmodified_drivers/ modules compiled for xen-platform-pci, and xen-balloon
+ 512M of RAM assigned
+ Disk and network are still emulated, using qemu

To repro:
* Boot the VM
* modprobe xen_balloon
* In one VM shell:
 # while true ; do rm -f zero ; dd if=/dev/zero of=zero ; done
* In another VM shell, use 'free' to see when the amount of free
memory is near zero
* In dom0:
 # xm mem-set debian-hvm 256
* In the VM shell, use 'free' to see when the amount of total memory
reaches 256 (this may take awhile, as the guest OS has to write data
out to disk.)
* In dom0:
 # xm mem-set debian-hvm 512

qemu will crash shortly.

When I install xen-vbd in the initrd, the problem goes away.  So it
seems almost certain that there's some mapping in qemu not getting
flushed when the balloon driver hands pages back to Xen, so that when
it asks Xen for pages again, and then tries to DMA into the same gpfn
space, something gets lost in the translation.

Any ideas?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>