From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:33341) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QM5lC-0006Wp-0n for qemu-devel@nongnu.org; Mon, 16 May 2011 17:55:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QM5lA-00080G-Uf for qemu-devel@nongnu.org; Mon, 16 May 2011 17:55:29 -0400 Received: from mail-yw0-f45.google.com ([209.85.213.45]:57236) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QM5lA-00080B-QB for qemu-devel@nongnu.org; Mon, 16 May 2011 17:55:28 -0400 Received: by ywl41 with SMTP id 41so2009015ywl.4 for ; Mon, 16 May 2011 14:55:27 -0700 (PDT) From: "Adnan Khaleel" In-Reply-To: 20110421165255.06bb77b3@shadowfax.no-ip.com Message-ID: <20110516215523.1d77baf4@shadowfax.no-ip.com> Date: Mon, 16 May 2011 16:55:23 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------9d70802832fe62a7e7856ece7f84c37a" Subject: Re: [Qemu-devel] [PATCH 00/26] q35 chipset support for native pci express support Reply-To: adnan@khaleel.us List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Isaku Yamahata This is a multi-part message in MIME format. -------------9d70802832fe62a7e7856ece7f84c37a Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I finally got this work after I realised that the AHCI driver was not be= ing loaded in my disk image and that ACHI was not being enabled in the S= eabios .config file. This is really good work Yamahata, thanks. As far as I can tell, everything works like the stock Qemu 0.14 except n= etworking. The guest OS sees the network device and initialises it but I= think the Qemu DHCP server/firewall never gets back, since the network = device doesn't even get a 10.0.2.15 ip address during bootup and the gue= st dhcp client never gets an ip address,=20 eth0 device: Intel Corporation 82540EM Gigabit Ethernet Controller (re= v 03) eth0 Starting DHCP4 client. . . . . . . . eth0 DHCP4 continues in background=20 eth0 device: Intel Corporation 82540EM Gigabit Ethernet Controller (re= v 03) eth0 DHCP4 client (dhcpcd) is running eth0 . . . but is still waiting for data eth0 interface could not be set up until now So doing an ifconfig later on just shows eth0 Link encap:Ethernet HWaddr 52:54:00:12:34:56 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) lo Link encap:Local loopback =20 inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) I'm going to start a separate thread to see what the possible cause migh= t be and what might be the best way to debug this. Do you have any idea = if this q35 chipset going to be committed to Qemu upstream=3F Thanks AK -------------9d70802832fe62a7e7856ece7f84c37a Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I finally got this work after I realised that the AHCI driver was not be= ing loaded in my disk image and that ACHI was not being enabled in the S= eabios .config file.

This is really good work Yamahata, thanks.

As far as I can tell, everything works like the stock Qem= u 0.14 except networking. The guest OS sees the network device and initi= alises it but I think the Qemu DHCP server/firewall never gets back, sin= ce the network device doesn't even get a 10.0.2.15 ip address during boo= tup and the guest dhcp client never gets an ip address,

=

eth0 &n= bsp; device: Intel Corporation 82540EM Gigabit Ethernet Controller (rev = 03)

e= th0 Starting DHCP4 client. . . . . . . .

eth0 DHCP4 continues i= n background

eth0 device: Intel Corporation 82540EM Gigabit Ethe= rnet Controller (rev 03)

eth0 DHCP4 client (dhcpcd) is running<= /div>

eth0 = . . . but is still waiting for data

eth0 interface could not be set up= until now

So doing an ifconfig later on= just shows

eth0 Link encap:Ethernet HWaddr 52:54:= 00:12:34:56

UP BROADCAST MULTICAST MT= U:1500 Metric:1

RX packets:0 errors:0= dropped:0 overruns:0 frame:0

TX packets:0 = errors:0 dropped:0 overruns:0 carrier:0

col= lisions:0 txqueuelen:1000

RX bytes:0 (0.0 b= ) TX bytes:0 (0.0 b)

lo Link encap:Local loop= back

inet addr:127.0.0.1 Mask:= 255.0.0.0

inet6 addr: ::1/128 Scope:Host

&= nbsp; UP LOOPBACK RUNING MTU:16436 Metr= ic:1

= RX packets:0 errors:0 dropped:0 overru= ns:0 frame:0

TX packets:0 errors:0 dropped:= 0 overruns:0 carrier:0

collisions:0 txqueue= len:1000

RX bytes:0 (0.0 b) TX bytes= :0 (0.0 b)

I'm going to start a se= parate thread to see what the possible cause might be and what might be = the best way to debug this. Do you have any idea if this q35 chipset goi= ng to be committed to Qemu upstream=3F

Thanks

AK

-------------9d70802832fe62a7e7856ece7f84c37a--