On (Mon) Mar 22 2010 [16:46:12], Li Ming wrote:
> Greetings Amit,

Hello Li,


> I tried to find you on IRC, but you seemed to be not there.We are

I'm available as 'amitshah' on freenode and 'amit' on oftc.

> very interested in virtio-serial. I just want to know this is possible
> for current anaconda of F13:
> Install F13 in KVM, during install,anaconda will create the log in
> /tmp/anaconda.log, can we get this file(anaconda.log) or the content of
> this file via virtio-serial in host? I mean while anaconda is generating
> logs in /tmp/anaconda.log in guest ,we can get this log in host at the
> same time.

We'll need some co-operation by the anaconda folks and libvirt /
virt-manager for this.

If Anaconda can successfully open something like

/dev/virtio-ports/org.fedoraproject.anaconda.log

then the logs could be routed directly to the host.

Libvirt/virt-manager could spawn a virtio-serial port that connects to
some socket on the host (tcp/udp/unix domain sockets).

It should be possible on a F13 guest image with qemu-kvm from
virt-preview. (I don't know if the relevant changes have been pushed to
F12 yet.)

In fact, someone from the Anaconda team had contacted me for doing such
a thing but I don't think it has moved forward at all. CC'ing the
anaconda-devel list (and I hope it's not moderated).

Amit

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

On 03/22/2010 05:52 PM, Amit Shah wrote:

On (Mon) Mar 22 2010 [16:46:12], Li Ming wrote:

Greetings Amit,


Hello Li,



I tried to find you on IRC, but you seemed to be not there.We are


I'm available as 'amitshah' on freenode and 'amit' on oftc.


very interested in virtio-serial. I just want to know this is possible
for current anaconda of F13:
Install F13 in KVM, during install,anaconda will create the log in
/tmp/anaconda.log, can we get this file(anaconda.log) or the content of
this file via virtio-serial in host? I mean while anaconda is generating
logs in /tmp/anaconda.log in guest ,we can get this log in host at the
same time.


We'll need some co-operation by the anaconda folks and libvirt /
virt-manager for this.

If Anaconda can successfully open something like

/dev/virtio-ports/org.fedoraproject.anaconda.log

then the logs could be routed directly to the host.

Libvirt/virt-manager could spawn a virtio-serial port that connects to
some socket on the host (tcp/udp/unix domain sockets).

It should be possible on a F13 guest image with qemu-kvm from
virt-preview. (I don't know if the relevant changes have been pushed to
F12 yet.)


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?
2. What command can create guest with virtio-serial port which is
required to route logs.



In fact, someone from the Anaconda team had contacted me for doing such
a thing but I don't think it has moved forward at all. CC'ing the
anaconda-devel list (and I hope it's not moderated).



I want to know this too, who can tell us the progress?

Thanks
Liam

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

On (Tue) Mar 23 2010 [11:03:05], Li Ming wrote:
> On 03/22/2010 05:52 PM, Amit Shah wrote:
>> On (Mon) Mar 22 2010 [16:46:12], Li Ming wrote:
>>> Greetings Amit,
>>
>> Hello Li,
>>
>>
>>> I tried to find you on IRC, but you seemed to be not there.We are
>>
>> I'm available as 'amitshah' on freenode and 'amit' on oftc.
>>
>>> very interested in virtio-serial. I just want to know this is possible
>>> for current anaconda of F13:
>>> Install F13 in KVM, during install,anaconda will create the log in
>>> /tmp/anaconda.log, can we get this file(anaconda.log) or the content of
>>> this file via virtio-serial in host? I mean while anaconda is generating
>>> logs in /tmp/anaconda.log in guest ,we can get this log in host at the
>>> same time.
>>
>> We'll need some co-operation by the anaconda folks and libvirt /
>> virt-manager for this.
>>
>> If Anaconda can successfully open something like
>>
>> /dev/virtio-ports/org.fedoraproject.anaconda.log
>>
>> then the logs could be routed directly to the host.
>>
>> Libvirt/virt-manager could spawn a virtio-serial port that connects to
>> some socket on the host (tcp/udp/unix domain sockets).
>>
>> It should be possible on a F13 guest image with qemu-kvm from
>> virt-preview. (I don't know if the relevant changes have been pushed to
>> F12 yet.)
>
> 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 will need changes in the anaconda code.

> 2. What command can create guest with virtio-serial port which is
> required to route logs.

See the page at

https://fedoraproject.org/wiki/Features/VirtioSerial

for usage.

>> In fact, someone from the Anaconda team had contacted me for doing such
>> a thing but I don't think it has moved forward at all. CC'ing the
>> anaconda-devel list (and I hope it's not moderated).
>>
>
> I want to know this too, who can tell us the progress?

Someone from the anaconda team -- additionally CC'ing David Cantrell.

Amit

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

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.



2. What command can create guest with virtio-serial port which is
required to route logs.


Shouldn't the hypervisor just create the machine with the port the same
way it creates e.g. virtio disk drives?


Ales

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

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 :
https://bugzilla.redhat.com/show_bug.cgi?id=576439

Liam

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

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 :
> https://bugzilla.redhat.com/show_bug.cgi?id=576439

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?
Assuming that works, are there known problems that would restrict using
this same solution inside stage2 anaconda?

Thanks,
James

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

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 :
> > https://bugzilla.redhat.com/show_bug.cgi?id=576439
>
> 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?

Yes.

> 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 using
> 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.

Amit

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list