Directly reserve an interrupt IDT entry for Hyper-V

Hello, Sending to Xen, drivers and virtualization mailing lists since this might be of interest to the folks on these aliases. I am working for Microsoft to improve the performance of FreeBSD running on Hyper-V. Right now I am adding a feature in the vmbus driver which could handle the host-gu

Re: libvirt and rebooting of a bhyve VM

Allan Jude wrote: > On 2014-08-19 11:50, John Nielsen wrote: > > On Aug 19, 2014, at 9:40 AM, Roman Bogorodskiy wrote: > > > >> Craig Rodrigues wrote: > >> > >>> Roman, > >>> > >>> I am using libvirt and bhyve according to this XML: > >>> http://libvirt.org/drvbhyve.html > >>> and it works gr

Re: Directly reserve an interrupt IDT entry for Hyper-V

On 20/08/14 11:19, Wei Hu wrote: > Hello, > > Sending to Xen, drivers and virtualization mailing lists since this might be > of interest to the folks on these aliases. > > I am working for Microsoft to improve the performance of FreeBSD running on > Hyper-V. Right now I am adding a feature in t

Re: libvirt and rebooting of a bhyve VM

On Tuesday, August 19, 2014 2:33:19 pm Craig Rodrigues wrote: > On Tue, Aug 19, 2014 at 10:32 AM, John Baldwin wrote: > > The exit code is different. An ACPI shutdown uses an exit code of 1 whereas a > > reboot uses an exit code of 0 IIRC. > > > Hi, > > I have a CURRENT system, and ran some t

Re: Directly reserve an interrupt IDT entry for Hyper-V

On Wednesday, August 20, 2014 9:31:54 am Roger Pau Monné wrote: > On 20/08/14 11:19, Wei Hu wrote: > > Hello, > > > > Sending to Xen, drivers and virtualization mailing lists since this might be of interest to the folks on these aliases. > > > > I am working for Microsoft to improve the performa

Re: Directly reserve an interrupt IDT entry for Hyper-V

On 20/08/14 17:31, John Baldwin wrote: > On Wednesday, August 20, 2014 9:31:54 am Roger Pau Monné wrote: >> Hello, >> >> I don't think using the same IDT vector is the right approach, I would >> just pick a different IDT vector and use that for Hyper-V. Using the >> same IDT vector (like your sugge

Re: libvirt and rebooting of a bhyve VM

On Tue, Aug 19, 2014, Craig Rodriques wrote: On Tue, Aug 19, 2014 at 12:18 PM, Allan Jude wrote: The name of the vm is in the title of the bhyve process, but yes, it Hmm, OK, that would require me to grep the processes and send SIGTERM to the right pid. That's not ideal, especially if I star

Re: Directly reserve an interrupt IDT entry for Hyper-V

Hi John, On Wed, Aug 20, 2014 at 8:31 AM, John Baldwin wrote: > On Wednesday, August 20, 2014 9:31:54 am Roger Pau Monné wrote: >> On 20/08/14 11:19, Wei Hu wrote: >> > Hello, >> > >> > Sending to Xen, drivers and virtualization mailing lists since this might > be of interest to the folks on thes

Re: libvirt and rebooting of a bhyve VM

On Wed, Aug 20, 2014 at 8:15 AM, John Baldwin wrote: > It probably would be good to document the return codes in the man page, but > eventually they will all go away. The long term plan is to make bhyve operate > more like other hypervisors in which case a single process invocation will > mimic a

Re: libvirt and rebooting of a bhyve VM

Kurt Lidl wrote: > On Tue, Aug 19, 2014, Craig Rodriques wrote: > > On Tue, Aug 19, 2014 at 12:18 PM, Allan Jude > > wrote: > >> > >> The name of the vm is in the title of the bhyve process, but yes, it > > > > Hmm, OK, that would require me to grep the processes and send SIGTERM > > to the ri

RE: Directly reserve an interrupt IDT entry for Hyper-V

Hi Roger and John, I will request a free IDT slot instead of sharing the same vector with Xen. It would be great to have an API to do this. Before the API is available, I will probably use the same way as in vmm_ipi.c to find a free slot. Thanks so much for your help, Wei -Original Mess