Hi
On Sunday 19 August 2012, Avi Kivity wrote:
> On 08/19/2012 04:22 PM, Stefan Lippers-Hollmann wrote:
> > Hi
> >
> > On Wednesday 15 August 2012, Avi Kivity wrote:
> >> From: Orit Wasserman <[email protected]>
> >>
> >> For example migration between Westmere and Nehelem hosts, caught in big
> >> real mode.
> >>
> >> The code that fixes the segments for real mode guest was moved from
> >> enter_rmode
> >> to vmx_set_segments. enter_rmode calls vmx_set_segments for each segment.
> >>
> >> Signed-off-by: Orit Wasserman <[email protected]>
> >> Signed-off-by: Avi Kivity <[email protected]>
> >> (cherry picked from commit b246dd5df139501b974bd6b28f7815e53b3a792f)
> > […]
> >
> > I just got informed that this patch[1], as part of the current stable
> > queue-3.5 seems to break cryptsetup/ LUKS on a USB harddisk attached to
> > a sandybridge i5-2300 (USB 2.0). While I personally don't see a direct
> > relation, especially considering the other USB patches in queue-3.5,
> > bisecting the problem led to this patch - and reverting only this patch
> > from 3.5.2+queue-3.5 fixes the problem for the user.
>
> Looks very unlikely. The log doesn't look like it came from a virtual
> machine (though with enough device assignment, it's not impossible), and
> the patch only affects kvm guests.
Yes, it look pretty unlikely to me as well - especially as this is on
the native/ unvirtualized system; kvm-intel is loaded in order to use
kvm.
> Can you please double-check?
I've asked the user to recheck, and he can reproduce it reliably on
his i5-2300 (x86_64 kernel) and now also a Core2 T5600 (i386 kernel)
system, using the same encrypted USB HDD in both cases.
The USB disk fails on 3.5.2+queue-3.5 with both systems and over
several reboots, while it works with 3.5.2+queue-3.5 and only this
patch reverted.
Regards
Stefan Lippers-Hollmann
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
