WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-users] domU can not start in Xen 4.0.1-rc3-pre using tapdisk

To: xen-users@xxxxxxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] domU can not start in Xen 4.0.1-rc3-pre using tapdisk
From: Jia Rao <rickenrao@xxxxxxxxx>
Date: Tue, 22 Jun 2010 11:01:18 -0400
Cc:
Delivery-date: Tue, 22 Jun 2010 08:08:35 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=W5tcWUtMT+fIx/pgw+SAXyCkkbJopniVMWE++AaObKk=; b=jV5Vcqjk2xiTZGitln9J7Ie5FKiU5bCAHPkL6AQ0fDpHK+D4P5LpVHg3RPDueKHl3M ITo8xj7gpuMHFN4KycZFGXhroaUJHZPXeNNZPJASrP6Wu8EERuDKI4BFJA0xmKWQ+xnZ Ctzl7bU/6tBYarmgLfYenGx4sDrxklh6SuWX0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=FwFDmSYthxORmxC8PKEMqd/GtbCvhDeKe7y+pTtLea+1mil3dDLS5FObAJbVnabjKb e0pxelc21vggOMA8RDv/+ArVnvJUM4f0whGkwy4eGIA+qtBjX5/HCb56sDIzK+ESWvmp vhXS5YJ99BWKqnHX9yHxVrvoEFbN0bm1FFHF4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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 list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>