Hi Haydn,
The '-net nic' clause on it's own tells qemu to create a virtual nic in the
guest but doesn't tell qemu how to connect it to the host. after '-net nic'
you need another -net clause, such as '-net user' to use qemu's internal NAT
or '-net tap' to create a tun/tap virtual interface on the host (useful for
binding to bridges and such). I believe the qemu documentation has more
info on this.
Wes
On 9/18/07, Haydn Solomon <[EMAIL PROTECTED]> wrote:
> I'm unable to get my networking functioning for windows 2003 server R2
> virtual machine. This is the first time I've installed 2003 Server under
> kvm ( release 40 ) and had no problems installing.
>
> Once it iwas installed I start the 2003 server machine with the following
> parameters.
>
>
> /usr/local/kvm/bin/qemu-system-x86_64 \
> -hda server2k3r2.img \
> -m 512 \
> -no-rtc \
> -localtime \
> -usb \
> -usbdevice tablet \
> -net nic,model=rtl8139 \
> -cdrom /home/hsolomon/isos/en_win_srv_2003_r2_enterprise_cd1.iso &
>
> Is there some parameter i'm missing for getting networking going? Any
> guidance will be appreciated. Thanks.
>
> Haydn
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
