On Mon, Aug 20, 2018 at 9:41 AM, Stefan <[email protected]> wrote: > Hello Mike, > > Am 15.08.2018 16:28, schrieb Mike Gerdts: > >> 1. Are the 'old' SmartOS virtual machines images, [...] >>> supposed to be usable under bhyve? [...] >>> >> >> That is expected. With KVM, QEMU provides a built-in dhcp server. >> > > Sure. I need to set up a DHCP server.
This is an area that has not received much testing. I think that setting nics.*.ip[s] (see vmadm man page) to "dhcp" should allow the DHCP packets through. See the other notes on "dhcp" in that man page if setting up another instance to act as a dhcp server. Alternatively, you can statically configure the IP address(es) to match the IP(s) in nics.*.ip[s]. > > > This >> allows the guest OS's DHCP client and QEMU to cooperate to get the >> network configuration that is found in the zone configuration. This >> does not exist for bhyve. Instead, we are shifting over to using >> cloud-init in all of our linux images. >> > > Will there be any "compatibility mode" in order to make bhyve behave > as a plug-in-replacement of qemu-kvm? > Nothing is planned at this time. That doesn't mean it won't happen, it just means our focus right now is getting bhyve to work well for new installations. > > You can find a version of >> cloud-init that should work with centos 7 at >> >> [...] >> >> To install: >> > > I cannot install software in already deployed VMs. > Understood. > > 2. Is there a migration path from TYPE=KVM to TYPE=BHYV? >>> >> >> There is not a supported conversion procedure, but it can usually be >> done. >> What I say below (and above) is largely from memory and a >> smattering of notes generated as we were working on official images. >> >> I modified the >>> brand attribute in /etc/zones/...xml file of an a earlier installed >>> instance (image uuid 6aac0370-56b8-11e7-a29b-df1de8b42795 = >>> centos-6 >>> 20170621) and startet the VM. It comes up, network is up, I can ssh >>> into the VM. But >>> >>> - there is no output on vmadm console >>> >> >> You will need to update /etc/default/grub, adding this about the first >> title line: >> >> serial --unit=0 --speed 115220 >> terminal --timeout=2 serial console >> [...] >> > > Instead of changing of VMs (I can't do that anyway) I would prefer > a "compatibility mode": Can bhyve be started such that the serial console > is configured as before? > > If your kvm instance already had something responding to "vmadm console", that will continue to work via "vmadm console" or "zlogin -C". Note that kvm is an oddball for the escape sequence to disconnect from "vmadm console". kvm treats "^]" as the complete sequence to exit the console. All other brands (including bhyve) require "^].". This is because kvm does not use "zlogin -C" to implement "vmadm console" but all other brands do. Those that use "zlogin -C" pass "-e ^]" to zlogin. Mike ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125 Powered by Listbox: https://www.listbox.com
