Hi,
> On 23 Feb 2024, at 18:37, Matthew Grooms wrote:
>
>> ...
> The problem occurs when an image file is used on either ZFS or UFS. The
> problem also occurs when the virtual disk is backed by a raw disk partition
> or a ZVOL. This issue isn't related to a specific underlying filesystem.
>
lease look at the TRIM operations when you perform WRITE testing. It
could be also related to the slow write I/O.
——
Vitaliy
> On 28 Feb 2024, at 21:29, Matthew Grooms wrote:
>
> On 2/27/24 04:21, Vitaliy Gusev wrote:
>> Hi,
>>
>>
>>> On 23 Feb 202
--filename=/dev/nvme0n2
—
Vitaliy
> Thanks,
>
> -Matthew
>
>
>
>> ——
>> Vitaliy
>>
>>> On 28 Feb 2024, at 21:29, Matthew Grooms
>>> <mailto:mgro...@shrew.net> wrote:
>>>
>>> On 2/27/24 04:21, Vitaliy Gusev
You probably should set up dump device to get crash info, stack, etc.
——
Vitaliy Gusev
> On 7 Jul 2022, at 15:29, Andriy Gapon wrote:
>
>
> I have a strange issue with running an 'appliance' image based on FreeBSD 12
> in bhyve on a machine with Ryzen 5800x proce
You probably should set up a dump device to get crash info, stack, etc.
——
Vitaliy Gusev
> On 7 Jul 2022, at 15:29, Andriy Gapon wrote:
>
>
> I have a strange issue with running an 'appliance' image based on FreeBSD 12
> in bhyve on a machine with Ryzen 5800x proce
Interesting enough. It would be nice if you find out what exactly triggered
your VM to reset.
—
Vitaliy
> On 1 Aug 2022, at 17:39, Andriy Gapon wrote:
>
> On 2022-07-10 20:28, Gleb Smirnoff wrote:
>> On Thu, Jul 07, 2022 at 03:29:04PM +0300, Andriy Gapon wrote:
>> A> I have a strange issue wit
breaking backward compatibility (resume can be
performed with old snapshots)
Remove variables without breaking backward compatibility
Use one file for snapshot
Improve restore command line: "bhyve -r $snapshot”, i.e. w/o additional
arguments
——
Vitaliy Gusev
>>> before
oints look good to me.
>
> -Rob
Of course no. Guest memory should be saved as is. As possible improvement -
only dirty memory/pages.
I was taking about saving with nvlist: device’s variables, registers, internal
data, etc.
Overall description will be provided shortly.
———
Vitaliy Gusev
0 00 ...
size=0x84
[pmtimer]
pmtimer.vds_version = 0x1 (1)
pmtimer.uptime = 0x26fd133e5cc (2679274464716)
[rtc]
rtc.vds_version = 0x1 (1)
rtc.data(BINARY): 0A 00 00 00 00 FE FF FF 10 35 13 3D 40 F7 14 00 ...
size=0x98
—
Thanks,
Vitaliy Gusev
me process and
would introduce just another level of complexity.
——
Vitaliy Gusev
Hi Tomek,
Try to answer to the all questions below, please let me know if I miss some
important.
> On 23 May 2023, at 21:58, Tomek CEDRO wrote:
>
> On Tue, May 23, 2023 at 6:06 PM Vitaliy Gusev wrote:
>> Hi,
>> Here is a proposal for bhyve snapshot/checkpoint image forma
It is ready but in internal git repo, and it needs time to port it to CURRENT
version. Probably week or so.
When I create review, I will notify you.
Thanks,
Vitaliy Gusev
> On 24 May 2023, at 20:33, Mario Marietto wrote:
>
> @gusev.vita...@gmail.com <mailto:gusev.vita...@gmail.c
Hi,
> On 24 May 2023, at 20:46, Miroslav Lachman <000.f...@quip.cz> wrote:
>
> On 24/05/2023 17:10, Vitaliy Gusev wrote:
>
>>>> Current snapshot implementation has disadvantages:
>>>> 3 files per snapshot: .meta, .kern, vram
>>>
>>>
It is impossible. However, as first attempt you can verify that multidev branch
works fine for you.
https://github.com/gusev-vitaliy/freebsd/tree/dev/D35590
——
Vitaliy Gusev
> On 24 May 2023, at 20:47, Mario Marietto wrote:
>
> Give me the internal git. I want to test it asap :)
&g
> On 25 May 2023, at 04:30, Tomek CEDRO wrote:
>
> On Wed, May 24, 2023 at 5:11 PM Vitaliy Gusev wrote:
>> Protecting requires more efforts and it should be clearly defined: what is
>> purpose. If
>> purpose is having checksum with 99.9% reliability, NVLIST HEA
dbook/book/#kernelconfig-building
Make sure that BHYVE_SNAPSHOT is enabled.
Also look at build(7):
https://man.freebsd.org/cgi/man.cgi?build(7)
>
> On Thu, May 25, 2023 at 3:40 PM Vitaliy Gusev <mailto:gusev.vita...@gmail.com>> wrote:
>>
>>
>>> On 25 May 202
Hi Corvin,
Thanks for your comments and advices.
Answers are below,
> On 5 Jun 2023, at 18:32, Corvin Köhne wrote:
>
> On Tue, 2023-05-23 at 19:05 +0300, Vitaliy Gusev wrote:
>> 2. HEADER PHYS format:
>>
>> 0+—+
>
type = nvlist
vers = 1
subvers = 0
[devices]
offset = 0x2b9d (11165)
size = 0x10145ba (16860602)
type = nvlist
vers = 2
subvers = 1
[memory]
offset = 0x120 (18874368)
size = 0x3ce0 (1021313024)
type = pages
vers = 1
subvers = 0
I hope I gained a whole understanding.
Thanks,
Vitaliy Gusev
ld be nice, if you provide more information and metrics for your
system, total RAM, memory assigned for VM, additional statistics for all
intensive processes (SIZE, RES), etc.
—
Vitaliy Gusev
> On 26 Jun 2023, at 13:44, Aryeh Friedman wrote:
>
> I am a 12 core machine that I want allocat
> On 26 Jun 2023, at 15:06, Aryeh Friedman wrote:
>
> On Mon, Jun 26, 2023 at 7:50 AM Vitaliy Gusev <mailto:gusev.vita...@gmail.com>> wrote:
>> ...
>> As recommendation:
>>
>> Look at an another memory consumers like ZFS, another processes
>>
20 matches
Mail list logo