Re: [Qemu-devel] Norton Ghost crashes with page fault for me too.

[<jeebs@yango.us>]

"Henrik Nordstrom"

>> All us users can do is make a report and sit back and wait to see if
>> anything happens.  Sometimes it can be a long wait.
>
> Or you could go the open-source approach and hire a developer (there is

That's more than a little extreme.

Frankly, it'd be a heck of a lot cheaper to buy and use vmware.... Oh 
wait... I *do* use vmware.

I'm not silly enough to actually depend on qemu.  Qemu is an opensource 
project that I hope I will be able to use someday.  Until that time, I'm 
helping the development as best I can.

> plenty on the market if one cares to look) to fix the problems you may 
> have. Certainly several (but perhaps not all) of the quirks you mentioned 
> doesn't even require any qemu specifik knowledge.

They would require at least some knowledge.  Some of them more than a little 
amount.

> Only relying on the existing qemu developers pride may work in some cases, 
> but it should be taken for what it is, not a warranty that things do get 
> fixed in the line you want or when.

No, I know there's no warranty.

But it gets more than a little darn frustrating when you are enthused about 
the project, you try to help the devlopers and project by deliberately doing 
the testing to find bugs and problems, you report the bugs and problems..... 
And nothing happens.

Not an acknowledgement.  Not a fix.  Nothing.

Not that week.  Not that month.  Not the next month.  Basically, the effort 
you deliberately put into finding bugs and reporting the bugs has 
disappeared.

I don't expect bugs to get fixed in 36 hours.  No, of course not.  Or even 
in a week or so.  But it would be nice if the bug reports didn't just 
disappear into the void.



As I said in my other message, Savanah has facilities for helping users and 
developers alike.

Ways to report bugs (so they don't get lost)  (Really... Do you know what 
bugs still exist in qemu???  No.  Nobody does.  Because they get forgotten 
about in a few days.  Or the interested parties may miss the messages due to 
spam filtering.)

Ways for bugs to be confirmed.

Ways for developers to submit patches (so they don't get lost in spam 
filtering.)

And so on.


Qem is outgrowing the 'mailing list' approach.