The results of comment 23 suggest that the issue is not 100%
reproducible. Can you please run the benchmark 3-4 times
(presave/postrestore) and showall 4 results? One benchmark only, e.g.
simple read will do.
Also please try putting a big file on disk (something like dd
if=/dev/zero of=bigfile
Can you please check if you have EPT enabled? This could be
https://bugzilla.kernel.org/show_bug.cgi?id=58771
** Bug watch added: Linux Kernel Bug Tracker #58771
http://bugzilla.kernel.org/show_bug.cgi?id=58771
--
You received this bug notification because you are a member of Ubuntu
Server
Oops, I missed Chris's comment #28. Thanks.
From comment #23, the 1.4 machine type seems to be fast, while 1.3 is
slow. This doesn't make much sense, given the differences between the
two machine types:
enable_compat_apic_id_mode();
.driver = usb-tablet,\
.property
Fixed in upstream commit 4e79bcbb96d3c189e50adbdac7b1e28d834ba43e.
** Changed in: qemu
Status: New = Fix Released
--
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/427612
To some extent it is a bug in the upstream kernel, which doesn't reset
state properly. However, the qemu patch is also good. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
** Changed in: qemu
Status: New = In Progress
** Changed in: qemu
Assignee: (unassigned) = Paolo Bonzini (bonzini)
--
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/1077838
Please try -global mc146818rtc.lost_tick_policy=slew.
--
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/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
Fix will be part of QEMU 1.7.0 (commit fc1c4a5, migration: drop
MADVISE_DONT_NEED for incoming zero pages, 2013-10-24).
** Changed in: qemu
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm
The patch is in 0.13.0, so changing the status.
** Changed in: qemu
Status: Invalid = Fix Released
--
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/524447
Title:
virsh save
** Also affects: libsdl1.2 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=317010
Importance: Unknown
Status: Unknown
--
does not pass pressed caps lock to client
https://bugs.launchpad.net/bugs/427612
You received this bug notification because you are a member of
The sdl patch was correctly submitted as
+SDL_UseLockKeys = getenv (SDL_DISABLE_LOCK_KEYS) == NULL;
...
+use_lock_keys = SDL_UseLockKeys;
...
+if (!use_lock_keys)
+break;
(i.e. by default do not change anything) but the maintainer apparently
The faulty patch indeed is only present until Karmic
(205_lock_keys.diff, not 005). I guess that then the best workaround is
to patch the karmic qemu-kvm as in comment #13.
--
does not pass pressed caps lock to client
https://bugs.launchpad.net/bugs/427612
You received this bug notification
This patch has already been nacked because caps lock works in every
other distro.
--
does not pass pressed caps lock to client
https://bugs.launchpad.net/bugs/427612
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
I'll download FreeBSD 9.2 and debug it. In the meanwhile, does it work
with an additional option -cpu Nehalem?
--
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/1251470
Title:
Guest not
** No longer affects: qemu
--
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/1307473
Title:
guest hang due to missing clock interrupt
To manage notifications about this bug go to:
** No longer affects: qemu
--
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/1379340
Title:
qemu-kvm guest panic for AMD smp trusty guests
To manage notifications about this bug go to:
The bug was reported on the Linux bugzilla and marked as invalid.
--
kernel overwrites MAP_PRIVATE mmap
https://bugs.launchpad.net/bugs/150920
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
This is a kernel bug. I could reproduce it with 2.6.20 and 2.6.22
(tested with i386 and x86-64).
1) Download http://www.inf.unisi.ch/phd/bonzini/smalltalk-2.95d.tar.gz
2) Compile it with ./configure make CFLAGS=-g (the cflags is only for
easier debuggability).
3) Run
** Also affects: debian
Importance: Undecided
Status: New
--
kernel overwrites MAP_PRIVATE mmap
https://bugs.launchpad.net/bugs/150920
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
(If a single line works while the full script doesn't, this might be a
bug in sed indeed).
--
sed crashes after special character in command
https://bugs.launchpad.net/bugs/452620
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
What is the exact content (in binary) of the script?
What is $LANG, $LC_ALL and $LC_CTYPE?
--
sed crashes after special character in command
https://bugs.launchpad.net/bugs/452620
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
If you don't know the charset of the file, you should set the LANG or
LC_CTYPE variables to C:
$ echo $'\x88' | sed -e 's/[^0123456789]//g' | od -x
000 0a88
002
$ echo $'\x88' | LANG=C sed -e 's/[^0123456789]//g' | od -x
000 000a
001
This is different from Perl
sed 4.2 will provide --follow-symlinks, for now it is a feature that you
cannot turn off. Sorry.
--
sed -i destroys symlink
https://bugs.launchpad.net/bugs/367211
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Fixed upstream by 8819a0d5
diff --git a/gst-tool.c b/gst-tool.c
index 642cdb7..1d6a464 100644
--- a/gst-tool.c
+++ b/gst-tool.c
@@ -338,7 +338,7 @@ parse_short_options (const char *name, const char *arg)
}
else /* if (have_arg == OPT_MANDATORY) */
-option_error (expected
Public bug reported:
Configure scripts that used to use --print-multi-os-directory to find
.so files (e.g. GNU Smalltalk's) do not have an alternative way that
they can use with multiarch. -print-multiarch is in gcc 4.6, but not in
4.5.
Introduction of multiarch broke 20 years worth of
I still see occasional errors:
[33945.269075] ecryptfs_decrypt_page: Error attempting to read lower page; rc =
[-4]
[33945.269084] ecryptfs_readpage: Error decrypting page; rc = [-4]
that are reported as short read: Success when doing a git grep on an
encrypted repository. Redoing the grep
The EINTR is not passed up, and leaves bad data in the cache as if
ecryptfs thought the files were not encrypted. This is what causes the
short writes. Getting an strace is quite difficult, but this time I
succeeded:
lstat(include/asm-ia64/ia64_int.h, {st_mode=S_IFREG|0664, st_size=12288,
Can you please update the patch so that it avoids spamming the kernel
log upon EINTR?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/509180
Title:
ecryptfs sometimes seems to add trailing garbage to
I'm seeing errors like this in /var/log/messages at the same time as
corruptions:
Feb 9 14:03:26 yakj kernel: [135241.310137]
ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4]
Feb 9 14:03:26 yakj kernel: [135241.310146] ecryptfs_decrypt_page: Error
attempting to
I'll apply the patch myself, thanks. But I think hunks are missing for
the other two functions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/521523
Title:
severe ecryptfs corruption
--
Here is the actual patch I am testing.
** Patch added: Patch that should fix the bug (still untested)
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/521523/+attachment/1850991/+files/ecryptfs-fix-eintr.patch
--
You received this bug notification because you are a member of
Yes, it is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/521523
Title:
severe ecryptfs corruption
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Patch http://launchpadlibrarian.net/64378182/ecryptfs-fix-eintr.patch
from bug 521523 seems to work for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/509180
Title:
ecryptfs sometimes seems to
Added new Bug tracker which has a patch attached.
** Bug watch added: GNOME Bug Tracker #640082
https://bugzilla.gnome.org/show_bug.cgi?id=640082
** Changed in: vinagre
Importance: Wishlist = Unknown
** Changed in: vinagre
Status: Invalid = Unknown
** Changed in: vinagre
Remote
Agreed, let's close this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/521523
Title:
severe ecryptfs corruption
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have many GB of free space and I get random stuff added at the end of
files. git repositories seem to be more susceptible to this. Next time
it happens I'll make sure to check how many bytes are added and other
suspicious things (e.g. whether the full size becomes close to a 4kb
multiple or
Any git repository I use heavily (mostly kernel, Xen and qemu in my
case, but it is not relevant I think) will corrupt at least once a day,
as proved from the fact that I just reproduced it. :) Probably
interactive rebases and switching branches help.
However, I don't know how to make the error
I'm not using Ubuntu, so adding parent ecryptfs product.
** Also affects: ecryptfs
Importance: Undecided
Status: New
** Changed in: ecryptfs
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
2.6.35.10 is the Fedora 14 kernel. I can upgrade to a newer 2.6.37
kernel if you want me to test that, but I don't see anything relevant in
the log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This patch has already been nacked because caps lock works in every
other distro.
--
does not pass pressed caps lock to client
https://bugs.launchpad.net/bugs/427612
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Also affects: libsdl1.2 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=317010
Importance: Unknown
Status: Unknown
--
does not pass pressed caps lock to client
https://bugs.launchpad.net/bugs/427612
You received this bug notification because you are a member of
The sdl patch was correctly submitted as
+SDL_UseLockKeys = getenv (SDL_DISABLE_LOCK_KEYS) == NULL;
...
+use_lock_keys = SDL_UseLockKeys;
...
+if (!use_lock_keys)
+break;
(i.e. by default do not change anything) but the maintainer apparently
The error message is ugly, but the bug is that the script is not valid
UTF-8, it is encoded as ISO-8859-1. When you create the line in a new
script, vi saves it as UTF-8 for you.
Run sed with LANG=en_US.ISO-8859-1 or with LANG=C instead.
** Changed in: sed (Ubuntu)
Status: New = Invalid
** Changed in: sed (Ubuntu)
Status: New = Invalid
--
sed stops replacing when reaching a special character
https://bugs.launchpad.net/bugs/447866
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Fixed in karmic thanks to update to sed-4.2.1
** Changed in: sed (Ubuntu)
Status: New = Fix Released
--
sed -i destroys symlink
https://bugs.launchpad.net/bugs/367211
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Fixed in 4.2.1 which is included in karmic.
** Changed in: sed (Ubuntu)
Status: Confirmed = Fix Released
--
sed: In-place editing (-i flag) drops EA (ACLs and user-defined)
https://bugs.launchpad.net/bugs/25921
You received this bug notification because you are a member of Ubuntu
Bugs,
Agreed since sed's man page is pretty complete. As they say, patches are
welcome. :-)
--
sed manpage does not document I modifier (case insensitive)
https://bugs.launchpad.net/bugs/330735
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The faulty patch indeed is only present until Karmic
(205_lock_keys.diff, not 005). I guess that then the best workaround is
to patch the karmic qemu-kvm as in comment #13.
--
does not pass pressed caps lock to client
https://bugs.launchpad.net/bugs/427612
You received this bug notification
The patch is in 0.13.0, so changing the status.
** Changed in: qemu
Status: Invalid = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/524447
Title:
virsh save is very slow
--
I am seeing these messages whenever I have two processes reading the
same file. Note that write access is not necessary.
The simplest way to reproduce it is
git grep abczzz git grep abczzz
but this is probably because git uses multiple threads, rather than
because the bug is related to
To some extent it is a bug in the upstream kernel, which doesn't reset
state properly. However, the qemu patch is also good. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1077838
Title:
** Changed in: qemu
Status: New = In Progress
** Changed in: qemu
Assignee: (unassigned) = Paolo Bonzini (bonzini)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1077838
Title:
qemu-nbd
NAT networking is provided by libvirt, changing the package.
** Project changed: qemu = libvirt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078305
Title:
source IP address of broadcast
Please try -global mc146818rtc.lost_tick_policy=slew.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174654
Title:
qemu-system-x86_64 takes 100% CPU after host machine resumed from
suspend to ram
The results of comment 23 suggest that the issue is not 100%
reproducible. Can you please run the benchmark 3-4 times
(presave/postrestore) and showall 4 results? One benchmark only, e.g.
simple read will do.
Also please try putting a big file on disk (something like dd
if=/dev/zero of=bigfile
Can you please check if you have EPT enabled? This could be
https://bugzilla.kernel.org/show_bug.cgi?id=58771
** Bug watch added: Linux Kernel Bug Tracker #58771
http://bugzilla.kernel.org/show_bug.cgi?id=58771
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Oops, I missed Chris's comment #28. Thanks.
From comment #23, the 1.4 machine type seems to be fast, while 1.3 is
slow. This doesn't make much sense, given the differences between the
two machine types:
enable_compat_apic_id_mode();
.driver = usb-tablet,\
.property
There's no such thing as a virtio-blk CD-ROM, only hard-disks. For
installation it shouldn't matter, since .iso images usually can work
also as hard-disk images (for putting them on a USB stick).
If you want to test installation from a real virtio CD-ROM, use
virtio-scsi:
-drive
It seems the installer does not consider virtio devices when doing its
search.
That's another bug in the installer then.
it seems a bit wasteful to go through a layer of scsi emulation.
Indeed treating the virtio disk similarly to installation from a USB
stick is better, but SCSI emulation is
if=virtio means virtio-blk, not virtio-something.
Also, Linux is perfectly fine with ISO images on virtio, the Ubuntu
installer is wrong in not scanning virtio disks. Since Ubuntu wouldn't
work either way, they should first fix the installer and then we can re-
evaluate if QEMU can do something
The media argument seems a perfectly natural
way to select between the two.
Then how do you distinguish between a virtio-scsi and a virtio-blk hard
disk? These may even require changes to the guest, since one becomes
/dev/vda and the other becomes /dev/sda.
virtio-scsi will grow more and more
Fix will be part of QEMU 1.7.0 (commit fc1c4a5, migration: drop
MADVISE_DONT_NEED for incoming zero pages, 2013-10-24).
** Changed in: qemu
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed in upstream commit 4e79bcbb96d3c189e50adbdac7b1e28d834ba43e.
** Changed in: qemu
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/427612
Title:
kvm sends caps
I'll download FreeBSD 9.2 and debug it. In the meanwhile, does it work
with an additional option -cpu Nehalem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251470
Title:
Guest not working in KVM
You don't need +xsave, -cpu host just works.
The bug is invalid. You are requesting a CPU that doesn't exist (a
core2duo that supports XSAVE), and the guest's behavior is probably not
going to be well defined.
** Changed in: qemu
Status: New = Invalid
--
You received this bug
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379340
Title:
qemu-kvm guest panic for AMD smp trusty guests
To manage notifications about this bug go to:
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock interrupt
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1346917 ***
https://bugs.launchpad.net/bugs/1346917
Fred, this bug is for STOP 0x101, not STOP 0x5c.
STOP 0x101 cannot be fixed by an upgrade. You have to disable the
watchdog using QEMU option hv_relaxed or the equivalent in libvirt.
--
You received this
Can you reproduce with other 16-bit applications (e.g. skifree from
http://ski.ihoc.net/#download)?
--
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/1404396
Title:
[regression] vgabios
Can you reproduce with other 16-bit applications (e.g. skifree from
http://ski.ihoc.net/#download)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404396
Title:
[regression] vgabios - seabios
Also, can you attach a screenshot of the 16-bit application with
vgabios, so we can have a clue of why the vgabios is involved?
--
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/1404396
Also, can you attach a screenshot of the 16-bit application with
vgabios, so we can have a clue of why the vgabios is involved?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404396
Title:
Fixed in QEMU 2.4.
** Changed in: qemu
Status: New => Fix Released
--
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/1465935
Title:
kvm_irqchip_commit_routes: Assertion `ret ==
Fixed in QEMU 2.4.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1465935
Title:
kvm_irqchip_commit_routes: Assertion `ret == 0' failed
To
> Especially I found that the "created on Trusty, migrated to xenial
> (works), but later migrated back to trusty (fails)" seems affected by
> it as well.
The first migration of the t->x->t sequence does not really matter (if
anything it could introduce _more_ bugs!), so if x->t is not supported
75 matches
Mail list logo
