Date: Sun, 12 Jan 2014 23:13:07 -0600 (CST) From: Bryan Venteicher <bryanv@daemoninthecloset.org> To: sbruno@freebsd.org Cc: freebsd-virtualization@freebsd.org Subject: Re: Virtio Driver Message-ID: <33701594.2026.1389589987223.JavaMail.root@daemoninthecloset.org> In-Reply-To: <1389555487.1395.7.camel@powernoodle.corp.yahoo.com> References: <CA%2BQLa9DPKVFN74wi0XMakKnMbWE%2BC1wC-3srPwqZ_tV6UxJp=Q@mail.gmail.com> <1389555487.1395.7.camel@powernoodle.corp.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- > What happens if you "camcontrol rescan all" ? > A VirtIO block device (and a parent VirtIO PCI device) is what is likely getting created here, so there is no SCSI bus to rescan. I had a prior private conversation with Robert last week. This particular use case will not work until PCI hotplug support is there - this is not a limitation of VirtIO (fundamentally or as implemented in FreeBSD). Workarounds include use VirtIO SCSI since it supports hot plug. In FreeBSD 10, VirtIO block supports the resize events from the hypervisor, but the GEOM support for this was not MFC'ed to 9. > sean > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?33701594.2026.1389589987223.JavaMail.root>