Re: bhyve with wlan0
As far as I remember it works just fine other than the standard caveats about bridging over wireless interfaces which involve some odd inconsistencies that could crop up from time to time especially with like DHCP, but a lot of that depends on your network config as a whole. The approach I would consider taking for a wireless host is if the guest doesn't need direct access to the network just do a NAT network or a routed network and route through the wlan interface instead of trying to do bridging with it directly. --- Jason Barbier | E: ja...@corrupted.io GPG: FD7D2D5F0A0FBE39 (https://keybase.io/kusuriya) On Fri, Nov 27, 2020, at 09:03, tech-lists wrote: > Hi, > > As subject: can a machine that only uses wlan0 for its connectivity > be a bhyve host? Context is 12.2-stable r367858 amd64. > > Asking because ISTR some issue with bridging, but that was a while ago. > I'm anticipating managing instances with vm-bhyve. Previously have set > instances manually on other server hardware. > > thanks, > -- > J. > > Attachments: > * signature.asc ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Need X-server to run in bhyve guest
honestly, I just use remmina after enabling the vnc console on the guest, works like a charm every time Sent from my a tiny pocket computer. > On Nov 30, 2019, at 22:13, Victor Sudakov wrote: > > Dear Colleagues, > > If I were to test different desktop environments (gnome, xfce etc) in a > FreeBSD guest in bhyve, what X server (probably with vnc access, or rdp > access, or whatever?) would you advise? > > I actually want to see the *local* graphical desktop of a guest, not just > X-clients forwarded from guest to host, or drawing to a remote $DISPLAY > on the host. > > Any advice what to install on the guest and how to start it there? I > would probably need to persuade the Gnome/XFCE on the guest that the > guest has a monitor and video card... > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > 2:5005/49@fidonet http://vas.tomsk.ru/ ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: sysutils/docker-freebsd ?
yes there are plans, there is some coordinating going on at ircs://chat.freenode.net/#freebsd-docker but it's nothing impressive right now just a few users starting Sent from my a tiny pocket computer. > On May 7, 2019, at 22:22, Victor Sudakov wrote: > > Dear Colleagues, > > Do you know if there are plans to revive sysutils/docker-freebsd? It has > been "broken" for 2 months, and the FreeBSD Wiki says that > docker-freebsd is the recommended way of running docker apps. > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > 2:5005/49@fidonet http://vas.tomsk.ru/ ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: [vm-bhyve] Windows 2012 and 2016 servers guests would not stop
> On Apr 22, 2019, at 21:13, Victor Sudakov wrote:
>
> Paul Vixie wrote:
>>
>> Victor Sudakov wrote on 2019-04-22 19:43:
>> ...
And the implementation is pretty brutal:
# 'vm stopall'
# stop all bhyve instances
# note this will also stop instances not started by vm-bhyve
#
core::stopall(){
local _pids=$(pgrep -f 'bhyve:')
echo "Shutting down all bhyve virtual machines"
killall bhyve
sleep 1
killall bhyve
wait_for_pids ${_pids}
}
>>
>> yow.
Eew no that is painful to read!
>
> To be sure, I was unable to find the above code (as is) in
> /usr/local/lib/vm-bhyve/vm-* (the vm-bhyve port 1.3.0). It may be that
> something more intelligent is happening in a more recent version, like a
> sequential shutdown. However, "kill $pid; sleep 1; kill $pid" seems to
> be still present.
>
>>
I wonder what the effect of the second kill is,
that seems odd.
>>>
>>> Indeed.
>>
>> the first killall will cause each client OS to see a soft shutdown
>> signal. the sleep 1 gives them some time to flush their buffers. the
>> second killall says, time's up, just stop.
>>
>> i think this is worse than brutal, it's wrong. consider freebsd's own
>> work flow when trying to comply with the first soft shutdown it got:
>>
>> https://github.com/freebsd/freebsd/blob/master/sbin/reboot/reboot.c#L220
>>
>> this has bitten me more than once, because using "pageins" as a proxy
>> for "my server processes are busy trying to synchronize their user mode
>> state" is inaccurate. i think _any_ continuing I/O should be reason to
>> wait the full 60 seconds.
>
> Would it be beneficial to just hack /usr/local/lib/vm-bhyve/vm-* ?
>>
>> and so i think the "sleep 1" above should be a "sleep 65".
I would echo this and say it should probably be done in a way that you can have
a sliding window, some servers and services are not very fault tolerant on
their own. The example that springs to mind for me is the busy AD domain
controller I manage. It takes 15 mins to flush the disk buffer, if I kill it
before the buffer flushes I will have a bad day as my domain at best loses a
few transactions at worst is corrupted.
___
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"
Re: Windows 2019 server
happen to catch a stack trace for the crash? --- Jason Barbier | E: ja...@corrupted.io GPG: 0x40B8FA1D72EF0D89 (https://keybase.io/kusuriya) On Tue, Apr 2, 2019, at 9:05 AM, Michael wrote: > Hi, > I just tried on FreeBSD12 and Windows10, bhyve crashes when loading the > virtstor driver. > > > Am 2. April 2019 16:56:13 MESZ schrieb Nick Wolff : > >There is paravirtulized support in FreeBSD 11.2 and 12 but you need to > >sideload the virtio drivers into windows. Sadly microsoft doesn't ship > >with > >them even with how "cloud" focused they are. Ahci-hd will allow you to > >get > >around this. I know we had some restrictions in the past on needing > >specific virt-io drivers for windows I'm not sure if that is fixed now. > >I > >think nvme paravirtual might also just work with windows but haven't > >confirmed that lately. > > > >On Sun, Mar 3, 2019 at 8:19 AM Victor Sudakov > >wrote: > > > >> Jason Tubnor wrote: > >> > > >> > > Which kind of storage did you present to the Windows 2019 guest, > >> > > paravirtualized or ahcd-hd ? > >> > > >> > ahci-hd is what you want with bhyve and uefi > >> > >> Still no paravirtualized disks support for Windows guests, even in > >> FreeBSD 12? How sad. > >> > >> -- > >> Victor Sudakov, VAS4-RIPE, VAS47-RIPN > >> 2:5005/49@fidonet http://vas.tomsk.ru/ > >> > >___ > >freebsd-virtualization@freebsd.org mailing list > >https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > >To unsubscribe, send any mail to > >"freebsd-virtualization-unsubscr...@freebsd.org" > > Gruß > --- > Michael > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscr...@freebsd.org" > ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve: Detecting that a guest kernel has booted
None I know off the top of my head nor would that be really something easily done without some sort of agent. We could probably make some sort of inference based calls to the emulated registers but even then that wouldn't be that correct. --- Jason Barbier | E: ja...@corrupted.io On Mon, Mar 11, 2019, at 10:05 AM, Mark Raynsford via freebsd-virtualization wrote: > Hello! > > Leaving aside userland monitoring tools such as Prometheus[0], is there > any way to detect on the host that a guest kernel running in bhyve has > booted? I'm assuming "booted" in this sense to mean "PID 1 has probably > started". I'm guessing that there probably isn't, but I thought I'd > better ask anyway. "Not booted" would mean something like "Is sitting > at the Grub prompt doing nothing". > > [0] https://prometheus.io/ > > -- > Mark Raynsford | http://www.io7m.com > > > Attachments: > * null ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: sysutils/docker-freebsd: Searching for people to help
Sounds like fun, Ill try to pop into the IRC channel. --- Jason Barbier | E: ja...@corrupted.io GPG: 0x40B8FA1D72EF0D89 (https://keybase.io/kusuriya) On Tue, Feb 26, 2019, at 6:42 AM, Jochen Neumeister wrote: > Hello everybody. > > Currently @decke and I are working on the update of the port. We try to > change it completely to moby, and then of course, that the port is > working properly. > > For this we are still looking for people who want to work on this very > large update, or later can test the work. > > If you want, you can get it on Freenode on IRC #freebsd-docker. We try > to coordinate it there. > > > Cheers > > Jochen > > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscr...@freebsd.org" > ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Installing drivers onto WinPE image for bhyve
Yeah there really isnt an RTFM for this one. so what I would try is using the raw image file just like you would a drive, technically you should be able to DD it to the zvol but lets try to retrace the baby steps here. Also I would make sure the windows image is actually setup for UEFI boot or try the UEFI-CSM firmware for it. if you look in the same folder you installed the UEFI firmware there should be a file that contains UEFI- CSM in the name. That is just a legacy boot mode for UEFI that I have had luck getting somethings that are picky about EFI to boot. --- Jason Barbier | E: kusur...@corrupted.io On Wed, Jan 23, 2019, at 12:00 PM, Darren David wrote: > Certainly, Jason. I should also mention I'm running this VM under > FreeNAS 11.2-RELEASE. Basic details (from FreeNSD UI) are:> * Type Bhyve > * Autostart: false > * Virtual CPUs: 2 > * Memory: 4096 > * BootLoader: UEFI > * Com Port: /dev/nmdm8B> The ISO is simply mounted as a CDROM. > > I've got two other VMs working just fine on this server (Linux and > Windows 10), but both were created/installed from original ISO > installers. The VM with issues is a Windows 7 VM I'm attempting to > port from ESXi. So far, I have converted the .vmdk to a RAW image with > virtualbox, dd'd the RAW file to a ZFS zvol, and set that as the > primary storage for this VM. The good news is that the drive shows up, > but upon boot the VM just dumps out into EFI shell. My thinking was to > boot into a third-party windows EFI partition fixer (in this case, > it's a WinPE disk that loads EaseUS Partition Master, which is the > application having the input driver issues - only the Tab key works. I > did try using the OEM Windows recovery utils, but it didn't solve my > boot woes). Mind you, I've not found any evidence of folks > successfully porting VMs from ESXi to bhyve, so please stop me now if > it's known that this isn't something that can be done!> > FWIW, I'm fairly new to bhyve virtualization, so if there's a very > clear RTFM pointer out there that might clear some of this up, I'm > happy to review on my own time.> > Darren > > On Wed, Jan 23, 2019 at 11:39 AM Jason Barbier > wrote:>> Giving us your launch options/VM Configs > would probably help. >> depending on how you have the disks attached you may not need any >> drivers.>> >> --- >> Jason Barbier | E: kusur...@corrupted.io >> >> >> On Wed, Jan 23, 2019, at 11:30 AM, Darren David wrote: >> > Hey all- >> > >> > I'm working on a project to migrate some VMs over from ESXi to >> > bhyve. I'm>> > making a bit of progress (and will absolutely document >> what I've >> > learned if>> > and when I get it to work!), but I'm hung up on doing >> some EFI >> > boot repair.>> > I've got a WinPE disk image with some partition fixing >> software >> > I'm wanting>> > to try, but when the VM boots into the partition >> software, the >> > only thing>> > that works under VNC is the Tab key (!). No other keys, >> no mouse.>> > >> > I'm guessing I need to load some additional drivers to get this to >> > play>> > nice, but can anyone possibly tell me what drivers I need to get >> > additional>> > input working in Windows under Bhyve? >> > >> > Thank you in advance for any and all help, >> > Darren >> > ___ >> > freebsd-virtualization@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>> > To >> unsubscribe, send any mail to "freebsd-virtualization- >> > unsubscr...@freebsd.org" >> ___ >> freebsd-virtualization@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to "freebsd-virtualization- >> unsubscr...@freebsd.org" ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Installing drivers onto WinPE image for bhyve
Giving us your launch options/VM Configs would probably help. depending on how you have the disks attached you may not need any drivers. --- Jason Barbier | E: kusur...@corrupted.io On Wed, Jan 23, 2019, at 11:30 AM, Darren David wrote: > Hey all- > > I'm working on a project to migrate some VMs over from ESXi to bhyve. I'm > making a bit of progress (and will absolutely document what I've learned if > and when I get it to work!), but I'm hung up on doing some EFI boot repair. > I've got a WinPE disk image with some partition fixing software I'm wanting > to try, but when the VM boots into the partition software, the only thing > that works under VNC is the Tab key (!). No other keys, no mouse. > > I'm guessing I need to load some additional drivers to get this to play > nice, but can anyone possibly tell me what drivers I need to get additional > input working in Windows under Bhyve? > > Thank you in advance for any and all help, > Darren > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization- > unsubscr...@freebsd.org" ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve uefi="csm"
testing. the VM itself doesn't exist anymore and only gets spun up if I have to test CSM. Sent from my a tiny pocket computer. > On Oct 21, 2018, at 8:33 AM, Victor Sudakov wrote: > > Jason Barbier wrote: >> Nope I don't use vm-bhyve I use some scrips I home rolled. The os I was >> booting with CSM was arch linux. > > Why would you want to boot Arch Linux with CSM? It should be possible > to boot it either with grub2-bhyve or with UEFI. > > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > 2:5005/49@fidonet http://vas.tomsk.ru/ ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve uefi="csm"
Nope I don't use vm-bhyve I use some scrips I home rolled. The os I was booting with CSM was arch linux. Sent from my a tiny pocket computer. > On Oct 21, 2018, at 6:59 AM, Victor Sudakov wrote: > > Jason Barbier wrote: > >>> Has anyone been able to boot *anything* with uefi="csm"? >> Can you tell us a bit about your set up, like are you using helper scripts >> like libvirt? > > Sorry, I forgot to mention. I use sysutils/vm-bhyve with > sysutils/uefi-edk2-bhyve-csm firmware (uefi-edk2-bhyve-csm-0.1,1) > >> To answer the question you asked when I run a vm with the CSM firmware it >> works for me. > > Do you also use vm-bhyve and most importantly, what OS do you boot > with CSM firmware? > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > 2:5005/49@fidonet http://vas.tomsk.ru/ ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Question about bhyve
yep your using RDP wrong. So on the windows vm enable remote desktop, then RDP directly to the guest, not to the guest console. > On Jan 13, 2018, at 2:42 AM, Manish Jain <bourne.ident...@hotmail.com> wrote: > > >> On 01/12/18 07:46, Jason Barbier wrote: >> >>> On Thu, Jan 11, 2018, at 6:13 PM, Paul Webster via freebsd-virtualization >>> wrote: >>> I believe if you used TightVNC server on the windows box and the likewise >>> client on freebsd you can sync clipboards over it >>> >>> On 12 January 2018 at 01:51, Manish Jain <bourne.ident...@hotmail.com> >>> wrote: >>> >>>> Hi, >>>> >>>> I have a Win 10 vm under bhyve on my FreeBSD 11.1 box. Is there some way >>>> I can share clipboards between FreeBSD X and Windows ? > > > >> It may be better to install rdesktop or freerdp/remmina and use RDP > > > Hi Jason/others, > > I am really struggling in my RDP essay. I installed remmina twice over: > once from github and from ports. But when I ask remmina to connect to > :3350, I either get nothing at all or a forever-lasting > message "Connecting To ...", or a curt dump with "Illegal instruction". > > Pretty much the same behaviour with rdesktop. > > Am I doing something basically wrong ? Note that bhyve is being > instructed to send its output to port 3350. > > When I use TigerVNC@5900, everything works in a flash - except clipboard > sharing. > > I could not have imagined that setting up RDP is such a > calorie-consumer. There does not even seem like a FreeBSD RDP usage doc > on the web. > > Can someone kindly provide some tips ? > > > Thanks & Regards, > Manish Jain ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Question about bhyve
Tight can do it but its a pain to get it set up right in X windows. It may be better to install rdesktop or freerdp/remmina and use RDP, it will sync a bit better with windows and is a bit more reliable in my experience --- Jason Barbier | E: kusur...@corrupted.io GPG: 0x40B8FA1D72EF0D89 (https://keybase.io/kusuriya) On Thu, Jan 11, 2018, at 6:13 PM, Paul Webster via freebsd-virtualization wrote: > I believe if you used TightVNC server on the windows box and the likewise > client on freebsd you can sync clipboards over it > > On 12 January 2018 at 01:51, Manish Jain <bourne.ident...@hotmail.com> > wrote: > > > Hi, > > > > I have a Win 10 vm under bhyve on my FreeBSD 11.1 box. Is there some way > > I can share clipboards between FreeBSD X and Windows ? > > > > Thanks for any help. > > -- > > Manish Jain > > ___ > > freebsd-virtualization@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > To unsubscribe, send any mail to "freebsd-virtualization- > > unsubscr...@freebsd.org" > > > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization- > unsubscr...@freebsd.org" ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
