[GSOC] Instruction caching for bhyve

2014-03-17 Thread Mihai Carabas
Hi, My name is Mihai Carabas and I'm a first year student at PhD in University POLITEHNICA from Bucharest, Romania. After some discussions with Neel Natu about choosing a bhyve project, I came with a GSOC proposal for the project "Instruction caching for bhyve" which is publicly av

[GSoC-Proposal] Porting bhyve on an ARMv8 platform

2016-03-19 Thread Mihai Carabas
Hi everyone, My name is Mihai Carabas and I'm a third year student at PhD in University POLITEHNICA from Bucharest, Romania. After some discussions with Peter Grehan about next steps in bhyve-arm, I came with a GSoC proposal for the project "Porting bhyve an an ARMv8 platform" wh

Re: [GSoC-Proposal] Porting bhyve on an ARMv8 platform

2016-03-25 Thread Mihai Carabas
gible. I apologize to the FreeBSD organization members that manage the GSoC program because I didn't read carefully this year's rules. Thank you, Mihai Carabas On Sat, Mar 19, 2016 at 11:19 AM, Mihai Carabas wrote: > Hi everyone, > > My name is Mihai Carabas and I'm a

Re: [GSoC-Proposal] Porting bhyve on an ARMv8 platform

2016-03-25 Thread Mihai Carabas
ects will not be >> done which seem a bigger issue when someone participating 3 times >> >> On 25 March 2016 at 11:50, Mihai Carabas wrote: >> >>> Hi everyone, >>> >>> Unfortunatelly I have to officially retreat my proposal from GSoC due >>>

Re: [GSoC-Proposal] Porting bhyve on an ARMv8 platform

2016-03-25 Thread Mihai Carabas
Hello, I didn't exclude my work on the port. I've only retreat my proposal for GSoC not to invalidate a student slot for FreeBSD. That's all. I'm still interested in all bhyve related projects. Thank you, Mihai On Mar 25, 2016 5:16 PM, "Allan Jude" wrote: > O

Re: Inspect pages created after a vm_object is marked as copy-on-write

2018-06-30 Thread Mihai Carabas
On Sat, Jun 30, 2018 at 1:52 AM, Mark Johnston wrote: > On Fri, Jun 29, 2018 at 11:58:31AM +0300, Elena Mihailescu wrote: >> Hello, >> >> I am interested if there is a method to inspect what pages/objects were >> created after a vm_object (the vm_map_entry associated with the object) is >> marked

Re: bhyve/arm64 status

2019-05-27 Thread Mihai Carabas
Hello, There is no bhyve-arm/arm64 in current. All the code is on our repo here [1], but has an old HEAD. We did a rebase last week but we did not tested [2]. Currently the code is not mergeable as bhyve does not have a structure of machine dependent/independent code and creating such a structur

Re: bhyve/arm64 status

2019-05-27 Thread Mihai Carabas
And also: - for ARM you have here a tutorial: https://github.com/FreeBSD-UPB/freebsd/wiki/Running-a-FreeBSD-guest-under-bhyve-on-ARM-systems - for ARM64 here: https://github.com/FreeBSD-UPB/bhyvearm64-utils On Mon, May 27, 2019 at 10:26 AM Mihai Carabas wrote: > > Hello, > > There

Re: bhyve fails on arm64 -- unknown exception type

2019-07-17 Thread Mihai Carabas
Hello Kamil, We will try to look into that but probably from September. Now we are engaged with reviewing save/restore and live migration. Thank you for testing, Mihai On Mon, Jul 15, 2019 at 1:41 PM Alexandru Elisei wrote: > > Hello, > > From the error message and the symptoms you described, i

Re: [bhyve][arm64] Number of allowed vcpus

2021-01-13 Thread Mihai Carabas
Hello, >From my perspective bhyve should use what is stated in the device tree if no parameter is given and throw an error when N is greater than the device tree value. Mihai On Wed, Jan 13, 2021 at 1:55 PM Andrei Martin wrote: > Hello, > > While working on enabling multiple virtual cpus for t

Re: [bhyve][arm64] Number of allowed vcpus

2021-01-13 Thread Mihai Carabas
On Wed, Jan 13, 2021 at 4:55 PM Rodney W. Grimes < freebsd-...@gndrsh.dnsmgr.net> wrote: > > Hello, > > > > >From my perspective bhyve should use what is stated in the device tree > if > > no parameter is given and throw an error when N is greater than the > device > > tree value. > > > > Mihai >

Re: Warm Migration feature for bhyve - review on Phabricator

2021-01-22 Thread Mihai Carabas
Hello Matt, Thank you for your input. The Warm/Live Migration feature is designated for cloud and cluster environments. Storage Live Migration is a feature that would be nice to have, but will be tackled after we get in warm migration and live migration using a shared storage. The code base is big