FWIW, this bug tracker is not used for qemu for a long time. See
https://gitlab.com/qemu-project/qemu/ instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055003
Title:
Qemu cmdline core
Hi here!
What's the reason here to change the compile-time default value for the
usershare max shares (from 0 to 100) instead of just letting the admin
to configure this feature if they wants to? It is just a flip of a
single parameter in smb.conf.
I for one have to disable this debian-enabled
Oh wow!!! :)
Just as I said, q-b-e should also list qemu-utils as one of the
alternatives. This is the problem here, not the long list of other
alternatives you're trying to remove, but the single alternative - qemu-
utils - which is missing here. This one I'll fix right away. That's
really an
Actually this is fixed quite long time ago (but not in any released
stable version), in this commit:
commit 15bf92b50ca51e078575587bf0f26085d1ecbf88
Author: Michael Tokarev
Date: Wed Aug 18 16:43:23 2021 +0300
d/control: reformat Depends for qemu-block-extra, do not include -xen
version
nope, you're wrong.
qemu-block-extra is a set of plugins. This package is useless without one of
the other binary packages which can load these plugins. This is one of
qemu-system-foo, AND qemu-utils - that's the set of packages q-b-e should
depend on in order to actually work. And speaking of
FWIW, it looks to me that this issue is ought to be fixed in binfmt
package, not in all of its users.. This is a general issue for
containers, not only qemu is affected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well. This is definitely wrong. It is a valid bug, but it needs quite
serious work to fix, which requires major refactoring of the tcg code.
Upstream is working on it, see http://wiki.qemu.org/Features/tcg-
multithread
** Changed in: qemu
Status: Invalid => Confirmed
--
You received
Well. This is definitely wrong. It is a valid bug, but it needs quite
serious work to fix, which requires major refactoring of the tcg code.
Upstream is working on it, see http://wiki.qemu.org/Features/tcg-
multithread
** Changed in: qemu
Status: Invalid => Confirmed
--
You received
Looking at what? At the lack of problems as comment #14 says?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1025244
Title:
qcow2 image increasing disk size above the virtual
Looking at what? At the lack of problems as comment #14 says?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025244
Title:
qcow2 image increasing disk size above the virtual limit
To manage
I'm not sure I follow. I tried to answer to the last inquiry in this
bugreport, Eduardo asked if someone can confirm that +nx solves this
problem (it doesn't). Now you say with certainity that it is a bug in
TCG (if it is a bug, why only uncertain guesses are present in this
bugreport?),
I'm not sure I follow. I tried to answer to the last inquiry in this
bugreport, Eduardo asked if someone can confirm that +nx solves this
problem (it doesn't). Now you say with certainity that it is a bug in
TCG (if it is a bug, why only uncertain guesses are present in this
bugreport?),
This prob is still present in current (2.1) qemu, and it is NOT solved
by -cpu kvm64,+nx -- win bluescreens the same way.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/921208
Title:
I tried running qemu-system-x86 -cpu qemu64 with tcg and kvm, and
compared cpu flags. There are 2 flags present in kvm case which are not
present in tcg case: de and x2apic, all other flags are identical (nx is
present in both). But enabling these two flags explicitly does not
help, win still
This prob is still present in current (2.1) qemu, and it is NOT solved
by -cpu kvm64,+nx -- win bluescreens the same way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921208
Title:
win7/x64
I tried running qemu-system-x86 -cpu qemu64 with tcg and kvm, and
compared cpu flags. There are 2 flags present in kvm case which are not
present in tcg case: de and x2apic, all other flags are identical (nx is
present in both). But enabling these two flags explicitly does not
help, win still
Hmm. Speaking of wrong executables. We have another bugreport in
debian, -- https://bugs.debian.org/754336 -- which might be related. But
I tried qemu-2.1-rc and it didn't run these binaries. Is it not the
same thing? (The debian bugreport has sample files attached).
** Bug watch added:
Hmm. Speaking of wrong executables. We have another bugreport in
debian, -- https://bugs.debian.org/754336 -- which might be related. But
I tried qemu-2.1-rc and it didn't run these binaries. Is it not the
same thing? (The debian bugreport has sample files attached).
** Bug watch added:
It looks like libfte-dev before 1.4 was merely unusable because the
mentioned file - libfdt_env.h - is included by the main libfdt.h too,
even in version 1.3, so if libfdt_env.h is missing, libfdt-dev is simply
unusable. At least that's what it was on debian, see
http://bugs.debian.org/706137 .
It looks like libfte-dev before 1.4 was merely unusable because the
mentioned file - libfdt_env.h - is included by the main libfdt.h too,
even in version 1.3, so if libfdt_env.h is missing, libfdt-dev is simply
unusable. At least that's what it was on debian, see
http://bugs.debian.org/706137 .
FWIW, Debian (upstream qemu following) now finally switched to vgabios
from seabios (so bochs lgpl vgabios isn't used anymore), and seavgabios
now have the resolutions mentioned - it looks like we've added these
based on the patch for bochs vgabios mentioned here.
--
You received this bug
FWIW, Debian (upstream qemu following) now finally switched to vgabios
from seabios (so bochs lgpl vgabios isn't used anymore), and seavgabios
now have the resolutions mentioned - it looks like we've added these
based on the patch for bochs vgabios mentioned here.
--
You received this bug
I'm not sure x86*-linux-user targets are being tested at all. Last time
I checked, x86-64 variant crashed left and right to the point of being
completely unusable...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
I'm not sure x86*-linux-user targets are being tested at all. Last time
I checked, x86-64 variant crashed left and right to the point of being
completely unusable...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
doesn't qemu itself print an error message in this case before exiting?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1178884
Title:
unhelpful kvm error msg thrown when cache=none
doesn't qemu itself print an error message in this case before exiting?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178884
Title:
unhelpful kvm error msg thrown when cache=none and no direct IO
Thank you very much Peter for the work you did. That is not of historic
interest, not at all - it is of a good value for Debian users!
And thank you Nikolaus for the testing, as well!
I take your (both of you!) words that the problem is now solved, and am
uploading new release to debian
Thank you very much Peter for the work you did. That is not of historic
interest, not at all - it is of a good value for Debian users!
And thank you Nikolaus for the testing, as well!
I take your (both of you!) words that the problem is now solved, and am
uploading new release to debian
Peter, are you able to run git bisect or something like that, to try to
pinpoint either the commit which introduced this issue or which fixed
it?
I tried to reproduce this issue several times with various devices, but
I can't do it reliable, it always more or less works on my machine. If
I were
Peter, are you able to run git bisect or something like that, to try to
pinpoint either the commit which introduced this issue or which fixed
it?
I tried to reproduce this issue several times with various devices, but
I can't do it reliable, it always more or less works on my machine. If
I were
So closing it with fix released.
(which had a complication for me: I changed status for ubuntu package
instead of changing it for qemu line, and now I can't restore it back
for ubuntu - since I don't know how/when ubuntu bugs are closed, only
upstream)
** Changed in: qemu-kvm (Ubuntu)
FWIW, this is implemented and works in seabios 0.7.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/611142
Title:
seabios should have native scsi support
To manage notifications
by default images are expected to be open read-write. I'm against too
much intelligence here, -- we may be running qemu as wrong user, or
with wrong permissions of the image in question, and qemu should fail to
start if the image can't be open using specified access flags (which is
read-write by
There has been numerous reports/wishlists about removing features from
qemu. Different people consider different features to be undesirable.
But this is not how debian/ubuntu works: on these systems, packages are
built with as much as possible features (and hence external
dependencies). If you
FWIW, this is implemented and works in seabios 0.7.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/611142
Title:
seabios should have native scsi support
To manage notifications about this bug go
by default images are expected to be open read-write. I'm against too
much intelligence here, -- we may be running qemu as wrong user, or
with wrong permissions of the image in question, and qemu should fail to
start if the image can't be open using specified access flags (which is
read-write by
There has been numerous reports/wishlists about removing features from
qemu. Different people consider different features to be undesirable.
But this is not how debian/ubuntu works: on these systems, packages are
built with as much as possible features (and hence external
dependencies). If you
if x or y 0, set them to 0 (and decrement with/height accordingly)
If it is possible in this context to have negative x or y, it is also
possible to have them larger than width and heigth by absolute value, so
that when decrementing width/height accordingly, width/height becomes
negative too.
** Bug watch added: Debian Bug tracker #668186
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668186
** Also affects: qemu-kvm (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668186
Importance: Unknown
Status: Unknown
--
You received this bug notification because
busybox syslogd truncates input lines at 255 bytes. There's debian bug
report about this, #519356. In debian, we consider it is a
documentation bug, but indeed, it may be possible to increase buffer
size a bit.
** Bug watch added: Debian Bug tracker #519356
I see activity around this bug is going on and on, but I don't understand -- is
the talk about this patch --
http://anonscm.debian.org/gitweb/?p=collab-maint/qemu-kvm.git;a=commit;h=7e32b4ca0ea280a2e8f4d9ace1a15d5e633d9a95
?
--
You received this bug notification because you are a member of
I just wanted to point out that we've this patch in Debian since ages,
and it's been included in upstream for a long time too. Added a debbug
reference for this as well.
** Bug watch added: Debian Bug tracker #597517
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597517
** Also affects:
I see activity around this bug is going on and on, but I don't understand -- is
the talk about this patch --
http://anonscm.debian.org/gitweb/?p=collab-maint/qemu-kvm.git;a=commit;h=7e32b4ca0ea280a2e8f4d9ace1a15d5e633d9a95
?
--
You received this bug notification because you are a member of
I just wanted to point out that we've this patch in Debian since ages,
and it's been included in upstream for a long time too. Added a debbug
reference for this as well.
** Bug watch added: Debian Bug tracker #597517
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597517
** Also affects:
** Bug watch added: Debian Bug tracker #611134
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611134
** Also affects: qemu-kvm (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611134
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Bug watch added: Debian Bug tracker #611134
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611134
** Also affects: qemu-kvm (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611134
Importance: Unknown
Status: Unknown
--
You received this bug notification because
savevm _is_ slow, because it's writing to a qcow2 file with full
(meta)data allocation which is terrible slow since 0.13 (and 0.12.5)
unless you use cache=unsafe. It's the same slowdown as observed with
default cache mode when performing an operating system install into a
freshly created qcow2 -
savevm _is_ slow, because it's writing to a qcow2 file with full
(meta)data allocation which is terrible slow since 0.13 (and 0.12.5)
unless you use cache=unsafe. It's the same slowdown as observed with
default cache mode when performing an operating system install into a
freshly created qcow2 -
** Bug watch added: Debian Bug tracker #603223
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603223
** Also affects: qemu-kvm (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603223
Importance: Unknown
Status: Unknown
--
KVM segmentation fault, using
** Bug watch added: Debian Bug tracker #603223
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603223
** Also affects: qemu-kvm (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603223
Importance: Unknown
Status: Unknown
--
KVM segmentation fault, using
virtio disk is entrely different story, unrelated to this issue.
** Changed in: qemu
Status: Incomplete = Fix Committed
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of Ubuntu
Server Team, which is
virtio disk is entrely different story, unrelated to this issue.
** Changed in: qemu
Status: Incomplete = Fix Committed
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Does anyone else has similar problem? With 0.12.4 I were able to repeat
it. With 0.12.5 all winxp and win2003 installations, existing and new,
just work with either -drive or -hda or with virtio...
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug
Does anyone else has similar problem? With 0.12.4 I were able to repeat
it. With 0.12.5 all winxp and win2003 installations, existing and new,
just work with either -drive or -hda or with virtio...
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug
This is fixed by a backport of the mentioned patchset to stable-0.12
branch, in qemu git tree, see
http://git.savannah.gnu.org/gitweb/?p=qemu.git;a=commit;h=6394bd0e05441c363ebb73597c74c951378810e6
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug
This is fixed by a backport of the mentioned patchset to stable-0.12
branch, in qemu git tree, see
http://git.savannah.gnu.org/gitweb/?p=qemu.git;a=commit;h=6394bd0e05441c363ebb73597c74c951378810e6
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug
This appears to be fixed in 0.13-tobe by this patch:
http://lists.gnu.org/archive/html/qemu-devel/2010-07/msg00152.html
(hence it's fix released in debian which now has 0.13 in experimental).
** Bug watch added: Debian Bug tracker #588739
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588739
(and it is also filed agains debian qemu-kvm package, not just qemu --
http://bugs.debian.org/588739 )
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
This appears to be fixed in 0.13-tobe by this patch:
http://lists.gnu.org/archive/html/qemu-devel/2010-07/msg00152.html
(hence it's fix released in debian which now has 0.13 in experimental).
** Bug watch added: Debian Bug tracker #588739
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588739
(and it is also filed agains debian qemu-kvm package, not just qemu --
http://bugs.debian.org/588739 )
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
um. Can't you just take approach used in Debian, namely, to provide the
sources for the bios files and compile them at build time? That is
somewhat ugly, but at least it works...
--
kvm with -vga std is broken since karmic
https://bugs.launchpad.net/bugs/513273
You received this bug
um. Can't you just take approach used in Debian, namely, to provide the
sources for the bios files and compile them at build time? That is
somewhat ugly, but at least it works...
--
kvm with -vga std is broken since karmic
https://bugs.launchpad.net/bugs/513273
You received this bug
This is fixed by http://marc.info/?l=qemu-develm=127436114712437
--
kvm + virtio disk corrupts large volumes (1TB).
https://bugs.launchpad.net/bugs/574665
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
This is fixed by http://marc.info/?l=qemu-develm=127436114712437
--
kvm + virtio disk corrupts large volumes (1TB).
https://bugs.launchpad.net/bugs/574665
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It appears this bug (or similar) is back in 0.12. See Debian bug report
#580649 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580649 ).
** Bug watch added: Debian Bug tracker #580649
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580649
--
Block I/O crashes after migration
It appears this bug (or similar) is back in 0.12. See Debian bug report
#580649 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580649 ).
** Bug watch added: Debian Bug tracker #580649
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580649
--
Block I/O crashes after migration
This bug is present in kvm-0.11 and is fixed in 0.12. JFYI.
--
floating point exception when Windows NT 4 guest uses its cirrus driver
https://bugs.launchpad.net/bugs/59
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
This bug is present in kvm-0.11 and is fixed in 0.12. JFYI.
--
floating point exception when Windows NT 4 guest uses its cirrus driver
https://bugs.launchpad.net/bugs/59
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This is in fact reproduceable. I had the same issue too, was difficult
to debug (due to setuid-ness of the binary in question), but finally it
turned out to be wrong permissions for /dev/full (local config error
really) - it was 0660 instead of 0666, so unix_chkpwd was unable to open
it when run
69 matches
Mail list logo
