Applied. Thanks.
Regards,
Anthony Liguori
On Tue, Jun 11, 2013 at 04:53:51PM -0500, mdroth wrote:
On Wed, May 22, 2013 at 11:32:51AM -0500, Michael Roth wrote:
When this VMSD was introduced it's version fields were set to
sizeof(I6300State), making them essentially random from build to build,
version to version.
To fix this,
mdroth mdr...@linux.vnet.ibm.com writes:
On Tue, Jun 11, 2013 at 04:53:51PM -0500, mdroth wrote:
On Wed, May 22, 2013 at 11:32:51AM -0500, Michael Roth wrote:
When this VMSD was introduced it's version fields were set to
sizeof(I6300State), making them essentially random from build to
mdroth mdr...@linux.vnet.ibm.com wrote:
On Tue, Jun 11, 2013 at 04:53:51PM -0500, mdroth wrote:
On Wed, May 22, 2013 at 11:32:51AM -0500, Michael Roth wrote:
When this VMSD was introduced it's version fields were set to
sizeof(I6300State), making them essentially random from build to build,
On Wed, May 22, 2013 at 11:32:51AM -0500, Michael Roth wrote:
When this VMSD was introduced it's version fields were set to
sizeof(I6300State), making them essentially random from build to build,
version to version.
To fix this, we lock in a high version id and low minimum version id to
On (Wed) 22 May 2013 [11:32:51], Michael Roth wrote:
When this VMSD was introduced it's version fields were set to
sizeof(I6300State), making them essentially random from build to build,
version to version.
To fix this, we lock in a high version id and low minimum version id to
support
When this VMSD was introduced it's version fields were set to
sizeof(I6300State), making them essentially random from build to build,
version to version.
To fix this, we lock in a high version id and low minimum version id to
support old-new migration from all prior versions of this device's
On Wed, May 22, 2013 at 11:32:51AM -0500, Michael Roth wrote:
When this VMSD was introduced it's version fields were set to
sizeof(I6300State), making them essentially random from build to build,
version to version.
To fix this, we lock in a high version id and low minimum version id to
On 05/22/13 18:32, Michael Roth wrote:
When this VMSD was introduced it's version fields were set to
sizeof(I6300State), making them essentially random from build to build,
version to version.
To fix this, we lock in a high version id and low minimum version id to
support old-new migration
