On Fri, Feb 06, 2015 at 01:46:36PM +, Stefan Hajnoczi wrote:
> On Wed, Jan 07, 2015 at 04:08:29PM +, Stefan Hajnoczi wrote:
> > On Thu, Dec 18, 2014 at 05:22:19PM +0800, Amos Kong wrote:
> > > After enabled network debug of e1000 in Win2012-64r2 guest,
> > > Bus mastering of e1000 can't be
On Wed, Jan 07, 2015 at 04:08:29PM +, Stefan Hajnoczi wrote:
> On Thu, Dec 18, 2014 at 05:22:19PM +0800, Amos Kong wrote:
> > After enabled network debug of e1000 in Win2012-64r2 guest,
> > Bus mastering of e1000 can't be enabled by e1000 driver. It
> > caused guest can't get IP address.
> >
>
On Thu, Dec 18, 2014 at 05:22:19PM +0800, Amos Kong wrote:
> After enabled network debug of e1000 in Win2012-64r2 guest,
> Bus mastering of e1000 can't be enabled by e1000 driver. It
> caused guest can't get IP address.
>
> # bcdedit /debug on
> # bcdedit /dbgsettings net hostip:192.168.122.10
On Thu, Dec 18, 2014 at 09:57:29AM +0008, Jason Wang wrote:
>
>
> On Thu, Dec 18, 2014 at 5:22 PM, Amos Kong wrote:
> >After enabled network debug of e1000 in Win2012-64r2 guest,
> >Bus mastering of e1000 can't be enabled by e1000 driver. It
> >caused guest can't get IP address.
> >
> > # bcded
On Thu, Dec 18, 2014 at 5:22 PM, Amos Kong wrote:
After enabled network debug of e1000 in Win2012-64r2 guest,
Bus mastering of e1000 can't be enabled by e1000 driver. It
caused guest can't get IP address.
# bcdedit /debug on
# bcdedit /dbgsettings net hostip:192.168.122.100 port:5
(