On Wed, Jun 08, 2016 at 02:05:10PM +0100, George Dunlap wrote:
> On 08/06/16 13:46, Wei Liu wrote:
> > On Wed, Jun 08, 2016 at 07:53:53AM -0400, Doug Goldstein wrote:
> >> On 6/8/16 6:57 AM, George Dunlap wrote:
> >>> On 08/06/16 11:07, Daniel P. Berrange wrote:
> On Wed, Jun 08, 2016 at 10:50
On 08/06/16 13:46, Wei Liu wrote:
> On Wed, Jun 08, 2016 at 07:53:53AM -0400, Doug Goldstein wrote:
>> On 6/8/16 6:57 AM, George Dunlap wrote:
>>> On 08/06/16 11:07, Daniel P. Berrange wrote:
On Wed, Jun 08, 2016 at 10:50:24AM +0100, George Dunlap wrote:
> On 07/06/16 16:57, Wei Liu wrote:
On 08/06/16 13:11, Daniel P. Berrange wrote:
> On Wed, Jun 08, 2016 at 11:57:45AM +0100, George Dunlap wrote:
>>
>> Well we definitely want to make it possible for people to use xl while
>> still avoiding DoSes. But at the simplest level this could be done by
>> having qemu's stderr/stdout piped t
On Wed, Jun 08, 2016 at 07:53:53AM -0400, Doug Goldstein wrote:
> On 6/8/16 6:57 AM, George Dunlap wrote:
> > On 08/06/16 11:07, Daniel P. Berrange wrote:
> >> On Wed, Jun 08, 2016 at 10:50:24AM +0100, George Dunlap wrote:
> >>> On 07/06/16 16:57, Wei Liu wrote:
> > I must admit I'm not familia
On Wed, Jun 08, 2016 at 11:07:16AM +0100, Daniel P. Berrange wrote:
[...]
> > situation, but that's just a matter of plumbing I think.)
> >
> > The options we've come up with, broadly, are as follows:
> >
> > 1. Try to use the existing syslog facilities
> >
> > 2. Re-purpose one of our existing
On Wed, Jun 08, 2016 at 11:57:45AM +0100, George Dunlap wrote:
>
> Well we definitely want to make it possible for people to use xl while
> still avoiding DoSes. But at the simplest level this could be done by
> having qemu's stderr/stdout piped to /dev/null by default, and allowing
> an option f
On 6/8/16 6:57 AM, George Dunlap wrote:
> On 08/06/16 11:07, Daniel P. Berrange wrote:
>> On Wed, Jun 08, 2016 at 10:50:24AM +0100, George Dunlap wrote:
>>> On 07/06/16 16:57, Wei Liu wrote:
> I must admit I'm not familiar with the division of responsibility
> for managing QEMU between the
On 08/06/16 11:07, Daniel P. Berrange wrote:
> On Wed, Jun 08, 2016 at 10:50:24AM +0100, George Dunlap wrote:
>> On 07/06/16 16:57, Wei Liu wrote:
I must admit I'm not familiar with the division of responsibility
for managing QEMU between the Xen provided libxl library(s) and
the lib
On Wed, Jun 08, 2016 at 10:50:24AM +0100, George Dunlap wrote:
> On 07/06/16 16:57, Wei Liu wrote:
> >> I must admit I'm not familiar with the division of responsibility
> >> for managing QEMU between the Xen provided libxl library(s) and
> >> the libvirt libxl driver code. Naively I would expect t
On 07/06/16 16:57, Wei Liu wrote:
>> I must admit I'm not familiar with the division of responsibility
>> for managing QEMU between the Xen provided libxl library(s) and
>> the libvirt libxl driver code. Naively I would expect the libvirt
>> libxl driver code to deal with virtlogd and then configur
On Tue, Jun 07, 2016 at 02:21:17PM +0100, Daniel P. Berrange wrote:
> On Tue, Jun 07, 2016 at 01:11:53PM +0100, Wei Liu wrote:
> > Hello libvirt maintainers,
> >
> > Libvirt implements virtlogd in version 1.3 which now handles logging
> > for QEMU process. I am wondering if it is possible to make
On Tue, Jun 07, 2016 at 01:11:53PM +0100, Wei Liu wrote:
> Hello libvirt maintainers,
>
> Libvirt implements virtlogd in version 1.3 which now handles logging
> for QEMU process. I am wondering if it is possible to make it a
> separate package and maintain stable interfaces for external users?
Ok
12 matches
Mail list logo
