Sorry for the noise, a pristine 3.1.0 source tree solved the problem.
Regards,
Zoltan HERPAI
Zoltan HERPAI wrote:> Hello,
>
> I have a 64-bit Xen-3.1.0 dom0, on which I would like to run a 32-bit
> domU. Kernel and userland for dom0 was compiled on a 64-bit host
> machine, kernel for the domU was compiled on an another 32-bit host,
> using stock kernel config at the latter. At boot time, the following
> error happens:
>
> [2318558.522636] register_blkdev: cannot get major 8 for sd
> [2318558.522676] vbd vbd-2049: 19 xlvbd_add at
> /local/domain/0/backend/vbd/41/2049
> [2318558.524610] register_blkdev: cannot get major 8 for sd
> [2318558.524620] vbd vbd-2049: 19 xlvbd_add at
> /local/domain/0/backend/vbd/41/2049
> [2318558.527499] register_blkdev: cannot get major 8 for sd
> [2318558.527517] vbd vbd-2050: 19 xlvbd_add at
> /local/domain/0/backend/vbd/41/2050
> [2318558.537944] netfront: device eth0 has copying receive path.
> [2318568.605993] XENBUS: Timeout connecting to device: device/vbd/2049
> (state 6)
> [2318568.606007] XENBUS: Timeout connecting to device: device/vbd/2050
> (state 6)
> [2318568.606013] XENBUS: Device with no driver: device/console/0
> [2318568.606156] VFS: Cannot open root device "sda1" or
> unknown-block(0,0)
> [2318568.606161] Please append a correct "root=" boot option
> [2318568.606166] Kernel panic - not syncing: VFS: Unable to mount root
> fs on unknown-block(0,0)
>
> It can be seen that netfront registers itself successfully, only
> blkfront has problems with accessing the block backend. Other 64-bit
> domUs run fine, even with kernel used back from 3.0.4, namely
> 2.6.16.33-xen.
>
> Anyone can shed some light on this? (32-bit domU is a requirement now.)
>
> Regards,
> Zoltan HERPAI
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users