After getting the bug mail for this bug and reading it with interest, I
happened to run into this issue today myself and did some investigation
at a seabios level.
My original hit of the issue was with RHEL, but I reproduced it with the
same card (Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
Steve,
Looks like the latest version of the patch was not applied (libvirt
maintainers applied a modified patch to upstream that fixed a couple
more memory leaks.
This version does work, but I know others still had some lingering
problems that I couldn't reproduce.
The patch they are now using
Attached is proposed debdiff for SRU.
Also includes updated patch for Bug #571093
** Description changed:
I was testing attaching and detaching an AoE block device and all was
going fine until I tried to attach a device twice in a row without
changing the target device. Doing so resulted
I've included the attached patch in an SRU candidate for Bug #455832,
you can view the proposed debdiff there.
** Patch added: 9024-free-memory-for-invalid-devices.patch
I can confirm this is an issue in Lucid w/ qemu-kvm 0.12.3+noroms-
0ubuntu9.
Microsoft Kbase has a little bit of details of specifically is likely to
be wrong, at http://support.microsoft.com/kb/314830 (browse down to
0x0011)
--
Windows Server 2008 won't boot with more than 4 vCPUs
I've had a bit more of a look...
I have been experimenting w/ Windows 2008 64-bit original release
installing the Enterprise edition.
Lucid ships with seabios 0.5.1-0ubuntu2 which experiences the issue.
Maverick ships with seabios 0.6.0-0ubuntu1 which from my testing doesn't.
I did a quick
** Changed in: seabios (Ubuntu)
Status: New = Confirmed
--
Windows Server 2008 won't boot with more than 4 vCPUs
https://bugs.launchpad.net/bugs/589063
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
I isolated fix to upstream patch
http://git.linuxtogo.org/?p=kevin/seabios.git;a=blobdiff;f=src/acpi.c;h=244536a276ae360f016e58b2eefaee83654abd75;hp=f613b034120d3595f9e9c4104acffbeae8dbd228;hb=3012af189e0f89bd33df1c0711a46f098053e9a7;hpb=92a5742b5f9f217ba6315fa13d075ba98ebc3fd6
If someone wants
I was going to try and get hold of Dustin via IRC, but I wasn't able to.
I'm not sure how this package fits into the Server SRU picture, and I'm
not really in a position to call how safe an ACPI change like this on
it's own is (although, this was the first of only a few that I can tell
between
Thanks for the testing Troy.
Just attaching the individual patch from the debdiff for now, I'll check
w/ the Server Team regarding getting this as an SRU.
** Patch added: Patch included in SRU Debdiff
0001-fix-PkgLength-calculation-for-the-SSDT.patch
I've done a bit of digging here:
I encounter the issue in both Lucid and Maverick.
gdb on the generated core, w/ a 'bt' shows:
snip
#2 0x0046f2c5 in oom_check (size=value optimised out)
at qemu-malloc.c:30
#3 qemu_malloc (size=value optimised out) at qemu-malloc.c:59
#4
Upstream have fixed this in commit
d6fa4b77fb8f27ac84cf23fb1e15016673d98a47
Which I have modified for what we currently have in Lucid Maverick,
the patch seems to apply cleanly.
Tested with Maverick already and seems to be fine.
** Patch added: Proposed patch from upstream git
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
kvm -initrd 'file' dumps core if 'file' does not exist
https://bugs.launchpad.net/bugs/619302
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
I can confirm this on a clean install from the Maverick 20100816 Desktop
CD Build (will update shortly in case another update has fixed it), I
have a feeling that this might be an X bug.
Running via virt-manager I get exactly the same output as Dave, however
when running from a gnome-terminal
More testing: only happens if XAUTHORITY is set as an environment
variable it seems, an interesting thing to note is that xhost doesn't
work either, so it doesn't look like an AIGLX bug (I disabled it) but it
does look X related.
--
[Maverick] SDL local window broken in last update
** Tags added: regression-potential
--
[Maverick] SDL local window broken in last update
https://bugs.launchpad.net/bugs/615077
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
I've tagged the bug regression-potential as it looks like a regression
between Lucid Maverick, here is what I know from reproducing:
Reproduction:
Bug can be reproduced by creating (in virt-manager) on a clean Maverick
install, by creating a virtual machine, editing the configuration (using
** Attachment added: strace Output - parent process
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/615077/+attachment/1531966/+files/qemuregbroke.1904.gz
--
[Maverick] SDL local window broken in last update
https://bugs.launchpad.net/bugs/615077
You received this bug notification
FYI: The uploaded package still works:
njo...@fantail:~$ apt-cache policy libvirt-bin
libvirt-bin:
Installed: 0.7.5-5ubuntu27.3
Candidate: 0.7.5-5ubuntu27.3
Version table:
*** 0.7.5-5ubuntu27.3 0
500 http://nz.archive.ubuntu.com/ubuntu/ lucid-proposed/main Packages
100
I've tested this bug again w/ the new patch, it is working fine as
expected for me, w/ no increase of RES memory while running the
multipath commands to add/remove devices in udev.
Looks ready to me (and w/ my testing of bug #455832), it should be ready
for pushing.
--
[SRU] multipath +
** Tags added: verification-done
** Tags removed: verification-needed
--
[SRU] multipath + libvirtd eats away more memory over time
https://bugs.launchpad.net/bugs/571093
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
To be clear, when I said FYI: The uploaded package still works: I had
meant:
The uploaded package contains the correct fix.
The 'target vdc already exists' error message is the correct error
message for this patch.
** Tags added: verification-done
** Tags removed: verification-needed
--
I've done a bit of an experiment and this is what I've found:
Running valgrind on libvirtd -v ($ sudo valgrind -v --leak-check=full
--show-reachable=yes /usr/sbin/libvirtd -v) produced the output in
lp571093-libvirt-val-run1
A quick summary:
==15520== 78,696 (18,048 direct, 60,648 indirect)
Some more investigation:
--technical bits-- (non tech lower down)
libvirtd debug logging (attached) shows running multipath -F/multipath
-v4 does the following:
14:02:28.570: debug : udevEventHandleCallback:1363 : udev action: 'add'
14:02:28.570: info : udevGetDeviceProperty:111 : udev reports
I've had another look at this bug, reproducing etc, this time through
GDB, with the output from valgrind the debug output in my last two
posts, here is what I believe is happening:
1. multipath -v4 gets called (or other appropriate trigger)
- multipath detects a device that it believes is new,
Okay, I've created a patch that should fix the issue in two ways, first
as observed in my previous comment I suspected that adding a
virNodeDeviceDefFree(def) to udevAddOneDevice() would solve the issue,
it for the most part did but still left approximately an 8k RES memory
leak.
Looking at the
Public bug reported:
Binary package hint: multipath-tools
Environment:
njo...@fantail:~$ lsb_release -rd
Description:Ubuntu 10.04 LTS
Release:10.04
njo...@fantail:~$ apt-cache policy multipath-tools
multipath-tools:
Installed: 0.4.8-14ubuntu4
Candidate: 0.4.8-14ubuntu4
Version
I have forwarded the bug/patch to Debian BTS as http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=582965 so they can incorporate the fix there.
** Bug watch added: Debian Bug tracker #582965
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582965
** Also affects: libvirt (Debian) via
I had a look at this bug and I seem to have prevented it, i.e.:
njo...@fantail:~$ cat /tmp/455832.xml
disk type='block'
driver name='virtio'/
source dev='/dev/sdd'/
target dev='vdc' bus='virtio'/
/disk
(sdd is a USB stick)
Before patch:
njo...@fantail:~$ virsh list; virsh destroy
Also, I forgot to mention in my previous comment, I'm yet to determine
if this also affects the current release of libvirt.
--
segfault when attaching disk with same physical device
https://bugs.launchpad.net/bugs/455832
You received this bug notification because you are a member of Ubuntu
** Tags added: patch
--
segfault when attaching disk with same physical device
https://bugs.launchpad.net/bugs/455832
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
Ariel,
What was the previous rate of increase?
I don't personally have the hardware to reproduce the issue (looks like
ocfs2 + EMC SAN based on your udev output), so could you maybe provide
the following:
* valgrind -v --leak-check=full --show-reachable=yes /usr/sbin/libvirtd -v
(Once it's
Just to note, this appears to be working out of the box with current
Maverick packages for me, there appears to be quite a few changes to NTP
packaging as well.
--
Date not updated by ntp when network interfaces started
https://bugs.launchpad.net/bugs/567701
You received this bug notification
Yes, as stated in my original comment, it is reproducible (myself and
Dustin Kirkland), with variants of while true; do sudo multipath -F;
sudo multipath -v4 ; done.
All that is required is a device that multipath will create a
/dev/mapper entry for (use_friendly_names or not) and remove with -F
Since SPICE was introduced into Debian, it was picked up for Oneiric and
Precise, so I'm going to close the bug as it no longer needs packaging.
** Changed in: ubuntu
Assignee: Nigel Jones (dev-nigelj) = (unassigned)
** Changed in: ubuntu
Status: In Progress = Fix Released
--
You
Thanks to micahg geser on IRC, it seems what has happened (and quoting
from the bugs.debian.org bug I just submitted...) is:
It was noticed [...] with the LDAP linker bug patched (the same patch
as in Debian Bug #556770), that the patches do not get properly applied
by dpkg-buildpackage, when it
Hi Mahyuddin,
I realise you were assigned to the bug, but as I hadn't seen any
activity I went ahead and incorporated the patch that Gentoo used for
http://bugs.gentoo.org/show_bug.cgi?id=333425 (attachment
http://bugs.gentoo.org/attachment.cgi?id=258946action=diff), which
fixes the FTBFS issue.
Since Oneiric is now the dev target, I've created a merge proposal for
1:1.8.4-3 (current Debian version) to be entered into Ubuntu.
** Changed in: zabbix (Ubuntu)
Status: Incomplete = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
There seems to be a Ubuntu PPA package for pino in
https://launchpad.net/~troorl/+archive/pino
--
[needs-packaging] Pino
https://bugs.launchpad.net/bugs/574059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can't change the status of the bug, but I have myself begun working on
this, I am somewhat familiar with the workings on SPICE.
--
[needs-packaging] SPICE
https://bugs.launchpad.net/bugs/500385
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: ubuntu
Assignee: (unassigned) = Nigel Jones (dev-nigelj)
** Changed in: ubuntu
Status: New = In Progress
--
[needs-packaging] SPICE
https://bugs.launchpad.net/bugs/500385
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I've done a bit of an experiment and this is what I've found:
Running valgrind on libvirtd -v ($ sudo valgrind -v --leak-check=full
--show-reachable=yes /usr/sbin/libvirtd -v) produced the output in
lp571093-libvirt-val-run1
A quick summary:
==15520== 78,696 (18,048 direct, 60,648 indirect)
** Description changed:
MDC (Multiple Direct Communicator) - is a versatile multi-messenger with
support for operating systems Windows, Linux, MacOS X and protocols,
ICQ, Mail.Agent, Jabber, and others an intuitive interface, storage
history on the server, combining contacts from
Some more investigation:
--technical bits-- (non tech lower down)
libvirtd debug logging (attached) shows running multipath -F/multipath
-v4 does the following:
14:02:28.570: debug : udevEventHandleCallback:1363 : udev action: 'add'
14:02:28.570: info : udevGetDeviceProperty:111 : udev reports
FYI: The uploaded package still works:
njo...@fantail:~$ apt-cache policy libvirt-bin
libvirt-bin:
Installed: 0.7.5-5ubuntu27.3
Candidate: 0.7.5-5ubuntu27.3
Version table:
*** 0.7.5-5ubuntu27.3 0
500 http://nz.archive.ubuntu.com/ubuntu/ lucid-proposed/main Packages
100
I've tested this bug again w/ the new patch, it is working fine as
expected for me, w/ no increase of RES memory while running the
multipath commands to add/remove devices in udev.
Looks ready to me (and w/ my testing of bug #455832), it should be ready
for pushing.
--
[SRU] multipath +
** Tags added: verification-done
** Tags removed: verification-needed
--
[SRU] multipath + libvirtd eats away more memory over time
https://bugs.launchpad.net/bugs/571093
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
To be clear, when I said FYI: The uploaded package still works: I had
meant:
The uploaded package contains the correct fix.
The 'target vdc already exists' error message is the correct error
message for this patch.
** Tags added: verification-done
** Tags removed: verification-needed
--
I've had another look at this bug, reproducing etc, this time through
GDB, with the output from valgrind the debug output in my last two
posts, here is what I believe is happening:
1. multipath -v4 gets called (or other appropriate trigger)
- multipath detects a device that it believes is new,
Okay, I've created a patch that should fix the issue in two ways, first
as observed in my previous comment I suspected that adding a
virNodeDeviceDefFree(def) to udevAddOneDevice() would solve the issue,
it for the most part did but still left approximately an 8k RES memory
leak.
Looking at the
Public bug reported:
Binary package hint: multipath-tools
Environment:
njo...@fantail:~$ lsb_release -rd
Description:Ubuntu 10.04 LTS
Release:10.04
njo...@fantail:~$ apt-cache policy multipath-tools
multipath-tools:
Installed: 0.4.8-14ubuntu4
Candidate: 0.4.8-14ubuntu4
Version
I have forwarded the bug/patch to Debian BTS as http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=582965 so they can incorporate the fix there.
** Bug watch added: Debian Bug tracker #582965
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582965
** Also affects: libvirt (Debian) via
I had a look at this bug and I seem to have prevented it, i.e.:
njo...@fantail:~$ cat /tmp/455832.xml
disk type='block'
driver name='virtio'/
source dev='/dev/sdd'/
target dev='vdc' bus='virtio'/
/disk
(sdd is a USB stick)
Before patch:
njo...@fantail:~$ virsh list; virsh destroy
Also, I forgot to mention in my previous comment, I'm yet to determine
if this also affects the current release of libvirt.
--
segfault when attaching disk with same physical device
https://bugs.launchpad.net/bugs/455832
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: patch
--
segfault when attaching disk with same physical device
https://bugs.launchpad.net/bugs/455832
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I can confirm this is an issue in Lucid w/ qemu-kvm 0.12.3+noroms-
0ubuntu9.
Microsoft Kbase has a little bit of details of specifically is likely to
be wrong, at http://support.microsoft.com/kb/314830 (browse down to
0x0011)
--
Windows Server 2008 won't boot with more than 4 vCPUs
I've had a bit more of a look...
I have been experimenting w/ Windows 2008 64-bit original release
installing the Enterprise edition.
Lucid ships with seabios 0.5.1-0ubuntu2 which experiences the issue.
Maverick ships with seabios 0.6.0-0ubuntu1 which from my testing doesn't.
I did a quick
** Changed in: seabios (Ubuntu)
Status: New = Confirmed
--
Windows Server 2008 won't boot with more than 4 vCPUs
https://bugs.launchpad.net/bugs/589063
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I isolated fix to upstream patch
http://git.linuxtogo.org/?p=kevin/seabios.git;a=blobdiff;f=src/acpi.c;h=244536a276ae360f016e58b2eefaee83654abd75;hp=f613b034120d3595f9e9c4104acffbeae8dbd228;hb=3012af189e0f89bd33df1c0711a46f098053e9a7;hpb=92a5742b5f9f217ba6315fa13d075ba98ebc3fd6
If someone wants
I was going to try and get hold of Dustin via IRC, but I wasn't able to.
I'm not sure how this package fits into the Server SRU picture, and I'm
not really in a position to call how safe an ACPI change like this on
it's own is (although, this was the first of only a few that I can tell
between
Thanks for the testing Troy.
Just attaching the individual patch from the debdiff for now, I'll check
w/ the Server Team regarding getting this as an SRU.
** Patch added: Patch included in SRU Debdiff
0001-fix-PkgLength-calculation-for-the-SSDT.patch
I've done a bit of digging here:
I encounter the issue in both Lucid and Maverick.
gdb on the generated core, w/ a 'bt' shows:
snip
#2 0x0046f2c5 in oom_check (size=value optimised out)
at qemu-malloc.c:30
#3 qemu_malloc (size=value optimised out) at qemu-malloc.c:59
#4
Upstream have fixed this in commit
d6fa4b77fb8f27ac84cf23fb1e15016673d98a47
Which I have modified for what we currently have in Lucid Maverick,
the patch seems to apply cleanly.
Tested with Maverick already and seems to be fine.
** Patch added: Proposed patch from upstream git
** Changed in: qemu-kvm (Ubuntu)
Status: New = Confirmed
--
kvm -initrd 'file' dumps core if 'file' does not exist
https://bugs.launchpad.net/bugs/619302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I can confirm this on a clean install from the Maverick 20100816 Desktop
CD Build (will update shortly in case another update has fixed it), I
have a feeling that this might be an X bug.
Running via virt-manager I get exactly the same output as Dave, however
when running from a gnome-terminal
More testing: only happens if XAUTHORITY is set as an environment
variable it seems, an interesting thing to note is that xhost doesn't
work either, so it doesn't look like an AIGLX bug (I disabled it) but it
does look X related.
--
[Maverick] SDL local window broken in last update
** Tags added: regression-potential
--
[Maverick] SDL local window broken in last update
https://bugs.launchpad.net/bugs/615077
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I've tagged the bug regression-potential as it looks like a regression
between Lucid Maverick, here is what I know from reproducing:
Reproduction:
Bug can be reproduced by creating (in virt-manager) on a clean Maverick
install, by creating a virtual machine, editing the configuration (using
** Attachment added: strace Output - parent process
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/615077/+attachment/1531966/+files/qemuregbroke.1904.gz
--
[Maverick] SDL local window broken in last update
https://bugs.launchpad.net/bugs/615077
You received this bug notification
** Attachment added: strace Output - forked process
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/615077/+attachment/1531976/+files/qemuregbroke.1905
--
[Maverick] SDL local window broken in last update
https://bugs.launchpad.net/bugs/615077
You received this bug notification
Sorry, I forgot to mention that since my bug report, it has been fixed
upstream, looks like:
commit eebf932e9418b8a626488ced40294e4f5d580e49
Author: Jim Meyering meyer...@redhat.com
Date: Wed Dec 16 14:15:50 2009 +0100
qemu_driver.c: avoid NULL dereference upon disk-op failure
*
Attached is proposed debdiff for SRU.
Also includes updated patch for Bug #571093
** Description changed:
I was testing attaching and detaching an AoE block device and all was
going fine until I tried to attach a device twice in a row without
changing the target device. Doing so resulted
I've included the attached patch in an SRU candidate for Bug #455832,
you can view the proposed debdiff there.
** Patch added: 9024-free-memory-for-invalid-devices.patch
Steve,
Looks like the latest version of the patch was not applied (libvirt
maintainers applied a modified patch to upstream that fixed a couple
more memory leaks.
This version does work, but I know others still had some lingering
problems that I couldn't reproduce.
The patch they are now using
Public bug reported:
Binary package hint: nautilus
- Lucid Lynx 10.04 LTS
- Nautilus Version
Installed: 1:2.30.1-0ubuntu1.1
Candidate: 1:2.30.1-0ubuntu1.1
- After, creating a new folder, which appeared under the download
folder, I expected that it would create a new folder that was
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/53049046/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/53049047/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/53049048/ProcStatus.txt
** Attachment
Public bug reported:
Binary package hint: gnome-media
- Ubuntu Lucid Lynx 10.04 LTS
- I'm using the default volume control on a gnome desktop.
gnome-media:
Installed: 2.30.0-0ubuntu1
Candidate: 2.30.0-0ubuntu1
- I expected the volume control button to make my volume go as loud as
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/53050074/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/53050075/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/53050076/ProcStatus.txt
** Attachment
Ariel,
What was the previous rate of increase?
I don't personally have the hardware to reproduce the issue (looks like
ocfs2 + EMC SAN based on your udev output), so could you maybe provide
the following:
* valgrind -v --leak-check=full --show-reachable=yes /usr/sbin/libvirtd -v
(Once it's
Just to note, this appears to be working out of the box with current
Maverick packages for me, there appears to be quite a few changes to NTP
packaging as well.
--
Date not updated by ntp when network interfaces started
https://bugs.launchpad.net/bugs/567701
You received this bug notification
Yes, as stated in my original comment, it is reproducible (myself and
Dustin Kirkland), with variants of while true; do sudo multipath -F;
sudo multipath -v4 ; done.
All that is required is a device that multipath will create a
/dev/mapper entry for (use_friendly_names or not) and remove with -F
After getting the bug mail for this bug and reading it with interest, I
happened to run into this issue today myself and did some investigation
at a seabios level.
My original hit of the issue was with RHEL, but I reproduced it with the
same card (Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
Have now
- enabled trim (across lvm/filesystem/crypt) since primary drive is SSD
- ran full fsck (clean)
- switched to 3.7.5 kernel
as the hangs continued on 3.5
Note that I did get a hang with the 3.8 kernel but couldn't prove
(*through logs*) it was the same hang...
--
You received this
Updated to 3.7.6 (since I noticed it out). It's possible the
cleanup/trim/late kernel has resolved. Need to give it a few more days
(system wasn't used over weekend)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I'm periodically (every few days) getting a hang on my Thinkpad W500
running Ubuntu 12.10+updates whereby the system freezes for a few
minutes. During this time the mouse pointer won't work, music either
loops or stops
Checking the kernel syslog I see the following as the
** Attachment added: Kernel log -- not just time of latest occurance but boot
etc too
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1105010/+attachment/3499876/+files/kern.log.1105010.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Not sure if relevant but note I'm also using LUKS full disk encription
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1105010
Title:
INFO: Task blocked for more than 120 seconds
To manage
Ok. Now running with upstream kernel to see if problem still occurs.
Will report back
Linux jonesn-ThinkPad-W500 3.8.0-030800rc5-generic #201301251535 SMP Fri
Jan 25 20:36:24 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
In the energy saving applet on kubuntu 15.04 I have the dim screen
checkbox marked (5 minutes)
If I leave the computer untouched for this period of time, the screen
correctly dims.
However it does not restore to nornal brightness when the computer is
used - ie keyboard
Just raising the same issue.. if believed different please say I'll
open new. Again ubuntu 15.04 with upstream, cannot suspend - cause
located to invtsc being added to the command line +invtsc after
using the copy host configuration in virt-manager. I did also try
changing policy to disable in
Updated package to qemu after testing against the packages in
https://launchpad.net/ubuntu/+source/qemu (2.3 debs). With these
installed this bug does not occur. Note that I did remove USB
controller/redirector and changed spice-vnc in order to get the vm to
start since these 2.3 packages as of 8
Updated package to qemu after testing against the packages in
https://launchpad.net/ubuntu/+source/qemu (2.3 debs). With these
installed this bug does not occur. Note that I did remove USB
controller/redirector and changed spice-vnc in order to get the vm to
start since these 2.3 packages as of 8
qemu 2.3.1 appears to fix this, though see
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1472571 for the
new problem (unrelated) it causes. There is also no supported fix for
15.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I am running Ubuntu 15.04 (not 15.10/dev). Due to another bug in qemu
2.2 I decided to try the 2.3.1 packages (from build here). I realise
there is potential dependency issues and the config is likely untested.
However as this could be a genuin issue, I wanted to report that
for reference this was the original bug which prompted me to consider
trying 2.3 https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1472500
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
qemu 2.3.1 appears to fix this, though see
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1472571 for the
new problem (unrelated) it causes. There is also no supported fix for
15.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
for reference this was the original bug which prompted me to consider
trying 2.3 https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1472500
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472571
Public bug reported:
I am running Ubuntu 15.04 (not 15.10/dev). Due to another bug in qemu
2.2 I decided to try the 2.3.1 packages (from build here). I realise
there is potential dependency issues and the config is likely untested.
However as this could be a genuin issue, I wanted to report that
Public bug reported:
When running a windows vm under kvm, save-ing, and then restore-ing, the
restore fails with
Error restoring domain: internal error: process exited while connecting to
monitor: Unknown savevm section type 5
2015-07-08T07:18:09.422722Z qemu-system-x86_64: load of migration
Public bug reported:
➜ ~ sudo do-release-upgrade -d
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [1554 B]
Get:2 Upgrade tool [1344 kB]
Fetched 1346 kB in 0s (0 B/s)
authenticate 'focal.tar.gz' against 'focal.tar.gz.gpg'
extracting 'focal.tar.gz'
100 matches
Mail list logo
