From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Xen 4.0.0-rc5 with xen/stable 2.6.32.9 dom0 kernel, blktap2, relative mouse Date: Thu, 04 Mar 2010 10:22:20 -0800 Message-ID: <4B8FFA5C.2090201@goop.org> References: <20100304154421.GA2761@reaktio.net> <20100304155154.GB2761@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20100304155154.GB2761@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 03/04/2010 07:51 AM, Pasi K=E4rkk=E4inen wrote: > On Thu, Mar 04, 2010 at 05:44:21PM +0200, Pasi K=E4rkk=E4inen wrote: > =20 >> Hello, >> >> I just tried running Xen 4.0.0-rc5 (64bit) with latest xen/stable 2.6.= 32.9 dom0 kernel (64bit aswell). >> System boots up fine, and I'm able to run PV guests using phy: disk ba= ckend (lvm volumes). >> >> I tried using tap:aio: file-based storage with virt-manager for a PV g= uest. >> It seems it doesn't really work, the guest waits for a long time >> initializing disk drivers/devices, and then complains about not having= any disks. >> >> $ xm list -l testfoo >> .. >> (device >> (tap >> (protocol x86_64-abi) >> (uuid f7723325-9ff4-96f7-0808-9ec05a00a4b8) >> (bootable 1) >> (dev xvda:disk) >> (uname tap:aio:/var/lib/libvirt/images/testfoo.img) >> (mode w) >> (backend 0) >> (VDI ) >> ) >> ) >> >> Am I supposed to have that 'uname' there? This could be a problem with= virt-manager or libvirt, >> so I'll try with plain normal /etc/xen/ cfgfiles next.. >> >> =20 > Hmm, it seems phy: based guest has that 'uname' aswell: > > (device > (vbd > (protocol x86_64-abi) > (uuid b7c115d7-138a-5cd0-a179-3038ba49d349) > (bootable 1) > (devid 51712) > (driver paravirtualised) > (dev xvda:disk) > (uname phy:/dev/vg_f12test/f12test) > (mode w) > (backend 0) > ) > ) > > So I guess that's all fine. > > What's the best way to troubleshoot the blktap2 problem? > > I have 'blktap' module loaded in dom0, and xen 4.0.0-rc5 > should have the required blktap2 tools.. > =20 I haven't had any problems with blktap2 at all lately, using the xend/xm=20 toolstack. Are there any messages in the various logfiles and/or kernel=20 which might indicate a problem? J