From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jia Rao Subject: Re: domU can not start in Xen 4.0.1-rc3-pre using tapdisk Date: Wed, 23 Jun 2010 10:51:22 -0400 Message-ID: References: <1277247422.2566.2.camel@luis-port> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1462009247==" Return-path: In-Reply-To: <1277247422.2566.2.camel@luis-port> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: luis.silva@axiomasoft.pt Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1462009247== Content-Type: multipart/alternative; boundary=0016e6da934dd9564d0489b3ab0d --0016e6da934dd9564d0489b3ab0d Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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=EDs Silva wro= te: > Hello, > > I think that in order to use tap devices with pvops kernel you have to us= e > "*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=EDs > > 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=3Dy > > CONFIG_XEN_SCRUB_PAGES=3Dy > > CONFIG_XEN_DEV_EVTCHN=3Dy > > CONFIG_XEN_BACKEND=3Dy > > CONFIG_XEN_NETDEV_BACKEND=3Dy > > CONFIG_XEN_BLKDEV_BACKEND=3Dy > > CONFIG_XEN_BLKDEV_TAP=3Dm > > CONFIG_XEN_BLKBACK_PAGEMAP=3Dy > > CONFIG_XEN_PCIDEV_BACKEND=3Dy > > CONFIG_XEN_PCIDEV_BACKEND_VPCI=3Dy > > CONFIG_XEN_BLKDEV_FRONTEND=3Dm > > CONFIG_XEN_NETDEV_FRONTEND=3Dm > > > > 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 > > > --0016e6da934dd9564d0489b3ab0d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Yes, that solves the problem.
Thanks a lot.
BTW. what configu= ration will lead me to the blktap (blktap1) driver instead of the new blkta= p2 driver?

On Tue, Jun 22, 2010 at= 6:57 PM, Lu=EDs Silva <luis.silva@axiomasoft.pt> wrote:
=20 =20
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=EDs

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 bl= ktap driver.


When using tap:aio: PATH/disk.img in domU disk configuration, th= e 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 te= rminated 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:=A0
CONFIG_XEN_BALLOON=3Dy
CONFIG_XEN_SCRUB_PAGES=3Dy
CONFIG_XEN_DEV_EVTCHN=3Dy
CONFIG_XEN_BACKEND=3Dy
CONFIG_XEN_NETDEV_BACKEND=3Dy
CONFIG_XEN_BLKDEV_BACKEND=3Dy
CONFIG_XEN_BLKDEV_TAP=3Dm
CONFIG_XEN_BLKBACK_PAGEMAP=3Dy
CONFIG_XEN_PCIDEV_BACKEND=3Dy
CONFIG_XEN_PCIDEV_BACKEND_VPCI=3Dy
CONFIG_XEN_BLKDEV_FRONTEND=3Dm
CONFIG_XEN_NETDEV_FRONTEND=3Dm


I did load the modules: blktap xen_blkfront xen_netfront before startin= g xend.


xen: 4.0.1-rc3-pre


any ideas?


Thanks. 




_______________________________________________
Xen-users mailing list
Xen-user=
s@lists.xensource.com
http://l=
ists.xensource.com/xen-users


--0016e6da934dd9564d0489b3ab0d-- --===============1462009247== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users --===============1462009247==--