search for: passthough

Greetings, I have a vm on debian 9.5 to which I pass an specific usb from the host. here is the relevant part in the vm's xml file: <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x148f'/> <product id='0x5572'/> </source> <address type='usb'

anyone has any idea regarding this issue? > Sent: Monday, November 05, 2018 at 7:55 PM > From: daggs <daggs@gmx.com> > To: libvirt-users@redhat.com > Subject: [libvirt-users] usb post passthough stopped workng after kernel upgrade > > Greetings, > > I have a vm on debian 9.5 to which I pass an specific usb from the host. here is the relevant part in the vm's xml file: > <hostdev mode='subsystem' type='usb' managed='yes'> > <...

Hello, I have success with passthough nvidia gtx 680 with hardware modification to nvidia grid k2 with using kvm, but i think it will works with xen too. This is is message about hardware modification http://www.eevblog.com/forum/projects/hacking-nvidia-cards-into-their-professional-counterparts/msg207550/#msg207550 Thank you. ____...

&nbsp;Hi! &nbsp;&nbsp;&nbsp;I&nbsp;want&nbsp;to make windows work&nbsp; with native graphics card on xen with no iommu (no vt-d) support. With many googling, I&nbsp;find that xen with Neocleuse 1:1 No-IOMMU passthough patches maybe can meet my requestment. &nbsp;&nbsp; I download and compile a copy of direct-io.hg source, and pass my graphics card to hvm windows domU.&nbsp;&nbsp;I hide the graphics card from dom0 linux with backpci.hide boot option, and&nbsp;allow dom0 linux auto loading wind...

Hello Early this summer I made the decision to eliminate my Windows dual boot, I rarely used windows. I have started a new job which will require using a 3d CAD Inventor/Solidworks (Windows software). Inventor starts in vmware workstation. I also switched from OpenSuSE to CentOS after evaluating Ubuntu, RHEL, SLED, and Centos, I wanted a more proven platform, less experimental stuff. For the

...t, e.g. what each layer is expected to control and manage > exactly. > > In my view, there might be possibly 3 different options to represent > the failover device conceipt to QEMU and libvirt (or any upper layer > software): > > a. Seperate device: in this model, virtio and passthough remains > separate devices just as today. QEMU exposes the standby feature bit > for virtio, and publish status/event around the negotiation process of > this feature bit for libvirt to react upon. Since Libvirt has the > pairing relationship itself, maybe through MAC address or somethi...

Hi experts I use xen-4.0.0 and dom0 is 2.6.33 and domU is 2.6.34 #lspci ............... 01:00.0 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 01:00.1 Ethernet controller: Intel Corporation Unknown device 10a7 (rev 02) 05:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 05:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit

...s expected to control and manage >> exactly. >> >> In my view, there might be possibly 3 different options to represent >> the failover device conceipt to QEMU and libvirt (or any upper layer >> software): >> >> a. Seperate device: in this model, virtio and passthough remains >> separate devices just as today. QEMU exposes the standby feature bit >> for virtio, and publish status/event around the negotiation process of >> this feature bit for libvirt to react upon. Since Libvirt has the >> pairing relationship itself, maybe through MAC ad...

...topology where all my nodes connect to a central node. Below is tinc.conf for main node *tinc.conf* Name = main Interface = tun0 Forwarding = kernel and the remote nodes have same with ConnectTo = main. I have tried to apply a basic iptable policy on the main node but the traffic still seems to passthough and the nodes can communicate with each other. How do I apply policy between the two remote nodes on the main hub node? I would like in future to only allow a selected ports to be allowed between the nodes but for now I want iptables to manage policy between nodes. *Main node IPTABLES rule* ipt...

...;> >> >> >> In my view, there might be possibly 3 different options to represent >> >> the failover device conceipt to QEMU and libvirt (or any upper layer >> >> software): >> >> >> >> a. Seperate device: in this model, virtio and passthough remains >> >> separate devices just as today. QEMU exposes the standby feature bit >> >> for virtio, and publish status/event around the negotiation process of >> >> this feature bit for libvirt to react upon. Since Libvirt has the >> >> pairing relat...

