similar to: manipulation extra features which hypervisors support

For the libvirt 5.8 release, I find that there is a new comment in qemu.conf: #slirp_helper = "/usr/bin/slirp-helper" It indicates that there is a slirp-helper to help setup slirp network. But I cannot find it even after I built the latest qemu(v4.1.0-1378-g98b2e3c9ab) and libvirt (v5.9.0-rc1-2-g73f91d659b). Could you please tell me where I can find that helper program? Thanks --

Hi to all, i'm new to the mailing list, because i already searched the whole list and google fot this, but i could not find anything: I have set up a cute Samba 3 PDC as described here: http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection.html#id2498710 In fact the setup is nearly exactly the same. (I've just added one more share.) Then i used a XP client to load a local

Hello, Does anyone have experience backing up their samba SMB shares with an NT-based backup system? I'm using Seagate Backup Exec 7.0, and whenever I select a share on Samba, I get a message saying "Unable to connect to server, <F5> to retry", and then another one saying "A device specefic error occured". My samba shares are all fully operational (I can access them

Today we have been having some problems with the dchannel of out T1's. I was wondering if there is a way for asterisk to send out an email or page whenan error occurs. Not I know errors happen quite offen for many reasons, but I would like an email sent when there is a TI problem, or specefic other problems. I am using the safe_asterisk to run asterisk and it sends an email when asterisk

Hi,?When installing packages is there any?preferable path. In my case I got this message in R consol:The downloaded binary packages are in? ? ? ? ?C: ~\ Temp \ RtmpQLTD5e \ downloaded_packages this is a temporary files that I delete every time. Is it possible to install packages in a specefic folder. [[alternative HTML version deleted]]

On Thursday, 6 December 2018 16:47:32 CET Richard W.M. Jones wrote: > We've been carrying this exact patch in RHEL 7 for several years. It > reverts the change made in 2014 where we switched to using the virbr0 > bridge for libguestfs networking instead of SLIRP. We thought SLIRP > was going to become unsupported in qemu, but recently there have been > more encouraging signs

Hi! If i want to use bridged network or openvswitch, does guestfwd only works with slirp network? Or how it work in case of using bridge/openvswitch? <devices> <channel type='unix'> <source mode='bind' path='/tmp/guestfwd'/> <target type='guestfwd' address='10.0.2.1' port='4600'/> </channel> </devices>

Hello all, I spent a couple of days figuring this out, and I found some related posts without solutions, so I figured I would sent this to the list. We run a small local network here with a mixed bag of Windows XP / 2000 / Linux clients. We have been using Samba to allow access to a set of shared printers using a linux server. We also have a separate linux server that handles our file serving

qemu in SLIRP mode offers DHCP services to the appliance. We don't use them, but use a fixed IP address intead. This changes the appliance to get its IP address using DHCP. Note: This is only used when the network is enabled. dhclient is somewhat slower, but the penalty (a few seconds) is only paid for network users. We could consider using the faster systemd dhcp client instead. ---

Dear All I'm making an instrumentation pass. The pass is supposed to modify the given IR in a specefic way. One of the required modifications is to insert a call to a function at a specific location. This is the signature of the called function: void myclass::foo(Function *f, BasicBlock* b) This function's prototype is in an foofile.h file in include/llvm And the function

Let's actually compile and test the patch this time, rather than trusting the RHEL 7.6 patch to apply directly to head ... Rich.

Possibly for post 1.40. Rich.

On Tue, Sep 30, 2014 at 04:44:05PM +0100, Richard W.M. Jones wrote: > When using the libvirt backend, don't use the SLIRP. Use > qemu-bridge-helper via libvirt to give us a full network connection. > One consequence of this is that 'ping' works in virt-builder > --run-command. > > Note unfortunately this does not fix virt-rescue (since it overrides > the default

On 03/12/2015 04:35 AM, Richard W.M. Jones wrote: >> leer@eng-leer:~/libguestfs-1.29.29$ virt-builder fedora-21 >> --run-command "ping -c 4 172.16.12.200" >> [ 1.0] Downloading: http://libguestfs.org/download/builder/fedora-21.xz >> [ 1.0] Planning how to build this image >> [ 1.0] Uncompressing >> [ 28.0] Opening the new disk >> [ 31.0]

Hi, i'm running a samba PDC on samba 3.0 and just had to reinstall the server because of a dead cpu causing corruption. luckily i had complete backups of the samba-files, so i copied them back to /etc/samba, /var/lib/samba and /var/cache samba. (tdb-files) i had one workstation (xp) removed from the domain and wanted to add it again, but then the station always gives me an error that i

On 03/10/2015 05:12 PM, Richard W.M. Jones wrote: > Just for comparison, libguestfs 1.29.29 on Fedora host, plus > virt-builder, with a Fedora guest does this: > libguestfs 1.29.29 on a ubuntu 14.04 host with fedora-21 guest seems have no functioning network, it cannot ping the host. Is there some configuration required on the host? leer@eng-leer:~/libguestfs-1.29.29$ virt-builder

v2: - Make virbr0 configurable. - Fix the tests.

Hi Han, The slirp-helper is a helper program provided in libslirp rust bindings. It seems that you need to build it yourself ATM. git clone https://gitlab.freedesktop.org/slirp/libslirp-rs.git > cd libslirp-rs > cargo build --bin slirp-helper --features=all > Han Han <hhan@redhat.com> 於 2019年11月7日 週四 下午2:01寫道： > For the libvirt 5.8 release, I find that there is a new comment

On 16 Dec 1997, Mark Evans wrote: > How do get information on domain logins shown > in the log files, currently all I am getting is > showing of the netlogon share being opened and > closed. see ipc.c: in the NetWkstaUserLogon and / or NetWkstaGetInfo functions, decrease the levels of the DEBUG statements, or add your own. > Whereas it would be usefull to have > successful

There's a heap overflow in qemu SLIRP which affects libguestfs, potentially allowing a malicious filesystem to take control of the confining qemu process and from there attack the host. It will affect libguestfs specifically when these two conditions are both met: - You're using the ‘direct’ backend. - Networking is enabled. The direct backend is the default upstream, but not in