[Qemu-devel] Windows BSOD with copied image

[Qemu-devel] Windows BSOD with copied image

[Bryan Christ]

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).

-- 
Bryan
<><

Re: [Qemu-devel] Windows BSOD with copied image

[Tomasz Chmielewski]

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

Re: [Qemu-devel] Windows BSOD with copied image

[Bryan Christ]

I'll provide that, but I can tell you they will not match because the
file size is slightly off.

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
<><

Re: [Qemu-devel] Windows BSOD with copied image

[Bryan Christ]

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
<><

Re: [Qemu-devel] Windows BSOD with copied image

[Tomasz Chmielewski]

Bryan Christ wrote:
> I'll provide that, but I can tell you they will not match because the
> file size is slightly off.

Even when copied with cp or dd?

Something fishy on your machine.

-- 
Tomasz Chmielewski
http://wpkg.org

Re: [Qemu-devel] Windows BSOD with copied image

[Bryan Christ]

When I use "cp" the md5sum hashes matches and the file sizes are the
same, but I still get a BSOD.

On Fri, Jun 5, 2009 at 11:10 AM, Tomasz Chmielewski <mangoo@wpkg.org> wrote:
> Bryan Christ wrote:
>>
>> I'll provide that, but I can tell you they will not match because the
>> file size is slightly off.
>
> Even when copied with cp or dd?
>
> Something fishy on your machine.
>
> --
> Tomasz Chmielewski
> http://wpkg.org
>



-- 
Bryan
<><

Re: [Qemu-devel] Windows BSOD with copied image

[Bryan Christ]

My sincerest apologies to everyone on this list.  As a developer
myself, I should have know to take Qemu Launcher out of the test
equation.  Running the copy from the command line works just fine with
no BSOD.

On Fri, Jun 5, 2009 at 11:49 AM, Bryan Christ<bryan.christ@gmail.com> wrote:
> When I use "cp" the md5sum hashes matches and the file sizes are the
> same, but I still get a BSOD.
>
> On Fri, Jun 5, 2009 at 11:10 AM, Tomasz Chmielewski <mangoo@wpkg.org> wrote:
>> Bryan Christ wrote:
>>>
>>> I'll provide that, but I can tell you they will not match because the
>>> file size is slightly off.
>>
>> Even when copied with cp or dd?
>>
>> Something fishy on your machine.
>>
>> --
>> Tomasz Chmielewski
>> http://wpkg.org
>>
>
>
>
> --
> Bryan
> <><
>



-- 
Bryan
<><

[Qemu-devel] How does one find out who ( or what ) is working on each aspect of QEMU ?

[AGSCalabrese]

How does one find out who ( or what ) is working on each aspect of  
QEMU ?

Gus Calabrese
nope9.com

Re: [Qemu-devel] How does one find out who ( or what ) is working on each aspect of QEMU ?

[Avi Kivity]

AGSCalabrese wrote:
> How does one find out who ( or what ) is working on each aspect of QEMU ?
>

Without long range mind reading equipment, there is really no way.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

Re: [Qemu-devel] How does one find out who ( or what ) is working on each aspect of QEMU ?

[Johannes Schindelin]

Hi,

On Sat, 6 Jun 2009, AGSCalabrese wrote:

> How does one find out who ( or what ) is working on each aspect of QEMU ?

If work has started already, one way to look at it is to call something 
like:

	$ git shortlog -s --since=6.months.ago -- <file>

Of course, that assumes that you already cloned qemu.git.

Ciao,
Dscho