similar to: [PATCH] QEMU KVM balloon support

Displaying 12 results from an estimated 12 matches similar to: "[PATCH] QEMU KVM balloon support"

2008 Jan 08
1
[PATCH] KVM: add KVM_SYNC_SHADOW_WITH_USER ioctl
The host needs to zap its shadow entries before performing an inflate operation to avoid the guest from using stale ones. So add an ioctl to interface with kvm_mmu_zap_all(). Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com> Index: kvm.quilt/arch/x86/kvm/x86.c =================================================================== --- kvm.quilt.orig/arch/x86/kvm/x86.c +++
2003 Apr 23
3
top failure
Hello gentlemen, I've discovered an interesting failure on some machine running 4.7. It's so weird so I'd very unlikely notice it at all, but thanks to top(1): when launched, instead of displaying some useful figures it exits with an error: "top: nlist failed". >From quick look it appears that kvm_nlist() returns NULL for nlst[0].n_type. Strange, ignoring; next exit point
2003 Apr 19
1
proc size mismatch - yes, I re-installed my kernel
Hi, Please, need help # ps ax ps: proc size mismatch (65720 total, 1056 chunks) "userland out of sync with kernel, recompile libkvm etc" This is after buildworld, what do I do? It messes up many things in the system yes, I re-installed my kernel and even tried GENERIC kernel that comes with new update. Thank you Best Regards, Anton
2008 Jun 27
2
PCI device assignment to guests (userspace)
Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.
2008 Jun 27
2
PCI device assignment to guests (userspace)
Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.
2007 May 15
1
Asterisk 1.4.4 reproducibly dumps core on Solaris 10
I have built Asterisk 1.4.4 on my Solaris 10 x86 box: LDFLAGS='-R/usr/sfw/lib -R/opt/csw/lib -L/opt/csw/lib -L/usr/sfw/lib' CPPFLAGS=-I/opt/csw/include ./configure -with-curl=/opt/csw --without-oss --without-vpb --prefix=/opt/asterisk-1.4 The build and install go fine but the asterisk executable reproducibly dumps core with a segmentation violation. If I start it as: asterisk -gc and
2007 Jul 26
0
Asterisk 1.4.9 reproducibly dumps core on Solaris 10
> Message: 1 > Date: Tue, 15 May 2007 23:01:24 -0400 > From: Frank Tarczynski <ftarz at mindspring.com> > Subject: [asterisk-users] Asterisk 1.4.4 reproducibly dumps core on > Solaris 10 > To: asterisk-users at lists.digium.com > Message-ID: <464A7404.5000706 at mindspring.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I have
2012 Sep 09
8
bsnmpd always died on HDD detach
I am running bsnmpd with basic snmpd.config (only community and location changed). When there is a problem with HDD and disk disapeared from ATA channel (eg.: disc physically removed) the bsnmpd always dumps core: kernel: pid 1188 (bsnmpd), uid 0: exited on signal 11 (core dumped) I see this for a long rime on all releases of 7.x and 8.x branches (i386 and amd64). I did not tested 9.x. Is
2008 Aug 25
11
pid-provider sees ld.so.1 only
I''m trying to do some userspace tracing on a server-process with the pid provider. My problem is, that the only probes the pid-provider lists for the server-process (to which I attach dtrace with "-p nnnn") are coming from "ld.so.1". There''s not a single one from my modules. If I''m specifying "a.out" (or any of our shared-objects) as the
2008 Feb 28
14
Upgrading to 7.0 - stupid requirements
In http://www.freebsd.org/releases/7.0R/announce.html says Updating Existing Systems > An upgrade of any existing system to FreeBSD 7.0-RELEASE constitutes > a major version upgrade, so no matter which method you use to update > an older system you should reinstall any ports you have installed on > the machine. This will avoid binaries becoming linked to inconsistent > sets
2004 Sep 24
0
Astrison - many thanks - lots of enthusiams
Hi, Thanks alot to Mark and his team for bringing a great voip project and a great conference. I am a developper in the *BSD projects and will go back to these with the intention to help in providing a better availability of '*' for these OS's and also working the zaptel4BSD. cheers and see you soon. Julien
2005 May 30
0
perl agi : get_variable problem
Hi, I'm developping some AGI in perl (5.8.6) on i386 using Asterisk 1.0.5. I want to get some variables such as DIALSTATUS and ANSWEREDTIME after a $AGI->exec("Dial", "dial_string"); but here is what i get actually: DIALSTATUS= DIALEDTIME=ANSWER ANSWEREDTIME=18 I searched the archives and saw that $AGI->verbose could mess the access to variables, but I don't use