public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Koen de Jonge <koen-OoqVcbiag8BWk0Htik3J/w@public.gmane.org>
To: Amit Shah <amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Guest Support Status wiki page
Date: Sat, 18 Aug 2007 11:47:39 +0200	[thread overview]
Message-ID: <46C6C03B.8090600@procolix.com> (raw)
In-Reply-To: <200708181437.05539.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

Amit Shah wrote:
> On Saturday 18 August 2007 02:42:56 Koen de Jonge wrote:
>   
>> Hi all,
>>
>> here is a list of Supported Guests:
>> http://kvm.qumranet.com/kvmwiki/Guest_Support_Status
>>
>> The tables are a bit unclear to me, I will explain using the 'Debian
>> Etch' example.
>>     
>
> There's no guideline on what the table should look like. It should just be 
> easy for new and returning users to find the information they're looking for, 
> easily at one place. If you think there's a better way in which the table can 
> be laid out, a trial version can be placed on a temporary wiki page for 
> others to comment.
>   
OK, that is a clear answer. I will create a temporary page then. I think 
we (I would, but only for the free ones out there) test a few of the 
most frequently used OSes after each release.


>> Should I leave the lines that are allready there about the same Guest
>> untouched?
>>     
>
> If you have also tried a 64-bit guest, you can just update the Host Version 
> field. Otherwise, a new line would be ok.
>   
Hmm ok. I will test a 64-bit guest in a few hours then, so I can update 
that line.

>> Should I test the same OS again when kvm-36 is released?
>>     
>
> If you regularly use kvm, it will definitely be beneficial to add the most 
> recent information to the wiki as well. But simply putting a '+' after the 
> release should do; like 'Host version: kvm-35+'. That avoids us mentioning 
> all the releases. When things break, they can be marked as such.
>   
I'm planning to use it each day every day, so that is ok.

Can I add this Q and A to the FAQ page below 'General info - What kernel 
version does it work with? (http://kvm.qumranet.com/kvmwiki/FAQ):

Q: What version of KVM should I use?
A: With all the rapid development these days you should always use the 
latest version of KVM, with any kernel.

Greetz,
Koen

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

  parent reply	other threads:[~2007-08-18  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17 21:12 Guest Support Status wiki page Koen de Jonge
     [not found] ` <46C60F58.9010407-OoqVcbiag8BWk0Htik3J/w@public.gmane.org>
2007-08-18  9:07   ` Amit Shah
     [not found]     ` <200708181437.05539.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-18  9:47       ` Koen de Jonge [this message]
2007-08-19  8:42       ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46C6C03B.8090600@procolix.com \
    --to=koen-ooqvcbiag8bwk0htik3j/w@public.gmane.org \
    --cc=amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox