similar to: OpenBSD 4.5 in HVM domU network timeouts

Hi list, Are there any problems with the if_re ? After upgrade RELENG_7 on my laptop NIC stopped to work:( uname -a: FreeBSD notebook.minsk.domain 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #3: Fri Apr 10 20:38:55 EEST 2009 root@notebook.minsk.domain:/usr/obj/usr/src/sys/tiger-asus-a6m i386 notebook# dhclient re0 DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 3 DHCPDISCOVER on re0 to

Having lots of problems with a restored from backup installation of Samba 4.1.9 on FreeBsd cannot use windows tools to assign permissions to shares, and now when a problem creating a Gpo. with log level 10 this is the output: root at BSD:/home # samba-tool gpo create testgpo INFO: Current debug levels: all: 10 tdb: 10 printdrivers: 10 lanman: 10 smb: 10 rpc_parse: 10 rpc_srv: 10

I have an Asus P5Q-WS running FreeBSD 7 and the onboard Realtek NIC's are not being detected. No Kernel modifications as this is a fresh install. pciconf -lv : re0@pci0:3:0:0: class=0x020000 card=0x82c61043 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network

Hello, I need some advice how to debug this issue ... Recently I got a new mainboard for a router, it's a Gigabyte GA-H77N-WIFI with two onboard re(4) NICs. The problem is that re0 works fine and re1 doesn't: It doesn't receive any packets. Tcpdump displays all outgoing packets, but no incoming ones on re1. Ifconfig shows the link correctly (100 or 1000 Mbit, depending on where I

This way it is possible to change where the matching start, instead of always assuming it is the beginning. --- common/mlpcre/PCRE.ml | 2 +- common/mlpcre/PCRE.mli | 5 ++++- common/mlpcre/pcre-c.c | 16 +++++++++++++--- common/mlpcre/pcre_tests.ml | 11 ++++++++--- 4 files changed, 26 insertions(+), 8 deletions(-) diff --git a/common/mlpcre/PCRE.ml b/common/mlpcre/PCRE.ml

This way it is possible to change where the matching start, instead of always assuming it is the beginning. --- common/mlpcre/PCRE.ml | 2 +- common/mlpcre/PCRE.mli | 5 ++++- common/mlpcre/pcre-c.c | 16 +++++++++++++--- common/mlpcre/pcre_tests.ml | 15 ++++++++++++--- 4 files changed, 30 insertions(+), 8 deletions(-) diff --git a/common/mlpcre/PCRE.ml b/common/mlpcre/PCRE.ml

Hi, After updating from 7.0-RELEASE to STABLE (around 15/08) my NIC refuses to handle large file transfers. pciconf -lv re0@pci0:4:0:0: class=0x020000 card=0x001a6409 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8110SB Single-Chip Gigabit LOM Ethernet Controller' class = network subclass = ethernet Log

Kip, Does the problem with Xen 3.1 in HVM/Intel manifest as those BTX halted errors (e.g. http://lists.xensource.com/archives/html/xen-users/2006-10/msg00014.html) ? If so, do you happen to know whether this problem has been solved in Xen 3.2 or 3.2.1? This message of yours was written this March, so I'm assuming that 3.2.1 will contain this fix? Can anybody confirm this? I'm having

Just thought I'd pass along that I have successfully installed FreeBSD 7.0 into a Xen 3.1 HVM. ?This one went as smooth as I expected, considering my experience with 6.3. ?Haven't done any benchmarking or stress testing or port installs or anything. ?But so far it's working nicely. Here's all the info. ?If you'd like to see anything else, let me know. Host hardware: ?

Hi all: I installed 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

Hi all: I installed 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

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

Hi, I upgraded my 7.1-RELEASE system to RELENG_7 yesterday and after booting, re0 works for only a short time, then gives "re0: PHY read failed" over and over. Does anyone have a suggestion on how to debug? Thanks, Steve

Dear colleagues, experimenting with new amd64-based router we found strange re(4) behaviour when working in autoselect media mode: whenever promisc mode turned on, renegotiating occurs, leading to 3 to 45 (depending on STP settings on the switch) network unavailability. Moreover, some other re(4) setting changes seem to disturb link state unneededly (such as ifconfig re0 -vlanhwtag) The most

Package: xen-utils-3.2-1 Version: 3.2.1-2 If I try to create an HVM domain I get the following error message: araminta:~# xm create -c heceptor.cfg Using config file "/etc/xen/heceptor.cfg". Error: Creating domain failed: name=heceptor xend-log has a Python backtrace in it: [2009-03-21 14:14:46 25927] DEBUG (XendDomainInfo:84) XendDomainInfo.create(['vm', ['name',

Hello list I have a shutdown problem. I have a machine with gigabyte GA-G33M-DS2R motherboard. Integrated network card is Realtek 8111B. I can not wake the computer after I shutdown it from FreeBSD. It is a dualboot system - windows xp and freebsd. If I shutdown the computer from windows - later I can wake it up with magic packet. Even if i shutdown the machine on the boot menu with the power

Add an option to specify the number of MSI-X vectors for PCI NIC cards. This can also be used to disable MSI-X, for compatibility with old qemu. This option currently only affects virtio cards. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- hw/virtio-net.c | 5 ++++- net.c | 18 +++++++++++++++++- net.h | 4 ++++ qemu-options.hx | 14 ++++++++------

Add an option to specify the number of MSI-X vectors for PCI NIC cards. This can also be used to disable MSI-X, for compatibility with old qemu. This option currently only affects virtio cards. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- hw/virtio-net.c | 5 ++++- net.c | 18 +++++++++++++++++- net.h | 4 ++++ qemu-options.hx | 14 ++++++++------

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

From 83e942e0c7634121243478fa2f4e3459b33d4a67 Mon Sep 17 00:00:00 2001 From: Dor Laor <dor.laor@qumranet.com> Date: Wed, 19 Dec 2007 23:43:24 +0200 Subject: [PATCH] virtio network device This patch implements the backend support for the virtio network device. The device is optimized for virtualized environments by limiting the number of guest=>host transitions per-packet. In the best