On Tue, Jan 02, 2024 at 08:29:03PM +0100, Kirill A. Korinsky wrote:
> And one more noticed bug in vmd regarding memory.
>
> If I changed memory in /etc/vm.conf for running machine, run rcctl reload vmd,
> and restart VM... It has no effect.
>
> The VM should be shutdown before reload.
>
> --
>
And one more noticed bug in vmd regarding memory.
If I changed memory in /etc/vm.conf for running machine, run rcctl reload vmd,
and restart VM... It has no effect.
The VM should be shutdown before reload.
--
wbr, Kirill
> On 2. Jan 2024, at 19:58, Kirill A. Korinsky wrote:
>
> Anyway, right now it fails as:
>
>> vmctl: start vm command failed: Invalid argument
>
> and if I revert may changes (to 10G for example) at cat /etc/login.conf.d/vmd
> from:
>> vmd:\
>> :datasize=100G:\
>> :tc=daemon:
>
>
> On 2. Jan 2024, at 20:13, Mischa wrote:
>
> On 2024-01-02 19:58, Kirill A. Korinsky wrote:
>>> On 2. Jan 2024, at 19:17, Dave Voutila wrote:
vmd: failed to start vm podman
vmd: vm_stop: vmd config_setvm stopping vm 3
This machine runs 4 more VM and this one (huge) should be
On 2024-01-02 19:58, Kirill A. Korinsky wrote:
On 2. Jan 2024, at 19:17, Dave Voutila wrote:
vmd: failed to start vm podman
vmd: vm_stop: vmd config_setvm stopping vm 3
This machine runs 4 more VM and this one (huge) should be 5th.
Try this:
# cd /dev && sh MAKEDEV tap4
By default I
> On 2. Jan 2024, at 19:17, Dave Voutila wrote:
>
>> vmd: failed to start vm podman
>> vmd: vm_stop: vmd config_setvm stopping vm 3
>>
>> This machine runs 4 more VM and this one (huge) should be 5th.
>
> Try this:
>
> # cd /dev && sh MAKEDEV tap4
>
> By default I believe on amd64 we create
"Kirill A. Korinsky" writes:
> [[PGP Signed Part:Undecided]]
>> On 2. Jan 2024, at 18:41, Dave Voutila wrote:
>> "Kirill A. Korinsky" writes:
>
>>> vmctl -v start... doesn't help a bit
>>
>> How much physicaly memory does the host machine have? We currently don't
>> allow oversubscribing
On 2024-01-02 19:16, Kirill A. Korinsky wrote:
On 2. Jan 2024, at 18:41, Dave Voutila wrote:
"Kirill A. Korinsky" writes:
vmctl -v start... doesn't help a bit
How much physicaly memory does the host machine have? We currently
don't
allow oversubscribing memory with vmm/vmd. If the host
> On 2. Jan 2024, at 18:41, Dave Voutila wrote:
> "Kirill A. Korinsky" writes:
>> vmctl -v start... doesn't help a bit
>
> How much physicaly memory does the host machine have? We currently don't
> allow oversubscribing memory with vmm/vmd. If the host only has 16GB
> that could be the cause.
"Kirill A. Korinsky" writes:
>> On 2. Jan 2024, at 12:07, Kirill A. Korinsky wrote:
>>
>> Confirmed that it is:
>>
>> island$ grep '^vmd:' -A 2 /etc/login.conf
>> vmd:\
>> :datasize=16384M:\
>> :tc=daemon:
>> island$
>
>
> Wel.. after that changes error has been changed to:
>
>>
> On 2. Jan 2024, at 12:07, Kirill A. Korinsky wrote:
>
> Confirmed that it is:
>
> island$ grep '^vmd:' -A 2 /etc/login.conf
> vmd:\
> :datasize=16384M:\
> :tc=daemon:
> island$
Wel.. after that changes error has been changed to:
> vmctl: start vm command failed: Unknown
> On 2. Jan 2024, at 08:58, Janne Johansson wrote:
>
> Den mån 1 jan. 2024 kl 21:44 skrev Kirill A. Korinsky :
>>
>> How can I run a VM with more than 16G of memory?
>> A naive approach fails with error:
>>> vmctl: start vm command failed: Cannot allocate memory
>>
>> Yes, the host machine
Den mån 1 jan. 2024 kl 21:44 skrev Kirill A. Korinsky :
>
> Greetings,
> How can I run a VM with more than 16G of memory?
> A naive approach fails with error:
> > vmctl: start vm command failed: Cannot allocate memory
>
> Yes, the host machine has that memory and much more.
Check datasize in
13 matches
Mail list logo
