From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Bainbridge Subject: Re: kernel oops with virtual block device driver Date: Wed, 21 Sep 2005 15:25:16 +0100 Message-ID: <623652d5050921072560ed0fa0@mail.gmail.com> References: <623652d505091909316279674@mail.gmail.com> Reply-To: chris.bainbridge@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <623652d505091909316279674@mail.gmail.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 19/09/05, Chris Bainbridge wrote: > [2005-09-19 17:15:14 xend] DEBUG (image:250) cmdline =3D > ip=3D192.168.1.2:1.2.3.4::::eth0:off root=3D/dev/hda1 ro > [2005-09-19 17:15:14 xend] DEBUG (image:251) ramdisk =3D > [2005-09-19 17:15:14 xend] DEBUG (image:252) flags =3D 0 > [2005-09-19 17:15:14 xend] DEBUG (image:253) vcpus =3D 1 > [2005-09-19 17:15:15 xend] DEBUG (blkif:24) exception looking up > device number for hda1: [Errno 2] No such file or directory: > '/dev/hda1' ^^^^^^ /dev/hda1 didn't exist in domain 0, I think that was causing the oops here.