search for: msg00342

Hi Daniel, thanks for the reply - The procedure I use is the same as I use for XenServer, and the certificate exchange works just fine. The only thing I'm a bit unclear on, is the location of the CA cert, which in the case of XenServer, I simply put it in /etc/pki/CA. And when I start the libvirtd daemon, it successfully picks it up. If I put the Server key and cert in /etc/vmware/ssl for

....archivum.info/linux-fsdevel@vger.kernel.org/2008-06/msg00337.html> So far it would appear to be Samba is not releasing the oplock when another process tries to break it. I am not entirely convinced this is Samba's fault: <http://www.archivum.info/linux-fsdevel@vger.kernel.org/2008-06/msg00342.html> However, somebody suggested I contact Samba people just in case. Any ideas? Thanks Brian May

...er certificate was not signed by any CA certificate that >> the libvirt client has access to. So it is a client side CA cert config >> problem most likely. I think this problem has already been discussed on this mailing list, see: https://www.redhat.com/archives/libvir-list/2012-March/msg00342.html What you basically have to do is create your own Certificate Authority (CA) and then issue a new server certificate with that CA as described in the guide you mentioned. Then transfer this server certificate to the ESX server and put it into the correct place. I think you already have done th...

...ill some performance problem): https://github.com/Fantu/Xen/commits/rebase/m2r-testing unstable (working equal to kvm): https://github.com/Fantu/Xen/commits/rebase/m2r-next About linux domUs this is my latest test with xorg backtrace included: http://lists.xen.org/archives/html/xen-devel/2014-06/msg00342.html I hope this information is helpful to anyone who wants to try/use qxl on xen. Can someone take a look at the problem remained on linux domUsplease? Unfortunately, recently I have no time for in-depth debugging and most probably I not be able to solve the problem. > --- > docs/man...

...1. Reloading the guest driver will break the Tx/Rx; 2. Zeroing the flags when detaching a used desc will break the guest -> host path. Some simple functional tests have also been done with Wei's packed ring implementation in QEMU: http://lists.nongnu.org/archive/html/qemu-devel/2018-04/msg00342.html Both of ping and netperf worked as expected (with EVENT_IDX disabled). Reloading the guest driver also worked as expected. TODO: - Refinements (for code and commit log) and bug fixes; - Discuss/fix/test EVENT_IDX support; - Test devices other than net; RFC v2 -> RFC v3: - Split into smal...