On (Wed) Mar 24 2010 [07:31:11], James Laska wrote:
On Wed, 2010-03-24 at 10:52 +0800, Li Ming wrote:
> On 03/23/2010 03:44 PM, Ales Kozumplik wrote:
> > Hi Liam,
> > On 03/23/2010 04:03 AM, Li Ming wrote:
> >> If it works on F13, do we have some specific steps?
> >> 1. how to tell anaconda to open /dev/virio-ports/...ananconda.log,pass
> >> some args during boot? or this is default?
> > This is not implemented, open a bug for this and assign it to me please.
> > It's not going to make F13 probably.
> Thanks Ales,I filed a bug :
Can you help me understand what anaconda support is missing? I
understand that may be beneficial for built-in installer support for
communicating logs over a virtio-serial device.
However, I'm curious if this is a working solution at a basic level. Is
it possible to communicate between F13 virt guest and host over a
virtio-serial device at all?
How does communication over the
virtio-serial device work, is it a network, a pipe, a block device?
It's a char device, available in /dev/vport*. The host (libvirt) can
create a device and give it the 'org.fedoraproject.anaconda.log' name so
that anaconda just has to open
'/dev/virtio-ports/org.fedoraproject.anaconda.log' and start writing its
logs to it. Assuming POLLOUT is set for the device.
Assuming that works, are there known problems that would restrict
this same solution inside stage2 anaconda?
I'm not sure about anaconda internals, but the virtio-serial device is a
simple char device that supports open/read/write/poll/close.