Bug#895046: RM: vgabios -- ROM; an old not-used-anymore package

Package: ftp.debian.org Severity: normal This package was used by old qemu/kvm. Now qemu, for a very long time now (several debian releases) uses vgabios from seabios package, so that vgabios isn't needed anymore. Thanks, /mjt

Bug#894852: Here's a URL to that core dump of qemu's segfault

05.04.2018 07:55, Kingsley G. Morse Jr. wrote: > It's at > > http://loaner.com/core_of_qemu_SIGSEGV.1.gz > > You should be able to decompress it with a command > like: > > $ gunzip kingsleys_stupendous_core_dump.gz Thank you very much for your attempts. But I *think* this bug has been

Bug#893843: please enable nbd applet

Package: busybox Version: 1:1.27.2-2 Severity: wishlist Please enable NBD applet for regular deb configuration. It costs almost nothing but it is useful for our environment for booting over network. Thanks! /mjt

Bug#890718: qemu-system: Please do not list all architectures as dependencies

18.02.2018 01:27, Krylov Michael wrote: > Package: qemu-system > Version: 1:2.1+dfsg-12+deb8u6 > Severity: minor > > Hello! > > Right now qemu-system lists all the architectures qemu supports as > Depends. This results in installation of a dozen of emulators where most > people only need one. >

Bug#813658: Further progress?

10.01.2018 05:03, Hillel Lubman wrote: > Now Debian already ships spice 0.14.0, so with this dependency issue out of > the way, what else is needed > to enable virgl support in qemu? [...] Can someone please tell me what _is_ virglrenderer? Is it useful on its own with, eg, spice, and/or libvirt

Bug#882296: qemu: please consider security support for virtio GPU

On 21.11.2017 16:45, gr...@airmail.cc wrote: > > https://security-tracker.debian.org/tracker/CVE-2017-9060 > https://security-tracker.debian.org/tracker/CVE-2017-5578 > > The notes at the bottom assume virtio gpu doesn't need security patches > because "1:2.8+dfsg-2 upload reverts enable virtio

Bug#882296: qemu: please consider security support for virtio GPU

Control: tag -1 moreinfo unreproducible On 21.11.2017 10:57, gr...@airmail.cc wrote: > Package: qemu > Version: 1:2.8+dfsg-6 > Severity: wishlist > > security support for Virtio GPU is marked as unimportant because 2.8+dfsg-6 > doesn't have virgl and opengl support. Virtio GPU can be used in 2d

Bug#881263: IPXE size change will break qemu cross release migrations and save/restore through upgrades

09.11.2017 16:47, Christian Ehrhardt wrote: > Package: qemu > Version: 1:2.10.0+dfsg-2 > Severity: important > > TL;DR: > - rom size change (coming on next ipxe merge for Debian) break migrations > - we need a way to allow incoming migrations to work but still be able > to update roms > - I sugges

Bug#881527: qemu: FTCBFS due to broken cross build depend on glusterfs-common

Control: tag -1 + moreinfo 12.11.2017 22:14, Héctor Orón Martínez wrote: > Source: qemu > Version: 1:2.10.0+dfsg-2 > Severity: normal > > Dear Maintainer, > > Your package fails to satisfy cross build dependency installability due to > glusterfs-common not being installable via multiarch: >

Bug#881290: qemu-kvm: Passthrough of SAS2008-based HBA card fails on E3-1225v3 due to failed DMA mapping (-14)

Control: severity -1 minor 09.11.2017 21:10, Johannes Falke wrote: > Package: qemu-kvm > Version: 1:2.8+dfsg-6+deb9u3 > Severity: important > > Dear Maintainer, > > there is a bug preventing many people with my combination of hardware > from using PCI passthrough. I am not actually sure whether

Bug#878087: qemu-system-x86: xmodmap + qemu, keyboard settings is ignored

