Control: tag -1 + confirmed upstream patch pending
27.06.2013 17:13, Christoph Anton Mitterer wrote:
The manpage claims it would use Bochs bios, but we use seabios:
QEMU uses the PC BIOS from the Bochs project and the Plex86/Bochs LGPL
VGA BIOS.
The VGA BIOS seems also to be
Please excuse me for this really long delay with the answer.
16.06.2013 23:29, Michael Gilbert wrote:
On Wed, Jun 5, 2013 at 1:12 PM, Michael Tokarev wrote:
02.06.2013 22:53, Michael Gilbert wrote:
Package: qemu
Severity: serious
version: 1.5.0+dfsg-1
Tags: security
Hi,
An out-of-bounds
On 18.04.2012 04:14, Vugar Dzhamalov wrote:
Package: qemu-kvm
Version: 1.0+dfsg-9
Severity: important
It seems that I am getting into something very similar to these bug reports:
https://bugzilla.redhat.com/show_bug.cgi?id=554078
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576838
On 18.04.2012 18:51, intrigeri wrote:
Hi,
Michal Suchanek wrote (05 May 2011 13:41:01 GMT) :
Booting this way from an Ubuntu USB install media is also very slow
but at least I can confirm the media is bootable.
I'm going to file a wishlist bug about USB2 redirection soon,
that will be
On 23.04.2012 11:54, Vugar Dzhamalov wrote:
[]
I'll take a look. For the next time, please don't send me
content of your /usr/bin or any other directories. Just
_versions_ of the software affected, and, most important,
the steps you did to (re)produce the issue. This includes
the way you start
Okay, I re-created your configuration with vde_switch,
and I found the kvm command lines you used in one of
the files -- you sent just too much information so
really important bits got lost in the noize initially.
I'm doing a copy test from one guest /dev/zero to another
guest /dev/null. It
On 26.04.2012 12:24, Vugar Dzhamalov wrote:
Thank you for doing this. I am very appreciate and sorry for wasting your
time
with this.
Lets be honest here I've reported it more than a week ago and so far no one
else joined the discussion. I guess it is quite obvious that there is
On 30.08.2012 22:03, malc wrote:
On Thu, 30 Aug 2012, Mike Gerber wrote:
[]
Vassily: Anything else you need when the hang happens again? Unfortunately
I'll
have to go into production with the guest, and I can't spend more weeks with
this bug after this week end.
Audio compiled without
On 02.09.2012 03:55, Thomas Nilsson wrote:
The problem is described with patch here:
https://bugzilla.redhat.com/show_bug.cgi?id=745781
So the fix apparently is just to disable mount --move.
And as usual, there's no documentation about what it
is for and why it is here.
Upstream included a
Package: dnsmasq
Version: 2.55-2
Severity: serious
Tags: security
The initscript (and postinst script) of dnsmasq creates /var/run/dnsmasq
directory and chowns it to dnsmasq:nogroup. However, dnsmasq daemon writes
the pidfile (which apparently is the only file there) as root user. Here's
the
On 02.09.2012 13:25, Thomas Nilsson wrote:
2012-09-02 09:18, Michael Tokarev skrev:
Thomas, can you verify that adding --disable-mount-move to the
configure flags of the package and rebuilding it fixes the problem for
you? If you want, I can prepare an already compiled version for you
On 02.09.2012 13:40, Simon Kelley wrote:
[]
The explanation for the current state of affairs is here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508560
Oh. I tried to find why/when this subdir appeared, but
failed. The changelog mentions PID in uppercase ;)
I'm sorry about this,
Control: tag 686524 + moreinfo
On 02.09.2012 22:34, Timo Weingärtner wrote:
Package: qemu-kvm
Version: 1.1.1+dfsg-1
Severity: grave
Justification: renders package unusable
Well, it is usable for lots of people.
After starting the guest with virsh start router the kvm process uses
100%
Control: tag 686524 + unreproducible
On 03.09.2012 01:58, Timo Weingärtner wrote:
[]
Please try reproducing it without libvirt. Maybe removing -M pc-0.12
will help with that.
Without the libvirt magic it doesn't use 100% CPU but it won't boot either.
I removed pc-0.12 from libvirt's
Control: tag 686146 + pending
On 29.08.2012 20:42, Michael Tokarev wrote:
[]
ii autofs 5.0.6-2 amd64
kernel-based automounter for Linux
pc autofs5 5.0.4-3.2+b1 amd64
kernel-based automounter for Linux, version 5
Control: tag 686524 - moreinfo unreproducible + confirmed
On 03.09.2012 21:49, Timo Weingärtner wrote:
bad:
kvm -nographic -nodefaults -kernel /boot/vmlinuz-3.2.0-3-amd64 -append
console=ttyS0 -chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0
good:
kvm
Control: retitle 686524 qemu-kvm: guests with -nographic -serial pty won't
start until input to console is made
Control: forwarded 686524
http://thread.gmane.org/gmane.comp.emulators.qemu/168265
I'm retitling the bugreport to reflect our findings. As stated
before, -serial pty works the same
Control: tag 686524 + patch pending
On 04.09.2012 01:28, Timo Weingärtner wrote:
Hallo Michael Tokarev,
2012-09-03 um 20:25:25 schriebst Du:
Control: retitle 686524 qemu-kvm: guests with -nographic -serial pty won't
start until input to console is made Control: forwarded 686524
http
Control: tag 684775 + upstream confirmed
Somehow this has been forgotten in the BTS. We talked with
Uwe on IRC about this.
As stated in the original bugreport, guest crashes, but
only when HOST kernel is 32bits, switching to 64bits
host kernel fixes the issue.
Since 64bit kernel and 32bit
On 04.09.2012 12:16, Harald Dunkel wrote:
On 09/03/12 07:04, Michael Tokarev wrote:
That turned out to be not so simple, and there's no established
way to deal with such a situation. Indeed, manually upgrading
autofs5 will let you to purge it. But in order to allow this
purging
tag 686706 - upstream + pending
reassign 686706 qemu 1.1.0+dfsg-1
severity 686706 important
merge 678217 686706
thanks
On 05.09.2012 02:07, bmorel wrote:
Package: seabios
Version: 1.7.0-1
Severity: normal
Tags: upstream
First, seabios package in debian does include this file,
in
Source: qemu
Version: 0.12.5+dfsg-3squeeze1
Severity: grave
Tags: security upstream patch
All versions of qemu (and qemu-kvm) since 2004 have a flaw in handling
VT100 escape sequences when emulating some devices with a virtual console
backend.
More information can be found at redhat bugreport
On 08.09.2012 00:35, folkert wrote:
[]
pSeries support is already present in 1.1. That said if it works well
[]
Are you sure?
It doesn't work:
folkert@nieuw:~$ qemu --version
QEMU emulator version 1.1.0 (Debian 1.1.0+dfsg-1), Copyright (c) 2003-2008
Fabrice Bellard
folkert@nieuw:~$
Control: severity 686979 wishlist
thanks
On 08.09.2012 01:03, folkert wrote:
Package: qemu
Version: 1.1.0+dfsg-1
Severity: normal
For the 'pseries' machine type, the files mentioned in the subject are
missing in the .deb-file.
I did an apt-file search for them and it seems there are no
On 08.09.2012 20:55, michael chlon wrote:
Package: qemu-kvm
Version: 1.1.1+dfsg-1
Severity: normal
Dear Maintainer,
I try to bind my WiFi card - Atheros ( module ath5k) - with my VM
in dorder to present WiFi card to the VM.
I try this with PCi Passtrough.
I have read a lot on
On 09.09.2012 01:38, Chlon Michaël wrote:
[]
= And in the VM log (qemu log):
2012-09-08 21:27:35.632+: starting up
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
HOME=/ QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.1 -enable-kvm -m 1024 -smp
Package: libutempter0
Version: 1.1.5-4
Severity: normal
As $Subject says, libutempter0 is not Multi-Arch-able. I can guess
this is because of /usr/lib/utempter/utempter executable which is
shipped in this package. Due to this non-multi-arch-awareness,
it isn't possible to install foreign
On 01.08.2009 20:22, Robert Millan wrote:
Package: qemu
Version: 0.10.5-1
Severity: wishlist
Tags: patch
Debug versions of vgabios.bin are provided, but they aren't useful
because support for debug information is not enabled in qemu.
Please enable DEBUG_BIOS so that the information that
these checks assuming we always use
recent enough versions. (Closes: #678555)
-- Michael Tokarev m...@tls.msk.ru Wed, 26 Sep 2012 21:15:05 +0400
autofs (5.0.6-4) unstable; urgency=low
* configure with --disable-mount-move -- upstream even removed the
code in question for 5.0.7 release
On 26.09.2012 23:49, Michael Tokarev wrote:
[]
Debdiff between wheezy and sid version will be sent in a separate
email, since it is large. The same but without upstream changes
(which are easily visible in the git tree referenced above) and
the removal of half-5.0.7 upstream diff from debian
Control: tags -1 + moreinfo
On 27.09.2012 18:27, Nikolai Kondrashov wrote:
Package: qemu-kvm
Version: 1.1.2+dfsg-2
Severity: important
A fully-updated 64-bit Fedora 17 guest using the 3.5.4-1.fc17.x86_64 kernel
hangs on boot with the following repeated messages on the console:
BUG: soft
On 27.09.2012 20:25, Nikolai Kondrashov wrote:
On 09/27/2012 06:23 PM, Michael Tokarev wrote:
Please provide full command line which virt-manager uses. You can find
it in virtmanager logs or in ps(1) output.
Here is the command line:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin
To clarify:
1. this only affects 1.1.x tree (which is a
history for most developers already)
2. the same guest boots okay with 1.2 (with
kvm and irqchip enabled).
BTW, what is this hda-duplex device anyway? I never heard of it
before now :). And I guess using QEMU_AUDIO_DRV=none with
On 27.09.2012 22:28, Jan Kiszka wrote:
[]
--- a/hw/intel-hda.c
+++ b/hw/intel-hda.c
@@ -1107,6 +1107,9 @@ static void intel_hda_reset(DeviceState *dev)
DeviceState *qdev;
HDACodecDevice *cdev;
+if (d-msi) {
+msi_reset(d-pci);
+}
intel_hda_regs_reset(d);
by the PCI code already.
Signed-off-by: Michael Tokarev m...@tls.msk.ru
Cc: Jan Kiszka jan.kis...@siemens.com
Cc: 688...@bugs.debian.org
---
hw/intel-hda.c | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/hw/intel-hda.c b/hw/intel-hda.c
index e38861e..da61323
On 27.09.2012 23:32, Michael S. Tsirkin wrote:
[]
Looks good to me.
I just sent another patch, now with proper S-o-b and
description, which does the same but touches 2 less
lines (by renaming the other half of the function), --
his is to be more like the 1.2+ version. The
functionality is
[Dropping the Cc list]
On 27.09.2012 23:57, Nikolai Kondrashov wrote:
On 09/27/2012 10:40 PM, Nikolai Kondrashov wrote:
Nikolai, please verify if this is the issue you're seeing, and
please try without sound device. If this is the case, let's
downgrade this bug from important to normal, since
Control: retitle -1 emulated hda-intel does not work since 1.1.1 upstream
release (linux guest hangs)
Control: found -1 1.1.1+dfsg-1
Control: affects -1 qemu
I tried a few other guests with the same command line, and
all shows bad behavor. Debian wheezy kernel also hangs
when loading hda-intel
Control: severity -1 wishlist
On 30.09.2012 21:51, Harald Roessler wrote:
Package: qemu-system
Version: 1.1.2+dfsg-2
Severity: important
Dear Maintainer,
After installatio of version 1.1.2+dfsg-2 rbd images does not working more.
The testing after the installation results in:
--
On 02.10.2012 17:20, Miquel van Smoorenburg wrote:
Package: mdadm
Version: 3.2.5-1
[version 2 of the patch]
The initramfs hook supplied by mdadm doesn't install mdmon. Also, mdmon
is not included in the .udeb for the installer.
This means that if you have an array with external
Control: tags -1 + moreinfo unreproducible
On 06.10.2012 00:41, David Starner wrote:
Package: autofs
Version: 5.0.7-1
Severity: serious
$ sudo apt-get install autofs udev
Reading package lists... Done
Building dependency tree
Reading state information... Done
udev is already the newest
:37.0 +0400
@@ -1,3 +1,10 @@
+autofs (5.0.7-2) unstable; urgency=low
+
+ * force transfer ucf autofs5=autofs ownership for all ucf-managed
+files (Closes: #689747)
+
+ -- Michael Tokarev m...@tls.msk.ru Sat, 06 Oct 2012 13:06:37 +0400
+
autofs (5.0.7-1) unstable; urgency=low
* new
Control: severity -1 normal
Control: tags -1 + moreinfo
08.10.2012 15:20, Josquin DEHAENE wrote:
Package: qemu-kvm
Version: 1.1.2+dfsg-2~bpo60+1
Severity: important
Hi,
We have different kind of VMs running on this host. All of them boot normaly
after update to 1.1.2 expect Win2k8 64b
08.10.2012 18:05, Josquin DEHAENE wrote:
I forgot to specify that VMs are managed through libvirt. Thus, the xml file
is in libvirt definition format.
A virsh version gives
Yes I understand it is libvirt. For various reasons I still can't use it
locally on my development/test machine.
Package: libldns1
Version: 1.6.13-1~bpo60+1
Severity: grave
Justification: breaks other package(s)
After updating unbound, which is linked with libldns1, from the
version in squeeze-backports to the one in wheezy, the daemon
does not start:
Starting recursive DNS server: unbound
Source: roxterm
Version: 2.6.5-1
Severity: grave
Tags: security
When trying to click on an URL inside the roxterm window that contains
a single quote ('), the resulting command sent to the shell includes
this quote and is interpreted by the shell, for example:
http://example.com/quote'here
Control: severity -1 normal
Control: tags -1 - security
29.12.2012 15:49, Michael Tokarev wrote:
Source: roxterm
Version: 2.6.5-1
Severity: grave
Tags: security
When trying to click on an URL inside the roxterm window that contains
a single quote ('), the resulting command sent to the shell
29.12.2012 16:59, Fabio Fantoni wrote:
Updated debian seabios package to 1.7.1 (on personal repository for now),
tested with wheezy and xen-unstable and is working.
Package repository: https://github.com/Fantu/pkg-seabios
Hmm. This repository contains just 2 commits:
initial import with
Control: tags -1 + moreinfo unreproducible
04.11.2012 08:49, Gianluigi Tiesi wrote:
Package: qemu-kvm
Severity: minor
Hi, I've noticed my kvm warns about using boot=on so I've decided to find some
documentation,
as I found boot=on enables extboot option rom removed upstream because seabios
29.12.2012 19:52, Fabio Fantoni wrote:
[]
I have taken debian folder from sid package, if you want simple see/update
repository override debian folder of debian seabios repository, if there will
be a problem tell me and I'll redo all forking repository from debian, updating
seabios upstream
Control: reopen -1
Control: retitle -1 potential guest-side buffer overflow caused by e1000 device
emulation and large incoming packets - CVE-2012-6075
Control: tags -1 + patch pending upstream
There is another half of the same issue. Current patch/fix which
has been applied is about the case
Control: severity -1 wishlist
Control: tags -1 + wontfix
[Replying to an old bugreport...]
11.07.2008 15:34, Petter Reinholdtsen wrote:
Package: qemu
Version: 0.9.1-1
When trying to run several qemu machines in a local mcast based
network, the hosts are not able to reliably talk to each
Package: qemu-system
Version: 1.1.2+dfsg-1
Severity: minor
Tags: confirmed
(This is actually an old problem, but still unsolved, reporting against
wheezy version).
qemu does not come with sgabios.bin file necessary for the SGA device
to work, it is because this (rom) image is not packaged for
Version: 1.1.2+dfsg-1
I'm closing this bugreport, since (at least some) support for
pseries is included in 1.1 version.
Maybe some bits are missing still (like (semi-optional) firmware),
but general support should be here.
Thanks!
/mjt
--
To UNSUBSCRIBE, email to
Control: tags -1 + confirmed upstream
This is still the case on version 1.3, but at least
it prints the real error message now (Permission denied).
See also #390444.
Thanks,
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
26.12.2012 02:53, patrick295767 wrote:
Package: qemu
Version: 0.12.5+dfsg-3squeeze1
Severity: normal
Hi,
If you install android you cannot make it to an image of ext3. yeap
indeed.
If you receive this error:
cannot mount /dev/sdaX
Then select the ntfs file system
Control: tags -1 + moreinfo unreproducible
[Replying to relatively old bugreport...]
13.06.2010 06:29, Seo Sanghyeon wrote:
Package: qemu-user
Version: 0.12.4+dfsg-2
Severity: important
QEMU user mode emulation binaries (specifically qemu-arm) fail with
mmap: Operation not permitted when run
31.12.2012 00:43, Gianluigi Tiesi wrote:
On 12/29/12 15:57, Michael Tokarev wrote:
[]
vm -m 1024 -snapshot -device ahci,id=ahci0,bus=pci.0,addr=0x5 -drive
file=/dev/sda,if=none,id=drive-sata0-0-0,format=raw,boot=on -device
ide-hd,bus=ahci0.0,drive=drive-sata0-0-0,id=sata0-0-0
Control: tag -1 + wontfix
[Replying to an old bugreport...]
05.04.2007 18:13, Raphael Hertzog wrote:
Package: qemu
Version: 0.8.2-4
Severity: wishlist
Basically implement this but for Debian:
http://people.redhat.com/berrange/olpc/sdk/network-bridge.html
The package would use vde_switch to
01.01.2013 06:32, Jonathan Nieder wrote:
Package: qemu-system
Version: 1.3.0+dfsg-1~exp1
Severity: serious
Justification: failed upgrade
From today's upgrade:
| Preparing to replace qemu-system 1.3.0+dfsg-1~exp1 (using
.../qemu-system_1.3.0+dfsg-1~exp3_amd64.deb) ...
| Unpacking replacement
01.01.2013 23:49, Venkat Kapur wrote:
This following patch seems to work, but I am not a really an expert in this
field.
That patch does not fix the problem for me. It still segfaults as before.
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
06.04.2013 12:56, Guido Trotter wrote:
Package: busybox-static
Version: 1:1.20.0-7
Severity: wishlist
I know that acpid was disabled on purpose, but would it be possible to
reenable it? It is useful on VMs running with busybox only, for example.
For many years, i've the following
I'm pinging this bug, as we're getting seriously out of time.
Now, I guess, we should either let the whole thing go (it has
already been unblocked for, only d-i block remains), or mark
the relevant bugs as non-RC for wheezy.
Thanks,
/mjt
25.03.2013 15:38, Michael Tokarev wrote:
Let me start
06.04.2013 16:02, Guido Trotter wrote:
On Sat, Apr 6, 2013 at 11:05 AM, Michael Tokarev m...@tls.msk.ru wrote:
06.04.2013 12:56, Guido Trotter wrote:
Package: busybox-static
I know that acpid was disabled on purpose, but would it be possible to
reenable it? It is useful on VMs running
08.04.2013 11:57, Cyril Brulebois wrote:
Forgot to mention one thing:
Cyril Brulebois k...@debian.org (08/04/2013):
My take is: until we hit real bugs in real situations, we keep busybox as it
is. If release managers want to cherry-pick a few fixes, I won't stop them
from requesting so.
Control: reassign -1 qemu-system
Control: force-merge -1 689239
10.04.2013 14:11, Thomas Goirand wrote:
Package: qemu-kvm
Version: 1.1.2+dfsg-6
Severity: wishlist
Hi Vagrant, Aurelien and others,
To use Ceph in OpenStack, we would need that the --enable-rdb is added
in the ./configure.
Package: qemu-utils
Version: 1.1.2+dfsg-1
Severity: normal
Tags: security patch upstream
qemu-nbd utility does not has an option to specify format of the block
image it serves, so it is possible by a guest (user of nbd device) to
write data to it the way so it looks like some format known to
11.01.2013 20:42, Graham wrote:
Hi,
Though I'm currently not using md, I have done so in the past, and it
has always worked well for me. I saw this bug report and thought that
I might try to reproduce it. Here's what I did:
That's basically the steps I used too, more or less, when trying to
+
+ * fix USB regression introduced in 1.1 (Closes: #683983)
+uhci-don-t-queue-up-packets-after-one-with-the-SPD-flag-set.patch
+Big thanks to Peter Schaefer (https://bugs.launchpad.net/bugs/1033727)
+for the help identifying the fix.
+
+ -- Michael Tokarev m...@tls.msk.ru Mon, 14 Jan 2013 12
Package: libseccomp-dev
Version: 1.0.1-1
Severity: important
The subject says it all: there's no static library provided
by libseccomp-dev package.
Thanks,
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Source: libseccomp
Version: 1.0.1-1
Severity: normal
It looks like kernel supports seccomp on a number of architectures,
3.2 has it on:
s390 arm sh powerpc microblase mips sparc x86
please provide the package for more architectures, not just i386 and amd64.
Thanks!
/mjt
--
To UNSUBSCRIBE,
Control: severity -1 wishlist
20.01.2013 01:03, Kees Cook wrote:
I would strongly prefer to avoid shipping a static library for this package
to avoid programs linking to this non-dynamically, especially since it
makes security updates more difficult to track.
Well, this is a standard excuse
21.01.2013 03:27, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the src:libseccomp package:
#698606: please provide package for other architectures, not just x86
It has been closed by Kees Cook k...@debian.org.
Their
21.01.2013 01:42, Jonathan Nieder wrote:
* add qemu-kvm package (transitional, depends on qemu-system),
and add /usr/bin/kvm wrapper that calls qemu-system-x86_64
with some arguments to match original qemu-kvm behavour.
(Closes: #560853)
Oh, excellent!
Actually it might
19.01.2013 15:23, Julien Cristau wrote:
qemu{,-kvm} unblocked.
Thank you very much Julien!
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
23.01.2013 02:06, Gerardo Esteban Malazdrewicz wrote:
Package: qemu-system
Version: 1.3.0+dfsg-3exp
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Newest qemu-system absorbs old qemu-kvm functionality.
However, script to launch kvm is /usr/bin/kvm/kvm, where it is
23.01.2013 13:38, Raoul Bhatia [IPAX] wrote:
Package: qemu
Version: 1.1.2+dfsg-5
Severity: whishlist
Now that's interesting you used this version number... ;) But ok.
Please rebuild qemu 1.1.2+dfsg-5 (or later),
which includes the e1000 CVE-2012-6075 bugfix, for backports.
Do you really
23.01.2013 17:23, Raoul Bhatia [IPAX] wrote:
On 2013-01-23 10:47, Michael Tokarev wrote:
Do you really mean qemu or actually qemu-kvm?
qemu-*? ;)
My currently installed packages are qemu-keymaps, qemu-kvm and qemu-utils.
Would src:qemu have been more appropriate?
qemu-kvm builds from
-fakeraid arrays.
Thanks,
/mjt
29.10.2012 00:42, Michael Tokarev wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
This is a pre-upload unblock request for mdadm/3.2.5-4.
Recently, upstream released a new version of mdadm, v3.2.6,
which
18.03.2013 01:06, Michael Gilbert wrote:
Do you have a link to the patch fixing this issue? This would be
useful for anyone considering nmuing a fix.
The fix has been in the qemu-kvm debian package git tree since the
day this bug has been reported, and the bug has been marked as
pending since
18.03.2013 14:41, Francesco Potortì wrote:
Package: mdadm
Version: 3.2.5-5
Severity: normal
Dear Maintainer,
The disk /dev/sdb is broken. However, the kernel sees it, as you can
see in /proc/partitions. In this situation, I see this:
tucano:~# mdadm /dev/md3 --add /dev/sdb1
19.03.2013 01:49, Helge Deller wrote:
Hi Michael,
On 03/12/2013 09:13 PM, Helge Deller wrote:
On 03/09/2013 02:57 AM, Michael Tokarev wrote:
As Ian replied to your patch on autofs mailinglist, this is only needed for
old kernels, but he applies your patch anyway. I'd go for removing whole
19.03.2013 15:04, Konrad Vrba пишет:
I have exactly the same problem, as described.
Is there away to specify (in preseeding) to skip installing busybox ?
Busybox is used in regular initramfs. While techincally initramfs might
work without busybox, no one really test things that way. So
19.03.2013 15:29, Konrad Vrba wrote:
I see, but custom kernel without initramfs should work. If there is a
way to skip installing busybox, I would appreciate.
That appears to be a wrong solution to a wrong problem.
Something is wrong with the archive mirror system apparently, or with
the
[Replying back to the bugreport AND to NeilB.
Hope you're okay with that
Neilb: This is just the (excellent!) analisys of the problem,
I can send a patch if you like
]
20.03.2013 22:19, Francesco Potortì wrote:
And also (as root) apt-get install build-essential to
install build dependencies
Package: qemu-user, qemu-user-static
Version: 1.1.2+dfsg-1
Severity: normal
Tags: upstream, confirmed
Forwarded: http://thread.gmane.org/gmane.comp.emulators.qemu/202103
$ ./x86_64-linux-user/qemu-x86_64 bash64
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
$ gdb
25.03.2013 13:37, Didier Raboud wrote:
Hi all,
I propose to upload busybox to t-p-u with only the RC bugfixes (#686502
and #701965, CVE-2013-1813). I have cherry-picked thoses changes on top
of wheezy's. The resulting debdiff is attached, with version
1:1.20.0-7+deb7u0.1.
I really hoped it
25.03.2013 13:54, Didier Raboud wrote:
I propose to upload busybox to t-p-u with only the RC bugfixes (#686502
and #701965, CVE-2013-1813).
IRC feedback on that subject lead to dropping the fix for #701965,
rationale being http://bugs.debian.org/702278#17 .
That's lovely. I haven't even
Let me start from scratch please. I wasn't aware of this
bugreport/discussion, and I made a mistake by not filing
a proper unblock request when I uploaded the busybox
package with all the fixes. So here are descriptions of
every change.
A sort of a fore-word first. Busybox is kind of unusual
And sure thing I forgot to Cc debian-boot@. I think if this needs
to be discussed further, debian-boot@ should receive it too.
Thanks!
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 14.11.2012 13:22, Laurent Joye wrote:
Hello,
I need to use the virtfs support of Qemu. Because the virtfs support is not
enabled in the latest versions (Debian testing), I still need to use an old
version (1.0.1).
This is a packaging error. In new qemu, additional
build dependency
Control: tags -1 + confirmed
On 16.12.2012 13:15, Tomas Martišius wrote:
Package: libiscsi1
Version: 1.4.0-3
Severity: wishlist
File: libiscsi
Dear Maintainer,
There are new new upstream version of libiscsi, please upgrade. Some
projects as proxmox depend on new wesion.
Yes I know
On 16.12.2012 14:23, Geert Stappers wrote:
Over here with version 1.1.2 I also get a
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Not much changed in MIPS emulation in 1.1.x stable series.
But I can't find the dumped core with
sudo find . -name *core*
Does
Source: qemu
Severity: serious
Tags: patch upstream pending
There's a long-standing bug in qemu's vmdk format handling, which may
lead to data corruption when using vmdk-format images. It is fixed
by upstream commit b1649fae49a899a222c3ac53c5009dd6f23349e1 .
Original thread:
Source: qemu
Severity: serious
Tags: upstream patch pending security
When guest does not enable large packet receiving from the qemu-emulated
e1000 device, and a large packet is received from the network, qemu will
happily transfer whole thing to guest, causing a guest buffer overflow.
This is
Package: qemu-kvm
Version: 1.1.2+dfsg-2
Severity: important
Tags: upstream patch pending
There's a small bug in ahci emulation which results, among others,
in some guests (eg windows 7) to not recognize emulated SATA drives,
asking for a driver disk during install.
This is fixed by upstream
Package: qemu-kvm
Version: 1.1.2+dfsg-2
Severity: normal
Tags: patch upstream pending
When qemu opens a tap device on host to configure networking, it
assumes that the device is not configured to use vnet header.
But this might not be the case with persistent tap devices, when
previously vnet
Package: qemu-kvm
Version: 1.1.2+dfsg-2
Severity: normal
Tags: upstream patch pending
This is a bug in e100 emulation in qemu, fixed by upstream commit
1069985fb132cd4324fc02d371f1e61492a1823f . Commit description says:
From: Bo Yang boy...@suse.com
Date: Wed, 29 Aug 2012 19:26:11 +0800
Package: qemu-kvm
Version: 1.1.2+dfsg-2
Severity: normal
Tags: upstream
From upstream qemu commit series intro message
(http://lists.gnu.org/archive/html/qemu-devel/2012-08/msg01594.html):
When the guests replenish the receive ring buffer, the network device
should flush its queue of
Control: tag -1 + moreinfo
On 20.04.2009 10:38, gulfstream wrote:
Package: qemu
Version: 0.10.1-1
Severity: normal
In order to use online bank services, I install a windowsxp in qemu
because it supports ie only. The transactions of online bank need a
usb token to encrypt and sign the
901 - 1000 of 2533 matches
Mail list logo
