similar to: InfiniBand Passthrough not working

Hi, I am using syslinux-3.85 (and before till 3.72) and I have seen a peculiar problem on a couple of machines that I have in my lab. The problem is that if the machine boots onto PXE, and then does a "LOCALBOOT 0", the networking component of the OS stops working !!! If I skip PXE boot, and just let the OS boot, the OS's networking is working fine. The problem is seen of all the

OK - finished some tests over tcp and ironed out a lot of problems. rdma is next; should be snap now.... [I must admit that this is my 1st foray into the land of IB, so some of the following may be obvious to a non-naive admin..] except that while I can create and start the volume with rdma as transport: ================================== root at pbs3:~ 622 $ gluster volume info glrdma

Hi! I would need an advice from those that use IB (as admins :) ) i have a choice between : 1. Mellanox InfiniHost? III Lx HCA card, single-port CX4, DDR, PCIe x8, mem-free, tall bracket, RoHS R5 2. QLogic Single Port 20 Gb InfiniBand to x16 PCI Express Adapter (Single Pack) aside the price is there anything else that could help me make a discrimination between this two? (these will be used in

This issue was brought up about a year and a half ago. So I''ll bring it up again and see if anything happens. I''ve got an infiniband network and am attempting to pass the infiniband card through the host and give it to the guest. I''m working with standard CentOS 5.2 on both guest and host with their provided xen (3.0.3 ish). I''ve also attempted to install the

This issue was brought up about a year and a half ago. So I''ll bring it up again and see if anything happens. I''ve got an infiniband network and am attempting to pass the infiniband card through the host and give it to the guest. I''m working with standard CentOS 5.2 on both guest and host with their provided xen (3.0.3 ish). I''ve also attempted to install the

Getting a crash with R1.8.1 on windows 2000 an linux with the strsplit. Version: platform = i386-pc-mingw32 arch = i386 os = mingw32 system = i386, mingw32 status = major = 1 minor = 8.1 year = 2003 month = 11 day = 21 language = R Version: platform = i386-pc-mingw32 arch = i386 os = mingw32 system = i386, mingw32 status = major = 1 minor = 8.1 year = 2003 month = 11 day =

ast_waitfordigit that accepts milliseconds as input. Douglas Garstang wrote: > Admittedly I have not used the ExternalIVR app. Is it any good? > > I'm not sure I agree that Asterisk is GOOD for building IVR's. Sure, > it can do it, but boy it is UGLY. There's also the fact that you can't > call Backgound() in a macro, which forces you to use Read() which >

On Wed, 25 May 2016 11:48:55 -0400 Pat Haley <phaley at mit.edu> wrote: > We have a new install of CentOS 6.7 with infiniband support > installed. We can see the card in hardware and we can see the mlx4 > drivers loaded in the kernel but cannot see the card as an ethernet > interface, using ifconfig -a. Can you recommend an install procedure > to see this as an ethernet

Jan 19 10:00:29 VERBOSE [7177] logger.c: -- Executing [1000 at ext-meetme:7] Read("DAHDI/2-1", "PIN|enter-conf-pin-number||||") in new stack Jan 19 10:00:29 VERBOSE [7177] logger.c: -- Playing 'enter-conf-pin-number' (language 'en') Jan 19 10:00:43 VERBOSE [7177] logger.c: -- USER ENTERED 'THE PIN NUMBER' Jan 19 10:00:43 VERBOSE [7177] logger.c: --

Hello, I going to try to install OFED 1.4 on Xen 3.3 and I`d like to realize a VMM kernel bypass. Thanks to it my doomU will be able to communicate directly with my HCA and not pass by the dom 0. How can I realize that ? Is there a soft or something like that to do the kernel by pass ? I saw that it exist things like XEN-IB driver and SoftIB, there can i get it ? Or is VMM kernel bypass

Hello, I''m trying to get working infiniband device in Xen. I have Xen v3 with 2.6.18 kernel. I export PCI device from Dom0 into DomU. I''ve enabled permisive device in Dom0. However, inserting infiniband module results in the following messages (with little more verbosity which I have added): pcifront pci-0: Installing PCI frontend pcifront pci-0: Creating PCI Frontend Bus

Hello, I see a reproducable panic when doing ibping and aborting it with ^C. My setup is two machines with Mellanox Infinihost III HCAs (one Linux one FreeBSD) connected back-to-back. Details below. I can upload 2 crash dumps, if this is useful. For some reason the port doesn't become ACTIVE, so no packets arrive, but that is probably unrelated. % uname -a FreeBSD cosel.inf.tu-dresden.de

I've read everything I've found on tcpdump-smb, and still can't get it to work right. I downloaded the binary from samba.org, and executed the command like so: (The command belowis directly from the README.smb that comes with tcpdump-3.4a5.tar.gz) ./tcpdump -i eth0 port 139 host 192.168.0.1 tcpdump: parse error How do I use it to get the decoded smb output? BTW: I also

A bug can be easily reproduced: Host# cat guest-agent.xml <channel type="unix"> <source mode="bind" path="/var/lib/libvirt/qemu/stretch.agent"/> <target type="virtio" name="org.qemu.guest_agent.0" state="connected"/> </channel> Host# virsh attach-device instance guest-agent.xml Host# virsh detach-device

A bug can be easily reproduced: Host# cat guest-agent.xml <channel type="unix"> <source mode="bind" path="/var/lib/libvirt/qemu/stretch.agent"/> <target type="virtio" name="org.qemu.guest_agent.0" state="connected"/> </channel> Host# virsh attach-device instance guest-agent.xml Host# virsh detach-device

A bug can be easily reproduced: Host# cat guest-agent.xml <channel type="unix"> <source mode="bind" path="/var/lib/libvirt/qemu/stretch.agent"/> <target type="virtio" name="org.qemu.guest_agent.0" state="connected"/> </channel> Host# virsh attach-device instance guest-agent.xml Host# virsh detach-device

On Sun, Apr 28, 2019 at 09:50:04AM +0800, zhenwei pi wrote: > A bug can be easily reproduced: > Host# cat guest-agent.xml > <channel type="unix"> > <source mode="bind" path="/var/lib/libvirt/qemu/stretch.agent"/> > <target type="virtio" name="org.qemu.guest_agent.0" state="connected"/> >

Hi, i want to set up expire plugin with my dovecot configuration. host# dovecot -n # 1.1.1: /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3):

Hi, I''m currently trying xen 4.1.1 with the 3.0.0-rc5 (heard that it now contains the xen code to run as front or back xen domain). Everything seems to run fine, except that I am trying since a few hours to mount a .vhd file in the dom0. What I tried so far: to create a blank vhd file (this is working): host# vhd-util create -n /storage/test.vhd -s 20G Then i try to mount the file

> > Well, i''m using here the qla2340 on several boxes. It works > > with Xen 2.0 but noch with Xen 3.0. as part of SUSE Linux 10.0: > > Interesting. If the driver really doews work flawlessly in > Xen 2, then I think the culprit has to be interrupt routeing. > > Under Xen 3, does /proc/interrupts show you''re receiving interrupts? I cannot boot with