This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] para- and full-virtualization on same system?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] para- and full-virtualization on same system?
From: Kent Watsen <kent@xxxxxxxxxx>
Date: Sun, 19 Mar 2006 07:48:27 -0800
Delivery-date: Sun, 19 Mar 2006 15:49:59 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <441C7D92.8070201@xxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <441C7D92.8070201@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5 (Macintosh/20051201)

Based on a few of the follow-ups, I wanted to add some detail:
  • all the machines could be headless (only command-line access is needed)
  • we may need real machines for Windows and MacOS if their displays can't be turned off
  • the software we are developing exposes a SOAP-based interface that is tested via scripts
  • each built/test-machine builds and tests the code many times a day (we are doing continuous builds)
  • in addition to the servers, developers have desktops machines (that are samba/nfs mounted) for their graphical needs
  • developers will SSH into to a build/test machine if their component is failing on that OS

Kent Watsen wrote:

Can I consolidate all my servers to one machine - here are my current machines:
  1. OpenBSD (used for external services: dns, http, smtp)
  2. OpenBSD (used for internal services: dns, http, smtp, imap, ldap, smb, nfs, svn, bugzilla)
  3. OpenSBD (used for upgrading either of the above servers without any downtime)
  4. OpenBSD (used as a build/test machine)
  5. FreeBSD (used as a build/test machine)
  6. NetBSD (used as a build/test machine)
  7. RedHat (used as a build/test machine)
  8. CentOS (used as a build/test machine)
  9. SuSE (used as a build/test machine)
  10. Solaris (used as a build/test machine)
  11. Windows (used as a build/test machine)
  12. MacOS X (used as a build/test machine)
  • The OpenBSD-based servers are RAID-ed
  • There are actually more machines as I run multiple releases of each build/test OS...

If it can't be done on one machine, than would either of these 2-machine solutions work:
  1. Partition machines by server vs. build/test
    • one machine has:  1-3 (all para-virtualized)
    • other machine has:  4-12 (5/9 para-virtualized)
  2. Partition machines by para- vs. full-virtualization
    • one machine has: 1-4 and 10-12 (all full-virtualized) [would GSX be better?]
    • other machine has: 5-9 (all para-virtualized)

What would you do?


_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users

Xen-users mailing list