Debian Bug report logs - #572991
qemu-kvm: "Could not open SDL display" when running fullscreen with guest resolution equal to the host resolution

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Bjørn Mork <bjorn@mork.no>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: qemu-kvm: "Could not open SDL display" when running fullscreen with guest resolution equal to the host resolution

Date: Mon, 08 Mar 2010 03:52:13 +0100

Package: qemu-kvm
Version: 0.12.3+dfsg-2
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have a Windows XP guest configured to use the same resolution as the
host, so that it fits nicely on the display when running in fullscreen.
This used to work with KVM-85, but after upgrading to qemu-kvm I get:


 QEMU 0.12.3 monitor - type 'help' for more information
 (qemu) Could not open SDL display

which AFAIK is the expected result if you have a guest with a resolution
*higher* than the host.  This is not the case here.  The guest resolution
matches the host exactly (both are running 1440x900).

Running in windowed mode works, but I really like letting the guest use
the full LCD panel from time to time.


Bjørn


- -- Package-specific info:


selected information from lshal(1):



/proc/cpuinfo:

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Intel(R) Core(TM)2 Duo CPU     U9400  @ 1.40GHz
stepping	: 6
cpu MHz		: 800.000
cache size	: 3072 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm ida tpr_shadow vnmi flexpriority
bogomips	: 2793.33
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 23
model name	: Intel(R) Core(TM)2 Duo CPU     U9400  @ 1.40GHz
stepping	: 6
cpu MHz		: 800.000
cache size	: 3072 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm ida tpr_shadow vnmi flexpriority
bogomips	: 2793.63
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:




