From: Bryan Christ <bryan.christ@gmail.com>
To: Tomasz Chmielewski <tch@wpkg.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Windows BSOD with copied image
Date: Fri, 5 Jun 2009 11:09:46 -0500 [thread overview]
Message-ID: <444391460906050909w276349c4p1790ba0d992fe86b@mail.gmail.com> (raw)
In-Reply-To: <4A294212.6060704@wpkg.org>
image 1 (original)
file_sz = 5198807040
md5 = 4b876cb73179b10e3ddb9efe501138a1
image 2 (copy)
file_sz = 5150924800
md5 = 3e191730ddd150fafbcf0e4fe82f46b3
On Fri, Jun 5, 2009 at 11:04 AM, Tomasz Chmielewski <tch@wpkg.org> wrote:
> Bryan Christ wrote:
>>
>> Sorry to be a pest, but I posted this on the user forum and haven't
>> received any replies.
>>
>> ...
>>
>> I have a working Windows XP qcow2 image. I have tried several ways to
>> copy it. I have used cp, dd, and qemu-img convert. In all cases,
>> Windows XP will BSOD when the copied image is run. Any thoughts? I
>> suspect that it might be related to the fact that the original file
>> has "-rw-r--r--." permissions and the copy does not have the "." in
>> the right-most column (no idea what that means and how to change it).
>
> What does:
>
> md5sum xp-image xp-image-copy
>
> say?
>
>
> --
> Tomasz Chmielewski
> http://wpkg.org
>
--
Bryan
<><
next prev parent reply other threads:[~2009-06-05 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 15:48 [Qemu-devel] Windows BSOD with copied image Bryan Christ
2009-06-05 16:04 ` Tomasz Chmielewski
2009-06-05 16:05 ` Bryan Christ
2009-06-05 16:10 ` Tomasz Chmielewski
2009-06-05 16:49 ` Bryan Christ
2009-06-05 18:47 ` Bryan Christ
2009-06-05 16:09 ` Bryan Christ [this message]
2009-06-07 1:05 ` [Qemu-devel] How does one find out who ( or what ) is working on each aspect of QEMU ? AGSCalabrese
2009-06-07 5:45 ` Avi Kivity
2009-06-07 9:43 ` Johannes Schindelin
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=444391460906050909w276349c4p1790ba0d992fe86b@mail.gmail.com \
--to=bryan.christ@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=tch@wpkg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).