www.archive-org-2014.com » ORG » Q » QEMU

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".

    Archived pages: 1382 . Archive date: 2014-06.

  • Title: QEMU
    Descriptive info: .. Log in.. QEMU.. Page.. Discussion.. View source.. History.. Search.. About.. Home.. Get.. Download.. Contribute.. Start Here.. Report a Bug.. Report a security issue.. Submit a Patch.. Mailing Lists.. Testing QEMU.. Virtualize.. KVM.. Learn.. Documentation.. Links.. License.. Toolbox.. What links here.. Related changes.. Special pages.. Main Page.. From QEMU.. QEMU is a generic and open source machine emulator and virtualizer.. When used as a machine emulator, QEMU can run OSes and programs made for one machine (e.. g.. an ARM board) on a different machine (e.. your own PC).. By using dynamic translation, it achieves very good performance.. When used as a virtualizer, QEMU achieves near native performances by executing the guest code directly on the host CPU.. QEMU supports virtualization when executing under the Xen hypervisor or using the KVM kernel module in Linux.. When using KVM, QEMU can virtualize x86, server and embedded PowerPC, and S390 guests.. Creating Accounts.. To help control spam, we have disabled account  ...   See the.. page for more information.. April 14th, 2014.. 0-rc3 is out.. April 8th, 2014.. 0-rc2 is out.. April 4th, 2014.. 0-rc1 is out.. March 25th, 2014.. QEMU version 1.. 7.. 1 is out.. March 13th, 2014.. 0-rc0 is out.. December 16th, 2013.. 6.. 2 is out.. November 28th, 2013.. November 21th, 2013.. October 9th, 2013.. August 27th, 2013.. 5.. 3 is out.. August 15th, 2013.. August 12th, 2013.. August 7th, 2013.. August 1st, 2013.. July 25th, 2013.. June 26th, 2013.. May 24th, 2013.. 4.. May 20th, 2013.. May 17th, 2013.. May 15th, 2013.. May 8th, 2013.. Apr 15th, 2013.. Feb 15th, 2013.. Feb 14th, 2013.. Feb 6th, 2013.. Jan 28th, 2013.. 3.. Dec 11th, 2012.. 2.. Dec 3rd, 2012.. Nov 26th, 2012.. Nov 20th, 2012.. Nov 19th, 2012.. Sep 5th, 2012.. Retrieved from ".. http://wiki.. qemu.. org/Main_Page.. ".. Content is available under.. GNU Free Documentation License 1.. QEMU is a trademark of Fabrice Bellard.. Hosting generously provided by.. OSUOSL..

    Original link path: /Main_Page
    Open archive

  • Title: Log in / create account - QEMU
    Descriptive info: Log in / create account - QEMU.. Special page.. Log in / create account.. You must have cookies enabled to log in to QEMU.. Username:.. Password:.. Remember my login on this computer.. org/Special:UserLogin..

    Original link path: /index.php?title=Special:UserLogin&returnto=Main_Page
    Open archive

  • Title: Talk:Main Page - QEMU
    Descriptive info: Talk:Main Page - QEMU.. Talk:Main Page.. I think it would be really neat to have a nice screenshot of QEMU running different types of interesting VMs on the main page.. We have to make sure we use guests that have reasonable screenshot licenses (iow, no Windows).. If anyone wants to upload ones, we could even rotate through a set of  ...   a good advertising to write "Hosted by QEMU/KVM" (or so) on the home page.. http //qemu-buch.. de.. 06:43, 5 February 2010 (UTC).. Why Qemu Accelerator modulo is now obsolete ?.. Will the 0.. 12 version support Qemu accelerator ?.. Those are appropriate questions for the mailing list or IRC.. Not the wiki talk page.. 14:58, 21 June 2010 (UTC).. org/Talk:Main_Page..

    Original link path: /Talk:Main_Page
    Open archive

  • Title: View source - QEMU
    Descriptive info: View source - QEMU.. for.. You do not have permission to edit this page, for the following reasons:.. The action you have requested is limited to users in the group:.. Users.. This page has been locked to prevent editing.. You can view and copy the source of this page:.. {{DISPLAYTITLE:About}} QEMU is a generic and open source machine emulator and virtualizer.. == Creating Accounts == To help control spam, we have disabled account creation on this wiki.. If you need assistance, please ask on [[MailingLists|qemu-devel]].. == News == '''April 17th, 2014''' *QEMU version 2.. See the [[Download|Download]] page for more information.. '''April 14th, 2014''' *QEMU version 2.. '''April 8th, 2014''' *QEMU version 2.. '''April 4th, 2014''' *QEMU version 2.. '''March 25th, 2014''' *QEMU version 1.. '''March  ...   *QEMU version 1.. '''August 7th, 2013''' *QEMU version 1.. '''August 1st, 2013''' *QEMU version 1.. '''July 25th, 2013''' *QEMU version 1.. '''June 26th, 2013''' *QEMU version 1.. '''May 24th, 2013''' *QEMU version 1.. '''May 20th, 2013''' *QEMU version 1.. '''May 17th, 2013''' *QEMU version 1.. '''May 15th, 2013''' *QEMU version 1.. '''May 8th, 2013''' *QEMU version 1.. '''Apr 15th, 2013''' *QEMU version 1.. '''Feb 15th, 2013''' *QEMU version 1.. '''Feb 14th, 2013''' *QEMU version 1.. '''Feb 6th, 2013''' *QEMU version 1.. '''Jan 28th, 2013''' *QEMU version 1.. '''Dec 11th, 2012''' *QEMU version 1.. '''Dec 3rd, 2012''' *QEMU version 1.. '''Nov 26th, 2012''' *QEMU version 1.. '''Nov 20th, 2012''' *QEMU version 1.. '''Nov 19th, 2012''' *QEMU version 1.. '''Sep 5th, 2012''' *QEMU version 1.. [[OlderNews|.. ]].. Return to..

    Original link path: /index.php?title=Main_Page&action=edit
    Open archive

  • Title: Revision history of "Main Page" - QEMU
    Descriptive info: Revision history of Main Page - QEMU.. RSS.. Atom.. Revision history of Main Page.. View logs for this page.. Browse history.. From year (and earlier):.. From month (and earlier):.. all.. January.. February.. March.. April.. May.. June.. July.. August.. September.. October.. November.. December.. (Latest |.. Earliest.. ) View (newer 50) (.. older 50.. ) (.. 20.. |.. 50.. 100.. 250.. 500.. ).. Diff selection: mark the radio boxes of the revisions to compare and hit enter or the button at the bottom.. Legend:.. (cur).. = difference with current revision,.. (prev).. = difference with preceding revision,.. m.. = minor edit.. (cur) (.. prev.. ).. 14:58, 17 April 2014.. Mdroth.. (.. Talk.. contribs.. (4,673 bytes).. →.. News.. cur.. 04:16, 15 April 2014.. (4,563 bytes).. 21:03, 8 April 2014.. (4,449 bytes).. 15:36, 4 April 2014.. (4,336 bytes).. 14:10, 25 March 2014.. (4,223 bytes).. 03:18, 14 March 2014.. (4,112 bytes).. 16:19, 16 December 2013.. (3,999 bytes).. 17:53, 26 November 2013.. (3,890 bytes).. 18:40, 21 November 2013.. (3,773 bytes).. 19:30, 9 October 2013.. (3,656 bytes).. 15:14, 27 August  ...   2013.. (2,434 bytes).. 22:28, 8 May 2013.. (2,322 bytes).. 20:36, 15 April 2013.. (2,211 bytes).. 23:15, 15 February 2013.. (2,103 bytes).. 20:56, 14 February 2013.. (1,995 bytes).. 01:38, 7 February 2013.. (1,883 bytes).. 21:12, 28 January 2013.. (1,771 bytes).. 22:38, 11 December 2012.. (1,664 bytes).. 20:11, 3 December 2012.. (1,556 bytes).. 20:10, 3 December 2012.. (4,475 bytes).. 00:27, 27 November 2012.. (4,368 bytes).. 01:16, 20 November 2012.. (4,256 bytes).. 23:07, 19 November 2012.. (4,148 bytes).. 16:03, 5 September 2012.. (4,036 bytes).. (4,047 bytes).. 12:51, 4 September 2012.. (3,929 bytes).. 19:08, 30 August 2012.. (3,818 bytes).. 15:54, 23 August 2012.. (3,706 bytes).. 21:22, 16 August 2012.. (3,594 bytes).. 18:36, 17 July 2012.. (3,482 bytes).. 20:35, 12 July 2012.. (3,288 bytes).. 09:15, 5 June 2012.. (3,180 bytes).. 09:09, 2 June 2012.. (2,956 bytes).. 03:18, 31 May 2012.. (2,851 bytes).. 14:23, 22 May 2012.. (2,743 bytes).. 16:00, 15 May 2012.. (2,635 bytes).. 12:48, 10 May 2012.. (2,527 bytes).. 06:51, 26 March 2012.. Mjt.. (2,419 bytes).. Creating Accounts.. 21:01, 17 February 2012.. (2,420 bytes).. (2,418 bytes)..

    Original link path: /index.php?title=Main_Page&action=history
    Open archive

  • Title: Download - QEMU
    Descriptive info: Download - QEMU.. Releases.. File.. Comment.. qemu-2.. tar.. bz2.. signature.. Source code (.. ChangeLog.. qemu-1.. 1.. Latest Source Code.. QEMU is developed using.. git.. The main tree is located at.. http://git.. org/qemu.. git.. The latest development happens on the master branch.. The stable tree is located in a.. stable-0.. XX' branch where '0.. XX' is the minor release version.. To download the latest development tree, use the following command:.. git clone git://git.. qemu-project.. git.. and also see instructions on that page for other ways to access the source.. org/Download..

    Original link path: /Download
    Open archive

  • Title: Contribute/StartHere - QEMU
    Descriptive info: Contribute/StartHere - QEMU.. Contribute/StartHere.. Contents.. 1.. Project Infrastructure.. 2.. Key Information.. 3.. Students.. 4.. Planning.. 5.. Features.. Work in progress.. Downstream.. 6.. GIT repo.. 7.. Developers and Maintainers.. Project Infrastructure.. Source repository:.. Mainline qemu.. and.. developer repositories.. Mailing list:.. mailing list.. IRC: #qemu on.. irc.. oftc.. net.. Bug tracker:.. launchpad.. Continuous integration:.. buildbot.. Wiki:.. this website.. Phone call: Scheduled for Tuesdays on as-needed basis for agenda topics raised on mailing list.. Contact.. Juan Quintela.. for dial-in details.. To find the time in your location, use:.. date -d 'TZ="America/New_York" Tuesday 10:00 am'.. Key Information.. Getting started for developers.. How to submit a patch.. How to submit a trivial patch.. How to report a bug.. Students.. QEMU participated in Google's Summer of Code 2011 program.. Some reports on the processed topics (partially or fully) from 2010 can be found here:.. QMP.. - about syncing QEMU monitor and QEMU Machine Protocol (QMP) features.. VNC.. - about improvements in speed and features of QEMU supported VNC protocols.. For more information on GSoC-2011 and especially lots more of probably still open topics for improvement please see.. this  ...   Interpreter.. Tracing.. Tracing/Roadmap.. Tracing/UseCases.. Usability.. VirtioBlkBoot.. VirtioIoeventfd.. Work in progress.. 40p.. BeBox.. CPUHotplug.. GtkDisplayState.. PReP cleanup.. RL78.. Tegra2.. RDMA Live Migration.. Micro Checkpointing.. Downstream.. 6502 (on.. GitHub.. AT91SAM9263 (on.. Github.. Beagleboard (at Linaro).. Blackfin.. Goldfish (at Android).. HPPA.. Meta (on.. Taskit Portux920T (on.. Z80.. GIT repo.. org GIT repo.. repo.. or.. cz.. Anthony Liguori's QEMU tree.. Anthony Liguori's QEMU queue.. Qemu patches by Michael S.. Tsirkin.. Warning: constantly rebased.. pci subsystem.. kwolf Random patches.. block device.. Developers and Maintainers.. Alexander Graf.. (maintainer for PPC, S390).. Anthony Liguori.. (committer, maintainer).. Bill Traynor.. Blueswirl.. (committer, maintainer for SPARC, bsd-user).. Edgar E.. Iglesias.. (committer, maintainer for CRIS, Microblaze).. Gerd Hoffmann.. (maintainer for audio, SPICE, USB).. Joro.. Luiz Capitulino.. (maintainer for QMP/QAPI).. Màrius Montón.. Michael Tsirkin.. (maintainer for PCI, vhost).. Miguel Di Ciurcio Filho.. Natalia Portillo.. Paolo Bonzini.. (maintainer for NBD, SCSI).. Paul Brook.. (committer, maintainer for ARM, m68k).. Stefan Weil.. (maintainer for.. TCI.. ,.. w32, w64.. Stefan Hajnoczi.. (maintainer for tracing).. Zhi Yong Wu.. Block I/O throttling.. virtio-scsi tcm_vhost.. See file.. MAINTAINERS.. in the QEMU source distribution for the latest list of QEMU maintainers.. org/Contribute/StartHere..

    Original link path: /Contribute/StartHere
    Open archive

  • Title: Contribute/ReportABug - QEMU
    Descriptive info: Contribute/ReportABug - QEMU.. Contribute/ReportABug.. Bugs can be filed at our.. bug tracker.. When submitting a bug report, please try to do the following:.. Make sure you're reporting the bug against the.. latest release.. If possible, please try to reproduce with the latest development tree too.. Include the full command  ...   directly with a QEMU command-line.. Avoid frontends and management stacks, this shows that the bug is in QEMU itself and not in a frontend.. Include as information about the guest (operating system, version, 32/64-bit).. Do not contribute patches on the bug tracker,.. send patches to the mailing list.. org/Contribute/ReportABug..

    Original link path: /Contribute/ReportABug
    Open archive

  • Title: SecurityProcess - QEMU
    Descriptive info: SecurityProcess - QEMU.. SecurityProcess.. QEMU takes security very seriously, and we aim to take immediate action to address serious security-related problems that involve our product.. Please report any suspected security vulnerability in QEMU to the following addresses.. You can use GPG keys for respective receipients to communicate with us securely.. If you do, please upload your GPG public key or supply it to us in some other way, so that we can communicate to you in a secure way, too! Please include the tag [QEMU-SECURITY] on the subject line to help us identify your message as security-related.. QEMU Security Contact List: please copy everyone on this list.. Contact Person(s).. Contact Address.. Company.. GPG key.. GPG key fingerprint.. aliguori@amazon.. com.. Amazon.. com Inc.. [.. ].. Fingerprint=EF0F 60F4 390F A270 BC30 4A93 1AAD C710 5682 E5FF.. Michael S.. Tsirkin.. mst@redhat.. Red Hat Inc.. Fingerprint=0270 606B 6F3C DF3D 0B17 0970 C350 3912 AFBE 8E67.. Security Response Team.. secalert@redhat.. GPG key.. How to Contact Us Securely.. How we respond.. Publication embargo.. CVE allocation.. When to Contact the QEMU Security Contact List.. When not to Contact the QEMU Security Contact List.. What to Send to the QEMU Security Contact List.. How to Contact Us Securely.. We use a GNU Privacy Guard (GnuPG or GPG) keys to secure communications.. Mail sent to members of the list can be encrypted with public keys of all  ...   progress.. We might take one or more of the following steps:.. Publication embargo.. As a security issue reported, that is not already publically disclosed elsewhere, has an embargo date assigned and communicated to reporter.. Embargo periods will be negotiated by mutual agreement between members of the security team and other relevant parties to the problem.. Members of the security contact list agree not to publically disclose any details of the security issue until the embargo date expires.. CVE allocation.. An security issue is assigned with a CVE number.. The CVE numbers will usually be allocated by one of the vendor security engineers on the security contact list.. When to Contact the QEMU Security Contact List.. You should contact the Security Contact List if:.. You think there may be a security vulnerability in QEMU.. You are unsure about how a known vulnerability affects QEMU.. You can contact us in English.. We are unable to respond in other languages.. When.. not.. to Contact the QEMU Security Contact List.. You need assistance in a language other than English.. You require technical assistance (for example, "how do I configure QEMU?").. You need help upgrading QEMU due to security alerts.. Your issue is not security related.. What to Send to the QEMU Security Contact List.. Please provide as much information about your system and the issue as possible when contacting the list.. org/SecurityProcess..

    Original link path: /SecurityProcess
    Open archive

  • Title: Contribute/SubmitAPatch - QEMU
    Descriptive info: Contribute/SubmitAPatch - QEMU.. Contribute/SubmitAPatch.. QEMU welcomes contributions of code (either fixing bugs or adding new functionality).. However, we get a lot of patches, and so we have some guidelines about submitting patches.. If you follow these, you'll help make our task of code review easier and your patch is likely to be committed faster.. All contributions to QEMU must be.. sent as patches.. to the qemu-devel.. Patch contributions should not be posted on the bug tracker, posted on forums, or externally hosted and linked to.. You do not have to subscribe to post (list policy is to reply-to-all to preserve CCs and keep non-subscribers in the loop on the threads they start), although you may find it easier as a subscriber to pick up good ideas from other posts.. If you do subscribe, be prepared for a high volume of email, often over one thousand messages in a week.. The list is moderated; first-time posts from an email address (whether or not you subscribed) may be subject to some delay while waiting for a moderator to whitelist your address.. Send patches to the mailing list and.. CC the relevant maintainer.. -- look in the MAINTAINERS file to find out who that is.. Also try using scripts/getmaintainer.. pl from the repository for learning the most common committers for the files you touched.. Send patches inline.. so they are easy to reply to with review comments.. Do not put patches in attachments.. Use the right patch format.. git format-patch.. will produce patch emails in the right format (check the documentation to find out how to drive it).. You can then edit the cover letter before using.. git send-email.. to mail the files to the mailing list.. (We recommend.. because mail clients often mangle patches by wrapping long lines or messing up whitespace.. Some distributions do not include send-email in a default install of git; you may need to download additional packages, such as 'git-email' on Fedora-based systems.. ) Patch series need a cover letter, with shallow threading (all patches in the series are in-reply-to the cover letter, but not to each other); single unrelated patches do not need a cover letter.. A one-time setup of.. git config diff.. renames true.. is encouraged for anyone sending file rename patches, as it gives a more compact representation that focuses only on the differences across the file rename, instead of showing the entire old file as a deletion and the new file as an insertion.. Patches are easier to find if they start a new top-level thread, rather than being buried in-reply-to another existing thread.. Patch emails must include a Signed-off-by: line.. For more information see.. SubmittingPatches 1.. 12.. This is vital or we will not be able to apply your patch! Please use your real name to sign a patch (not an alias name).. Make the cover letter meaningful.. When reviewers don't know your goal at the start of their review, they may object to early changes that don't make sense until the end of the series, because they do not have enough context yet at that point of their review.. A series where the goal is unclear also risks a higher number of review-fix cycles because the reviewers haven't bought into the idea yet.. It is in everyone's interest to explain the goal in the cover letter.. Then the patches get reviewed more smoothly and merged faster.. Make sure your cover letter includes a diffstat of changes made over the entire series, as it is easier for a potential reviewer to check your cover letter than it is to check every letter in the series when determining if the series touches files they are interested in.. Follow the coding style.. and run.. scripts/checkpatch.. pl patchfile.. before submitting.. (Be aware that checkpatch.. pl is not infallible, though, especially where C preprocessor macros are involved; use some common sense too.. ) See also:.. QEMU Coding Style.. QEMU Coding Guidelines.. Correct English.. is appreciated.. If you are not sure,.. codespell.. or other programs help finding the most common spelling mistakes in code and documentation.. Patches should be against current git master.. There's no point submitting a patch which is based on a released version of QEMU because development will have moved on from then and it probably won't even apply to master.. We only apply selected bugfixes to release branches and then only as backports once the code has gone into master.. Split up longer patches.. into a patch series of logical code changes.. Each change should compile and execute successfully.. For instance, don't add a file to the makefile  ...   it a followup to version 1.. (This helps automatic patch email handling tools distinguish between v1 and v2 emails.. ).. When resending patches add a v2/v3 suffix.. (eg [PATCH v2]).. This means people can easily identify whether they're looking at the most recent version.. (The first version of a patch need not say "v1", just [PATCH] is sufficient.. ) For patch series, the version applies to the whole series -- even if you only change one patch, you resend the entire series and mark it as "v2".. Don't try to track versions of different patches in the series separately.. both understand the.. --subject-prefix=.. option to make this easier.. Send each new revision as a new top-level thread, rather than burying it in-reply-to an earlier revision, as many reviewers are not looking inside deep threads for new patches.. For later versions of patches.. include a summary of changes from previous versions, but not in the commit message itself.. In an email formatted as a git patch, the commit message is the part above the "---" line, and this will go into the git changelog when the patch is committed.. This part should be a self-contained description of what this version of the patch does, written to make sense to anybody who comes back to look at this commit in git in six months' time.. The part below the "---" line and above the patch proper (git format-patch puts the diffstat here) is a good place to put remarks for people reading the patch email, and this is where the "changes since previous version" summary belongs.. Proper use of Reviewed-by: tags can aid review.. When reviewing a large series, a reviewer can reply to some of the patches with a Reviewed-by tag, stating that they are happy with that patch in isolation (sometimes conditional on minor cleanup, like fixing whitespace, that doesn't affect code content).. You should then update those commit messages by hand to include the Reviewed-by tag, so that in the next revision, reviewers can spot which patches were already clean from the previous round.. Conversely, if you significantly modify a patch that was previously reviewed, remove the reviewed-by tag out of the commit message, as well as listing the changes from the previous version, to make it easier to focus a reviewer's attention to your changes.. If your patch seems to have been ignored.. you should "ping" it after a week or two, by sending an email as a reply-to-all to the patch mail, including the word "ping" and ideally also a link to the page for the patch on.. patchwork.. or GMANE.. It's worth double-checking for reasons why your patch might have been ignored (forgot to CC the maintainer? annoyed people by failing to respond to review comments on an earlier version?), but often for less-maintained areas of QEMU patches do just slip through the cracks.. If your ping is also ignored, ping again after another week or so.. As the submitter, you are the person with the most motivation to get your patch applied, so you have to be persistent.. Is my patch in?.. Once your patch has had enough review on list, the maintainer for that area of code will send notification to the list that they are including your patch in a particular staging branch.. Periodically, the maintainer then sends a.. pull request.. for aggregating topic branches into mainline qemu.. Generally, you do not need to send a pull request unless you have contributed enough patches to become a maintainer over a particular section of code.. Maintainers may further modify your commit, by resolving simple merge conflicts or fixing minor typos pointed out during review, but will always add a Signed-off-by line in addition to yours, indicating that it went through their tree.. Occasionally, the maintainer's pull request may hit more difficult merge conflicts, where you may be requested to help rebase and resolve the problems.. It may take a couple of weeks between when your patch first had a positive review to when it finally lands in qemu.. git; release cycle freezes may extend that time even longer.. Return the favor.. Peer review only works if everyone chips in a bit of review time.. If everyone submitted more patches than they reviewed, we would have a patch backlog.. A good goal is to try to review at least as many patches from others as what you submit.. Don't worry if you don't know the code base as well as a maintainer; it's perfectly fine to admit when your review is weak because you are unfamiliar with the code.. org/Contribute/SubmitAPatch..

    Original link path: /Contribute/SubmitAPatch
    Open archive

  • Title: MailingLists - QEMU
    Descriptive info: MailingLists - QEMU.. MailingLists.. QEMU developers mailing list.. QEMU stable mailing list.. QEMU trivial patch mailing list.. QEMU users mailing list.. QEMU PowerPC mailing list.. See also.. →.. External Documentation.. org/MailingLists..

    Original link path: /MailingLists
    Open archive

  • Archived pages: 1382