On 10/24/2014 05:44 PM, Toralf Förster wrote:
> I just reverted
>
> $ grep commit virtcons_*
> virtcons_1.patch:commit f5866db64f341776c2d9ed48080f82459fea6a55
> virtcons_2.patch:commit 401bbdc901b268113d7c562616feb7fc37492aca
>
> on top of -rc1 which solved the issue entirely here.
(but I had
On 10/21/2014 06:40 PM, Josh Boyer wrote:
> On Tue, Oct 21, 2014 at 12:10 PM, Toralf Förster
> wrote:
>> On 10/20/2014 07:34 PM, Toralf Förster wrote:
>>> I uploaded the screen shots from the virt-manager to [1] and [2]
>>>
>>> FWIW e56d9fccb was fine so the bug slipped in after that.
>>>
>>
>>>
On 10/21/2014 06:40 PM, Josh Boyer wrote:
On Tue, Oct 21, 2014 at 12:10 PM, Toralf Förster toralf.foers...@gmx.de
wrote:
On 10/20/2014 07:34 PM, Toralf Förster wrote:
I uploaded the screen shots from the virt-manager to [1] and [2]
FWIW e56d9fccb was fine so the bug slipped in after that.
On 10/24/2014 05:44 PM, Toralf Förster wrote:
I just reverted
$ grep commit virtcons_*
virtcons_1.patch:commit f5866db64f341776c2d9ed48080f82459fea6a55
virtcons_2.patch:commit 401bbdc901b268113d7c562616feb7fc37492aca
on top of -rc1 which solved the issue entirely here.
(but I had to
On 10/21/2014 06:40 PM, Josh Boyer wrote:
> On Tue, Oct 21, 2014 at 12:10 PM, Toralf Förster
> wrote:
>> On 10/20/2014 07:34 PM, Toralf Förster wrote:
>>> I uploaded the screen shots from the virt-manager to [1] and [2]
>>>
>>> FWIW e56d9fccb was fine so the bug slipped in after that.
>>>
>>
>>>
On Tue, Oct 21, 2014 at 12:10 PM, Toralf Förster wrote:
> On 10/20/2014 07:34 PM, Toralf Förster wrote:
>> I uploaded the screen shots from the virt-manager to [1] and [2]
>>
>> FWIW e56d9fccb was fine so the bug slipped in after that.
>>
>
>>
>> [1]
On 10/20/2014 07:34 PM, Toralf Förster wrote:
> I uploaded the screen shots from the virt-manager to [1] and [2]
>
> FWIW e56d9fccb was fine so the bug slipped in after that.
>
>
> [1] http://www.directupload.net/file/d/3781/j9mwrtpq_jpg.htm
> [2]
On 10/20/2014 07:34 PM, Toralf Förster wrote:
I uploaded the screen shots from the virt-manager to [1] and [2]
FWIW e56d9fccb was fine so the bug slipped in after that.
[1] http://www.directupload.net/file/d/3781/j9mwrtpq_jpg.htm
[2]
On Tue, Oct 21, 2014 at 12:10 PM, Toralf Förster toralf.foers...@gmx.de wrote:
On 10/20/2014 07:34 PM, Toralf Förster wrote:
I uploaded the screen shots from the virt-manager to [1] and [2]
FWIW e56d9fccb was fine so the bug slipped in after that.
[1]
On 10/21/2014 06:40 PM, Josh Boyer wrote:
On Tue, Oct 21, 2014 at 12:10 PM, Toralf Förster toralf.foers...@gmx.de
wrote:
On 10/20/2014 07:34 PM, Toralf Förster wrote:
I uploaded the screen shots from the virt-manager to [1] and [2]
FWIW e56d9fccb was fine so the bug slipped in after that.
On Mon, Oct 20, 2014 at 1:34 PM, Toralf Förster wrote:
> I uploaded the screen shots from the virt-manager to [1] and [2]
>
> FWIW e56d9fccb was fine so the bug slipped in after that.
>
> (The term "fine" is exceptional to this already reported issue :
>
> $> modprobe nf_reject_ipv4
> modprobe:
I uploaded the screen shots from the virt-manager to [1] and [2]
FWIW e56d9fccb was fine so the bug slipped in after that.
(The term "fine" is exceptional to this already reported issue :
$> modprobe nf_reject_ipv4
modprobe: ERROR: could not insert 'nf_reject_ipv4': Unknown symbol in module,
I uploaded the screen shots from the virt-manager to [1] and [2]
FWIW e56d9fccb was fine so the bug slipped in after that.
(The term fine is exceptional to this already reported issue :
$ modprobe nf_reject_ipv4
modprobe: ERROR: could not insert 'nf_reject_ipv4': Unknown symbol in module,
or
On Mon, Oct 20, 2014 at 1:34 PM, Toralf Förster toralf.foers...@gmx.de wrote:
I uploaded the screen shots from the virt-manager to [1] and [2]
FWIW e56d9fccb was fine so the bug slipped in after that.
(The term fine is exceptional to this already reported issue :
$ modprobe nf_reject_ipv4
14 matches
Mail list logo