Displaying 6 results from an estimated 6 matches for "qemu_job_wait_tim".
Did you mean:
qemu_job_wait_time
2017 Feb 14
0
Re: high memory guest issues - virsh start and QEMU_JOB_WAIT_TIME
...; seeing attempting to launch high memory KVM guests backed by hugepages...
>
> In this case the guests have 240GB of memory allocated from two host NUMA
> nodes to two guest NUMA nodes. The trouble is that allocating the hugepage
> backed qemu process seems to take longer than the 30s QEMU_JOB_WAIT_TIME
> and so libvirt then most unhelpfully kills the barely spawned guest. Dan
> said there was currently no workaround available so I'm now looking at
> building a custom libvirt which sets QEMU_JOB_WAIT_TIME=60s.
>
> I have two related questions:
> 1) will this change have any...
2017 Feb 14
3
high memory guest issues - virsh start and QEMU_JOB_WAIT_TIME
...is of an issue we are
seeing attempting to launch high memory KVM guests backed by hugepages...
In this case the guests have 240GB of memory allocated from two host NUMA
nodes to two guest NUMA nodes. The trouble is that allocating the hugepage
backed qemu process seems to take longer than the 30s QEMU_JOB_WAIT_TIME
and so libvirt then most unhelpfully kills the barely spawned guest. Dan
said there was currently no workaround available so I'm now looking at
building a custom libvirt which sets QEMU_JOB_WAIT_TIME=60s.
I have two related questions:
1) will this change have any untoward side-effects?
2) if...
2017 Feb 15
0
Re: high memory guest issues - virsh start and QEMU_JOB_WAIT_TIME
On 02/15/2017 03:43 AM, Blair Bethwaite wrote:
> On 15 February 2017 at 00:57, Daniel P. Berrange <berrange@redhat.com> wrote:
>> What is the actual error you're getting during startup.
>
> # virsh -d0 start instance-0000037c
> start: domain(optdata): instance-0000037c
> start: found option <domain>: instance-0000037c
> start: <domain> trying as
2017 Feb 15
0
Re: high memory guest issues - virsh start and QEMU_JOB_WAIT_TIME
On 15 February 2017 at 20:40, Daniel P. Berrange <berrange@redhat.com> wrote:
> On Wed, Feb 15, 2017 at 10:27:46AM +0100, Michal Privoznik wrote:
>> On 02/15/2017 03:43 AM, Blair Bethwaite wrote:
>> > On 15 February 2017 at 00:57, Daniel P. Berrange <berrange@redhat.com> wrote:
>> >> What is the actual error you're getting during startup.
>> >
2017 Feb 15
2
Re: high memory guest issues - virsh start and QEMU_JOB_WAIT_TIME
On 15 February 2017 at 00:57, Daniel P. Berrange <berrange@redhat.com> wrote:
> What is the actual error you're getting during startup.
# virsh -d0 start instance-0000037c
start: domain(optdata): instance-0000037c
start: found option <domain>: instance-0000037c
start: <domain> trying as domain NAME
error: Failed to start domain instance-0000037c
error: monitor socket did
2017 Feb 15
2
Re: high memory guest issues - virsh start and QEMU_JOB_WAIT_TIME
On Wed, Feb 15, 2017 at 10:27:46AM +0100, Michal Privoznik wrote:
> On 02/15/2017 03:43 AM, Blair Bethwaite wrote:
> > On 15 February 2017 at 00:57, Daniel P. Berrange <berrange@redhat.com> wrote:
> >> What is the actual error you're getting during startup.
> >
> > # virsh -d0 start instance-0000037c
> > start: domain(optdata): instance-0000037c
>