qemu/qemu.git, branch stable-0.12

pc: Fix CMOS info for drives defined with -device

2010-08-16T17:42:40+00:00

Drives defined with -drive if=ide get get created along with the IDE controller, inside machine->init(). That's before cmos_init(). Drives defined with -device get created during generic device init. That's after cmos_init(). Because of that, CMOS has no information on them (type, geometry, translation). Older versions of Windows such as XP reportedly choke on that. Split off the part of CMOS initialization that needs to know about -device devices, and turn it into a reset handler, so it runs after device creation. Signed-off-by: Markus Armbruster Signed-off-by: Kevin Wolf (cherry picked from commit c0897e0cb94e83ec1098867b81870e4f51f225b9)

ide: Make PIIX and ISA IDE init functions return the qdev

2010-08-16T17:42:04+00:00

Signed-off-by: Markus Armbruster Signed-off-by: Kevin Wolf (cherry picked from commit 57c888664b5eb7edbbce4be98cb1406aa0d85c2b)

Update for 0.12.5 release

2010-07-22T12:39:04+00:00

Signed-off-by: Aurelien Jarno

audio/alsa: Handle SND_PCM_STATE_SETUP in alsa_poll_handler

2010-07-22T12:37:23+00:00

Signed-off-by: malc (cherry picked from commit d9812b033a17c82f9e933757c1c3ef364e3ba62d)

block: Handle multiwrite errors only when all requests have completed

2010-07-14T11:09:24+00:00

Don't try to be clever by freeing all temporary data and calling all callbacks when the return value (an error) is certain. Doing so has at least two important problems: * The temporary data that is freed (qiov, possibly zero buffer) is still used by the requests that have not yet completed. * Calling the callbacks for all requests in the multiwrite means for the caller that it may free buffers etc. which are still in use. Just remember the error value and do the cleanup when all requests have completed. Signed-off-by: Kevin Wolf (cherry picked from commit de189a1b4a471d37a2909e97646654fc9751b52f)

block: Fix early failure in multiwrite

2010-07-14T11:09:24+00:00

bdrv_aio_writev may call the callback immediately (and it will commonly do so in error cases). Current code doesn't consider this. For details see the comment added by this patch. Signed-off-by: Kevin Wolf (cherry picked from commit 453f9a1652629e5805995b165be2e634c8487139) Conflicts: block.c Signed-off-by: Kevin Wolf

vpc: Use bdrv_(p)write_sync for metadata writes

2010-07-14T11:08:45+00:00

Use bdrv_(p)write_sync to ensure metadata integrity in case of a crash. Signed-off-by: Kevin Wolf (cherry picked from commit 078a458e077d6b0db262c4b05fee51d01de2d1d2) Conflicts: block/vpc.c Signed-off-by: Kevin Wolf

vmdk: Use bdrv_(p)write_sync for metadata writes

2010-07-14T11:08:04+00:00

Use bdrv_(p)write_sync to ensure metadata integrity in case of a crash. Signed-off-by: Kevin Wolf (cherry picked from commit b8852e87d9d113096342c3e0977266cda0fe9ee5) Conflicts: block/vmdk.c Signed-off-by: Kevin Wolf

qcow2: Use bdrv_(p)write_sync for metadata writes

2010-07-14T10:39:38+00:00

Use bdrv_(p)write_sync to ensure metadata integrity in case of a crash. Signed-off-by: Kevin Wolf (cherry picked from commit 8b3b720620a1137a1b794fc3ed64734236f94e06) Conflicts: block/qcow2-cluster.c block/qcow2-refcount.c block/qcow2-snapshot.c block/qcow2.c Signed-off-by: Kevin Wolf

qcow: Use bdrv_(p)write_sync for metadata writes

2010-07-14T10:18:35+00:00

Use bdrv_(p)write_sync to ensure metadata integrity in case of a crash. Signed-off-by: Kevin Wolf (cherry picked from commit 5e5557d97026d1d3325e0e7b0ba593366da2f3dc) Conflicts: block/qcow.c Signed-off-by: Kevin Wolf