| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
[Xen-users] SOLVED Re: AMD64 domU with i386 dom0
After much googling I found that the initrd
(created on apt-get/dpkg of linux-image-2.6.26-2-xen-686) must be
created on a 32bit (i386) system. This then incorporates the
32bit version of the modprobe binary.
I'm a happy camper.
Many thanks to the author of the blog that helped -- http://www.kytalia.com.au/blog/2-xen/7-xen-to-the-rescue.html
Cheers
Derek
On 9/09/10 3:58 PM, Derek wrote:
Sorry, got my dom's backwards here.
On 9/09/10 2:38 PM, Derek wrote:
Hi All,
i've read that a xen domU running amd64 can host i386 dom0
clients. This is really useful for me so I decided to give it
a shot.
I'm running Debian lenny, I grabbed
linux-image-2.6.26-2-xen-686_2.6.26-25_i386.deb
linux-modules-2.6.26-2-xen-686_2.6.26-25_i386.deb and used
dpkg -i --force-architecture to get them installed.
I used xen-create-image with --arch=i386 to build the dom0,
this completes fine, I get the following on the console while
booting the dom0
---- snip ----
[ 0.297627] XENBUS: Device with no driver: device/console/0
[ 0.297634] drivers/rtc/hctosys.c: unable to open rtc
device (rtc0)
[ 0.297691] Freeing unused kernel memory: 196k freed
[ 0.298963] request_module: runaway loop modprobe
binfmt-464c
[ 0.298970] request_module: runaway loop modprobe
binfmt-464c
[ 0.299017] request_module: runaway loop modprobe
binfmt-464c
[ 0.299022] request_module: runaway loop modprobe
binfmt-464c
[ 0.299092] request_module: runaway loop modprobe
binfmt-464c
[ 132.071310] INFO: task swapper:1 blocked for more than 120
seconds.
[ 132.071322] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 132.071327] swapper D 11bf370a 0 1 0
[ 132.071333] dfc21900 00000246 dfc20068 11bf370a
00000000 dfc21a88 c1560b40 00000000
[ 132.071346] c035a000 00000001 c011bf5f 00000280
00000000 00000001 dfc20040 c011794e
[ 132.071359] 00000003 00000001 dfc4dfbc dfc1de84
00000001 00000000 7fffffff 7fffffff
[ 132.071373] Call Trace:
[ 132.071380] [<c011bf5f>]
check_preempt_wakeup+0xa6/0xc6
[ 132.071393] [<c011794e>] try_to_wake_up+0xe8/0xf1
[ 132.071398] [<c02caf77>] schedule_timeout+0x13/0x86
[ 132.071409] [<c0116913>] __wake_up+0x29/0x39
---- snip ----
I can provide more on request.
Any help is appreciated, I couldn't find much documentation on
doing the above so I might write something up if there is a
solution.
Kind regards
Derek
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home