- -- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages qemu-kvm depends on:
ii  adduser           3.110                  add and remove users and groups
ii  bridge-utils      1.4-5                  Utilities for configuring the Linu
ii  iproute           20080725-2             networking and traffic control too
ii  libasound2        1.0.22-2               shared library for ALSA applicatio
ii  libbluetooth3     4.60-1                 Library to use the BlueZ Linux Blu
ii  libbrlapi0.5      3.10~r3724-1+lenny1    braille display access via BRLTTY 
ii  libc6             2.10.2-6               Embedded GNU C Library: Shared lib
ii  libcurl3-gnutls   7.18.2-8lenny3         Multi-protocol file transfer libra
ii  libgnutls26       2.8.5-2                the GNU TLS library - runtime libr
ii  libncurses5       5.7+20081213-1         shared libraries for terminal hand
ii  libpci3           1:3.1.7-1              Linux PCI Utilities (shared librar
ii  libpulse0         0.9.21-1               PulseAudio client libraries
ii  libsasl2-2        2.1.22.dfsg1-23+lenny1 Cyrus SASL - authentication abstra
ii  libsdl1.2debian   1.2.13-2               Simple DirectMedia Layer
ii  libuuid1          2.16.2-0               Universally Unique ID library
ii  libvdeplug2       2.2.2-3                Virtual Distributed Ethernet - Plu
ii  libx11-6          2:1.3.3-1              X11 client-side library
ii  python            2.5.2-3                An interactive high-level object-o
ii  zlib1g            1:1.2.3.3.dfsg-12      compression library - runtime

Versions of packages qemu-kvm recommends:
ii  linux-image-2.6.32-2-amd64 [l 2.6.32-8   Linux 2.6.32 for 64-bit PCs
ii  linux-image-2.6.32-3-amd64 [l 2.6.32-9   Linux 2.6.32 for 64-bit PCs

Versions of packages qemu-kvm suggests:
pn  debootstrap                   <none>     (no description available)
ii  hal                           0.5.14-2   Hardware Abstraction Layer
pn  samba                         <none>     (no description available)
ii  vde2                          2.2.2-3    Virtual Distributed Ethernet

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkuUZlkACgkQ10rqkowbIsngBwCfZBzau495ixVTPPMsbvzCVEXA
92YAnRubFPerA9EdZQiPaVvMdhqCBeNJ
=GVOD
-----END PGP SIGNATURE-----

Message #10 received at 572991@bugs.debian.org (full text, mbox, reply):

From: Bjørn Mork <bjorn@mork.no>

To: 572991@bugs.debian.org

Subject: This looks like a problem with reporting supported modes to the client

Date: Mon, 08 Mar 2010 04:52:31 +0100

I added this bit of debugging to sdl.c
	fprintf(stderr, "Could not open SDL display (%dx%dx%d): %s\n", width, height, bpp, SDL_GetError());
and got

 QEMU 0.12.3 monitor - type 'help' for more information
 (qemu) Could not open SDL display (1280x1024x32): No video mode large enough for 1280x1024

which kind of suprised me because I was pretty sure that the guest was
configured to use 1440x900.  But checking it in windowed mode confirmed:
The *guest* video mode had changed after upgrading the host from kvm-85
to qemu-kvm 0.12.3.  That was unexpected to me at last...

Looking at the list of available modes in the guest showed that there
was no 1440x900 anymore, which probably explains why Windows chose
another one close by.  There were also a number of other expected modes
missing. 

After downgrading to kvm 85+dfsg-4.1 all modes are back in the guest,
and the default is 1440x900 again. Which makes fullscreen work.

Any idea what's changed?  I guess there is some exchange of available
video modes between host and guest, ensuring that the odd native LCD
panel mode show up in the guest?  But why not in qemu-kvm 0.12.3?


Bjørn

Message #15 received at 572991@bugs.debian.org (full text, mbox, reply):

From: Bjørn Mork <bjorn@mork.no>

To: 572991@bugs.debian.org

Subject: Re: This looks like a problem with reporting supported modes to the client

Date: Mon, 08 Mar 2010 05:38:57 +0100

[Message part 1 (text/plain, inline)]

tags 572991 + patch
thanks

Bjørn Mork <bjorn@mork.no> writes:

> Looking at the list of available modes in the guest showed that there
> was no 1440x900 anymore, which probably explains why Windows chose
> another one close by.  There were also a number of other expected modes
> missing. 

Think I got it.  

The modes were once added to KVMs local copy of vgabios:
http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=commitdiff;h=ebfac597cf
but never made it upstream or into QEMU.  So when you included a copy of
the vgabios source from QEMU in the Debian qemu-kvm package, you
removed these modes.

I'm attaching a patch to be applied on top of
debian/patches/vgabios-0.12.3.diff
which fixes this problem for me.

See also https://bugzilla.redhat.com/show_bug.cgi?id=501545


Bjørn

[vgabios-fix.diff (text/x-diff, inline)]

--- a/roms/vgabios/vbetables-gen.c	2010-03-08 04:16:02.000000000 +0100
+++ b/roms/vgabios/vbetables-gen.c	2010-02-26 03:34:00.000000000 +0100
@@ -2,7 +2,7 @@
 #include <stdlib.h>
 #include <stdio.h>
 
-#define VBE_DISPI_TOTAL_VIDEO_MEMORY_MB 8
+#define VBE_DISPI_TOTAL_VIDEO_MEMORY_MB 16
 
 typedef struct {
     int width;
@@ -55,6 +55,30 @@
 { 1152, 864, 16                      , 0x14a},
 { 1152, 864, 24                      , 0x14b},
 { 1152, 864, 32                      , 0x14c},
+{ 1280, 768, 16                      , 0x175},
+{ 1280, 768, 24                      , 0x176},
+{ 1280, 768, 32                      , 0x177},
+{ 1280, 800, 16                      , 0x178},
+{ 1280, 800, 24                      , 0x179},
+{ 1280, 800, 32                      , 0x17a},
+{ 1280, 960, 16                      , 0x17b},
+{ 1280, 960, 24                      , 0x17c},
+{ 1280, 960, 32                      , 0x17d},
+{ 1440, 900, 16                      , 0x17e},
+{ 1440, 900, 24                      , 0x17f},
+{ 1440, 900, 32                      , 0x180},
+{ 1400, 1050, 16                     , 0x181},
+{ 1400, 1050, 24                     , 0x182},
+{ 1400, 1050, 32                     , 0x183},
+{ 1680, 1050, 16                     , 0x184},
+{ 1680, 1050, 24                     , 0x185},
+{ 1680, 1050, 32                     , 0x186},
+{ 1920, 1200, 16                     , 0x187},
+{ 1920, 1200, 24                     , 0x188},
+{ 1920, 1200, 32                     , 0x189},
+{ 2560, 1600, 16                     , 0x18a},
+{ 2560, 1600, 24                     , 0x18b},
+{ 2560, 1600, 32                     , 0x18c},
 { 0, },
 };
 

Message #22 received at 572991@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: Bjørn Mork <bjorn@mork.no>, 572991@bugs.debian.org

Subject: Re: Bug#572991: This looks like a problem with reporting supported modes to the client

Date: Mon, 08 Mar 2010 12:09:13 +0300

Bjørn Mork wrote:
> 
>> Looking at the list of available modes in the guest showed that there
>> was no 1440x900 anymore, which probably explains why Windows chose
>> another one close by.  There were also a number of other expected modes
>> missing. 
> 
> Think I got it.  
> 
> The modes were once added to KVMs local copy of vgabios:
> http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=commitdiff;h=ebfac597cf
> but never made it upstream or into QEMU.  So when you included a copy of
> the vgabios source from QEMU in the Debian qemu-kvm package, you
> removed these modes.
> 
> I'm attaching a patch to be applied on top of
> debian/patches/vgabios-0.12.3.diff
> which fixes this problem for me.

Thank you very much Bjørn for the excellent bugreport.
All bios code were dropped from qemu-kvm in 0.12 for some reason
(or without, I dunno), and you're right all the local modifications,
useful or not, were lost.

I too noticed that the list of video modes available is quite a bit
shorter than it used to be, but at that time I were dealing with
another bug and didn't pay enough attention to that fact, and it
were "successfully" forgotten.  But without your findings it'd be
much more difficult to find and fix things.

I'm adding the thing to the Debian qemu-kvm git repository now, to
be fixed in the next release.

By the way, you can just use vgabios from kvm-88 - there were no
changes (except of missing bugfixes like you discovered) since that...

Thank you!

/mjt

Message #27 received at 572991@bugs.debian.org (full text, mbox, reply):

From: Bjørn Mork <bjorn@mork.no>

To: Michael Tokarev <mjt@tls.msk.ru>

Cc: 572991@bugs.debian.org

Subject: Re: Bug#572991: This looks like a problem with reporting supported modes to the client

Date: Mon, 08 Mar 2010 12:51:42 +0100

Michael Tokarev <mjt@tls.msk.ru> writes:
> Bjørn Mork wrote:
>> 
>> The modes were once added to KVMs local copy of vgabios:
>> http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=commitdiff;h=ebfac597cf
>> but never made it upstream or into QEMU. 

I have to correct myself here.  The patch has made it upstream
http://cvs.savannah.gnu.org/viewvc/vgabios/vbetables-gen.c?root=vgabios&r1=1.4&r2=1.5
and is part of the latest release.

> I too noticed that the list of video modes available is quite a bit
> shorter than it used to be, but at that time I were dealing with
> another bug and didn't pay enough attention to that fact, and it
> were "successfully" forgotten.  But without your findings it'd be
> much more difficult to find and fix things.
>
> I'm adding the thing to the Debian qemu-kvm git repository now, to
> be fixed in the next release.

I'm afraid my primitive approach is not the proper way to fix it.
qemu-kvm should depend on vgabios and just install symlinks as qemu
does:

 bjorn@nemi:~$ ls -la /usr/share/qemu/vgabios*
 lrwxrwxrwx 1 root root 22 2010-01-10 20:31 /usr/share/qemu/vgabios.bin -> ../vgabios/vgabios.bin
 lrwxrwxrwx 1 root root 29 2010-01-10 20:31 /usr/share/qemu/vgabios-cirrus.bin -> ../vgabios/vgabios.cirrus.bin

Which is bug #489442.  Fixing that one will close both bugs.

BTW, I think I'm going to propose some variant of my debugging patch to
qemu upstream.  The "Could not open SDL display" is rather useless as a
fatal error message, given how easy it is to trigger this error with a
simple guest (mis)onfiguration.


Bjørn

Message #32 received at 572991@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: Bjørn Mork <bjorn@mork.no>, 572991@bugs.debian.org

Subject: Re: Bug#572991: This looks like a problem with reporting supported modes to the client

Date: Mon, 08 Mar 2010 16:46:43 +0300

tags 572991 + pending
thanks

Bjørn Mork wrote:
> Michael Tokarev <mjt@tls.msk.ru> writes:
[]
>> I too noticed that the list of video modes available is quite a bit
>> shorter than it used to be, but at that time I were dealing with
>> another bug and didn't pay enough attention to that fact, and it
>> were "successfully" forgotten.  But without your findings it'd be
>> much more difficult to find and fix things.
>>
>> I'm adding the thing to the Debian qemu-kvm git repository now, to
>> be fixed in the next release.
> 
> I'm afraid my primitive approach is not the proper way to fix it.
> qemu-kvm should depend on vgabios and just install symlinks as qemu
> does:
> 
>  bjorn@nemi:~$ ls -la /usr/share/qemu/vgabios*
>  lrwxrwxrwx 1 root root 22 2010-01-10 20:31 /usr/share/qemu/vgabios.bin -> ../vgabios/vgabios.bin
>  lrwxrwxrwx 1 root root 29 2010-01-10 20:31 /usr/share/qemu/vgabios-cirrus.bin -> ../vgabios/vgabios.cirrus.bin
> 
> Which is bug #489442.  Fixing that one will close both bugs.

No, that wont work either.  #489442 isn't fixed by purpose:
current qemu-kvm wont work with latest vgabios v 0.6c because
some more changes are required in qemu to support it.  I'm
not sure qemu will work with 0.6c correctly in all cases
either.

But this bug -- #572991 -- is actually due to my lack of attention.

qemu upstream includes ROM sources in roms/{vga,sea}bios, but in
qemu-kvm-0.12 the directories were both empty for some reason.
So I concluded that kvm now comes without any bios sources, and
took both bioses from qemu upstrem.  But it turned out that the
vga bios is still at the same place it was in kvm-88 and previous
releases, namely in kvm/vgabios.

So proper(*) fix to this bug is to drop vgabios patch and use vgabios
from kvm/vgabios/ as it used to be in 0.11 and before.

(*) by "proper" here I mean something appropriate for this release
anyway (0.12), -- having in mind the fact that it wont work with
current vgabios as shipped in Debian.  It's upstream decision to
bundle bios into the tarball, and it comes not without a reason,
regardless if we like it or not.  It shouldn't be difficult to
fix, but it has to be done anyway.

> BTW, I think I'm going to propose some variant of my debugging patch to
> qemu upstream.  The "Could not open SDL display" is rather useless as a
> fatal error message, given how easy it is to trigger this error with a
> simple guest (mis)onfiguration.

There's more to the point than that.  Error handling/reporting is not in
a best shape in qemu, but it is being worked on slowly.  Just a few days
ago there was a series of patches posted to qemu-devel@ to add I/O error
reporting to various places.  For example, before that, qemu-img had
"nice" error reporting like "Unable to format disk image".  Now it can
do more, like "Unable to format disk image: Dermission denied".  There
was a patch to temporarily fix that in ubuntu kvm package, but I didn't
take it to Debian package because, while it fixes most common cases,
there are many other cases (many other sources of errors) which it does
not cover correctly, and the just-posted upstream patch series fixes it
for all.  That to say, -- error reporting is something that should
receive good thinking and planning, simplistic "fixes" does not work
there.  At least in our qemu/kvm case.  But it is a good idea to report
the bad examples anyway, so at least the upstream will be aware of
the problem... ;)

Thank you!

/mjt

Message #39 received at 572991-close@bugs.debian.org (full text, mbox, reply):

From: Jan Lübbe <jluebbe@debian.org>

To: 572991-close@bugs.debian.org

Subject: Bug#572991: fixed in qemu-kvm 0.12.3+dfsg-4

Date: Thu, 11 Mar 2010 17:31:46 +0000

Source: qemu-kvm
Source-Version: 0.12.3+dfsg-4

We believe that the bug you reported is fixed in the latest version of
qemu-kvm, which is due to be installed in the Debian FTP archive:

kvm_0.12.3+dfsg-4_i386.deb
  to main/q/qemu-kvm/kvm_0.12.3+dfsg-4_i386.deb
qemu-kvm-dbg_0.12.3+dfsg-4_i386.deb
  to main/q/qemu-kvm/qemu-kvm-dbg_0.12.3+dfsg-4_i386.deb
qemu-kvm_0.12.3+dfsg-4.diff.gz
  to main/q/qemu-kvm/qemu-kvm_0.12.3+dfsg-4.diff.gz
qemu-kvm_0.12.3+dfsg-4.dsc
  to main/q/qemu-kvm/qemu-kvm_0.12.3+dfsg-4.dsc
qemu-kvm_0.12.3+dfsg-4_i386.deb
  to main/q/qemu-kvm/qemu-kvm_0.12.3+dfsg-4_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 572991@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jan Lübbe <jluebbe@debian.org> (supplier of updated qemu-kvm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Thu, 11 Mar 2010 17:15:31 +0100
Source: qemu-kvm
Binary: qemu-kvm qemu-kvm-dbg kvm
Architecture: source i386
Version: 0.12.3+dfsg-4
Distribution: unstable
Urgency: low
Maintainer: Jan Lübbe <jluebbe@debian.org>
Changed-By: Jan Lübbe <jluebbe@debian.org>
Description: 
 kvm        - dummy transitional pacakge from kvm to qemu-kvm
 qemu-kvm   - Full virtualization on x86 hardware
 qemu-kvm-dbg - Debugging info for qemu-kvm
Closes: 572924 572930 572943 572991 573280 573439
Changes: 
 qemu-kvm (0.12.3+dfsg-4) unstable; urgency=low
 .
   [ Michael Tokarev ]
   * added patch from upstream, ff5414990645653bf43bf64adfc1ca77ffb9edcb,
     revert-sdlaudio:-make-it-suck-less.diff (closes: #572943)
     Note that this is only relevant to sdl audio (QEMU_AUDIO_DRV=sdl)
   * don't report system dmi information in the bugreports anymore, it
     serves almost no useful purpose these days, much less than previously.
     VMX/SVM is either enabled or not, and if it is not enabled, kvm module
     will warn user about this fact in dmesg during load.
     (closes: #572930, #572924)
   * switch back to vgabios as shipped in upstream tarball in kvm/vgabios.
     I overlooked it, thinking it went away together with seabios as
     both roms/seabios and roms/vgabios are empty in upstream, but vgabios
     has never been removed.  So we're back at using it.
     Big thanks to Bjørn Mork for the hard work he did finding bugs in the
     version we shipped in 0.12.3+dfsg-2, which is wrong and the work
     should have not been required.  But it helped finding all the pieces
     finally. (closes: #572991)
   * build-depend on linux-libc-dev >= 2.6.32, to enable KSM (Kernel
     Samepage Merge) and to ensure we'll not have spurious preadv()
     problems
   * build-depend on libaio-dev to compile in aio support
     (which does not do any harm if not explicitly enabled)
   * fix cleanups of old conffiles in preinst. (closes: #573280)
   * include 573439-fail-to-set-hdd-serial-number.diff - a fix by
     Kouichi ONO broken hdd serial number support (closes: #573439)
Checksums-Sha1: 
 b0f5b3c846c168fc2c6e00c507c787cb1e6d5ed4 1613 qemu-kvm_0.12.3+dfsg-4.dsc
 9531db1ec2735df2fe442f6cb1ad66fc71277b8d 274694 qemu-kvm_0.12.3+dfsg-4.diff.gz
 df61b26daf80685c006daacaa1e2b3c2927680c3 1481226 qemu-kvm_0.12.3+dfsg-4_i386.deb
 aa14d254b540cb89d7ada6817987496e3c5d7ed2 2772852 qemu-kvm-dbg_0.12.3+dfsg-4_i386.deb
 16f6abd8276babf1fb435fb04486daa4cf5f16f8 6700 kvm_0.12.3+dfsg-4_i386.deb
Checksums-Sha256: 
 1b296482342715876e0212ceaf9fa48d3f63083b59d860b596f7f1a4ed139061 1613 qemu-kvm_0.12.3+dfsg-4.dsc
 2b3c3cff5bb7329b0310e14bf8d9451fa597f438cf26f2f8c3fccae34c4f574f 274694 qemu-kvm_0.12.3+dfsg-4.diff.gz
 39f29f97f96a0628263a1ff3e5cb3a9387fa161f226c60d52a83b0c734f99c26 1481226 qemu-kvm_0.12.3+dfsg-4_i386.deb
 232ba4787c12af721e48e5e935510689b4690717bd4a1b87f285116beb3e2116 2772852 qemu-kvm-dbg_0.12.3+dfsg-4_i386.deb
 4d1751bb116a179bcf42cdaa9bba0a1454f16d754b09cf17025f014bf386221e 6700 kvm_0.12.3+dfsg-4_i386.deb
Files: 
 d76149f45a72681bf28ba97d5dfddf64 1613 misc optional qemu-kvm_0.12.3+dfsg-4.dsc
 06f9fe7fff1e70b57704c2e9bed291e9 274694 misc optional qemu-kvm_0.12.3+dfsg-4.diff.gz
 21d3a30072ad958a60c68533f6f50e71 1481226 misc optional qemu-kvm_0.12.3+dfsg-4_i386.deb
 748e418c4e321ab130ca442de1f8d8d1 2772852 debug extra qemu-kvm-dbg_0.12.3+dfsg-4_i386.deb
 ff654fceb140ebf244574040d42c0c49 6700 oldlibs optional kvm_0.12.3+dfsg-4_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkuZIxIACgkQioOL5NhIDy5tDQCgudPU8FlKpjET3PKwJYwh3p3D
RsgAnjrql0WSdM1XePszOmhFFBhDOZG4
=a8vn
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.