search for: rickenrao

Hi, all, I just found out that xen assigns the NOOP disk scheduler for linux guest OSes. Dom0 uses cfq scheduler (it is the linux default). Is there a reason for xen to turn off disk request merging in the quest OS by selecting a NOOP scheduler? Is it because the request optimization will be performed in dom0 or VMM ? Thansk in advance, Jia. _______________________________________________

This issue has been posted before, but no clear solution, i am sending again. 2.6.32 pvops dom0 booted with xen 4.0. However the xend can not start. I believe that is something related to the *evtchn*. I compile the CONFIG_XEN_DEV_EVTCHN=y in kernel, so i donot need to load it. When the dom0 booted, I can see there is a entry for evtchn in /dev/xen along with gntdev. But when xend starts, the

This issue has been posted before, but no clear solution, i am sending again. 2.6.32 pvops dom0 booted with xen 4.0. However the xend can not start. I believe that is something related to the *evtchn*. I compile the CONFIG_XEN_DEV_EVTCHN=y in kernel, so i donot need to load it. When the dom0 booted, I can see there is a entry for evtchn in /dev/xen along with gntdev. But when xend starts, the

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:

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: