From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33340) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZHmtp-00074G-BY for qemu-devel@nongnu.org; Wed, 22 Jul 2015 01:49:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZHmtl-0000vI-As for qemu-devel@nongnu.org; Wed, 22 Jul 2015 01:49:01 -0400 Received: from fm2nodo1.polito.it ([130.192.180.12]:36152) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZHmtk-0000v7-WC for qemu-devel@nongnu.org; Wed, 22 Jul 2015 01:48:57 -0400 Message-ID: <55AF2EC6.1060500@polito.it> Date: Wed, 22 Jul 2015 07:48:54 +0200 From: Ivano Cerrato MIME-Version: 1.0 References: <55AE1B42.5040306@polito.it> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Does PCI hotplug work with IVSHMEM? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?B?TWFyYy1BbmRyw6kgTHVyZWF1?= Cc: =?UTF-8?B?TWF1cmljaW8gVsOhc3F1ZXo=?= , Fulvio Risso , QEMU Thank you for the answer! Why do you say that it is not safe to do hotplug with ivshmem? Ivano Il 21/07/2015 18:37, Marc-Andr=C3=A9 Lureau ha scritto: > Hi > > On Tue, Jul 21, 2015 at 12:13 PM, Ivano Cerrato wrote: >> Is there any way to force the Guest OS to recognize the new device wit= hout >> rebooting? Such as rmmod/insmod or equivalent? > This can be observed in qemu monitor too, info qtree: > > dev: ivshmem, id "" > chardev =3D "" > size =3D "2048M" > vectors =3D 1 (0x1) > ioeventfd =3D false > msi =3D true > shm =3D "foo" > role =3D "" > use64 =3D 1 (0x1) > addr =3D 05.0 > romfile =3D "" > rombar =3D 1 (0x1) > multifunction =3D false > command_serr_enable =3D true > class RAM controller, addr 00:05.0, pci id 1af4:1110 (sub 1af4= :1100) > bar 0: mem at 0x40000000 [0x400000ff] > bar 2: mem at 0xffffffffffffffff [0x7ffffffe] > > Check dmesg, it fails to allocate for me, but with 1G it works (f22 > x86_64). I don't know what's the reason behind it. > > Note that it's not safe to do hotplug with ivshmem (it may assert in > various ways), I proposed a patch series a few weeks ago, I am going > to send an updated version soon. >