search for: blairo

Displaying 10 results from an estimated 10 matches for "blairo".

Did you mean: blair
2017 Nov 14
2
Re: dramatic performance slowdown due to THP allocation failure with full pagecache
...irectly reclaim and defrag in order to allocate a hugepage if at all possible. In my test-case there is almost no free memory, so some pagecache has to be reclaimed for the process, I don't understand why the THP allocation fails in this case versus when pagecache is lower though. -- Cheers, ~Blairo
2017 Feb 14
3
high memory guest issues - virsh start and QEMU_JOB_WAIT_TIME
...uestions: 1) will this change have any untoward side-effects? 2) if not, then is there any reason not to change it in master until a better solution comes along (or possibly better, alter qemuDomainObjBeginJobInternal to give a domain start job a little longer compared to other jobs)? -- Cheers, ~Blairo
2017 Nov 14
2
dramatic performance slowdown due to THP allocation failure with full pagecache
...lated and possibly dumb question: in the case of a high-performance KVM where the guest is hugepage backed and pinned in host memory anyway, why do we still have a table based resolution for guest physical to host virtual address translation - couldn't this just be done by offset? -- Cheers, ~Blairo
2016 Dec 06
0
Re: How to best I/O performance for Window2008 and MSSQL guest VM
...look at and/or what would be the right setup? > > Thanks in advance. > Roberto Fichera > > > _______________________________________________ > libvirt-users mailing list > libvirt-users at redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users -- Cheers, ~Blairo
2017 Nov 14
1
Re: dramatic performance slowdown due to THP allocation failure with full pagecache
...lated and possibly dumb question: in the case of a high-performance KVM where the guest is hugepage backed and pinned in host memory anyway, why do we still have a table based resolution for guest physical to host virtual address translation - couldn't this just be done by offset? -- Cheers, ~Blairo
2017 Feb 15
0
Re: high memory guest issues - virsh start and QEMU_JOB_WAIT_TIME
...thinking about building a custom package to work around this for the moment, or even attempting to find the right hexedit against the existing shared object o_0... probably a line of thinking I should squash now. Would it be helpful to have this registered as a customer RFE with Red Hat? Cheers, ~Blairo
2016 Dec 06
1
Re: How to best I/O performance for Window2008 and MSSQL guest VM
On 12/06/2016 06:06 AM, Blair Bethwaite wrote: > Hi Roberto, Hi Blair > What is the cpu and memory configuration of your guest? I've set to copy host configuration (16 cores) and memory is set to 24GB, host has 64GB. Guest is Windows 2012 64bits version Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 16
2016 Dec 05
2
How to best I/O performance for Window2008 and MSSQL guest VM
Hi There, I've moved some Windows2012 with MSSQL VMs from an hold ESXi 5.5 machine to a more recent and powerful machine running Fedora 24 x86_64 and related libvirt + KVM virtualization. I've moved the VMs filesystem to LVM slices and installed the VirtIO drivers in to all Windows VMs. I've also set both Disk and Network interface to work using VirtIO. So far so good everything works
2017 Feb 15
2
Re: high memory guest issues - virsh start and QEMU_JOB_WAIT_TIME
...5 int monfd; 326 int timeout = 30; /* In seconds */ Is this safe to increase? Is there any reason to keep it at 30s given (from what I'm seeing on a fast 2-socket Haswell system) that hugepage backed guests larger than ~160GB memory will not be able to start in that time? -- Cheers, ~Blairo
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 >