Re: Warm Migration feature for bhyve - review on Phabricator

2021-01-24 Thread John-Mark Gurney
Matt Churchyard wrote this message on Fri, Jan 22, 2021 at 10:09 +:
> > Hello, all,
> 
> > We have recently opened a review on Phabricator for the warm migration code 
> > for > bhyve [1]. Please take a look and let us know if it is anything we 
> > can improve.
> 
> > [1] https://reviews.freebsd.org/D28270
> 
> > Thank you,
> > Elena
> 
> I appreciate that this isn't really related to the current review, and 
> commend the work being put into bhyve - it's an invaluable addition to 
> FreeBSD. I'm just wondering if any thought has been put into the future 
> possibility for transfer of disk data during migration (i.e. the equivalent 
> of "storage vmotion")
> 
> The current process (from a mile high overview) effectively seems to be the 
> following -
> 
> * Start guest on host2 pointing at a shared disk, and halt any execution
> * use bhyvectl to pause and begin migration on host1
> * Start the guest on host2
> 
> What would be the feasibility of being able to run a process such as the 
> following? Obviously it would likely need to be orchestrated by an external 
> tool, but to me it seems the main requirement is really just to be able to 
> provide separate control over the pause and migrate steps on host1 -
> 
> * send a ZFS snapshot of the running machine to host2
> * start the guest in migrate recv mode on host2
> * pause the guest on host1
> * send a new snapshot
> * initiate the migration of memory/device data
> * start guest on host2
> 
> Are there any major complications here I'm not aware of other than the 
> requirement to pause the guest and kick off the state migration as two 
> separate calls?

There's also hastd which can aid with this...

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 "All that I will do, has been done, All that I have, has not."
___
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"


Problem reports for virtualizat...@freebsd.org that need special attention

2021-01-24 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
In Progress |247208 | mpt(4): VMWare virtualized LSI controller panics  
New |240945 | [hyper-v] [netvsc] hn network driver incorrectly  

2 problems total for which you should take action.
___
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: RHEL virtualization

2021-01-24 Thread Chuck Tuffli
On Sat, Jan 23, 2021 at 3:16 PM John Kennedy  wrote:
...
> That being said, RHEL on bhyve has been a pain to figure out.  The best I've
> done so far is using sysutils/grub2-bhyve to set up the boot CD, using
> BHYVE_UEFI.fd as UEFI firmware (sysutils/bhyve-firmware I think) and then
> getting at the console via net/tigervnc-viewer.
>
> Currently I'm fighting grub-bhyve's issue finding the kernel to load (if I'm
> finding the right problem reports, it doesn't seem to like modern XFS or
> ext4 partitions).  I couldn't get net/ipxe to PXE boot anything, and I din't
> manage to get very far with sysutils/uefi-edk2-bhyve.  And of course some
> of these are flagged with python2.7 isses.

Hi

I ran into a similar situation (RHELL VM's in bhyve) and created a
version of grub-bhyve that knows how to find the grub.cfg and/or
syslinux.conf files in a VM's disk image. Because of this, you don't
have to maintain a copy of the grub configuration just for grub-bhyve.
I implemented this on the latest version of grub which includes XFS
and other goodies. The fine print:
 - The syntax is slightly different. To load an image use
grub-bhyve --disk=/path/to/vm/disk.img --vm=vm_name
note that the root, device-map, and directory options are no
longer necessary
- The project is at the "it works for me" stage and hasn't received
much usage aside from myself. That said, feedback is welcome.
 - It builds on FreeBSD 12.x but 13.x has an issue

Code is here: https://gitlab.com/ctuffli/grub

To build:
$ env PYTHON=python3.7 ./bootstrap
$ env MAKE=gmake ./configure --with-platform=bhyve
$ gmake

The resulting binary, `grub-bhyve`, will be in the `grub-core/`
directory. If you have success or troubles with it, please let me
know.

--chuck
___
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"