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-users] balloon driver oops

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] balloon driver oops
From: Minoru Kato <kato.minoru@xxxxxxxxxxxx>
Date: Tue, 29 Nov 2005 15:45:42 +0900
Delivery-date: Tue, 29 Nov 2005 06:45:37 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello all,

I'm using xen-2.0.7.
I tried following operations.

1) create dom1 initial memory 256MB
2) balloon dom1 128
3) save /tmp/dom1
4) restore /tmp/dom1
-- It work fine.
 However, the next operation surely causes hang-up.
5) balloon dom1 256

Kernel-Oops displayed in dom1 console.
It is always pointed at balloon.c line 218,219.

Even if it is not as the above example, 
it will generate kernel-oops.
For example (512->256->save->restore->512). 

Did I perform violation operation ?

 CentOS4.2(Both dom0 and domU)
 Linux- from source as HIGHMEM4G support)


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] balloon driver oops, Minoru Kato <=