similar to: PCI Passthrough and Surprise Hotplug

On Mon, 5 Oct 2020 11:05:05 -0400 Marc Smith <msmith626@gmail.com> wrote: > Hi, > > I'm using QEMU/KVM on RHEL (CentOS) 7.8.2003: > # cat /etc/redhat-release > CentOS Linux release 7.8.2003 > > I'm passing an NVMe drive into a Linux KVM virtual machine (<type > arch='x86_64' machine='pc-i440fx-rhel7.0.0'>hvm</type>) which has the

Considering that the technic of SPDK + QEMU is making progress toward maturity. Personally I'd like to do the integration work. Not sure somebody would mind to give me some clue on that? Because I'm not familiar with libguestfs code structures. Thanks, Bob

On Thu, Dec 12, 2019 at 5:40 AM Michal Privoznik <mprivozn@redhat.com> wrote: > > On 11/27/19 4:12 PM, Mauricio Tavares wrote: > > I have been following the patches on nvme support on the list and was > > wondering: If I wanted to build a vm host to be on the bleeding edge > > for nvme and spdk fun in libvirt, which linux distro -- > > fedora/ubuntu/centos/etc

> What do you think about virtio-nvme+vhost-nvme? What would be the advantage over virtio-blk? Multiqueue is not supported by QEMU but it's already supported by Linux (commit 6a27b656fc). To me, the advantage of nvme is that it provides more than decent performance on unmodified Windows guests, and thanks to your vendor extension can be used on Linux as well with speeds comparable to

> What do you think about virtio-nvme+vhost-nvme? What would be the advantage over virtio-blk? Multiqueue is not supported by QEMU but it's already supported by Linux (commit 6a27b656fc). To me, the advantage of nvme is that it provides more than decent performance on unmodified Windows guests, and thanks to your vendor extension can be used on Linux as well with speeds comparable to

Hi there, when I try to start the nmbd -D daemon on my OpenServer5.0.5 box, I'll get the errormessage in log.nmbd: [...] [2002/03/12 19:30:18, 0] nmbd/nmbd.c:(783) Netbios nameserver version 2.2.3a started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2002/03/12 19:30:18, 0] lib/util_sock.c:(789) bind failed on port 137 socket_addr = 0.0.0.0. Error = Address already in use

hello, if i start a transient guest doamin via "virsh create abcd.xml" i see an additional libvirt thread and also some open files: pstree -h `pgrep libvirtd` libvirtd───11*[{libvirtd}] libvirtd 3016 root 21w REG 253,0 6044 1052094 /var/log/libvirt/libxl/abcd.log libvirtd 3016 root 22r FIFO 0,8 0t0 126124 pipe libvirtd 3016 root

Thanks for the information, I am unclear how to implement the winbind 'rid' backend. I've identified that winbindd is not operating on my demo server (fresh installation of Ubuntu 16), and am looking for some assistance if possible. 1] 'apt-get install winbind' informs me that the package is already installed (v4.3.9), yet it is not operating; 2] Lsof -Pnl +M -i4 provides:

------------------------ Dovecot Version: ------------------------ 2.0.13 ------------------------ Output of "dovecot -n": ------------------------ # 2.0.13: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.35-28-generic x86_64 Ubuntu 10.10 ext4 mail_location = maildir:/home/%u/Maildir passdb { args = %s driver = pam } protocols = imap pop3 ssl = no userdb { driver = passwd }

Hi Friends, I encountered a strange issue. I am running Asterisk 11.8.1 on Cent OS with no firewall running. It has 3 NIC interfaces. in my sip.conf I have allowguest=yes bindaddr=0.0.0.0 udpbindaddr = 0.0.0.0 But my Asterisk instance does not pick the call at all. When I check the listening apps using lsof -i I get asterisk 3046 asterisk 7u IPv4 1191172 0t0 TCP *:5038 (LISTEN)

