WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] unstable grant table issues?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] unstable grant table issues?
From: Gerd Knorr <kraxel@xxxxxxx>
Date: Mon, 4 Jul 2005 16:49:10 +0200
Delivery-date: Mon, 04 Jul 2005 14:53:50 +0000
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
  Hi,

current unstable (hg22ccddf93c40c7962109d1763d88b9f65af1f680)
fails to boot DomU for me (32-bit, unpatched).  Seems to be a
problem with the grant tables.

Last DomU messages:

  VFS: Mounted root (ext2 filesystem) readonly.
  Freeing unused kernel memory: 168k freed
  attempt to access beyond end of device
  sda1: rw=0, want=1717986920, limit=8388608

The domain is still in the "xm list" after that and can't be
killed by "xm destroy".

In the xen message log I see this (xen built with debug=y):

  [ ... ]
  (XEN) Scrubbing Free RAM: ...........done.
  (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to 
Xen).
  (XEN) 
(file=/work/bk/xen/test-build-i686-22ccddf93c40c7962109d1763d88b9f65af1f680/xen/include/asm/mm.h,
 line=187) Error pfn 100: rd=ff19d080, od=00000000, caf=00000000, taf=00000000
  (XEN) 
(file=/work/bk/xen/test-build-i686-22ccddf93c40c7962109d1763d88b9f65af1f680/xen/include/asm/mm.h,
 line=187) Error pfn 100: rd=ff19d080, od=00000000, caf=00000000, taf=00000000
  (XEN) 
(file=/work/bk/xen/test-build-i686-22ccddf93c40c7962109d1763d88b9f65af1f680/xen/include/asm/mm.h,
 line=187) Error pfn 100: rd=ff19d080, od=00000000, caf=00000000, taf=00000000
  (XEN) (file=grant_table.c, line=500) Bad handle (0).
  (XEN) (file=grant_table.c, line=500) Bad handle (8192).
  (XEN) (file=grant_table.c, line=500) Bad handle (40264).
  (XEN) (file=grant_table.c, line=500) Bad handle (0).
  (XEN) (file=grant_table.c, line=500) Bad handle (20480).
  (XEN) (file=grant_table.c, line=500) Bad handle (0).

The error messages from mm.h appeared during Dom0 bootup, but seem to be
harmless.  The grant_table.c messages where triggered by the attempt to boot
DomU.

Config file looks like this:

  master-xen root ~# cat /vm/sl93/config.xen3
  # general
  kernel = "/vm/sl93/vmlinuz3";
  memory = 128;
  name = "sl93";
  builder = "linux";

  # disk
  #disk = [ 'file:/dev/xen/sl93,sda1,w' ];
  disk = [ 'phy:xen/sl93,sda1,w' ];
  root = "/dev/sda1 ro";

  # network
  vif = [ 'mac=aa:00:78:65:6e:31, bridge=eth0' ];
  dhcp = "dhcp";

Which of the two "disk = " lines I use doesn't make a difference (Is there any
btw.?).

Any idea?

  Gerd


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

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