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] Unable to read memory/target

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Unable to read memory/target
From: Ted Kaczmarek <tedkaz@xxxxxxxxxxxxx>
Date: Wed, 19 Oct 2005 17:05:20 -0400
Delivery-date: Wed, 19 Oct 2005 21:02:41 +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
Unable to read memory/target error is back again.
Happened when I started xend.

Tyan 2626 SMP
changeset:   7425:7c951e3eb5ab
Dom0 FC4

This is is the first changeset in a while where the domu's all boot up
first shot and network works with isolated bridge, meaning no other
broadcast domain participants.

I will gladly keep the Unable to read memory/target  :-)

Also, the delays on the console are gone as well, I wasn't sure if this
was my terminal settings but the consoles are much snappier now :-)

Beers for the Xen team on the IBM blade salesman :-)


Regards,
Ted



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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Unable to read memory/target, Ted Kaczmarek <=