Hello Rowland, I think avahi-daemon is not installed as standard in ubuntu 14.04.3 LTS Here is in our server : ROOT at SERVER:~# DPKG -L |GREP AVAHI II  LIBAVAHI-CLIENT3:AMD64              0.6.31-4UBUNTU1                  AMD64        AVAHI CLIENT LIBRARY II  LIBAVAHI-COMMON-DATA:AMD64          0.6.31-4UBUNTU1                  AMD64        AVAHI COMMON DATA FILES II 

Attempting to lookup why rsyslogd is listening on the high port UDP/51427. Have not succeeded in what this port is used for and what directive controls what interface it binds to. [root at bedrock ~]# netstat --listen --inet --program --numeric | grep syslog udp??0??0 0.0.0.0:51427??0.0.0.0:*???66655/rsyslogd? -- Adam Tauno Williams <mailto:awilliam at whitemice.org> GPG D95ED383

Hi! On my FreeBSD 12.0-RELEASE-p7 server I was unable to retrieve the correct information from my two UPS. Every time only the first UPS will returned when I entering "upsc apc900" or "upsc apc901". I don't know why (Bug or configuration issue on my side?!). I have downloaded the latest source code and with my "patch" I was able to get the right information

Hi Alberto, With systemd it will be as easy as creating additional unit files ( one for > each memcached instance) with its corresponding config file. That should > allow to stop / start / restart each memcache instance individually while > also being systemd compliant. Thanks for the info and for the examples. It really does make sense the way you explain it. Thanks for letting me

Hello, I am attempting to install Samba as a file server within an Active Directory domain to use the AD server for group authentication. I have worked through various guides, but all leave me unable to authenticate into the samba shares using my organizations existing user groups in Active Directory. I need the following configuration: Share - users : description Admin - Admin : This share is

On 14.05.20 08:44, teawater wrote: > Hi David, > > I got a kernel warning with v2 and v3. Hi Hui, thanks for playing with the latest versions. Surprisingly, I can reproduce even by hotplugging a DIMM instead as well - that's good, so it's not related to virtio-mem, lol. Seems to be some QEMU setup issue with older machine types. Can you switch to a newer qemu machine version,

Occasionally, all of our directors get stuck in an endless loop. Likely triggered by some network event, but I haven't been able to isolate exactly what triggers it, and am unable to reproduce at the moment. When this happens, it makes the dovecot/director process on all directors unresponsive, making login impossible. Restarting dovecot "fixes" it. Here's the info collected

On Thu, 2015-09-17 at 17:55 -0700, Nicholas A. Bellinger wrote: > On Thu, 2015-09-17 at 16:31 -0700, Ming Lin wrote: > > On Wed, 2015-09-16 at 23:10 -0700, Nicholas A. Bellinger wrote: > > > Hi Ming & Co, > > > > > > On Thu, 2015-09-10 at 10:28 -0700, Ming Lin wrote: > > > > On Thu, 2015-09-10 at 15:38 +0100, Stefan Hajnoczi wrote: > >

On Thu, 2015-09-17 at 17:55 -0700, Nicholas A. Bellinger wrote: > On Thu, 2015-09-17 at 16:31 -0700, Ming Lin wrote: > > On Wed, 2015-09-16 at 23:10 -0700, Nicholas A. Bellinger wrote: > > > Hi Ming & Co, > > > > > > On Thu, 2015-09-10 at 10:28 -0700, Ming Lin wrote: > > > > On Thu, 2015-09-10 at 15:38 +0100, Stefan Hajnoczi wrote: > >

On Thu, 2015-09-10 at 15:38 +0100, Stefan Hajnoczi wrote: > On Thu, Sep 10, 2015 at 6:48 AM, Ming Lin <mlin at kernel.org> wrote: > > These 2 patches added virtio-nvme to kernel and qemu, > > basically modified from virtio-blk and nvme code. > > > > As title said, request for your comments. > > > > Play it in Qemu with: > > -drive