similar to: qemu-kvm version for CentOS

Centos is not going to generally have the cutting edge stuff. For that why not try fedora which will generally package with the newest libraries from various packages, including qemu . I think the current fedora repos have qemu 2.1 > On Jul 6, 2014, at 10:01 AM, kerwin <piaoyuankui@gmail.com> wrote: > > WHY CentOS still using qemu-kvm 0.12? > > What I am need is high

Hi, I am running OpenStack Cluster and use libvirt + cgroup to limit vm’s performance https://wiki.openstack.org/InstanceResourceQuota What I am confusing is.. 1. After running a vm instance with some croup limit applied, I can’t find any related cgroup settings. 2. Can I change limit value after instance is running? like change disk_read_iops_sec from 10 to 20. One of the xml file like below.

On 06.07.2014 16:01, kerwin wrote: > WHY CentOS still using qemu-kvm 0.12? > > What I am need is high version of qemu-kvm for CentOS, but seems like > they do not officially provide newest qemu, only qemu 0.12 source code > with 3522 patched rpm package. With distros it's always a question of stability vs bleeding edge. It's not possible to have git builds every day and

Hi list, i tried to write my first type and provider that should create logical volumes. Seems like i''m missing something as i get nothing when i use it: No errors and no logical volume :-( type/logicalvolume.rb: ================= Puppet::Type.newtype(:logicalvolume) do @doc = "Manage logical volumes" ensurable newparam(:lvname) do desc "The logcal

On Thu, 12 Mar 2015 14:56:08 -0400 Laine Stump <laine@laine.org> wrote: > Here is the info straight from the author (I've also Cc'ed him to this > mail): > > =============== > The AHCI migration series is here: > > http://lists.gnu.org/archive/html/qemu-devel/2015-02/msg05200.html > These are all just tests, at any rate -- the actual patch that enables

On Mon, 23 Mar 2015 10:36:33 -0400 John Snow <jsnow@redhat.com> wrote: > > Are the needed patches in 2.3.0-rc0? > > Is it possible to backport AHCI migration to RHEL 7.1 qemu or will it be too much work? > > The patches that improve the stability of AHCI migration are in 2.3-rc0. > We still have not /enabled/ migration upstream, but editing to code to > allow it

After 3.10 you'd need to use storhaug.... Which.... doesn't work (yet). You need to use 3.10 for now. On 07/06/2017 12:53 PM, Anthony Valentine wrote: > I'm running this on CentOS 7.3 > > [root at glustertest1 ~]# cat /etc/redhat-release > CentOS Linux release 7.3.1611 (Core) > > > Here are the software versions I have installed. > > [root at

Hey Keir, I committed the last of the big outstanding tools blockers for 4.2 yesterday. Currently they are still in staging because they added some new xenstore paths which tickled the leak detector in the test system What do you think of doing an rc0 release next week? There''s still some smaller issues remaining but I think they can wait until rc1. Ian.

02:00.0 VGA compatible controller: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) Chipset: G98 (NV98) Family : NV50 The same for all four kernel: - 3.18.0-0.rc0.git8.1.fc22.x86_64 - 3.18.0-0.rc0.git9.1.fc22.x86_64 - 3.18.0-0.rc0.git9.3.fc22.x86_64 - 3.18.0-0.rc0.git9.4.fc22.x86_64 after "fb: switching to nouveaufb from VESA VGA" display is powered off. The magic SysRq key

On 13.09.2014 22:58, Ilia Mirkin wrote: > On Sat, Sep 13, 2014 at 4:52 PM, poma <pomidorabelisima at gmail.com> wrote: >> On 13.09.2014 07:02, poma wrote: >>> On 13.09.2014 06:57, poma wrote: >>>> >>>> Actually I have nothing to show cause logs are all OK. >>>> Haha, it seems to me that the bugs become intelligent. >>>>

This information will be mirrored on the Xen 4.4 Roadmap wiki page: http://wiki.xen.org/wiki/Xen_Roadmap/4.4 Our timeline had us start the code freeze last Friday. However, we have not released an RC0 because we have been waiting for PVH dom0 support. Adding bug fixes during RCs makes sense, but RC0 should contain all of the functionality we expect to be in the final release. PVH dom0 support

On 20.10.2014 21:30, poma wrote: > On 20.10.2014 08:13, poma wrote: >> >> 02:00.0 VGA compatible controller: >> NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) >> Chipset: G98 (NV98) >> Family : NV50 >> >> The same for all four kernel: >> - 3.18.0-0.rc0.git8.1.fc22.x86_64 >> - 3.18.0-0.rc0.git9.1.fc22.x86_64 >> -

On 13.09.2014 07:02, poma wrote: > On 13.09.2014 06:57, poma wrote: >> >> Actually I have nothing to show cause logs are all OK. >> Haha, it seems to me that the bugs become intelligent. >> >> 3.15.10-201.fc20.x86_64 >> 3.16.2-200.fc20.x86_64 >> 3.17.0-0.rc4.git3.2.fc22.1.x86_64 >> nouveau [ DRM] suspending display... >> nouveau [

On 13.09.2014 23:45, Roy Spliet wrote: > Dear Poma, > > Don't get anyone wrong, your input is greatly valued. The reason why > "we" (nouveau developers) generally ask for a git bisection is because > we don't know or track specific distributions. Although your search has > narrowed the problem down (thanks for that!), we don't know how big the >

Hi Konrad, I just tried linux-3.4-rc0 (linus his tree, last commit f52b69f86e27903d6896ed5fa7cd280fec8de532) with 3 additional branches from your tree pulled on top of that: branch stable/for-ingo-3.4.v2 (required for dom0 to boot) branch stable/for-jens-3.4 branch stable/for-jens-3.4-bugfixes Hypervisor is xen-4.1.3-rc1-pre linux 3.3 vanilla works fine Booting dom0 goes fine, but

Running virt-builder in a guest Fedora-20 guest hypervisor w/ Rawhide Kernel, throws the below: $ virt-builder fedora-20 --format qcow2 --size 20G virt-builder: symbol lookup error: /lib64/libgnutls.so.28: undefined symbol: nettle_secp_256r1 Version on L1 (guest hypervisor) -------------------------------- $ uname -r; rpm -q libvirt-daemon-kvm qemu-system-x86 \ libguestfs gnutls

Can someone else from the Solaris realm that uses our package system verify that this should be done? It looks right, but I want another opinion before commiting. - Ben > On Wed, 27 Feb 2002, Antonio Navarro wrote: > >> Hi Ben, >> >> I have made some modifications to the buildpkg.sh script that is >> distributed with openssh. >> >> I am sending it to

Hi Konrad, I just tried to boot a 3.8.0-rc0 kernel (last commit: 7313264b899bbf3988841296265a6e0e8a7b6521) as dom0 on my machine with current xen-unstable. The boot stalls: [ 0.000000] ACPI: PM-Timer IO Port: 0x808 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01]

Hi, please consider this stripped down example: new Ajax.Request(''foo.php'', { onSuccess: function(t, json) { alert(json.myParam); } }); According to http://www.sergiopereira.com/articles/prototype.js.html, the second param is supposed to be the evaluated json object IF the X-JSON header is send in the response. I send the header in my script. However, the json var

Hi, I''m in the process of moving my blog over from lighttpd -> apache 2.2 + mongrel. Everything works fine as long as I don''t reboot :) On reboot apache comes up but mongrel_cluster doesn''t start up the pooches... I have added the mongrel_cluster call to my startup scripts like so: www:/etc/init.d# update-rc.d mongrel_cluster defaults Adding system startup for