|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [PATCH 5 of 9] libxl: only use interactive PyGrub mode w
> I think "-c" shouldn't affect the functionality of the domain, just
> whether the console is initially connected. Perhaps the console will
> be connected somewhere else.
>
> OTOH I think it would be fine to have an option (libxl config
> parameter, I guess) to make pygrub run noninteractively.
I've digged a little more into this issue, and found out that NetBSD
ptys have a 1024 buffer limit, and when this limit is hit, the select
from libxl_bootloader:211 blocks and no more data is writen to
xenconsole_fd and no more data is read from bootloader_fd (because
bootloader_buf contains data), which of course blocks the execution of
pygrub. Since the xenconsoled_fd pty is not monitored by xenconsole,
nobody is draining data from it. I don't know the best way to solve
this, but it seems like somebody should read the data from
xenconsoled_fd and dispose it if there is no console attached.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|