...t; >> exactly. > >> > >> In my view, there might be possibly 3 different options to represent > >> the failover device conceipt to QEMU and libvirt (or any upper layer > >> software): > >> > >> a. Seperate device: in this model, virtio and passthough remains > >> separate devices just as today. QEMU exposes the standby feature bit > >> for virtio, and publish status/event around the negotiation process of > >> this feature bit for libvirt to react upon. Since Libvirt has the > >> pairing relationship itself,...

I've been pointed to this discussion (which I had missed previously) and I'm getting a headache. Let me first summarize how I understand how this feature is supposed to work, then I'll respond to some individual points. The basic idea is to enable guests to migrate seamlessly, while still making it possible for them to use a passed-through device for more performance etc. The means to

...ne the boundary between VM and guest, e.g. what each layer is expected to control and manage exactly. In my view, there might be possibly 3 different options to represent the failover device conceipt to QEMU and libvirt (or any upper layer software): a. Seperate device: in this model, virtio and passthough remains separate devices just as today. QEMU exposes the standby feature bit for virtio, and publish status/event around the negotiation process of this feature bit for libvirt to react upon. Since Libvirt has the pairing relationship itself, maybe through MAC address or something else, it can cont...

...alling-the-free-g729-codec-for-asterisk/ A little more about our setup. All recordings have been converted to G729, all voicemail messages are also in G729, finally allow=g729, disallow=all is specified in our config. Questions: 1) Is there anything we overlooked in our attempt to implement g729 passthough, and stop all transcoding efforts? 2) do we still need to purchase 23 G729 licenses? If so, is asterisk 10$ license recognized by the patent holders (ie, is Digium authorized to sell the license on behalf of the patent holders)? 3) Is there a performance/stability/security gain when using the comme...

...RI T1 myself for local service. The fax machines are having some issues (I can use analog phone to call out fine) and I'm checking on modem passthrough with Verizon, but wonder if any else is using Verizon Business for SIP trunk and what your faxing milage was? Did they support G711 and modem-passthough, etc? Also checking QoS, etc. ----------------------------------------- Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you a...

...al node. Below is tinc.conf for main node > > *tinc.conf* > Name = main > Interface = tun0 > Forwarding = kernel > > and the remote nodes have same with ConnectTo = main. > > I have tried to apply a basic iptable policy on the main node but the > traffic still seems to passthough and the nodes can communicate with each > other. How do I apply policy between the two remote nodes on the main hub > node? I would like in future to only allow a selected ports to be allowed > between the nodes but for now I want iptables to manage policy between > nodes. > > *Ma...

Hi guys, i have 4 Xen servers, two with Xen 3.2.1 and the other two with Xen 4. All four servers with 3 network card attached to different networks, 3 of these interfaces are bridges (configured in the ''/etc/network/interfaces'' config file, NOT in xend-config.sxp file) and one is used for the ISCSI service, where the virtual machines are loaded. The problem is,

Hello All, Sorry to resend this email since I really want to know the answer. Did anybody know how I could make Linux Guest OS mount CD automatically with Nautilus? When I exposed a Music CD to my FC5 guest os on Xen 3.0.3, I found the CD wasn''t recognized as a Music CD, it was recognized as a blank CD. In Nautilus, when I clicked the icon of CD, a empty folder was opened. On general

Dear list, happy new year! I am still trying to make T.38 work. In the meantime, I have upgraded to Asterisk 13.1.0, and I am using the most recent PJSIP library (compiling that stuff myself). My local fax software is capable of T.38, as is my ITSP; Asterisk sits in the middle, of course. Asterisk is in the same private subnet as the local fax software and talks to the ITSP through a NAT'd

...the fax *gateway* feature if both endpoints are capable of T.38. On the other hand, I have read (at multiple places) the the *gateway* code is responsible for detecting the v21 preamble. How does this fit together? AFAIK, when both ends support T.38, you don't need the gateway and can turn to passthough mode. In passthrough mode, asterisk does not need to detect anything. Just take the packet it receives and pass the payload to the other end of the call. Cheers, Frederic