From: Koen de Jonge <koen-OoqVcbiag8BWk0Htik3J/w@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Guest Support Status wiki page
Date: Fri, 17 Aug 2007 23:12:56 +0200 [thread overview]
Message-ID: <46C60F58.9010407@procolix.com> (raw)
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.
The top line of the table states:
Guest: Debian Etch
Guest bitness: 32/64
Host version: kvm-29
Host cpu: Intel
Host bitness: 64
Status: Works
Comments:
Now I have just verified that there is a way to get kvm-35 running on a
Debian Etch amd64 (quite easily I must say).
And I have also verified that Debian Etch i386 as a Guest runs perfectly
on that host (installing with debian-40r0-i386-netinst.iso).
Should I now add a line to that table that states:
Guest: Debian Etch
Guest bitness: 32
Host version: kvm-35
Host cpu: AMD
Host bitness: 64
Status: Works
Should I leave the lines that are allready there about the same Guest
untouched?
Should I test the same OS again when kvm-36 is released?
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/
next reply other threads:[~2007-08-17 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 21:12 Koen de Jonge [this message]
[not found] ` <46C60F58.9010407-OoqVcbiag8BWk0Htik3J/w@public.gmane.org>
2007-08-18 9:07 ` Guest Support Status wiki page Amit Shah
[not found] ` <200708181437.05539.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-18 9:47 ` Koen de Jonge
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=46C60F58.9010407@procolix.com \
--to=koen-ooqvcbiag8bwk0htik3j/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