On 16 Dec 2004, at 19:20, Kip Macy wrote:
Are you using an uncompressed copy of the mdroot I posted?
Duh - obviously. The only thing I can think of is that the mdroot is
corrupted. I'll double check the bits I've posted.
I got exactly these symptoms with the posted mdroot, and we fixed
it with a slightly different block device export. I'm using this
as my domain definition:
kernel = "/boot/freebsd-5.2.1-xenU"
memory = 64
cpu = -1
name = "XXVIII"
nics=1
vif = [ 'mac=aa:00:00:00:00:28, bridge=xen-br0' ]
disk = [ 'phy:munkyII/vm-XXVIII,loopa,w' ]
extra = "boot.netif.ip=10.1.70.28"
extra += ",boot.netif.netmask=255.255.255.240"
extra += ",boot.netif.gateway=10.1.70.17"
extra += ",vfs.root.mountfrom=ufs:/dev/xbd0a"
extra += ",boot_verbose=yes"
I've put the mdroot image on a devicemapper device,
/dev/munkyII/vm-XXVIII.
This domain boots fine, although I do get this kind of log message to
the console after a while:
Expensive timeout(9) function: 0xc008c730(0) 0.010000091 s
and the domain chews through CPU time as indicated by 'xm list' even
when
apparently idle. I haven't played much beyond that though.
Cheers,
Chris.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
| 
Home