29.10.2017 18:54, Michael Gold wrote: [] > CPU type/count, etc. Is any workaround for this known? And does the -k > option have any effect now? My preference is to have it work as before; > but if it will have no effect, it should raise an error or be removed. For all modern UI types (introduce

Bug#879193: unable to exit mouse grab, segfaults

Control: tag -1 + unreproducible moreinfo 20.10.2017 12:44, Stéphane Glondu wrote: > Package: qemu > Version: 1:2.10.0+dfsg-2 > Severity: important > > Dear maintainer, > > Since this new version of qemu, I am no longer able to exit mouse > grab. With an i386 guest running stretch on an amd64 ho

Bug#685134: Bug#684909: Bug#685134: [s390-tools] please add patch from qemu

19.10.2017 15:36, Christian Ehrhardt wrote: > On Thu, Oct 19, 2017 at 2:01 PM, Philipp Kern > wrote: > On 02/03/2016 09:27 AM, Viktor Mihajlovski wrote: > > On 02.02.2016 01:01, Dimitri John Ledkov wrote: > >> On Fri, 17 Aug 2012 11:21:04 +0200 bastien ROUCARIE

Bug#870025: Broken display updating with SDL2

15.10.2017 10:35, Jindřich Makovička wrote: > Hi, > > attaching a few more fixes for the most annoying regressions I encountered > with the SDL2 UI. Hmm. Have you tried discussing this upstream? It looks like you've testcases and good expirence in that area, sending this stuff to qemu-de...@no

Bug#878087: qemu-system-x86: xmodmap + qemu, keyboard settings is ignored

09.10.2017 20:34, Antonio wrote: > Package: qemu-system-x86 > Version: 1:2.10.0+dfsg-2 > > Dear Maintainer, > > if you modify some keys with xmodmap (eg: xmodmap -e "keycode 91=Delete" -e > "keycode 90=Insert" -e "keycode 79=Home" -e "keycode 87=End" -e "keycode > 81=Prior" -e "keycode 89=Next"

Bug#871648: qemu-system-x86: /usr/bin/qemu-system-i386 eats slowly but surely all the Dom0 memory

05.10.2017 06:53, Kuba Dexter wrote: > This bug can be can be 'disarmed' by using below settings (or I shuld say > comment this settings): This bug has been fixed by the last security update of qemu. Thanks, /mjt

Bug#869173: exec: oob access during dma operation

Version: 1:2.8+dfsg-7 This has been fixed in 2.8+dfsg-7.

Bug#871702: Latest Stretch qemu-system-i386 process balloons in Xen Dom0 RAM, crashes DomU

24.09.2017 16:56, Thomas Keppler wrote: > Hi! > > I can confirm this bug and indeed it happens with "qemu-system-x86_64" on > 1:2.8+dfsg-6+deb9u2, too. > > However, it does *not* happen using 1:2.8+dfsg-6+deb9u1! I have not tried it > for a longer time but the memory consumption is a lot better

Bug#867978: /usr/bin/qemu-system-x86_64: virtio-net with vhost is broken with legacy interrupts

On Mon, 7 Aug 2017 21:11:27 +0200 (CEST) Stefan Fritsch wrote: > Hi, > > is it ok if I upload an NMU with the attached patch to > stable-proposed-updates? This is not how to stable-p-u works, you also need an ACK from the release managers. And once ACK'ed and accepted, it will be in the next p

Bug#871648: qemu-system-x86: /usr/bin/qemu-system-i386 eats slowly but surely all the Dom0 memory

On Thu, 31 Aug 2017 12:11:00 + astian wrote: > Control: found -1 1:2.8+dfsg-7 > Control: tags -1 + patch fixed-upstream > > Hi, > > After staring at GDB for ungodly spans of time I managed to track down this > bug, ipso facto discovering that it was already fixed upstream quite some time > a

Bug#871702: Latest Stretch qemu-system-i386 process balloons in Xen Dom0 RAM, crashes DomU

On Thu, 10 Aug 2017 14:45:56 -0400 "Michael J. Redd" wrote: > Package: qemu-system-x86Version: 1:2.8+dfsg-6+deb9u2 > Problem:==Latest Stretch `qemu-system-i386` process consumes the > majority of Xen Dom0's RAM, ultimately crashes DomU. Does this happen with version 1:2.8+dfsg-6+deb9u1 too? D

Bug#871648: qemu-system-x86: /usr/bin/qemu-system-i386 eats slowly but surely all the Dom0 memory

Control: tag -1 + moreinfo unreproducible 10.08.2017 15:16, Thierry JAOUEN wrote: > Package: qemu-system-x86 > Version: 1:2.8+dfsg-6+deb9u2 > Severity: normal > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situ

Bug#864718: fsdev emulation security_model=none not handling mode 000

I'm forwarding this upstream. It looks like the same issue is present in 2.10-tobe. 13.06.2017 16:01, Sjoerd Simons wrote: > Package: qemu-system > Version: 1:2.8+dfsg-6 > Severity: normal > > Hey, > > For $reasons i'm exposing /boot over a filesystem share with the host system, > fsdev is setup

Bug#869807: qemu: [regression] unknown CPU feature __kvm_hv_spinlocks after upgrade to +deb9u1

05.08.2017 15:02, Christian Seiler wrote: >>> xhci-guard-xhci_kick_epctx-against-recursive-calls-CVE-2017-9375.patch >> >> What's the complete qemu command line? > > It's quite long (generated from libvirt), I posted that in the initial > bug report: > > https://bugs.debian.org/cgi-bin/bugreport.

Bug#869807: qemu: [regression] unknown CPU feature __kvm_hv_spinlocks after upgrade to +deb9u1

05.08.2017 11:48, Christian Seiler wrote: > xhci-guard-xhci_kick_epctx-against-recursive-calls-CVE-2017-9375.patch What's the complete qemu command line? Does it include nec-xhci? /mjt

Bug#869807: qemu: [regression] unknown CPU feature __kvm_hv_spinlocks after upgrade to +deb9u1

26.07.2017 18:49, Christian Seiler wrote: > Package: qemu-system-x86 > Version: 1:2.8+dfsg-6+deb9u1 > Severity: important > X-Debbugs-Cc: secur...@debian.org > > Dear maintainers, dear security team, > > after performing the security upgrade to 1:2.8+dfsg-6+deb9u1 a virtual > machine (managed via

Bug#870025: qemu: Please switch to SDL2

29.07.2017 01:48, Manuel A. Fernandez Montecelo wrote: > Package: qemu-system-x86 > Version: 1:2.8+dfsg-6 > Severity: wishlist > > Hi! > > According to [1], it seems that since version 2.4 in 2015 this project > supports > both SDL1.2 and SDL2, and since the recent 2.10 [2] it prefers SDL2 if bo

Bug#870244: /usr/bin/qemu-system-x86_64: Assertion `!epctx->kick_active' failed.

Control: severity -1 normal Control: merge 869945 -1 31.07.2017 11:45, Pieter-Jan Crommen wrote: > Package: qemu-system-x86 > Version: 1:2.8+dfsg-6+deb9u1 > Severity: high > File: /usr/bin/qemu-system-x86_64 This is #869945, merging as such. Thanks, /mjt

Bug#869945: all kvm guests crash during startup

Control: tag -1 + confirmed Control: retitle -1 all qemu guests with nec-usb-xhci crash during startup (assertion falure) 28.07.2017 00:42, Ulrich Baum wrote: > Package: qemu-system-x86 > Version: 1:2.8+dfsg-6+deb9u1 > > When I try to start any kvm guest via virsh start , the guest > crashes dur

Bug#868718: qemu: Qemu fails to run on Stretch, due to missing libraries

18.07.2017 08:46, Michael Tokarev wrote: >> Qemu is not running on my Stretch machine, due to missing libraries. I'm >> going >> to build from source and see if that fixes it. >> >> ryan@t420:~$ qemu-system-i386 >> qemu-system-i386: error while loadin

Bug#868718: qemu: Qemu fails to run on Stretch, due to missing libraries

Control: tag -1 + moreinfo unreproducible 18.07.2017 01:54, Ryan Thoryk wrote: > Package: qemu > Version: 1:2.8+dfsg-6 > Severity: important > > Dear Maintainer, > > Qemu is not running on my Stretch machine, due to missing libraries. I'm > going > to build from source and see if that fixes it

Bug#864219: qemu: CVE-2017-9375: usb: xhci infinite recursive call via xhci_kick_ep

On Mon, 05 Jun 2017 13:45:53 +0200 Salvatore Bonaccorso wrote: > Source: qemu > Version: 1:2.8+dfsg-6 > Severity: normal > Tags: patch security upstream fixed-upstream > > Hi, > > the following vulnerability was published for qemu. > > CVE-2017-9375[0]: > usb: xhci infinite recursive call via

Bug#868124: please include vmxnet3 rom too

Package: ipxe-qemu Version: 1.0.0+git-20161027.b991c67-1 Severity: wishlist Please include vmxnet3 rom for qemu, since qemu-2.8 it can netboot from vmware vmxnet3 adaptor too.

Bug#842690: Please overthink the packaging layout

Just a small comment without trying to understand what's going on.. 28.04.2017 20:25, dann frazier wrote: [] > For 32-bit ARM, I propose we use: > /usr/share/AAVMF/AAVMF32_{CODE,VARS}.fd If it's QEMU-foo, why can't we drop things directly to /usr/share/qemu/ ? Thanks, /mjt

Bug#860715: [debian/qemu_2.8+dfsg-4] Hunk #1 FAILED at 3135.

26.04.2017 14:43, jean-christophe manciot wrote: > @christian.ehrha...@canonical.com > Thanks for keeping that thread alive. > There is some confusion indeed due partly to the fact that gbp does not > appear to be widely used in your community. I think t

Bug#860715: [debian/qemu_2.8+dfsg-4] Hunk #1 FAILED at 3135.

26.04.2017 11:44, jean-christophe manciot wrote: > As explained in this debian resource > , *gbp > buildpackage* is the modern way to build > packages from git repositories (gbp= git-buildpackage). > You will have to use it some da

Bug#860715: [debian/qemu_2.8+dfsg-4] Hunk #1 FAILED at 3135.

26.04.2017 11:37, jean-christophe manciot wrote: > Have you even tried to build qemu with gbp? I think I didn't, at least I don't remember I tried. Regular dpkg-buildpackage works just fine for me. Thanks, /mjt

Bug#696289: Cannot use virtfs with mount_tag=/dev/root

Control: tag -1 + patch Control: forwarded -1 https://lists.nongnu.org/archive/html/qemu-devel/2017-04/msg04196.html I just re-submitted the old change again, aiming to apply it finally. Thanks, /mjt

Bug#851694: qemu: Formatting USB disks to EXT4 with nec-xhci USB controller fails with Buffer I/O fails

24.04.2017 19:26, anonym wrote: [] >> I tried to reproduce this, but can not. What's needed to reproduce it? > > Sorry for the complicated reproducer, but here goes: > > 1. Download the latest Tails ISO image from: > http://dl.amnesia.boum.org/tails/stable/ > 2. Boot the Tails ISO image in a VM

Bug#851694: qemu: Formatting USB disks to EXT4 with nec-xhci USB controller fails with Buffer I/O fails

Control: tag -1 + moreinfo On Tue, 17 Jan 2017 18:19:00 + anonym wrote: > Package: qemu > Version: 1:2.8+dfsg-1 > Severity: normal > Tags: patch > User: tails-...@boum.org > Usertags: test-suite, virt-guest > > Dear Maintainer, > > It seems the fix of CVE-2016-8576 (Debian bug #840343) intr

Bug#860840: git-bisect: fatal: BUG: attempt to snprintf into too-small buffer with some locales

Package: git Version: 1:2.11.0-2 Severity: important Tags: upstream l10n When doing any git bisect with current git and LANG=ru_RU.UTF8, it fails with 100% cases with the following message: fatal: BUG: attempt to snprintf into too-small buffer This is because bisect.c:bisect_next_all() contains

Bug#860822: keyboard does not work in guest under wayland

Package: qemu-system-x86 Version: 1:2.8+dfsg-3 Severity: important Tags: upstream patch current qemu does not work correctly under wayland, it misreports keypresses. For example, arrow keys are not reported to guest at all, right Ctrl alone sends Esc-[-6-~ sequence, and other weird things. Upstre

Bug#859599: unblock: qemu/1:2.8+dfsg-4

19.04.2017 14:31, Michael Tokarev пишет: > Control: tag -1 - moreinfo > > 18.04.2017 11:06, Niels Thykier wrote: > >>> unblock qemu/1:2.8+dfsg-4 > >> Hi Michael, >> >> Please go ahead with this change set and let us know once it has been >>

Bug#859599: unblock: qemu/1:2.8+dfsg-4

Control: tag -1 - moreinfo 18.04.2017 11:06, Niels Thykier wrote: >> unblock qemu/1:2.8+dfsg-4 > Hi Michael, > > Please go ahead with this change set and let us know once it has been > built on all relevant release architectures in unstable. Thank you very much! It wasn't an easy job on your

Bug#860715: [debian/qemu_2.8+dfsg-4] Hunk #1 FAILED at 3135.

Control: tag -1 + unreproducible moreinfo 19.04.2017 11:53, jean-christophe manciot wrote: > Package: qemu > Version: 2.8+dfsg-4 > sources: https://anonscm.debian.org/git/pkg-qemu/qemu.git/ > branch: debian-unstable > tag: debian/qemu_2.8+dfsg-4 I'm not sure what you're doing there. It builds fin

Bug#859599: unblock: qemu/1:2.8+dfsg-4

12.04.2017 20:25, Niels Thykier wrote: [] >>> Just to be sure, are you recommending 1:2.8+dfsg-4 or that we go with >>> upstream's 2.8.1 release? >> >> Historically, for some reason I don't remember what, we >> kept the "major" upstream version and source in qemu and >> used just a patch (v2.8.1.pa

Bug#859854: qemu: CVE-2017-7377

commit 39ac9c9574ccf0be731be5f1d1dfe0e5f065ca48 Author: Michael Tokarev Date: Mon Apr 3 14:15:41 2017 +0300 9pfs-fix-file-descriptor-leak-CVE-2017-7377.patch pending d-release review (#859599) I'll add bug# reference. /mjt

Bug#859599: unblock: qemu/1:2.8+dfsg-4

05.04.2017 20:42, Niels Thykier wrote: > Control: tags -1 moreinfo > > On Wed, 05 Apr 2017 09:35:19 +0300 Michael Tokarev wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian@packages.debian.org >> Usertags: unblock

Bug#859487: probably wrong dependencies on systemd startup unit

Package: openbsd-inetd Version: 0.20160825-2 Severity: normal During system startup, inetd starts before networking, when local IP addresses hasn't been configured yet. As a result, services bound to specific IP addresses in inetd.conf can't be started, for example on my system it complains ne

Bug#859417: unblock: seabios/1.10.2-1

000 +0300 @@ -1,3 +1,12 @@ +seabios (1.10.2-1) unstable; urgency=medium + + * new upstream stable/bugfix release, +required for qemu 2.8.1+ due to ahci changes, +plus fixes for guest resume from S3 +and ps/2 keyboard/mouse handling + + -- Michael Tokarev Mon, 03 Apr 2017 13:47:29 +0300 + s

Bug#856721: unblock: libcacard/1:2.5.0-3

-vcard_apdu_new-CVE-2017-6414.patch +Closes: #856501, CVE-2017-6414 + * dont-fail-if-caller-didn-t-pick-previous-response.patch + + -- Michael Tokarev Sat, 04 Mar 2017 11:57:23 +0300 + libcacard (1:2.5.0-2) unstable; urgency=medium * add remove-requires.private.patch to remove

Bug#856591: unblock: qemu/1:2.8+dfsg-3

fsg/debian/changelog --- qemu-2.8+dfsg/debian/changelog 2017-01-23 14:06:54.0 +0300 +++ qemu-2.8+dfsg/debian/changelog 2017-03-01 12:32:26.0 +0300 @@ -1,3 +1,63 @@ +qemu (1:2.8+dfsg-3) unstable; urgency=high + + * urgency high due to security fixes + + [ Michael Tokarev ] + * se

Bug#855378: Feed back Ubuntu branches and Delta

01.03.2017 10:31, Christian Ehrhardt wrote: > > b 7a257a6a46 Enable seccomp for ppc64el > > This one isn't for stretch, delaying for now. > Why only ppc64el, why not other ppc variants? > > > Because ppc64el was the only one I could test/verify on. > If you can check more we

Bug#854892: Can't qemu-debootstrap ppc64: /sbin/ldconfig: Syntax error: word unexpected (expecting ")"

11.02.2017 19:09, Rebecca N. Palmer wrote: > Package: qemu-user-static > Version: 1:2.8+dfsg-2 > Control: found -1 1:2.1+dfsg-12+deb8u6 > This log contains: > /sbin/ldconfig: 1: /sbin/ldconfig: Syntax error: word unexpected (expecting > ")") It looks like the prob was in the archive, not in qemu

Bug#854889: Can't qemu-debootstrap sparc64: Assertion `!have_tb_lock' failed

11.02.2017 19:15, Rebecca N. Palmer wrote: > Package: qemu-user-static > Version: 1:2.8+dfsg-2 > > sid-amd64# KEEP_DEBOOTSTRAP_DIR=1 qemu-debootstrap --arch sparc64 > --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg sid sparc64 > http://ftp.de.debian.org/debian-ports/ > [...] > I: R

Bug#855378: Feed back Ubuntu branches and Delta

17.02.2017 13:48, Christian Ehrhardt wrote: > - a) Ubuntu only fixes that can be hidden under the vendor based > control-in -> control mechanism > - b) Fixes applying to Debian as well (only for those there will be a > debian/changelog entry needed) > > Since the ubuntu-zesty-2.8 is ava

Bug#855966: qemu: Please use full version number (2.8.0 instead of 2.8)

24.02.2017 00:16, Jeremy Bicha wrote: > Source: qemu > Version: 1:2.8+dfsg-2 > Severity: low > > Could you please use the full version number 2.8.0 instead of 2.8? What's wrong with using just 2-component version number? We do apply the stable patchsets, and we do apply the selected stable patche

Bug#855378: Feed back Ubuntu branches and Delta

21.02.2017 12:12, Christian Ehrhardt пишет: > On Tue, Feb 21, 2017 at 9:46 AM, Michael Tokarev <mailto:m...@tls.msk.ru>> wrote: > > Hello Christian! > > Thank you for doing this. > > 17.02.2017 13:48, Christian Ehrhardt wrote: > > >

Bug#855378: Feed back Ubuntu branches and Delta

Hello Christian! Thank you for doing this. 17.02.2017 13:48, Christian Ehrhardt wrote: > case sha1 summary > a 84dc4d05d3 ubuntu acl fix dependencies changed This really should be fixed in acl package, not in qemu. I filed a bugreport about this quite some time ago, and actual

Bug#851694: (no subject)

17.01.2017 21:22, anonym wrote: > ... and here's the patch. Please address this upstream. I'm not sure I understand the root of the problem so don't want to act as a broken phone between you and upstream :) Thanks, /mjt

Bug#855659: qemu-kvm: USB passthrough causes VM to terminate

Control: reassign -1 src:qemu 1:2.8+dfsg-1 21.02.2017 04:13, Alistair Phipps wrote: > qemu-kvm 2.8 (from jessie-backports) has an issue that breaks USB device > passthrough to guests. See: The same obviously applies to the stretch version. Please note that qemu-kvm is a dummy package which con

Bug#855263: sporadic (and very annoying) disconnects from qemu vnc server

Package: qemu-system Version: 1:2.8+dfsg-2 Severity: important Tags: patch upstream when using VNC display, a VNC client gets disconnected quite often by the QEMU VNC server, depending on connection speed, amount of display updates and so on. This is because qemu tries to send large amount of dat

Bug#854959: qemu-system-x86: Invalid parameter 'unix'

Control: tag -1 - upstream 12.02.2017 19:28, Michael Tokarev wrote: .. >> qemu-system-x86_64: -spice unix: Invalid parameter 'unix' > > Yes, upstream #ifdef'ed the code when adding the parameter in Jan-2015, > but never defined the #define. Actually it is just t

Bug#854959: qemu-system-x86: Invalid parameter 'unix'

Control: severity -1 minor Control: tag -1 + upstream confirmed 12.02.2017 18:18, Roland Sommer wrotre: > Package: qemu-system-x86 > Version: 1:2.8+dfsg-2~bpo8+1 > Severity: normal > > Dear Maintainer, > > I'm trying to use socket (which is reported to be faster) for spicec It's of comparable s

Bug#854181: RFH: busybox -- Tiny utilities for small and embedded systems

On Sat, 04 Feb 2017 19:16:16 +0100 Cyril Brulebois wrote: > Package: wnpp > Severity: normal > > Hi, > > We're entering the deep freeze in a few hours, and this mail should have > been sent a while ago, but let's not delay this any further: the Debian > Installer team requests assistance with ma

Bug#854032: qemu: vnc server disconnects clients randomly on large graphics updates

Source: qemu Version: 2.6+dfsg-1 Severity: important Tags: upstream patch Depending on network characteristics between qemu vnc server and a vnc client, and what the guest OS is doing, there's quite high chance of seeing sporadic disconnects from the server in the middle of ui update. This is beca

Bug#853973: qemu: QEMU user mode emulation on PowerPC fails to run i386 executables.

Control: severity -1 normal 02.02.2017 19:13, Steven Gawroriski wrote: > Package: qemu > Version: 1:2.8+dfsg-2 > Severity: critical > Justification: breaks unrelated software > > Dear Maintainer, > > For QEMU user mode, attempting to run i386 executables on a PowerPC > host fails. > > Running e

Bug#852302: ipxe-qemu: Crash with QEMU newer than 2.6

24.01.2017 14:34, Charles Malaheenee wrote: > Sorry Bastian, we don't understand your logic. You have the confirmed bug, > but you can't reproduce it. What you propose? > Buy a new hardware? Use an old version of QEMU? Or build ipxe ourselves? He's just asking for a way to verify/reproduce the p

Bug#852417: unblock: qemu/1:2.8+dfsg-2

After some thoughts, I think this should be pushed to testing faster. Because the features I enabled which are currently in testing are just plain buggy, there are multiple security bugs in virtio-3d display (which is being disabled in sid), and because with just 2 weeks of this being in testing, i

Bug#852417: unblock: qemu/1:2.8+dfsg-2

ing of #769983 (multi-threaded linux-user) by 2.7 + * mention closing of #842455, CVE-2016-9101 by 2.8 + * audio-ac97-add-exit-function-CVE-2017-5525.patch (Closes: #852021) + * audio-es1370-add-exit-function-CVE-2017-5526.patch (Closes: #851910) + * watchdog-6300esb-add-exit-function-CVE-2016-10

Bug#852302: ipxe-qemu: Crash with QEMU newer than 2.6

23.01.2017 16:00, Bastian Blank wrote: > Control: severity -1 important > Control: tags -1 moreinfo > > On Mon, Jan 23, 2017 at 03:55:13PM +0300, Michael Tokarev wrote: >> If that's the case, it's a serious issue, since this package >> mostly becomes useless. I

Bug#852302: ipxe-qemu: Crash with QEMU newer than 2.6

Control: severity -1 serious 23.01.2017 15:40, Charles Malaheenee wrote: > Package: ipxe-qemu > Version: 1.0.0+git-20161027.b991c67-1 > Severity: normal > Tags: upstream > > Dear Maintainer, > > It's not possible to PXE boot in QEMU at all. When we choose --pxe option in > virt-install (or virt

Bug#839695: 67 X11/GTK related packages on a headless server

23.01.2017 15:12, Rob J. Epping wrote: > Let me be the voice of other people who do not need any graphical stuff. > For me personally, I only run headless virtual machines on a headless > server and do not want to install all the additional libraries. > > As an example, some people want vim with

Bug#813658: Reverting gtk/virgl support in qemu for stretch

23.01.2017 15:23, ge...@riseup.net wrote: > > Could just push this to j-bp as well? As per bpo policy, a package needs to hit testing first. Since we're in a freeze, migration to testing require mandatory 10 days waiting period, and should be manually approved. So I'm not sure it's a good idea

Bug#829243: qemu-user-static: bad binfmts for mipsn32{,el}

Control: reopen -1 Control: found -1 1:2.8+dfsg-2 01.07.2016 18:10, Adam Borowski wrote: > Package: qemu-user-static > Version: 1:2.6+dfsg-3 > Severity: normal > Tags: patch > > Hi! > While you do ship -user executables for mipsn32 and mipsn32el, the binfmt > magics detect them as mips/mipsel whi

Bug#813658: Reverting gtk/virgl support in qemu for stretch

Control: reopen 839695 Control: reopen 813658 Control: found 839695 1:2.8+dfsg-2 Control: found 813658 1:2.8+dfsg-2 I'm reverting these changes (virgl and gtk support) for stretch. After the new qemu hit backports yesterday, I received HUGE number of complaints, just like I expected, from "server

Bug#851509: qemu: Please enable sdl frontend too

23.01.2017 13:44, Laurent Bigonville wrote: > Could you please keep a build with virgl, gtk3 and sdl2 in experimental? > With maybe also spice >= 0.13 if you have time? So people can test the > thing? Sure, will do right after I'll upload 2.8+dfsg-2 Thanks, /mjt

Bug#851509: qemu: Please enable sdl frontend too

23.01.2017 13:36, Laurent Bigonville wrote: > On Sun, 15 Jan 2017 21:31:07 +0100 Samuel Thibault > wrote: >> Hello, >> >> Currently, only the GTK frontend is enabled. From what I read in >> #839695, this is because Michael wanted to make it modular. But can't >> we just let qemu depend on both gtk

Bug#839695: 67 X11/GTK related packages on a headless server

23.01.2017 10:55, Rob J. Epping wrote: > Hi, > > qemu 1:2.8+dfsg-1 has hit jessie-backorts. > > With the fix for bug #839695 my server now wants to install 67 X11/GTK > related new packages. This is on a headless server where this is just > more atack surface, i.e. less security. > > Would it be

Bug#813658: virglrenderer support before the freeze?

21.01.2017 16:19, Michael Neuffer wrote: > On Mon, 14 Nov 2016 19:39:22 +0100 Andreas Cadhalpun > wrote: >> The only additional dependencies compared to the current >> qemu-system-x86 package are: >> libdrm2 libepoxy0 libexpat1 libgbm1 libvirglrenderer0 >> libwayland-client0 libwayland-server0 >>

Bug#851509: qemu: Please enable sdl frontend too

15.01.2017 23:31, Samuel Thibault wrote: > Source: qemu > Version: 1:2.8+dfsg-1 > Severity: normal > > Hello, > > Currently, only the GTK frontend is enabled. From what I read in > #839695, this is because Michael wanted to make it modular. But can't No, it was done because gtk supports 3d fea

Bug#851490: O: virglrenderer -- virtual GPU for KVM virtualization

15.01.2017 18:10, Daniel Pocock пишет: > Package: wnpp > Severity: normal > X-Debbugs-CC: pkg-qemu-de...@lists.alioth.debian.org > > > For virgl support in qemu > > slides: > > http://www.linux-kvm.org/images/f/f3/01x08b-KVMGT-a.pdf > > http://www.linux-kvm.org/images/3/36/Kvm-forum-2013-virgi

Bug#850584: qemu: Please provide qemu without GTK for headless machines

11.01.2017 08:29, Peter Colberg wrote: > Hi Michael, > >> Proper "fix" for this wishlist is to make display modular. Every >> qemu release makes this closer, but it is not there in 2.8 yet. >> So we have stretch without modular display in qemu, and qemu in >> stretch will pull a few more libs than

Bug#850584: qemu: Please provide qemu without GTK for headless machines

Control: tag -1 + wontfix 08.01.2017 09:14, Peter Colberg wrote: > Package: qemu > Version: 1:2.8+dfsg-1 > Severity: wishlist > > Dear Maintainer, > > The upgrade to the above version pulls in a large number of new packages: Yes. We were thinking about this for quite some years. But the problem

Bug#849569: spice: Please package 0.13 branch to experimental

04.01.2017 16:00, Erik Adler wrote: > ... crickets from their devs. Its a judgment call from Debian not RedHat > when and where this goes in. Yes. And if my opinion as a debian developer weights anything, I'd like to hear what the developers actually think, before making any decision. I wrote some

Bug#849884: qemu-kvm: USB host device pass through causes instant VM poweroff

02.01.2017 13:57, Kyle Gordon wrote: > Hi Michael, > > Thanks for the response. I have tried upgrading qemu* to > 2.7+dfsg-3~bpo8+2 from jessie-backports, and the behaviour is > unfortunately the same. I haven't tried upgrading the system to Stretch > yet, as that might be a bit of a one way road!

Bug#849569: spice: Please package 0.13 branch to experimental

So, maybe we really should let 0.13 to stretch, together with gl? Everything else is in place now, and not many people compialined so far about new dependencies (maybe that's just because of the new year holidays? :) ), the only missing part is spice... Thanks, /mjt

Bug#849884: qemu-kvm: USB host device pass through causes instant VM poweroff

Control: severity -1 normal Control: reassign -1 qemu-system-x86 02.01.2017 02:54, Kyle Gordon wrote: > Package: qemu-kvm > Version: 1:2.1+dfsg-12+deb8u6 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > Over the course of the past few weeks, a guest KVM inst

Bug#839695: qemu: GTK3 configure options not used in build

29.12.2016 20:15, Jindřich Makovička wrote: > I was trying to build a patched QEMU package, and for some reason, GTK3 > options were not passed to configure - I had to put them on separate lines: > > # gtk display (see also sdl display) > # --enable-gtk > # --with-gtkabi=3.0 > # --enable-vte > li

Bug#813658: Please enable virgl support

29.12.2016 11:15, johnw wrote: > Hi Michael, > > Sorry, I mean "qemu-system-x86_64 -display gtk,gl=on -sandbox on", > (not -seccomp on) > > when I launch -display gtk with -sandbox on, qemu-system-x86_64 will freeze, > and "ps aux" will show me [qemu-system-x86] I see, and still only with gl=on

Bug#813658: Please enable virgl support

29.12.2016 06:22, johnw wrote: > Hi, I still have some problem after upgrade qemu-system-x86 to 2.8+dfsg-1. > > When I launch qemu-system-x86 with spice and gl=on, it show me error and > can not start. > qemu-system-x86_64: -spice > unix,addr=/tmp/spice-02.sock,disable-ticketing,gl=on: Invalid pa

Bug#813658: Please enable virgl support

16.12.2016 04:41, john wrote: > Package: qemu-system-x86 > Version: 1:2.7+dfsg-3+b1 > Followup-For: Bug #813658 > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > Hi, Is it possible use virgl/opengl with debian's package? > (No

Bug#844361: qemu: Upgraded from 2.6 to 2.7. Win 2008 R2 machine crasches during boot. I can see "qemu-system-x86_64: pci_get_msi_message: unknown interrupt type" in libvirt log.

25.11.2016 09:35, Changlimin wrote: > -device pci-assign,configfd=30,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x3 > > KVM pci-assign is configured, maybe the same reason as Hm. pci-assign is deprecated for a long time, maybe it's a good chance to switch to vfio now? Thanks, /mjt

Bug#784070: Newly-created arrays don't auto-assemble - related to hostname change?

23.11.2016 05:34, NeilBrown wrote: > On Tue, Nov 22 2016, Andy Smith wrote: > >> Hi Neil, >> >> On Tue, Nov 22, 2016 at 09:56:28AM +1100, NeilBrown wrote: >>> Thanks. Sorry this is taking a lot of back-and-forth... >> >> No worries. This is very interesting to me and I'd also like to know >> what

Bug#844361: qemu: Upgraded from 2.6 to 2.7. Win 2008 R2 machine crasches during boot. I can see "qemu-system-x86_64: pci_get_msi_message: unknown interrupt type" in libvirt log.

16.11.2016 01:44, Peter Xu wrote: > On Mon, 14 Nov 2016 21:17:39 +0100 wrote: >> Package: qemu >> Version: 1:2.7+dfsg-3+b1 >> Severity: important >> >> I use libvirt for runing Windows 2008 R2 server on qemu-kvm. VirtIO disks and >> VirtIO network adapters. >> After upgrading qemu from 2.6 to 2.6

Bug#813658: virglrenderer support

09.11.2016 19:43, intrigeri wrote: > Michael Tokarev: [] >> On all my servers where qemu is used, upgrading to this new >> version pulls in a TON of new dependencies, >> […] >> Once we enable that, all server people will start screaming >> out very very loud. &

Bug#813658: virglrenderer support before the freeze?

10.11.2016 00:00, Andreas Cadhalpun wrote : > Hi intrigeri, > > On 09.11.2016 17:43, intrigeri wrote: >> Michael Tokarev: >>> I looked at this matter a bit more. I switched from sdl1 to gtk3 >>> and enabled gl and virglrenderer. It works. >> &

Bug#813658: virglrenderer support before the freeze?

I looked at this matter a bit more. I switched from sdl1 to gtk3 and enabled gl and virglrenderer. It works. But now, we're facing quite an.. interesting issue. On all my servers where qemu is used, upgrading to this new version pulls in a TON of new dependencies, including wayland (libwayland-

Bug#843571: qemu-user-static - Move binaries out of /usr/bin

07.11.2016 23:09, Bastian Blank wrote: > Package: qemu-user-static > Version: 1:2.7+dfsg-3 > Severity: wishlist > > Please move the binaries out of /usr/bin to /usr/lib/qemu-user or so. > Compatibility can be provided by symlinks. What sort of compatibility do you talk about? All the Internet, a

Bug#843118: seabios: Unable to boot KVM guest with "-display none"

Control: tag -1 + moreinfo unreproducible 04.11.2016 03:26, Gregory Auzanneau wrote: > Package: seabios > Version: 1.9.3-2 > Severity: normal > > Dear Maintainer, > > Since the latest update of seabios 1.9.3-2, a guest machine can't start with > qemu parameter "-display none". > The guest hang

<    5   6   7   8   9   10   11   12   13   14   >