This happens on my machine too, when I move the mouse pointer to a lengthy URL
on developer tool of Google Chrome.
Chrome attempts to show a very wide (one line) balloon of the URL, and Compiz
crashes with this message:
compiz (core) - Warn: Exceeded max texture size
Launching fallback window
This problem affects our 32-bit systems as well.
t...@kvm2:~$ uname -a
Linux kvm2 2.6.32-22-generic-pae #35-Ubuntu SMP Tue Jun 1 15:47:31 UTC 2010
i686 GNU/Linux
Our KVM host machines were running fine with previous kernel, but gives blank
screen (via vnc) on guest boot.
With -no-kvm it starts
This problem affects our 32-bit systems as well.
t...@kvm2:~$ uname -a
Linux kvm2 2.6.32-22-generic-pae #35-Ubuntu SMP Tue Jun 1 15:47:31 UTC 2010
i686 GNU/Linux
Our KVM host machines were running fine with previous kernel, but gives blank
screen (via vnc) on guest boot.
With -no-kvm it starts
I am also experiencing this problem, and found that some other processes have
this strange signal mask.
udevd and dhclient3.
They are not descendants of sshd.
So I guess the culprit is not sshd but somewhere in the system startup scripts.
** Attachment added: Output from ps axsf
The culprit is udev.
udev runs ifup when it founds eth0, then ifup starts dhclient3 and restarts
sshd!
Temporary fix to this:
- Remove auto eth0 from /etc/network/interfaces
- Add /sbin/ifup eth0 to /etc/rc.local (before exit 0, of course)
Now only udev has the strange signal mask on my
I am also experiencing this problem, and found that some other processes have
this strange signal mask.
udevd and dhclient3.
They are not descendants of sshd.
So I guess the culprit is not sshd but somewhere in the system startup scripts.
** Attachment added: Output from ps axsf
The culprit is udev.
udev runs ifup when it founds eth0, then ifup starts dhclient3 and restarts
sshd!
Temporary fix to this:
- Remove auto eth0 from /etc/network/interfaces
- Add /sbin/ifup eth0 to /etc/rc.local (before exit 0, of course)
Now only udev has the strange signal mask on my
Thank you!
What are the chances that this fix goes into Karmic?
--
Block I/O crashes after migration
https://bugs.launchpad.net/bugs/341682
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I found a workaround to this problem.
Before starting migration, stop guest (from qemu monitor) and wait 1 second,
and cont after migration.
This is not quite live migration, but guest kernel happily continues running
even under heavy I/O load.
This works for both ide and virtio.
--
Block I/O
Same problem on Jaunty guest.
Guest kernel was linux-image-virtual.
--
Block I/O crashes after migration
https://bugs.launchpad.net/bugs/341682
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:
Binary package hint: kvm
1. Start KVM on host A
2. Make heavy I/O in guest, e.g. while true; do dd if=/dev/zero of=testfile
bs=1M count=1k; done
3. Live-migrate to host B
4. Guest freezes (almost 100% reproducible)
Guest responds to ping and sysrq, but all processes are
** Attachment added: Output from sysrq-w
http://launchpadlibrarian.net/23778149/sysrq-w.txt
--
Block I/O crashes after migration
https://bugs.launchpad.net/bugs/341682
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Upgraded KVM packages today but same problem.
r...@star3:~# dpkg -l |grep kvm
ii kvm 1:84+dfsg-0ubuntu8Full
virtualization on i386 and amd64 hardwa
ii kvm-source1:84+dfsg-0ubuntu8Source
for the KVM driver
Thanks Bart, setting clocksource to jiffies fixed Time went backwards error
in my domU!
However, domU clock still goes back if I reboot dom0 (domUs are saved and
restored by /etc/init.d/xendomains script).
But this time, nothing freezes, no kernel messages, just 'date' command and
timestamps in
Try adding extra='xenconsole=tty'.
I think this should be default in xen-tools.
--
xen guest hangs after mounting filesystem
https://bugs.launchpad.net/bugs/144631
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Public bug reported:
When I save domU, reboot dom0, and restore domU,
I get many of the following error message from domU kernel:
clocksource/0: Time went backwards: delta=-384146242491
shadow=113003514089 offset=65775436
When this error occurs, in domU time is stalled.
Migrating domU to
16 matches
Mail list logo
