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/
Home Products Support Community News


[Xen-users] AMD64 domU with i386 dom0

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] AMD64 domU with i386 dom0
From: Derek <lists@xxxxxxxxxxxx>
Date: Thu, 09 Sep 2010 14:38:43 +1200
Delivery-date: Wed, 08 Sep 2010 19:40:13 -0700
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>
Reply-to: lists@xxxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv: Gecko/20100825 Lightning/1.0b2 Thunderbird/3.1.3
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
Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>