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-ia64-devel

RE: [Xen-ia64-devel] Weekly benchmark results [2/3rd week]

To: "'Akio Takebe'" <takebe_akio@xxxxxxxxxxxxxx>, "'Magenheimer, Dan \(HP Labs Fort Collins\)'" <dan.magenheimer@xxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] Weekly benchmark results [2/3rd week]
From: "yo.fujita" <yo.fujita@xxxxxxxxxxxxxxxx>
Date: Wed, 22 Feb 2006 10:19:34 +0900
Delivery-date: Wed, 22 Feb 2006 01:31:11 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20060222011219.87C091C003@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcY3SO9irIcubcHLQ72wv/jJdQXhsgAAk+iAAACIt8A=
Oops!

> Hi Dan,
> My environment is the same as Takeo.
It was Akio not Takeo. 
I'm sorry Akio.

Fujita

> 
> Thanks
> Fujita
> 
> > -----Original Message-----
> > From: Akio Takebe [mailto:takebe_akio@xxxxxxxxxxxxxx]
> > Sent: Wednesday, February 22, 2006 9:41 AM
> > To: Magenheimer, Dan (HP Labs Fort Collins); yo.fujita;
> > xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: RE: [Xen-ia64-devel] Weekly benchmark results [2/3rd week]
> >
> > Hi, Dan, Alex, all
> >
> > I tried udev-0.85 but it failed.
> >
> > >Cset 8604 seems to work for me.  Tip fails and cset 8717
> > >fails.
> > Really?
> > I think that cset 8790 patch is a cause.
> > I can boot domU by using cset 8789.
> > I'm trying to debug it.
> >
> > I can boot domU by using the following patch.
> >
> > diff -r ded14681ae84 tools/xenstore/xenstored_domain.c
> > --- a/tools/xenstore/xenstored_domain.c Sat Feb 18 13:17:24 2006 -0700
> > +++ b/tools/xenstore/xenstored_domain.c Wed Feb 22 06:00:49 2006 +0900
> > @@ -500,6 +500,7 @@ static int dom0_init(void)
> >         if (fd == -1)
> >                 return -1;
> >
> > +       kva=(0x0fffffffffffffff & kva) ;
> >         dom0->interface = mmap(NULL, getpagesize(),
PROT_READ|PROT_WRITE,
> >                                MAP_SHARED, fd, kva);
> >         if (dom0->interface == MAP_FAILED)
> >
> >
> > Please advice to me.
> >
> > Best Regards,
> >
> > Akio Takebe
> >
> > >After more investigation, this may not be related
> > >to a newer hotplug/udev.
> > >
> > >Fujita --
> > >
> > >Have you been able to get this to work on RH4?
> > >
> > >Everyone --
> > >
> > >Is anybody else seeing this problem?  It seems to
> > >occur starting domU on RH4 (but not on Debian).  The
> > >symptom is that when "xm create" is executed, the
> > >result is:
> > >
> > >Error: Device 769 (vbd) could not be connected.  Hotplug scripts not
> > >working.
> > >
> > >Cset 8604 seems to work for me.  Tip fails and cset 8717
> > >fails.
> > >
> > >If anyone is successfully booting a domU on a clean install of
> > >tip on RH4, please respond.
> > >
> > >Dan
> > >
> > >> -----Original Message-----
> > >> From: Magenheimer, Dan (HP Labs Fort Collins)
> > >> Sent: Friday, February 17, 2006 9:52 AM
> > >> To: 'yo.fujita'; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > >> Subject: RE: [Xen-ia64-devel] Weekly benchmark results [2/3rd week]
> > >>
> > >> Hi Fujita --
> > >>
> > >> Some recent change in the xen-unstable tree apparently
> > >> requires an updated hotplug/udev installed in domain0.
> > >> We are trying to understand how to fix this.
> > >>
> > >> Thanks,
> > >> Dan
> > >>
> > >> > -----Original Message-----
> > >> > From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > >> > [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf
> > >> > Of yo.fujita
> > >> > Sent: Friday, February 17, 2006 12:42 AM
> > >> > To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > >> > Subject: [Xen-ia64-devel] Weekly benchmark results [2/3rd week]
> > >> >
> > >> > Hi,
> > >> >
> > >> > I tried Xen build by the last changeset of 2/15(Cs:
> > >> > 8828:982b9678af2c).
> > >> > Then, when "Xend start" was done by the host machine, the
> > >> > keyboard did hang.
> > >> >
> > >> > In addition, domU not Boot.
> > >> > Please look at the attached file. Its "xm create" log.
> > >> >
> > >> > TEST ENVIRONMENT
> > >> >     Machine          : Tiger4
> > >> >     changeset        : 8828:982b9678af2c
> > >> >     Dom0 OS          : RHEL4 U2 (no SMP)
> > >> >
> > >> > Thanks
> > >> > Fujita
> > >> >
> > >>
> > >
> > >_______________________________________________
> > >Xen-ia64-devel mailing list
> > >Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > >http://lists.xensource.com/xen-ia64-devel
> 
> 
> 
> 
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel



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