Hello, I have a small problem with the blktap, that when I use "tap:aio" protocol to access my disk, the domU stop booting with following message: [ 0.185031] PCI: Fatal: No config space access function found [ 0.189998] Unable to read sysrq code in control/sysrq [ 0.350220] i8042: No controller found [ 0.452153] /home/abuild/rpmbuild/BUILD/kernel-xen-3.1.0/linux-3.1/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) but when i switched to then "file" protocol the domU boot process would succeed. Anyone knows how to solve this problem? ============================================Additional info: I''m using openSUSE 12.1 x86_64 and i''v built the xen from source by myself, the kernel i''m using is "kernel-xen"(3.1.10-1.9-xen) from official repositories. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Tue, May 22, 2012 at 04:43:40PM +0800, ????????? wrote:> Hello, >Hello,> I have a small problem with the blktap, that when I use "tap:aio" protocol > to access my disk, the domU stop booting with following message: > > [ 0.185031] PCI: Fatal: No config space access function found > [ 0.189998] Unable to read sysrq code in control/sysrq > [ 0.350220] i8042: No controller found > [ 0.452153] > /home/abuild/rpmbuild/BUILD/kernel-xen-3.1.0/linux-3.1/drivers/rtc/hctosys.c: > unable to open rtc device (rtc0) >Can you please post the full domU dmesg? Remove any "quiet" etc options. I assume this is a PV domU ?> but when i switched to then "file" protocol the domU boot process would > succeed. Anyone knows how to solve this problem? >Sounds like something is broken in your dom0 configuration.> ============================================> Additional info: > > I''m using openSUSE 12.1 x86_64 > and i''v built the xen from source by myself, > the kernel i''m using is "kernel-xen"(3.1.10-1.9-xen) from official > repositories.Does it work if you also use Xen from official repositories? What''s in your dom0 kernel "dmesg"? How about in "xm log" or "xm dmesg" ? Do you have blktap driver loaded in dom0 kernel? -- Pasi
Possibly Parallel Threads
- A little confusion between "tapdisk" and "tapdisk-ioemu"
- [LLVMdev] Lots of regtest failures on PPC64/Linux
- [LLVMdev] [3.4 branch] SystemZ regressions
- [LLVMdev] [PATCH] cmake: BugpointPasses depends on intrinsics_gen
- Disk add fails while domain creation, which uses disk backend- "storage driver domain" with xen-4.3.0 , with errors libxl.c:2125