From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Bainbridge Subject: Re: Unable to create guest domain AND mm.c/grant_table.c errors Date: Thu, 22 Sep 2005 11:36:39 +0100 Message-ID: <623652d5050922033611a6a471@mail.gmail.com> References: <623652d505092107102af9e745@mail.gmail.com> <3525342c68fe94116bb4887a4e870bdf@cl.cam.ac.uk> <623652d505092110382f3af1e7@mail.gmail.com> <623652d50509220149425f45d9@mail.gmail.com> <623652d5050922020375622bc5@mail.gmail.com> <20050922092748.GB2439@uk.xensource.com> Reply-To: Chris Bainbridge Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20050922092748.GB2439@uk.xensource.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel List-Id: xen-devel@lists.xenproject.org On 22/09/05, Ewan Mellor 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 =3D 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 w= ould > certainly happen at the moment if you restart xenstored. Are you doing t= hat? > 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.