Avi Kivity wrote:
I pulled yesterday so it should be all right (and you don't need me for
that; you can pull from Linus on top of kvm.git).
The machine runs kvm.git for a while now, seems to work ok.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Avi Kivity wrote:
I pulled yesterday so it should be all right (and you don't need me for
that; you can pull from Linus on top of kvm.git).
Thanks :-).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Carsten Otte wrote:
Avi Kivity wrote:
kvm.git is actually 2.6.24-rc, pulled from -linus at a random point in
time, so it's not at all surprising if something is broken.
Right. We have a backup now, so next time we'll be ok ;-). Would you
please pull from Linus again to get the fix into kvm.git
Avi Kivity wrote:
kvm.git is actually 2.6.24-rc, pulled from -linus at a random point in
time, so it's not at all surprising if something is broken.
Right. We have a backup now, so next time we'll be ok ;-). Would you
please pull from Linus again to get the fix into kvm.git so that we
can use
Avi Kivity wrote:
kvm.git is actually 2.6.24-rc, pulled from -linus at a random point in
time, so it's not at all surprising if something is broken.
Right. We have a backup now, so next time we'll be ok ;-). Would you
please pull from Linus again to get the fix into kvm.git so that we
can use
Carsten Otte wrote:
Avi Kivity wrote:
kvm.git is actually 2.6.24-rc, pulled from -linus at a random point in
time, so it's not at all surprising if something is broken.
Right. We have a backup now, so next time we'll be ok ;-). Would you
please pull from Linus again to get the fix into kvm.git
Avi Kivity wrote:
I pulled yesterday so it should be all right (and you don't need me for
that; you can pull from Linus on top of kvm.git).
Thanks :-).
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Avi Kivity wrote:
I pulled yesterday so it should be all right (and you don't need me for
that; you can pull from Linus on top of kvm.git).
The machine runs kvm.git for a while now, seems to work ok.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
Am Freitag, 19. Oktober 2007 schrieb Luca Tettamanti:
> linus-git has at least one bug with SG chaining, but usually it just
> hangs the machine. Patch is here:
>
> http://lkml.org/lkml/2007/10/17/269
Looks promising.
I pulled this fix by pulling the latest Linus-git into the kvm.git. I also
On 10/19/07, Christian Borntraeger <[EMAIL PROTECTED]> wrote:
> Am Freitag, 19. Oktober 2007 schrieb Laurent Vivier:
> > Did you patch kvm.git with patch-2.6.23.1.bz2 or did you download
> > linux-2.6.23.1.tar.bz2 ?
> >
> > 2.6.23.1 corrects nothing except sata_mv...
>
> Yes I know. The question
Am Freitag, 19. Oktober 2007 schrieb Laurent Vivier:
> Did you patch kvm.git with patch-2.6.23.1.bz2 or did you download
> linux-2.6.23.1.tar.bz2 ?
>
> 2.6.23.1 corrects nothing except sata_mv...
Yes I know. The question we tried to answer was: is the bug in 2.6.23 or was
it introduced after
Carsten Otte wrote:
> Hi list,
>
> we've experienced a severe bug in current kvm.git, that may have been
> introduced to the git tree quite recently around last weekend. 2.6.23
> is broken, 2.6.23-rc8 works for us. The symptom is, that our operon
> kvm test machine shredders its hard disk
Christian Borntraeger a écrit :
Am Freitag, 19. Oktober 2007 schrieb Jan Engelhardt:
On Oct 19 2007 15:44, Carsten Otte wrote:
Carsten Otte wrote:
First thing we do, is figure whether or not 2.6.23.1 as released breaks our
system too. This way, we can either focus on differences between Linus
Am Freitag, 19. Oktober 2007 schrieb Jan Engelhardt:
>
> On Oct 19 2007 15:44, Carsten Otte wrote:
> > Carsten Otte wrote:
> >> First thing we do, is figure whether or not 2.6.23.1 as released breaks our
> >> system too. This way, we can either focus on differences between Linus and
> >> Avi, or
On Oct 19 2007 15:44, Carsten Otte wrote:
> Carsten Otte wrote:
>> First thing we do, is figure whether or not 2.6.23.1 as released breaks our
>> system too. This way, we can either focus on differences between Linus and
>> Avi, or turn on the big red warning sign saying "regression".
>
> Looks
Carsten Otte wrote:
First thing we do, is figure whether or not 2.6.23.1 as released breaks
our system too. This way, we can either focus on differences between
Linus and Avi, or turn on the big red warning sign saying "regression".
Looks like 2.6.23.1 works fine on that box. We'll leave it
On Fri, 19 Oct 2007 09:07:42 pm Carsten Otte wrote:
> Aurelien Jarno wrote:
> > Could you please precise what is corrupted? The guest disk image?
>
> As stated, we actually did not run any guests and did not load the kvm
> kernel modules.
> The host root file system gets corrupted to an extend not
Mike Lampard wrote:
There was a commit ab9c232286c2b77be78441c2d8396500b045777e regarding libata
on linus's master tree that happened on Friday, that was pulled into kvm git
over the weekend.. I dont know if that may be affecting you.. there is/was
also chatter on LKML regarding some problems
Am Freitag, 19. Oktober 2007 schrieb Laurent Vivier:
> Carsten Otte a écrit :
> > Laurent Vivier wrote:
> >> How do you know the problem has been introduced by kvm ?
> > I don't. In fact I think it has not been introduced by kvm. All I
> > stated, is that we experienced the problem when running
Carsten Otte wrote:
2.6.23 is broken, 2.6.23-rc8 works for us.
Actually, the working version was 2.6.23-rc6, git-head of kvm.git as
of October 11.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Carsten Otte a écrit :
Laurent Vivier wrote:
How do you know the problem has been introduced by kvm ?
I don't. In fact I think it has not been introduced by kvm. All I
stated, is that we experienced the problem when running the kvm.git
kernel after the 2.6.23 update that has not been present
Laurent Vivier wrote:
How do you know the problem has been introduced by kvm ?
I don't. In fact I think it has not been introduced by kvm. All I
stated, is that we experienced the problem when running the kvm.git
kernel after the 2.6.23 update that has not been present in the
kvm.git -rc8 as
Carsten Otte a écrit :
Aurelien Jarno wrote:
Could you please precise what is corrupted? The guest disk image?
As stated, we actually did not run any guests and did not load the kvm
kernel modules.
The host root file system gets corrupted to an extend not correctable
by the file system
Aurelien Jarno wrote:
Could you please precise what is corrupted? The guest disk image?
As stated, we actually did not run any guests and did not load the kvm
kernel modules.
The host root file system gets corrupted to an extend not correctable
by the file system checker (we gave it 24h to
Carsten Otte a écrit :
> Hi list,
>
> we've experienced a severe bug in current kvm.git, that may have been
> introduced to the git tree quite recently around last weekend. 2.6.23
> is broken, 2.6.23-rc8 works for us. The symptom is, that our operon
> kvm test machine shredders its hard disk
Hi list,
we've experienced a severe bug in current kvm.git, that may have been
introduced to the git tree quite recently around last weekend. 2.6.23
is broken, 2.6.23-rc8 works for us. The symptom is, that our operon
kvm test machine shredders its hard disk content to a state that is
not
On Oct 19 2007 15:44, Carsten Otte wrote:
Carsten Otte wrote:
First thing we do, is figure whether or not 2.6.23.1 as released breaks our
system too. This way, we can either focus on differences between Linus and
Avi, or turn on the big red warning sign saying regression.
Looks like
Am Freitag, 19. Oktober 2007 schrieb Luca Tettamanti:
linus-git has at least one bug with SG chaining, but usually it just
hangs the machine. Patch is here:
http://lkml.org/lkml/2007/10/17/269
Looks promising.
I pulled this fix by pulling the latest Linus-git into the kvm.git. I also
Christian Borntraeger a écrit :
Am Freitag, 19. Oktober 2007 schrieb Jan Engelhardt:
On Oct 19 2007 15:44, Carsten Otte wrote:
Carsten Otte wrote:
First thing we do, is figure whether or not 2.6.23.1 as released breaks our
system too. This way, we can either focus on differences between Linus
Am Freitag, 19. Oktober 2007 schrieb Jan Engelhardt:
On Oct 19 2007 15:44, Carsten Otte wrote:
Carsten Otte wrote:
First thing we do, is figure whether or not 2.6.23.1 as released breaks our
system too. This way, we can either focus on differences between Linus and
Avi, or turn on the
Mike Lampard wrote:
There was a commit ab9c232286c2b77be78441c2d8396500b045777e regarding libata
on linus's master tree that happened on Friday, that was pulled into kvm git
over the weekend.. I dont know if that may be affecting you.. there is/was
also chatter on LKML regarding some problems
Am Freitag, 19. Oktober 2007 schrieb Laurent Vivier:
Carsten Otte a écrit :
Laurent Vivier wrote:
How do you know the problem has been introduced by kvm ?
I don't. In fact I think it has not been introduced by kvm. All I
stated, is that we experienced the problem when running the kvm.git
Carsten Otte wrote:
2.6.23 is broken, 2.6.23-rc8 works for us.
Actually, the working version was 2.6.23-rc6, git-head of kvm.git as
of October 11.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Carsten Otte a écrit :
Laurent Vivier wrote:
How do you know the problem has been introduced by kvm ?
I don't. In fact I think it has not been introduced by kvm. All I
stated, is that we experienced the problem when running the kvm.git
kernel after the 2.6.23 update that has not been present
Aurelien Jarno wrote:
Could you please precise what is corrupted? The guest disk image?
As stated, we actually did not run any guests and did not load the kvm
kernel modules.
The host root file system gets corrupted to an extend not correctable
by the file system checker (we gave it 24h to
Carsten Otte a écrit :
Hi list,
we've experienced a severe bug in current kvm.git, that may have been
introduced to the git tree quite recently around last weekend. 2.6.23
is broken, 2.6.23-rc8 works for us. The symptom is, that our operon
kvm test machine shredders its hard disk content
Hi list,
we've experienced a severe bug in current kvm.git, that may have been
introduced to the git tree quite recently around last weekend. 2.6.23
is broken, 2.6.23-rc8 works for us. The symptom is, that our operon
kvm test machine shredders its hard disk content to a state that is
not
On 10/19/07, Christian Borntraeger [EMAIL PROTECTED] wrote:
Am Freitag, 19. Oktober 2007 schrieb Laurent Vivier:
Did you patch kvm.git with patch-2.6.23.1.bz2 or did you download
linux-2.6.23.1.tar.bz2 ?
2.6.23.1 corrects nothing except sata_mv...
Yes I know. The question we tried to
Am Freitag, 19. Oktober 2007 schrieb Laurent Vivier:
Did you patch kvm.git with patch-2.6.23.1.bz2 or did you download
linux-2.6.23.1.tar.bz2 ?
2.6.23.1 corrects nothing except sata_mv...
Yes I know. The question we tried to answer was: is the bug in 2.6.23 or was
it introduced after
Carsten Otte wrote:
Hi list,
we've experienced a severe bug in current kvm.git, that may have been
introduced to the git tree quite recently around last weekend. 2.6.23
is broken, 2.6.23-rc8 works for us. The symptom is, that our operon
kvm test machine shredders its hard disk content to
Carsten Otte wrote:
First thing we do, is figure whether or not 2.6.23.1 as released breaks
our system too. This way, we can either focus on differences between
Linus and Avi, or turn on the big red warning sign saying regression.
Looks like 2.6.23.1 works fine on that box. We'll leave it
Carsten Otte a écrit :
Aurelien Jarno wrote:
Could you please precise what is corrupted? The guest disk image?
As stated, we actually did not run any guests and did not load the kvm
kernel modules.
The host root file system gets corrupted to an extend not correctable
by the file system
Laurent Vivier wrote:
How do you know the problem has been introduced by kvm ?
I don't. In fact I think it has not been introduced by kvm. All I
stated, is that we experienced the problem when running the kvm.git
kernel after the 2.6.23 update that has not been present in the
kvm.git -rc8 as
On Fri, 19 Oct 2007 09:07:42 pm Carsten Otte wrote:
Aurelien Jarno wrote:
Could you please precise what is corrupted? The guest disk image?
As stated, we actually did not run any guests and did not load the kvm
kernel modules.
The host root file system gets corrupted to an extend not
44 matches
Mail list logo
