All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Coiner <jcoiner@stanfordalumni.org>
To: qemu-devel@nongnu.org, brad@wasp.net.au
Subject: Re: [Qemu-devel] [patch] non-blocking disk IO
Date: Tue, 04 Oct 2005 19:03:32 -0400	[thread overview]
Message-ID: <43430A44.7010403@stanfordalumni.org> (raw)
In-Reply-To: <4342E8B7.8050507@wasp.net.au>



Brad Campbell wrote:
> With this patch qemu will not boot the qcow files but will boot the base 
> images (I copy them and then try to boot to test). As soon as I patch -R 
> && make, qemu will boot the qcow files no problems..
> 
> Let me clarify that..
> qemu-img create -f qcow xp.img 4G
> qemu -cdrom xp.iso -hda xp.img -boot d (Install XP from scratch)
> qemu-img create -b xp.img -f qcow xp2.img
> qemu -hda xp2.img
> 
> This gives me an invalid hard disk error. If I revert the patch I can 
> boot from xp2.img with no issues. With or without the patch I can boot 
> from xp.img.
> 
> I have tried installing XP with and without the patch and that works fine..
> 
> Regards,
> Brad

Thanks for the report. I was able to reproduce this.

The problem was due to missing Makefile dependencies. The patch modifies 
'block_int.h', which is #included in several '.c' files. The file 
'block.c' recompiled at 'make' time, but 'block-qcow.c' didn't. The 
resulting '.o' files had different opinions about what a 
BlockDriverState struct looked like, which broke the qcow code.

Unaware of this, I added a printf to 'block-qcow.c', and the printf 
fixed the problem! The man page for printf doesn't mention this... and 
then I was enlightened. :P

To be safe, try a 'make clean ; make install' and you should be all 
good. Let me know if not.

-- John

  reply	other threads:[~2005-10-04 23:04 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-03  6:49 [Qemu-devel] [patch] non-blocking disk IO John Coiner
2005-10-03  7:09 ` Magnus Damm
2005-10-03  9:57 ` Elefterios Stamatogiannakis
2005-10-03 12:58   ` Christian MICHON
2005-10-04  7:17     ` John Coiner
2005-10-04  7:46       ` Christian MICHON
2005-10-04  8:52       ` Elefterios Stamatogiannakis
2005-10-04  9:35         ` Christian MICHON
2005-10-04 11:19           ` Christian MICHON
2005-10-04 12:22             ` Jens Axboe
2005-10-04 13:14             ` John Coiner
2005-10-04 13:20               ` Christian MICHON
2005-10-03 13:58 ` Jens Axboe
2005-10-03 22:29   ` John Coiner
2005-10-04  6:41     ` Jens Axboe
2005-10-04  1:35   ` Troy Benjegerdes
2005-10-04  3:25     ` John Coiner
2005-10-04  3:49     ` Henrik Nordstrom
2005-10-04  5:24       ` Troy Benjegerdes
2005-10-04  6:44         ` Jens Axboe
2005-10-03 18:33 ` Fabrice Bellard
2005-10-04 20:40 ` Brad Campbell
2005-10-04 23:03   ` John Coiner [this message]
2005-10-05 11:27     ` Brad Campbell
2005-10-05 14:28       ` Troy Benjegerdes
2005-11-28 22:41         ` Ryan Rempel
  -- strict thread matches above, loose matches on Subject: below --
2005-10-03 12:41 John Coiner
2005-10-04  1:34 ` Troy Benjegerdes
2005-10-04  3:16   ` John Coiner
2005-10-04 14:26     ` Troy Benjegerdes
2005-10-04 22:11       ` John Coiner
2005-10-05  3:17         ` Troy Benjegerdes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43430A44.7010403@stanfordalumni.org \
    --to=jcoiner@stanfordalumni.org \
    --cc=brad@wasp.net.au \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.