| |
|
 |
|
 |
|
|
|
| |
|
|
xen-ia64-devel
RE: [Xen-ia64-devel] Weekly benchmark results [2/3rd week]
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
|
|
|
| |
|
Home