From: Jia Rao <rickenrao@gmail.com>
To: luis.silva@axiomasoft.pt
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: domU can not start in Xen 4.0.1-rc3-pre using tapdisk
Date: Wed, 23 Jun 2010 10:51:22 -0400 [thread overview]
Message-ID: <AANLkTikjsr-LUhE8Io-N9YCY6fkDUtmej4Y15EPvCQEM@mail.gmail.com> (raw)
In-Reply-To: <1277247422.2566.2.camel@luis-port>
[-- Attachment #1.1: Type: text/plain, Size: 2247 bytes --]
Yes, that solves the problem.
Thanks a lot.
BTW. what configuration will lead me to the blktap (blktap1) driver instead
of the new blktap2 driver?
On Tue, Jun 22, 2010 at 6:57 PM, Luís Silva <luis.silva@axiomasoft.pt>wrote:
> Hello,
>
> I think that in order to use tap devices with pvops kernel you have to use
> "*tap2*:aio:path_to_file". At least it works for me... Even for 4.0.1 rc2
> I had to use "*tap2*:tapdisk:aio:...".
>
> Luís
>
> On Tue, 2010-06-22 at 11:01 -0400, Jia Rao wrote:
>
> The domU is using pygrub to boot its own 2.6.18.8-xen kernel. It can be
> booted successfully under 2.6.18.8-xen dom0 and xen 3.3.1.
>
>
>
> However when upgrade dom0 to 2.6.32.15 and xen 4.0.1-rc3-pre, the domU
> can not boot with tapdisk. I am wondering it is something related to the
> blktap driver.
>
>
>
> *When using tap:aio:* PATH/disk.img in domU disk configuration, the boot
> process hanged at a prompt:
>
> XENBUS: Waiting for devices to initialise: 295s...290s...
>
> Then after reboot, the domU can not mount the filesystem /dev/root and
> kernel panic.
>
>
>
> *When using tap:tapdisk:aio* PATH/disk.img. the booting process
> terminated at a error:
>
> Error: [Errno 2] No such file or directory: 'aio:/PATH/disk.img'
>
>
>
> *When using file*:PATH/disk.img, domU can boot successfully.
>
>
>
> Thus I am afraid it is somethin wrong with tapdisk driver in dom0
>
>
>
> FYI
>
> dom0: 2.6.32.15 centos 5.4
>
> dom0 config:
>
> CONFIG_XEN_BALLOON=y
>
> CONFIG_XEN_SCRUB_PAGES=y
>
> CONFIG_XEN_DEV_EVTCHN=y
>
> CONFIG_XEN_BACKEND=y
>
> CONFIG_XEN_NETDEV_BACKEND=y
>
> CONFIG_XEN_BLKDEV_BACKEND=y
>
> CONFIG_XEN_BLKDEV_TAP=m
>
> CONFIG_XEN_BLKBACK_PAGEMAP=y
>
> CONFIG_XEN_PCIDEV_BACKEND=y
>
> CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
>
> CONFIG_XEN_BLKDEV_FRONTEND=m
>
> CONFIG_XEN_NETDEV_FRONTEND=m
>
>
>
> I did load the modules: blktap xen_blkfront xen_netfront before starting
> xend.
>
>
>
> xen: 4.0.1-rc3-pre
>
>
>
> any ideas?
>
>
>
> Thanks.
>
>
>
>
>
> _______________________________________________
> Xen-users mailing listXen-users@lists.xensource.comhttp://lists.xensource.com/xen-users
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 4556 bytes --]
[-- Attachment #2: Type: text/plain, Size: 137 bytes --]
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
prev parent reply other threads:[~2010-06-23 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 15:01 domU can not start in Xen 4.0.1-rc3-pre using tapdisk Jia Rao
2010-06-22 22:57 ` Luís Silva
2010-06-23 14:51 ` Jia Rao [this message]
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=AANLkTikjsr-LUhE8Io-N9YCY6fkDUtmej4Y15EPvCQEM@mail.gmail.com \
--to=rickenrao@gmail.com \
--cc=luis.silva@axiomasoft.pt \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).