From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hollis Blanchard Date: Thu, 20 Mar 2008 14:58:57 +0000 Subject: Re: [kvm-ppc-devel] guest panic fixed Message-Id: <1206025137.2918.3.camel@basalt> List-Id: References: <1205969120.11366.67.camel@basalt> In-Reply-To: <1205969120.11366.67.camel@basalt> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: kvm-ppc@vger.kernel.org On Thu, 2008-03-20 at 12:08 +0100, Christian Ehrhardt wrote: > Hollis Blanchard wrote: > > Thanks to some excellent debugging by Christian, we found the cause of > > our annoying guest panics. We had not implemented exception priorities > > (my bad), so a userspace ITLB miss was being delivered immediately after > > entry to the decrementer interrupt vector. Patch follows, > > http://penguinppc.org/~hollisb/kvm/ updated. > > > > NFS root with virtio-net still doesn't work for me, but it doesn't > > crash. :) > > > > my network works fine (at least initially) see the attached log: > > Sending DHCP requests .., OK > IP-Config: Got DHCP answer from 192.168.1.2, my address is 192.168.1.10 > IP-Config: Complete: > device=eth0, addr2.168.1.10, mask%5.255.255.0, gw2.168.1.2, > host2.168.1.10, domain=local-devnet, nis-domain=(none), > bootserver2.168.1.2, rootserver2.168.1.2, rootpath> Looking up port of RPC 100003/2 on 192.168.1.2 > Looking up port of RPC 100005/1 on 192.168.1.2 > VFS: Mounted root (nfs filesystem). > Freeing unused kernel memory: 116k init > modprobe: FATAL: Could not load /lib/modules/2.6.25-rc3-dirty/modules.dep: No such file or directory > modprobe: FATAL: Could not load /lib/modules/2.6.25-rc3-dirty/modules.dep: No such file or directory > INIT: version 2.85 booting > nfs: server 192.168.1.2 not responding, still trying > nfs: server 192.168.1.2 not responding, still trying > nfs: server 192.168.1.2 not responding, still trying > INFO: task rc.sysinit:679 blocked for more than 120 seconds. > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > > > After that I run into those lockup's for init:1 and rc.sysinit:679. > The network is working fine for a while and then that I get these nfs > timeouts you see above. > I think thats the track I will continue - find out whats wrong there > e.g. virtio mangles the packets, too high latency, lost virtio > interrupts, ... whatever. > > @Hollis let me know if I can help you with your nfs root setup somehow? No, that's pretty much exactly what I see, but my timeouts appear before modprobe and the INIT message. -- Hollis Blanchard IBM Linux Technology Center ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ kvm-ppc-devel mailing list kvm-ppc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel