Re: [Xen-devel] xm-test domain creation delay

[Dan Smith <danms@xxxxxxxxxx>]

EM> Well it would be better if we could compile and link against the
EM> version of libc in the ramdisk!

That's true for the libc case, but not for libxenctrl, right?

EM> How do all the other applications in the ramdisk get compiled now?

I believe that the only application on the ramdisk at the moment is
busybox, which is static.  uClibc is on there as well, since the
buildroot system can optionally download, compile, and link other
applications into the ramdisk automatically.

EM> Is it sufficient to say that once you can connect the console,
EM> then the guest is ready for commands? 

Well, not in the "xm console" sense, but in the xm-test console
library, this is true.  The xm-test console library isn't connected
and passed back to the test until it has seen the special shell
prompt.  So, this means the DomU is actually ready for commands.

EM> That wouldn't be the case for a "real" guest, of course, but if
EM> that's OK for xm-test (or close enough that we only need a 1
EM> second timeout or something) then that sounds like a better idea.

Right, which is why I asked if this sort of thing would be needed in a
generic sense.

I'm testing the modification to the console right now, which seems to
be working on my machine. 

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx


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