From: Michael Goldish <mgoldish@redhat.com>
To: Eduardo Habkost <ehabkost@raisama.net>
Cc: kvm@vger.kernel.org, Ryan Harper <ryanh@us.ibm.com>
Subject: Re: kvm-autotest: weird memory error during stepmaker test
Date: Fri, 3 Apr 2009 17:33:13 -0400 (EDT) [thread overview]
Message-ID: <1895115192.3950931238794393118.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <479395147.3950621238794089916.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
----- "Eduardo Habkost" <ehabkost@raisama.net> wrote:
> Excerpts from Ryan Harper's message of Qua Abr 01 12:55:58 -0300
> 2009:
> > Wondering if anyone else using kvm-autotest stepmaker has ever seen
> this
> > error:
> >
> > Traceback (most recent call last):
> > File
> >
> "/home/rharper/work/git/build/kvm-autotest/client/tests/kvm_runtest_2/stepmaker.
> > py", line 146, in update
> > self.set_image_from_file(self.screendump_filename)
> > File
> >
> "/home/rharper/work/git/build/kvm-autotest/client/tests/kvm_runtest_2/stepeditor
> > .py", line 499, in set_image_from_file
> > self.set_image(w, h, data)
> > File
> >
> "/home/rharper/work/git/build/kvm-autotest/client/tests/kvm_runtest_2/stepeditor
> > .py", line 485, in set_image
> > w, h, w*3))
> > MemoryError
>
> I've seen this error twice today, while trying to create a step file
> to
> install a Windows 2008 R2 64-bit guest (the Win2008-64 step file
> available on the git repository doesn't work for me). This happened
> when
> the guest was being rebooted by the windows installer. The contents
> of
> the screen dump file are this:
>
> $ cat
> /home/ehabkost/autotest/kvm-autotest/client/results/default/kvm_runtest_2.Win2008.64.install/debug/scrdump.ppm
> P6
> 0 0
> 255
> $
>
> And the 0x0 pixmap really makes gdk panic:
>
> >>> (w, h, data) =
> ppm_utils.image_read_from_ppm_file('/home/ehabkost/autotest/kvm-autotest/client/results/default/kvm_runtest_2.Win2008.64.install/debug/scrdump.ppm')
> >>> w,h,data
> (0, 0, '')
> >>> gtk.gdk.pixbuf_new_from_data(data, gtk.gdk.COLORSPACE_RGB, False,
> 8, w, h, w*3)
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> MemoryError
> >>>
This is very useful information. I've seen qemu/kvm produce 0x0 screendumps before,
but it's never happened to me while working with stepmaker.
A reasonable solution would be to make sure a screendump is OK before feeding it
to gdk. I'll try to commit this ASAP so it doesn't bother people any more.
Thanks,
Michael
next parent reply other threads:[~2009-04-03 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <479395147.3950621238794089916.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-04-03 21:33 ` Michael Goldish [this message]
[not found] <1649348235.3722371238655648751.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-04-02 7:07 ` kvm-autotest: weird memory error during stepmaker test Michael Goldish
2009-04-01 15:55 Ryan Harper
2009-04-03 20:37 ` Eduardo Habkost
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=1895115192.3950931238794393118.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com \
--to=mgoldish@redhat.com \
--cc=ehabkost@raisama.net \
--cc=kvm@vger.kernel.org \
--cc=ryanh@us.ibm.com \
/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).