MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "SPICE",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "1443": {
                "pageid": 1443,
                "ns": 0,
                "title": "RunningKVM",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "== Prerequisites ==\n\nYou will need (see download section):\n\n* qemu-kvm-''release''.tar.gz\n* kvm-kmod-''release''.tar.bz2 (if you want/need to compile kernel modules yourself)\n* A VT capable Intel processor, or an SVM capable AMD processor\n* qemu prerequisites:\n** `zlib` libraries and headers\n** `SDL` libraries and headers\n** `alsa` libraries and headers (optional alsa support: disabled by default but can be enabled with --enable-alsa)\n** `gnutls` libraries and headers (optional VNC TLS support: enabled by default but can be disabled with --disable-vnc-tls)\n** kernel headers (on Fedora, the kernel-devel package)\n\nOn a debian etch system you can install the prerequisites with:\n  apt-get install gcc libsdl1.2-dev zlib1g-dev libasound2-dev linux-kernel-headers pkg-config libgnutls-dev libpci-dev\n\n'''Note:''' When building from git, you also need gawk.\n\nPlease report problems (and successes) to the [[Lists,_IRC| mailing list]].\n\n== Unpacking and configuring kvm components ==\n\nYou may wish to take a look at the [\"Kernel-optimizations\"] page.\nThere exists a [attachment:kvm-26-alt-grab.diff.gz patch] which will change the SDL keygrab combination from ctrl-alt to ctrl-alt-shift.  It was written primarily to deal with the heavy use of ctrl-alt-delete in NT-based VMs.\n\nIf you are using a recent kernel (2.6.25+) with kvm modules included, boot into it, and:\n\n tar xzf qemu-kvm-release.tar.gz\n cd qemu-kvm-release\n ./configure --prefix=/usr/local/kvm\n make\n sudo make install\n sudo /sbin/modprobe kvm-intel\n # or: sudo /sbin/modprobe kvm-amd\n\nIf you're using an older kernel, or a kernel from your distribution without the kvm modules, you'll have to compile the modules yourself:\n\n tar xjf kvm-kmod-release.tar.bz2\n cd kvm-kmod-release \n ./configure\n make \n sudo make install \n sudo /sbin/modprobe kvm-intel \n # or: sudo /sbin/modprobe kvm-amd\n\n'''Note:''' if sound doesn't play in the guest vm you can add --audio-drv-list=\"alsa oss\" to ./configure as explained in http://www.linux-kvm.com/content/sound-problem-solved\n\n== Creating a disk image for the guest ==\n /usr/local/kvm/bin/qemu-img create -f qcow2 vdisk.img 10G \n\n\n== Installing a guest operating system ==\n\n sudo /usr/local/kvm/bin/qemu-system-x86_64 -hda vdisk.img -cdrom /path/to/boot-media.iso \\ \n    -boot d  -m 384\n\n(kvm doesn't make a distinction between i386 and x86_64 so even in i386 you should use `qemu-system-x86_64`)[[BR]]  \n\nIf you have less than 1GB of memory don't use the -m 384 flag (which allocates 384 MB of RAM for the guest). For computers with 512MB of RAM it's safe to use -m 192, or even -m 128 (the default)\n\n== Running the newly-installed guest ==\n sudo /usr/local/kvm/bin/qemu-system-x86_64 vdisk.img -m 384\n\nor a slightly more complicated example, where it is assumed that bridged networking is available on tap0; see [\"Kernel-optimizations\"] for some setup hints:\n\n /usr/local/kvm/bin/qemu-system-x86_64 -hda xp-curr.img -m 512 -soundhw es1370 -no-acpi -snapshot -localtime -boot c -usb -usbdevice tablet -net nic,vlan=0,macaddr=00:00:10:52:37:48 -net tap,vlan=0,ifname=tap0,script=no\n\n(kvm doesn't make a distinction between i386 and x86_64 so even in i386 you should use `qemu-system-x86_64`)\n\nIf you're on Debian Etch, substitute `kvm` for `qemu-system-x86_64` (thanks to fromport, soren and mael_). See also the entries under the label \"Ubuntu\" on the [[HOWTO]] page.\nqemu-system-x86_64`\n\nIf you're on Fedora/RHEL/CentOS (and installed a kvm package and not built kvm yourself from source) then substitute '''qemu-kvm''' for '''qemu-system-x86_64'''"
                    }
                ]
            },
            "1452": {
                "pageid": 1452,
                "ns": 0,
                "title": "Running libvirt with KVM",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "When I build from source KVM and Libvirt (Ubuntu 8.10 desktop), I found that Libvirtd could not connect to\n\n virsh -c qemu:///system\ncomplaining that it couldnt connect to the hypervisor. I found that the qemu driver in virsh was hard coded to look in the following places for the qemu executable:\n\n\n if ((virFileExists(\"/usr/bin/qemu\")) ||\n        (virFileExists(\"/usr/bin/qemu-kvm\")) ||\n        (virFileExists(\"/usr/bin/kvm\")) ||\n        (virFileExists(\"/usr/bin/xenner\")))\n        return 1;\n\n\nThe solution was to symlink\n\n /usr/bin/kvm -> /usr/local/bin/qemu-system-x86_64\n\n\nThen the libvirtd qemu driver found, and it all worked great"
                    }
                ]
            }
        }
    }
}