Re: [Qemu-devel] [PATCH] ide: Add resize callback to ide/core

2014-08-13 Thread Stefan Hajnoczi
On Tue, Aug 12, 2014 at 02:44:09PM -0400, John Snow wrote: Currently, if the block device backing the IDE drive is resized, the information about the device as cached inside of the IDEState structure is not updated, thus when a guest OS re-queries the drive, it is unable to see the expanded

Re: [Qemu-devel] [PATCH] ide: Add resize callback to ide/core

2014-08-13 Thread Stefan Hajnoczi
On Tue, Aug 12, 2014 at 02:44:09PM -0400, John Snow wrote: Currently, if the block device backing the IDE drive is resized, the information about the device as cached inside of the IDEState structure is not updated, thus when a guest OS re-queries the drive, it is unable to see the expanded

Re: [Qemu-devel] [PATCH] ide: Add resize callback to ide/core

2014-08-13 Thread Markus Armbruster
John Snow js...@redhat.com writes: Currently, if the block device backing the IDE drive is resized, the information about the device as cached inside of the IDEState structure is not updated, thus when a guest OS re-queries the drive, it is unable to see the expanded size. This patch adds a

[Qemu-devel] [PATCH] ide: Add resize callback to ide/core

2014-08-12 Thread John Snow
Currently, if the block device backing the IDE drive is resized, the information about the device as cached inside of the IDEState structure is not updated, thus when a guest OS re-queries the drive, it is unable to see the expanded size. This patch adds a resize callback to correct this, and

Re: [Qemu-devel] [PATCH] ide: Add resize callback to ide/core

2014-08-12 Thread Fam Zheng
On Tue, 08/12 14:44, John Snow wrote: Currently, if the block device backing the IDE drive is resized, the information about the device as cached inside of the IDEState structure is not updated, thus when a guest OS re-queries the drive, it is unable to see the expanded size. This patch