All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
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	[thread overview]
Message-ID: <4B8FFA5C.2090201@goop.org> (raw)
In-Reply-To: <20100304155154.GB2761@reaktio.net>

On 03/04/2010 07:51 AM, Pasi Kärkkäinen wrote:
> On Thu, Mar 04, 2010 at 05:44:21PM +0200, Pasi Kärkkäinen wrote:
>    
>> 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 backend (lvm volumes).
>>
>> I tried using tap:aio: file-based storage with virt-manager for a PV guest.
>> 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..
>>
>>      
> 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..
>    

I haven't had any problems with blktap2 at all lately, using the xend/xm 
toolstack.  Are there any messages in the various logfiles and/or kernel 
which might indicate a problem?

     J

  reply	other threads:[~2010-03-04 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 15:44 Xen 4.0.0-rc5 with xen/stable 2.6.32.9 dom0 kernel, blktap2, relative mouse Pasi Kärkkäinen
2010-03-04 15:51 ` Pasi Kärkkäinen
2010-03-04 18:22   ` Jeremy Fitzhardinge [this message]
2010-03-04 18:24 ` Jeremy Fitzhardinge
2010-03-04 18:27   ` Pasi Kärkkäinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B8FFA5C.2090201@goop.org \
    --to=jeremy@goop.org \
    --cc=pasik@iki.fi \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.