Kevin Wolf writes:
> Am 28.07.2010 13:22, schrieb Markus Armbruster:
>> Anthony Liguori writes:
>>
>>> On 07/27/2010 10:22 AM, Markus Armbruster wrote:
[...]
Raw can't be probed safely, by its very nature. For historical reasons,
we try anyway. I think we should stop doing that, eve
Am 28.07.2010 13:22, schrieb Markus Armbruster:
> Anthony Liguori writes:
>
>> On 07/27/2010 10:22 AM, Markus Armbruster wrote:
>>> Kevin Wolf writes:
>>>
>>>
Am 27.07.2010 15:00, schrieb Anthony Liguori:
> On 07/27/2010 02:19 AM, Markus Armbruster wrote:
>
>>
Anthony Liguori writes:
> On 07/27/2010 10:22 AM, Markus Armbruster wrote:
>> Kevin Wolf writes:
>>
>>
>>> Am 27.07.2010 15:00, schrieb Anthony Liguori:
>>>
On 07/27/2010 02:19 AM, Markus Armbruster wrote:
> Anthony Liguori writes:
>
>
>
>>
On 07/27/2010 08:01 PM, Daniel P. Berrange wrote:
It's annoying to us old hands, but it does give that nice integrated
system feel that we're missing, and it works even if virt-manager is in
the background (or if you don't use virt-manager at all).
Given that there's a kerneloops pluging that
On Tue, Jul 27, 2010 at 07:42:34PM +0300, Avi Kivity wrote:
> On 07/27/2010 07:36 PM, Chris Wright wrote:
> >
> >>If things work there's no reason for the user to go look at the
> >>logs. An exclamation point invites clicking.
> >>
> >>Even better would be an ABRT plugin, so if something goes
>
On 07/27/2010 07:47 PM, Avi Kivity wrote:
On 07/27/2010 07:42 PM, Daniel P. Berrange wrote:
I read that to mean...propagate stderr from qemu to be right in
front of
the user. So that's output from virsh or in virt-manager. Trouble is,
that's only useful (at best) when starting a guest. P
On 07/27/2010 07:42 PM, Daniel P. Berrange wrote:
I read that to mean...propagate stderr from qemu to be right in front of
the user. So that's output from virsh or in virt-manager. Trouble is,
that's only useful (at best) when starting a guest. Perhaps some
virt-manager thing (an exclamatio
On Tue, Jul 27, 2010 at 09:29:13AM -0700, Chris Wright wrote:
> * Daniel P. Berrange (berra...@redhat.com) wrote:
> > On Tue, Jul 27, 2010 at 07:17:06PM +0300, Avi Kivity wrote:
> > > On 07/27/2010 06:28 PM, Anthony Liguori wrote:
> > > >
> > > >If we add docs/deprecated-features.txt, schedule rem
On 07/27/2010 07:36 PM, Chris Wright wrote:
If things work there's no reason for the user to go look at the
logs. An exclamation point invites clicking.
Even better would be an ABRT plugin, so if something goes
(marginally) wrong, the siren pops up and you're invited to report
the bug.
Des
* Avi Kivity (a...@redhat.com) wrote:
> On 07/27/2010 07:29 PM, Chris Wright wrote:
> >
> >>QEMU stderr+out is already recorded in /var/lib/libvirt/qemu/$GUESTNAME.log
> >>along with the env variables and argv used to spawn it. Or did you mean
> >>provide an API + virsh command /virt-manager UI fo
On 07/27/2010 07:29 PM, Chris Wright wrote:
QEMU stderr+out is already recorded in /var/lib/libvirt/qemu/$GUESTNAME.log
along with the env variables and argv used to spawn it. Or did you mean
provide an API + virsh command /virt-manager UI for accessing the logs ?
I read that to mean...propag
* Daniel P. Berrange (berra...@redhat.com) wrote:
> On Tue, Jul 27, 2010 at 07:17:06PM +0300, Avi Kivity wrote:
> > On 07/27/2010 06:28 PM, Anthony Liguori wrote:
> > >
> > >If we add docs/deprecated-features.txt, schedule removal for at least
> > >1 year in the future, and put a warning in the c
On Tue, Jul 27, 2010 at 07:17:06PM +0300, Avi Kivity wrote:
> On 07/27/2010 06:28 PM, Anthony Liguori wrote:
> >
> >If we add docs/deprecated-features.txt, schedule removal for at least
> >1 year in the future, and put a warning in the code that prints
> >whenever raw is probed, I think I could
On 07/27/2010 06:28 PM, Anthony Liguori wrote:
If we add docs/deprecated-features.txt, schedule removal for at least
1 year in the future, and put a warning in the code that prints
whenever raw is probed, I think I could warm up to this.
Since libvirt should be insulating users from this to
On Tue, Jul 27, 2010 at 10:28:04AM -0500, Anthony Liguori wrote:
> On 07/27/2010 10:22 AM, Markus Armbruster wrote:
> >Kevin Wolf writes:
> >
> >
> >>Am 27.07.2010 15:00, schrieb Anthony Liguori:
> >>
> >>>On 07/27/2010 02:19 AM, Markus Armbruster wrote:
> >>>
> Anthony Liguori
On 07/27/2010 10:22 AM, Markus Armbruster wrote:
Kevin Wolf writes:
Am 27.07.2010 15:00, schrieb Anthony Liguori:
On 07/27/2010 02:19 AM, Markus Armbruster wrote:
Anthony Liguori writes:
- any additional input on probed_raw?
Isn't it a fait acco
Kevin Wolf writes:
> Am 27.07.2010 15:00, schrieb Anthony Liguori:
>> On 07/27/2010 02:19 AM, Markus Armbruster wrote:
>>> Anthony Liguori writes:
>>>
>>>
- any additional input on probed_raw?
>>> Isn't it a fait accompli? I stopped providing input when commit
>>> 79368c81 a
On 07/27/2010 09:30 AM, Anthony Liguori wrote:
> On 07/27/2010 06:51 AM, Daniel P. Berrange wrote:
>> On Mon, Jul 26, 2010 at 05:28:21PM -0500, Anthony Liguori wrote:
>>
>>> On 07/26/2010 04:28 PM, Chris Wright wrote:
>>>
Please send in any agenda items you are interested in covering
On 07/27/2010 06:51 AM, Daniel P. Berrange wrote:
On Mon, Jul 26, 2010 at 05:28:21PM -0500, Anthony Liguori wrote:
On 07/26/2010 04:28 PM, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
- 0.13 update
I'll pre-empt the 0.13 question wit
Am 27.07.2010 15:00, schrieb Anthony Liguori:
> On 07/27/2010 02:19 AM, Markus Armbruster wrote:
>> Anthony Liguori writes:
>>
>>
>>> - any additional input on probed_raw?
>>>
>> Isn't it a fait accompli? I stopped providing input when commit
>> 79368c81 appeared.
>>
>
> No. 79368
On 07/27/10 02:13, Alex Williamson wrote:
> On Mon, 2010-07-26 at 18:28 -0500, Anthony Liguori wrote:
>> On 07/26/2010 05:28 PM, Anthony Liguori wrote:
>>> On 07/26/2010 04:28 PM, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
>>>
>>> - 0.13 update
>>> I'
On 07/27/2010 02:19 AM, Markus Armbruster wrote:
Anthony Liguori writes:
- any additional input on probed_raw?
Isn't it a fait accompli? I stopped providing input when commit
79368c81 appeared.
No. 79368c81 was to close the security hole (and I do consider it a
security hol
On Mon, Jul 26, 2010 at 05:28:21PM -0500, Anthony Liguori wrote:
> On 07/26/2010 04:28 PM, Chris Wright wrote:
> >Please send in any agenda items you are interested in covering.
> >
>
> - 0.13 update
> I'll pre-empt the 0.13 question with an answer. I'm just testing the
> VNC changes and if
Anthony Liguori writes:
> - any additional input on probed_raw?
Isn't it a fait accompli? I stopped providing input when commit
79368c81 appeared.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
On Mon, 2010-07-26 at 18:28 -0500, Anthony Liguori wrote:
> On 07/26/2010 05:28 PM, Anthony Liguori wrote:
> > On 07/26/2010 04:28 PM, Chris Wright wrote:
> >> Please send in any agenda items you are interested in covering.
> >
> > - 0.13 update
> > I'll pre-empt the 0.13 question with an answer.
On 07/26/2010 05:28 PM, Anthony Liguori wrote:
On 07/26/2010 04:28 PM, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
- 0.13 update
I'll pre-empt the 0.13 question with an answer. I'm just testing
the VNC changes and if all goes well, I'll tag tonight.
On 07/26/2010 04:28 PM, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
- 0.13 update
I'll pre-empt the 0.13 question with an answer. I'm just testing the
VNC changes and if all goes well, I'll tag tonight.
Initial thinking is to keep 0.14 short a
Please send in any agenda items you are interested in covering.
thanks,
-chris
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
28 matches
Mail list logo
