On 22/09/05, Ewan Mellor <ewan@xxxxxxxxxxxxx> wrote:
> On Thu, Sep 22, 2005 at 10:03:59AM +0100, Chris Bainbridge wrote:
> > But the original problem with the block device still persists!
> >
> > # xm create ubuntu -c
> > store_evtchn = 1
> > xen_mem: Initialising balloon driver.
> > SCSI subsystem initialized
> > Grant table initialized
> > io scheduler noop registered
> > io scheduler anticipatory registered
> > io scheduler deadline registered
> > io scheduler cfq registered
> > loop: loaded (max 8 devices)
> > Xen virtual console successfully installed as tty1
> > Event-channel device installed.
> > xen_blk: Initialising virtual block device driver
> > xen_blk: Timeout connecting to device!
>
> When I see this, it clears after a reboot. Does that work for you? It would
> certainly happen at the moment if you restart xenstored. Are you doing that?
> If not, then we have a problem to chase.
I've tried rebooting, doesn't work, rm -rf /var/lib/xenstored, reboot,
doesn't work.
All I do after reboot is ssh in, cd /etc/xen/auto, xend start, xm
create ubuntu -c. I've built my own dom0 and domU kernels from
changeset 6987 and tried last nights binary release and they both fail
in this same way.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home