Thanks. It works when I replace tap:aio with tap2:tapdisk:aio
PS: I suggest some big gun could write some comprehensive docs to help
migration from lower xen to xen 4.1, for example, some config files working for
xen 3.4.2 don't work for xen 4.1.0.
From: Fajar A. Nugraha [mailto:list@xxxxxxxxx]
Sent: Monday, May 16, 2011 3:29 PM
To: Fan, Huaxiang
Subject: Re: [Xen-users] tap:aio driver for kernel2.6.32.x
On Mon, May 16, 2011 at 10:28 AM, Fan, Huaxiang <hufan@xxxxxxxxxxxx> wrote:
> Hi Fajar,
> Thanks. It is wired. I did have CONFIG_XEN_BLKDEV_TAP=m when I compile, and
> have blktap module loaded when the system boot. But when I start a domu with
> tap:aio indicator, I encounter the message on the domu console as below:
> XENBUS: Waiting for devices to initialize: 295s...290s...
> Until 300s time out. And the corresponding filesystem fails to be mounted.
> When I replace tap:aio with file, problem solved.
> Any idea?
Not sure. It's working in my setup. You can try:
- looking at files on /var/log/xen/*, look for the newest one and
what's on them (usually xend.log and qemu*.log will provide some
- try replacing tap:aio with tap:tapdisk:aio or tap2:tapdisk:aio
To report this as spam, please forward to spam@xxxxxxxxxxxxx Thank you.
Protected by Websense Hosted Email Security -- www.websense.com
Xen-users mailing list