[Xen-devel] xen 2.0 testing on amd64(32bit mode) runaway modprobe on lvm disk

[Robin van Leeuwen <robin.van.leeuwen@xxxxxxxxxxxxxxxxxxx>]

Hi,

I'm trying to get Xen 2.0 testing running on my amd64 (32 bit mode, debian
3.1 i386 sarge installed)
and i'm stuck on using a lvm partition as hda1. I'm getting the following
message during boot of domU:

--------
   ...
   kjournald starting.  Commit interval 5 seconds
   EXT3-fs: mounted filesystem with ordered data mode.
   VFS: Mounted root (ext3 filesystem) readonly.
   Freeing unused kernel memory: 120k freed
   request_module: runaway loop modprobe binfmt-464c
   request_module: runaway loop modprobe binfmt-464c
   request_module: runaway loop modprobe binfmt-464c
   request_module: runaway loop modprobe binfmt-464c
   request_module: runaway loop modprobe binfmt-464c
-------

and then it hangs. My xend.log shows:

---------
[2005-08-30 15:31:21 xend] DEBUG (XendDomainInfo:720) init_domain>
Created domain=2 name=samba-ha memory=128
[2005-08-30 15:31:21 xend] INFO (console:94) Created console id=14
domain=2 port=9602
[2005-08-30 15:31:21 xend] DEBUG (XendDomainInfo:1130) Creating vbd
dom=2 uname=phy:/dev/xen/samba-ha
[2005-08-30 15:31:21 xend] DEBUG (blkif:155) Connecting blkif
<BlkifBackendInterface 2 0>
[2005-08-30 15:31:21 xend] DEBUG (XendDomainInfo:1107) Creating vif
dom=2 vif=0 mac=aa:00:00:11:32:d4
[2005-08-30 15:31:21 xend] INFO (XendRoot:113) EVENT>
xend.console.create [14, 2, 9602]
[2005-08-30 15:31:21 xend] INFO (XendRoot:113) EVENT> xend.domain.create
['samba-ha', '2']
[2005-08-30 15:31:21 xend] INFO (XendRoot:113) EVENT>
xend.domain.unpause ['samba-ha', '2']
[2005-08-30 15:31:21 xend] INFO (console:44) Console connected 14
127.0.0.1 40210
[2005-08-30 15:31:21 xend] INFO (XendRoot:113) EVENT>
xend.console.connect [14, '127.0.0.1', 40210]
[2005-08-30 15:31:21 xend] DEBUG (blkif:203) Connecting blkif to event
channel <BlkifBackendInterface 2 0> ports=15:3
------------

But this appears in my logs before my domU hangs...

I also tried it with xen2.0 stable but i got the same results...






_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel