search for: ne2k_pci

Dear Experts, Does anyone install Windows Vista on XVM successfully? I am using machine Sun x4600 with AMD 8218 cpu with virtualization feature. i installed OpenSolaris build 75, My installation steps: # svccfg -s xvm/xend setprop config/vncpasswd = astring: \"secret\" # svccfg -s xvm/xend setprop config/vnc-listen = astring: \"0.0.0.0\" # svccfg -s xvm/xend setprop

I''ve searched all night long on google, discussions, threads, and the xen wiki... but I can''t find how to do this: vif = [''type=ioemu,mac=XX:XX:XX:XX:XX:XX,model=ne2k_pci''] where should I put this? I have sxce94, dom0 works nicely, and domUs too, but I''d like to select ne2k for an hvm openbsd dom0 that I''ve created because I''ve read that it doesn''t to the annoying timeouts that the emulated realtek does. So long if I dump...

...ed Fedora 6 on xen 3.0.4(which is intalled in fedoa 7) as domainU, I find the following information int the cfg file: # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci'' ] # type=ioemu specify the NIC is an ioemu device not netfront vif = [ ''type=ioemu, bridge=xenbr0'' ] So, I use mode=ne2k_pci and create a fedora virtual machine, but it''s network can only lasts for a few seconds, I deactive and active the network card ,then I...

...ed Fedora 6 on xen 3.0.4(which is intalled in fedoa 7) as domainU, I find the following information int the cfg file: # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci'' ] # type=ioemu specify the NIC is an ioemu device not netfront vif = [ ''type=ioemu, bridge=xenbr0'' ] So, I use mode=ne2k_pci and create a fedora virtual machine, but it''s network can only lasts for a few seconds, I deactive and active the network card ,then I...

...ing unusual.. any ideas ?? <<</etc/xen/w2k3 kernel = "/usr/lib/xen-ioemu-3.1/boot/hvmloader" builder= ''hvm'' memory = 1024 shadow_memory = 8 name = "w2k3" vcpus=2 vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci'' ] disk = [ ''phy:store/windows-test,hda,w'', ''file:/mnt/store/backup/wide032a01.iso,hdc:cdrom,r''] device_model = "/usr/lib/xen-ioemu-3.1/bin/qemu-dm" boot="d" sdl=0 vnc=1 vnclisten="0.0.0.0" vncconsole=1 vncpa...

I have finally gotten one version of windows 2003 r2 x64 installed as a guest. The bad news is no network. The network tab says it''s a realtek 8139 when I know it is a intel. I tried downloading the intel drivers and they wont install says it''s the wrong hard ware. Is this common that it uses a 8139 as a generic network card? Also the network card shows The

...ash = "restart" device_model = "/usr/lib64/xen/bin/qemu-dm" usb = 1 usbdevice = "tablet" sdl = 0 vnc = 1 vncunused = 1 keymap = "pt-br" disk = [ "phy:/dev/etherd/e3.3,hda,w" ] vif = [ "mac=00:16:36:2f:fd:7c,bridge=xenbr0,script=vif-bridge,model=ne2k_pci" ] parallel = "none" serial = "pty" But, on windows I just see one CPU... I don't understand why this happen!! Thanks for any help -- Gilberto Nunes

...; +# workaround for gpxe issue with the virt-preview qemu on F11 host kernel +# https://bugzilla.redhat.com/show_bug.cgi?id=512358 +RPMS="$RPMS gpxe-roms-qemu" +ln -snf ../etherboot/e1000-82542.zrom /usr/share/qemu/pxe-e1000.bin +ln -snf ../etherboot/ne.zrom /usr/share/qemu/pxe-ne2k_pci.bin +ln -snf ../etherboot/pcnet32.zrom /usr/share/qemu/pxe-pcnet.bin +ln -snf ../etherboot/rtl8139.zrom /usr/share/qemu/pxe-rtl8139.bin +ln -snf ../etherboot/virtio-net.zrom /usr/share/qemu/pxe-virtio.bin + # Things we could probably remove if libvirt didn't link against them #RPMS=&...

Hi, I''m running OpenBSD 4.5 as HVM guest. Here is part of my .cfg file: kernel = ''/usr/lib/xen-3.2-1/boot/hvmloader'' device_model = ''/usr/lib64/xen-3.2-1/bin/qemu-dm'' builder = ''hvm'' It is running fine with vnc, but when I ssh to openbsd, and I type cat, vi, etc. it freezes. Any ideas? Thanks in advance. -- Sergio Roberto Charpinel

In spite of reading howtos and this mailing list now for several weeks, I am still not able to get the network of my winXP guest connected to the host (opensuse 10.2) or the external network. There are some network interfaces missing on my host (peth0, vif0.0). ifconfig: eth0 Protokoll:Ethernet Hardware Adresse 00:18:8B:B3:1A:AC inet Adresse:192.168.0.66 Bcast:192.168.0.255

...freebsd/7.1-RELEASE-i386-dvd1.iso'], ['dev', 'ioemu:hdc:cdrom'], ['mode', 'r']]], ['device', ['vif', ['ip', '172.17.207.9'], ['mac', '00:16:3E:5B:18:B4'], ['type', 'ioemu'], ['model', 'ne2k_pci']]]]) [2009-03-21 14:14:46 25927] DEBUG (XendDomainInfo:1618) XendDomainInfo.constructDomain [2009-03-21 14:14:46 25927] DEBUG (balloon:132) Balloon: 2996 KiB free; need 2048; done. [2009-03-21 14:14:46 25927] ERROR (XendDomainInfo:440) VM start failed Traceback (most recent call last): Fi...

...nic[,vlan=@var{n}][,macaddr=@var{addr}][,model=@var{type}][,name=@var{name}] + at item -net nic[,vlan=@var{n}][,macaddr=@var{addr}][,model=@var{type}][,name=@var{name}][,vectors=@var{v}] Create a new Network Interface Card and connect it to VLAN @var{n} (@var{n} = 0 is the default). The NIC is an ne2k_pci by default on the PC target. Optionally, the MAC address can be changed to @var{addr} -and a @var{name} can be assigned for use in monitor commands. If no - at option{-net} option is specified, a single NIC is created. -Qemu can emulate several different models of network card. +and a @var{name} c...

...nic[,vlan=@var{n}][,macaddr=@var{addr}][,model=@var{type}][,name=@var{name}] + at item -net nic[,vlan=@var{n}][,macaddr=@var{addr}][,model=@var{type}][,name=@var{name}][,vectors=@var{v}] Create a new Network Interface Card and connect it to VLAN @var{n} (@var{n} = 0 is the default). The NIC is an ne2k_pci by default on the PC target. Optionally, the MAC address can be changed to @var{addr} -and a @var{name} can be assigned for use in monitor commands. If no - at option{-net} option is specified, a single NIC is created. -Qemu can emulate several different models of network card. +and a @var{name} c...

...the guest boot , i had the right emulation , but after a reboot , the guest loose the configuration . Someone can confirm the bug in centos 5.5 ? Have someone a patch ? Extract of my config : builder = "hvm" vif = [ 'type=ioemu, mac=00:16:3e:50:10:45, bridge=xenbr0, model=ne2k_pci'] device_model = "/usr/lib64/xen/bin/qemu-dm" #grep spa.*/usr/lib64/xen/bin/qemu-dm /var/log/xen/xend.log [2010-05-24 11:47:23 xend 3782] INFO (image:434) spawning device models: /usr/lib64/xen/bin/qemu-dm ['/usr/lib64/xen/bin/qemu-dm', '-d', '75', '-m...

...following instructions found on this mailing list * enabling IP forwarding in the host kernel (instead of using the automatically generated rules in the forward chain in iptables) * disabling the management mode on the card firmware, following instructions found on this mailing list * using the ne2k_pci driver in the guest instead of the default * trying different vm schemes (1, 2 or 3 VM at a time instead of 4) * pinning Dom0 to one CPU and the guest on another (as suggested somewhere on this mailing list) None of the above fixed the problem. I don''t know what else could I do to fix...

...(bus, nd, devfn); + } else if (strcmp(nd->model, "virtio") == 0) { + virtio_net_init(bus, nd, devfn); } else if (strcmp(nd->model, "?") == 0) { fprintf(stderr, "qemu: Supported PCI NICs: i82551 i82557b i82559er" - " ne2k_pci pcnet rtl8139\n"); + " ne2k_pci pcnet rtl8139 virtio\n"); exit (1); } else { fprintf(stderr, "qemu: Unsupported NIC: %s\n", nd->model); diff --git a/qemu/hw/virtio-net.c b/qemu/hw/virtio-net.c new file mode 100644 index 00000...

...(bus, nd, devfn); + } else if (strcmp(nd->model, "virtio") == 0) { + virtio_net_init(bus, nd, devfn); } else if (strcmp(nd->model, "?") == 0) { fprintf(stderr, "qemu: Supported PCI NICs: i82551 i82557b i82559er" - " ne2k_pci pcnet rtl8139\n"); + " ne2k_pci pcnet rtl8139 virtio\n"); exit (1); } else { fprintf(stderr, "qemu: Unsupported NIC: %s\n", nd->model); diff --git a/qemu/hw/virtio-net.c b/qemu/hw/virtio-net.c new file mode 100644 index 00000...

...network-route netdev=eth0'') (vif-script vif-route) (dom0-min-mem 196) (enable-dom0-ballooning yes) (total_available_memory 0) (dom0-cpus 0) (vnc-listen ''0.0.0.0'') (vncpasswd ''xxx'') (keymap ''fr'') I''ve tried with rtl8139 and ne2k_pci drivers but no luck : vif= [ ''ip=88.190.230.16, mac=00:16:3E:25:3B:58, type=ioemu, model=ne2k_pci'' ] What do I need for having network with a Squeeze DomU on a Squeeze Dom0 with LVM + routed + HVM ? Thanks a lot for any help. Sam ____________________________________________...

...ms ... --- 10.10.10.10 ping statistics --- 974 packets transmitted, 972 received, 0% packet loss, time 972996ms rtt min/avg/max/mdev = 1831.964/3849.323/7833.997/1421.748 ms, pipe 8 Does anybody know what's the problem? Is there any workaround? I've googled for something about "model=ne2k_pci" options in xen domain config, but haven't tried it yet (installation still in the progress..). Any hints? Thanks -- Sergey Smirnov email/xmpp: Sergey.A.Smirnov at Gmail.com

...when I try to force it by setting <model type="virtio"/> in the XML configuration, it seems to make no difference. I see that as per http://libvirt.org/formatdomain.html , "qemu -net nic,model=? /dev/null" returns the following: "ne2k_isa i82551 i82557b i82559er ne2k_pci pcnet rtl8139", but I have no qemu-kvm binary. Not sure if that's a telling symptom or not. Host kernel is 2.6.26-2-openvz-amd64, KVM version is 72+dfsg-5~lenny5, libvirt version is 0.4.6-10, all of which look good enough to use virtio according to http://wiki.libvirt.org/page/Virtio...