Re: KVM induced panic on 2.6.38[2367] 2.6.39

2011-06-01 Thread CaT
On Wed, Jun 01, 2011 at 06:53:31PM +0800, Brad Campbell wrote: I rebooted into a netfilter kernel, and did all the steps I'd used on the no-netfilter kernel and it ticked along happily. So the result of the experiment is inconclusive. Having said that, the backtraces certainly smell

Re: KVM induced panic on 2.6.38[2367] 2.6.39

2011-06-01 Thread CaT
On Wed, Jun 01, 2011 at 07:52:33PM +0800, Brad Campbell wrote: Unfortunately the only interface that is mentioned by name anywhere in my firewall is $DMZ (which is ppp0 and not part of any bridge). All of the nat/dnat and other horrible hacks are based on IP addresses. Damn. Not referencing

Re: [ANNOUNCE] Native Linux KVM tool

2011-04-03 Thread CaT
On Sun, Apr 03, 2011 at 11:53:34AM +0300, Pekka Enberg wrote: Yes, that's really unfortunate. I don't care too much what we call the tool but I definitely agree with Ingo that 'kvm' is more discoverable Indeed. It's great for finding info on keyboard-video-mouse switches. :) -- A search of

Re: 2.6.33.3: possible recursive locking detected

2010-05-11 Thread CaT
On Wed, May 05, 2010 at 10:52:50AM +0800, Américo Wang wrote: On Wed, May 5, 2010 at 10:32 AM, Yong Zhang yong.zh...@windriver.com wrote: On Tue, May 04, 2010 at 11:37:37AM +0300, Avi Kivity wrote: On 05/04/2010 10:03 AM, CaT wrote: I'm currently running 2.6.33.3 in a KVM instance emulating

2.6.33.3: possible recursive locking detected

2010-05-04 Thread CaT
I'm currently running 2.6.33.3 in a KVM instance emulating a core2duo on 1 cpu with virtio HDs running on top of a core2duo host running 2.6.33.3. qemu-kvm version 0.12.3. When doing: echo noop /sys/block/vdd/queue/scheduler I got: [ 1424.438241] = [