From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1JAMnb-0000pX-0z
	for qemu-devel@nongnu.org; Thu, 03 Jan 2008 04:55:39 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1JAMnZ-0000oV-83
	for qemu-devel@nongnu.org; Thu, 03 Jan 2008 04:55:38 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1JAMnX-0000oJ-RL
	for qemu-devel@nongnu.org; Thu, 03 Jan 2008 04:55:36 -0500
Received: from mail.hoster.ru ([195.128.50.33])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <mouse@mayc.ru>) id 1JAMnX-0001ke-De
	for qemu-devel@nongnu.org; Thu, 03 Jan 2008 04:55:35 -0500
Received: from [81.195.19.59] (helo=[192.168.1.2])
	by mail.hoster.ru with esmtpa (Exim 4.67 (FreeBSD))
	(envelope-from <mouse@mayc.ru>) id 1JAMnR-000DTy-TJ
	for qemu-devel@nongnu.org; Thu, 03 Jan 2008 12:55:29 +0300
Message-ID: <477CB111.4080602@mayc.ru>
Date: Thu, 03 Jan 2008 12:55:29 +0300
From: Anton D Kachalov <mouse@mayc.ru>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] the problem of booting linux kernel from NFS
References: <5bde6f770801022327m7a22ceabrc50a7d0a86398042@mail.gmail.com>
In-Reply-To: <5bde6f770801022327m7a22ceabrc50a7d0a86398042@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Hello¸

new bee wrote:
...
> when I boot the new kernel, there is the message :
> IP-Config: No network device available
> Looking up port of RPC 100003/2 on 192.168.15.1 <http://192.168.15.1>
>
> and the kernel cannot mount the root fs.but the kernel has the network 
> device driver.
>
> What is the reason? and What should I solve it?
The reason that you kernel didn't contain right driver module for your 
network card.

Rgds,
Anton