Date: Thu, 17 Dec 2015 08:52:24 -0700 From: Sergey Manucharian <sm@ara-ler.com> To: Peter Grehan <grehan@freebsd.org> Cc: Anish <akgupt3@gmail.com>, FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: CDROM options in bhyve Message-ID: <20151217155224.GA3487@debian.ara-ler.com> In-Reply-To: <567270F8.80102@freebsd.org> References: <20151216043720.GB22018@dendrobates.araler.com> <CALnRwMSi5FdsYCDS=rZs%2BpQK0qv9NYkL5kiW8W%2Bb0hBq5k12SQ@mail.gmail.com> <20151216194045.GJ9504@debian.ara-ler.com> <567270F8.80102@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Peter, Excerpts from Peter Grehan's message from Thu 17-Dec-15 18:23: > It should be a 'D' drive. Appended is a list from a w2k16 VM, with a > FreeBSD ISO on the ahci-cd drive (so it isn't bootable). You can also view > this graphically using Windows Administrative Tools -> System Information -> > Components -> CDROM. I think I haven't expressed my thoughts properly. Everything is OK on the guest side. The cdrom device is working fine in both Linux and Windows guests. My original question was about changing the cdrom image in the host when the guset is up and running - to make the guest seeing a new disk in the virtual drive. That's why I thought Anish mentioned devices created in the host system (vtbd0), but I was wrong. I was thinking about an idea to use a symlink to an .iso file in the host before the guest is booted, then, if needed, to re-point the symlink to another .iso file. But that doesn't work, of course. Thanks, Sergey
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151217155224.GA3487>