Directly reserve an interrupt IDT entry for Hyper-V

2014-08-20 Thread Wei Hu
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

Re: libvirt and rebooting of a bhyve VM

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

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

2014-08-20 Thread Roger Pau Monné
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 the

Re: libvirt and rebooting of a bhyve VM

2014-08-20 Thread John Baldwin
On Tuesday, August 19, 2014 2:33:19 pm Craig Rodrigues wrote: On Tue, Aug 19, 2014 at 10:32 AM, John Baldwin j...@freebsd.org 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

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

2014-08-20 Thread John Baldwin
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 performance of

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

2014-08-20 Thread Roger Pau Monné
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 suggestion

Re: libvirt and rebooting of a bhyve VM

2014-08-20 Thread Kurt Lidl
On Tue, Aug 19, 2014, Craig Rodriques wrote: On Tue, Aug 19, 2014 at 12:18 PM, Allan Jude allanjude at freebsd.org 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

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

2014-08-20 Thread Neel Natu
Hi John, On Wed, Aug 20, 2014 at 8:31 AM, John Baldwin j...@freebsd.org 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

Re: libvirt and rebooting of a bhyve VM

2014-08-20 Thread Craig Rodrigues
On Wed, Aug 20, 2014 at 8:15 AM, John Baldwin j...@freebsd.org 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

Re: libvirt and rebooting of a bhyve VM

2014-08-20 Thread Roman Bogorodskiy
Kurt Lidl wrote: On Tue, Aug 19, 2014, Craig Rodriques wrote: On Tue, Aug 19, 2014 at 12:18 PM, Allan Jude allanjude at freebsd.org 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