Date: Wed, 27 Mar 2013 19:05:02 +0900 From: Takuya ASADA <syuu@dokukino.com> To: Neel Natu <neelnatu@gmail.com> Cc: freebsd-virtualization@freebsd.org Subject: Re: suspend/resume on BHyVe Message-ID: <CALG4x-Wrhtq000-5RuVkdmRH%2BcjDvg-vGLaUzxWi9k2o5zEmHw@mail.gmail.com> In-Reply-To: <CAFgRE9FqqJSTrtTA4PmdSsCdbEGi57jHOLZH0EkK83yJ3HqYpQ@mail.gmail.com> References: <CAJ-Y7VcZ=EbAesb%2B8Pup1YsSE_yaM_345KZjwibjaC=GMo0xfA@mail.gmail.com> <CAFgRE9FqqJSTrtTA4PmdSsCdbEGi57jHOLZH0EkK83yJ3HqYpQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > A brute force way of figuring out all the state must be saved is to > look at all the initialization functions that are called when a vm and > a vcpu are created. So, this would be vm_create() and vcpu_init() in > the kernel module. I think these things are need to dump by resume action: - guest memory area - struct vmxctx - VMCS page - VLAPIC registers - virtio device state (dumping virtio ring?) - current configuration of bhyve process (with was configured by an arguments passed to bhyve process) Maybe there's more.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALG4x-Wrhtq000-5RuVkdmRH%2BcjDvg-vGLaUzxWi9k2o5zEmHw>