Xen - Recent changes [en]

User:Skinney629

2012-05-15T20:50:40Z

New user account

New page

User:OrleneCourtemanche

2012-05-15T16:53:09Z

deleted "[[User:OrleneCourtemanche]]" content was: "Orlene Courtemanche is an online marketing specialist currently working for a business consulting firm that specializes in information techn…" (and the only contributor was "OrleneCourtemanche")

New page

User:OrleneCourtemanche

2012-05-15T16:52:33Z

blocked [[OrleneCourtemanche (Talk | contribs)]] with an expiry time of infinite (account creation disabled) Spamming links to external sites

New page

Secondary GPU Passthrough

2012-05-15T10:53:56Z

← Older revision		Revision as of 10:53, 15 May 2012
Line 178:		Line 178:

	; 5. Notes/Hints on Installation:		; 5. Notes/Hints on Installation:
		+
		+	For additional Infos and Tips regarding VGA Passthrough see [[Xen_VGA_Passthrough]]

	It may be a good idea to install the DomU initially WITHOUT the "pci" line in the DomU config,		It may be a good idea to install the DomU initially WITHOUT the "pci" line in the DomU config,

Debian Guest Installation Using Debian Installer

2012-05-15T09:08:41Z

← Older revision		Revision as of 09:08, 15 May 2012
Line 120:		Line 120:
	or for a 64 bit guest:		or for a 64 bit guest:
	bootloader = "pygrub"		bootloader = "pygrub"
-	bootloader_args = "--kernel=/install.~~386/~~amd/vmlinuz --ramdisk=/install.amd/xen/initrd.gz"	+	bootloader_args = "--kernel=/install.amd/xen/vmlinuz --ramdisk=/install.amd/xen/initrd.gz"

	As with the netboot install you should specify suitable command line options. e.g.:		As with the netboot install you should specify suitable command line options. e.g.:

User:OrleneCourtemanche

2012-05-14T06:16:44Z

New user account

New page

Xen Serial Console

2012-05-12T01:20:59Z

No getty (login prompt) on the serial console so I can't login?:

← Older revision		Revision as of 01:20, 12 May 2012
Line 175:		Line 175:
	<pre><nowiki>		<pre><nowiki>
	s1:2345:respawn:/sbin/agetty ttyS1 57600		s1:2345:respawn:/sbin/agetty ttyS1 57600
		+	</nowiki></pre>
		+
		+
		+	Example /etc/inittab line to run agetty on Debian 6.0 using Xen 4.1.1 for hvc0 at speed 38400 bits per second:
		+
		+
		+	<pre><nowiki>
		+	s1:2345:respawn:/sbin/agetty 38400 hvc0
	</nowiki></pre>		</nowiki></pre>

User:Frodo

2012-05-12T01:18:22Z

New user account

New page

Xen Best Practices

2012-05-11T09:24:15Z

Mention xl and autoballoon=0 when using dom0_mem=

← Older revision		Revision as of 09:24, 11 May 2012
Line 24:		Line 24:
	</pre>		</pre>

-	The next step is to configure ~~xend~~ to make sure dom0 memory is never ballooned down while starting new guests.	+	The next step is to configure the toolstack to make sure dom0 memory is never ballooned down while starting new guests.

-	~~This~~ can be done by editing /etc/xen/~~xend-config~~.~~sxp~~ and ~~modifying the "dom0-min-mem" option to (dom0-min-mem 512) and also change the "enable-dom0-ballooning" option to (enable-dom0-ballooning no)~~. ~~These options~~ will ~~make sure xend never takes any~~ memory ~~away from~~ dom0.	+	If you are using the [[XL]] toolstack then this can be done by editing /etc/xen/xl.conf and setting autoballoon=0. This will prevent [[XL]] from ever automatically adjusting the amount of memory assigned to dom0.

-	After making these changes to grub.conf and to xend-config.sxp, reboot the system. After reboot you will notice dom0 has only 512 MB of memory, and the rest of the RAM is available in Xen hypervisor as a free memory. You can run "xm list" to verify the amount of memory dom0 has, and "xm info" to verify the amount of free memory in Xen hypervisor.	+	If you are using the xend toolstack then this can be done by editing /etc/xen/xend-config.sxp and modifying the "dom0-min-mem" option to (dom0-min-mem 512) and also change the "enable-dom0-ballooning" option to (enable-dom0-ballooning no). These options will make sure xend never takes any memory away from dom0.
		+
		+	After making these changes to grub.conf and to xend-config.sxp/xl.conf, reboot the system. After reboot you will notice dom0 has only 512 MB of memory, and the rest of the RAM is available in Xen hypervisor as a free memory. You can run "xl list" (or "xm list") to verify the amount of memory dom0 has, and "xl info" (or "xm info") to verify the amount of free memory in Xen hypervisor.

	== Why should I dedicate fixed amount of memory for Xen dom0? ==		== Why should I dedicate fixed amount of memory for Xen dom0? ==

Xen Common Problems

2012-05-11T05:15:52Z

← Older revision		Revision as of 05:15, 11 May 2012
(2 intermediate revisions not shown)
Line 11:		Line 11:

	== I'd like to contribute to the Xen wiki pages, I have something to add/edit/fix, how can I do it? ==		== I'd like to contribute to the Xen wiki pages, I have something to add/edit/fix, how can I do it? ==
-	Contributions are very welcome! You should create yourself a wiki account~~, and then send an email to Todd Deshane asking for~~ edit permissions. ~~Please include your Xen wiki username~~ in the ~~email~~. ~~Email address for Todd Deshane is todd dot deshane at xen dot~~ org.	+	Contributions are very welcome! You should create yourself a wiki account. No edit permissions are needed. More info on getting started at
		+	* [[Special:UserLogin\|Create an account or log in]]
		+	* [[Sandbox\|Play with the Sandbox]]
		+	* [http://upload.wikimedia.org/wikipedia/commons/8/89/Cheatsheet-mediawiki.pdf MediaWiki Cheat Sheet]
		+	* [http://www.mediawiki.org/wiki/Help:Contents MediaWiki Help Contents]
		+	* [http://www.mediawiki.org/wiki/Help:Formatting MediaWiki Formatting]
		+	* [http://www.mediawiki.org/wiki/Books_about_MediaWiki Books about MediaWiki]
		+	* [[Wiki_Community\|Wiki Community Portal]]
		+	* [[:Category:Wiki Management\|Wiki Management Tools]]
		+	* [[Xen:Multi-language Conventions\|Multi-language Conventions]]

	== I'd like to read some kind of overview about Xen ==		== I'd like to read some kind of overview about Xen ==
-	See the [[XenOverview]] wiki page. Also check the following PDF documents:	+	See the [[XenOverview]] wiki page and [[:Category:Overview]]. Also check the following PDF documents:

	* http://www.xen.org/files/Marketing/WhatisXen.pdf		* http://www.xen.org/files/Marketing/WhatisXen.pdf

Xen Common Problems

2012-05-11T00:47:28Z

I'd like to contribute to the Xen wiki pages, I have something to add/edit/fix, how can I do it?:

← Older revision		Revision as of 00:47, 11 May 2012
(One intermediate revision not shown)

User:Florida surrogate

2012-05-10T22:35:31Z

deleted "[[User:Florida surrogate]]" content was: "Some Helpful Tips on Surrogacy for Childless Couples Couples who cannot have children because of various reasons often look into several diff…" (and the only contributor was "Florida surrogate")

New page

User:Surrogates florida

2012-05-10T22:34:23Z

blocked [[Surrogates florida (Talk | contribs)]] with an expiry time of infinite (account creation disabled) Spamming links to external sites

New page

User:Florida surrogate

2012-05-10T22:33:58Z

blocked [[Florida surrogate (Talk | contribs)]] with an expiry time of infinite (account creation disabled) Spamming links to external sites

New page

XenStore

2012-05-10T18:10:13Z

Script only works in bash, not actually in more compliant implementations like dash.

← Older revision		Revision as of 18:10, 10 May 2012
Line 14:		Line 14:

	<pre><nowiki>		<pre><nowiki>
-	#!/bin/sh	+	#!/bin/bash

	function dumpkey() {		function dumpkey() {

User:Matthias

2012-05-10T18:09:41Z

New user account

New page

User:Florida surrogate

2012-05-10T16:03:52Z

New user account

New page

User:Surrogates florida

2012-05-10T14:51:52Z

New user account

New page

Xapi on debian user experience improvements

2012-05-10T12:39:29Z

Created page with "This page lists a number of things we could do to make the default experience of xapi on debian more smooth # "xe" could detect when it's talking to another webserver (e.g. apac…"

New page

This page lists a number of things we could do to make the default experience of xapi on debian more smooth

# "xe" could detect when it's talking to another webserver (e.g. apache) and print something more helpful than "Server internal error."
# the NFS SR could detect when "nfs-common" hasn't been installed and prompt to install it (or it could depend on it)
# the regenerate templates md5 stamp shouldn't be written if the regenerate templates fails (eg due to a dead xapi)
# xapi startup should print a more useful message if libXc doesn't work because the "xen" init.d script hasn't done the necessary setup

[[Category:XCP]]

User:Dave.scott

2012-05-10T12:35:57Z

← Older revision		Revision as of 12:35, 10 May 2012
Line 5:		Line 5:
	# Splitting domain management from xapi into [[xenopsd]]		# Splitting domain management from xapi into [[xenopsd]]
	# [[Inter-domain communication for XCP]]		# [[Inter-domain communication for XCP]]
		+	# [[xapi on debian user experience improvements]]

DomU Install with Virt-Install

2012-05-10T09:38:20Z

← Older revision		Revision as of 09:38, 10 May 2012
Line 85:		Line 85:
	[[Category:Xen]]		[[Category:Xen]]
	[[Category:Guest Install]]		[[Category:Guest Install]]
		+	[[Category:Fedora]]

DomU Install with Virt-Manager

2012-05-10T09:38:03Z

← Older revision		Revision as of 09:38, 10 May 2012
Line 149:		Line 149:
	[[Category:Xen]]		[[Category:Xen]]
	[[Category:Guest Install]]		[[Category:Guest Install]]
		+	[[Category:Fedora]]

Fedora 13 Xen 4 Tutorial

2012-05-10T09:37:25Z

Using ssh X11 forwarding:

← Older revision		Revision as of 09:37, 10 May 2012
Line 386:		Line 386:
	[[Category:Xen]]		[[Category:Xen]]
	[[Category:Host Install]]		[[Category:Host Install]]
		+	[[Category:Fedora]]

Project Zeus Fedora Spec

2012-05-10T09:36:00Z

Fedora 16 Dom0

2012-05-10T09:34:50Z

Installing a domU:

← Older revision		Revision as of 09:34, 10 May 2012
Line 91:		Line 91:
	[[Category:Xen]]		[[Category:Xen]]
	[[Category:Host Install]]		[[Category:Host Install]]
		+	[[Category:Fedora]]

User:Gcb1122

2012-05-10T07:41:55Z

New user account

New page

User:Huangjingyu

2012-05-10T03:00:23Z

New user account

New page

Fedora 16 Dom0

2012-05-09T14:33:48Z

Installing a domU:

← Older revision		Revision as of 14:33, 9 May 2012
Line 90:		Line 90:
	[[Category:Tutorial]]		[[Category:Tutorial]]
	[[Category:Xen]]		[[Category:Xen]]
		+	[[Category:Host Install]]

User:Scoobysoft

2012-05-08T21:58:41Z

New user account

New page

User:Guille

2012-05-08T13:38:02Z

New user account

New page

Xen Document Days/TODO

2012-05-08T13:33:06Z

← Older revision		Revision as of 13:33, 8 May 2012
Line 42:		Line 42:
	* vcpu pinning		* vcpu pinning
	* using xm trigger to poweroff or firing off NMIs		* using xm trigger to poweroff or firing off NMIs
		+	* Expand [[Host Configuration/Networking]] docs to cover non-bridge network configurations supported by xend (e.g. routed, nat'd). Possibly split into a page per config.

	== Developer Docs ==		== Developer Docs ==

Reporting Bugs against Xen

2012-05-08T10:48:41Z

Direct XCP questions to xen-api@, use lists.xen.org not lists.xensource.com, links to list info, typos

← Older revision		Revision as of 10:48, 8 May 2012
Line 7:		Line 7:
	== How to Report a Bug Against Xen ==		== How to Report a Bug Against Xen ==

-	The primary location for reporting bugs against the Xen hypervisor and associated bundled tools (e.g. against <code>xen-unstable.hg</code> or <code>xen-X.Y-testing.hg</code>) is by posting to the [mailto:xen-devel@lists.~~xensource~~.~~com~~ xen-devel] mailing list. However please read the following before posting.	+	The primary location for reporting bugs against the Xen hypervisor and associated bundled tools (e.g. against <code>xen-unstable.hg</code> or <code>xen-X.Y-testing.hg</code>) is by posting to the [mailto:xen-devel@lists.xen.org xen-devel] mailing list ([http://lists.xen.org/archives/html/xen-devel/ list info]). However please read the following before posting.

	Although a bugzilla instance does exist it is not well maintained or widely used by developers. If you really want to file a bug in bugzilla you are strongly recommended to also post to the mailing list.		Although a bugzilla instance does exist it is not well maintained or widely used by developers. If you really want to file a bug in bugzilla you are strongly recommended to also post to the mailing list.

-	If you are having a problem with Xen you should consider initially posting your issue to the [mailto:xen-users@lists.~~xensource~~.~~com~~ xen-users] mailing list, in order to rule out common configuration issues and user errors.	+	If you are having a problem with Xen you should consider initially posting your issue to the [mailto:xen-users@lists.xen.org xen-users] mailing list ([http://lists.xen.org/archives/html/xen-users/ list info]), in order to rule out common configuration issues and user errors.

-	~~Before posting a bug report you~~ are ~~strongly encouraged~~ to ~~read Simon Tatham~~'~~s excelent~~ [http://~~www~~.~~chiark.greenend~~.org~~.uk~~/~~~sgtatham~~/~~bugs.html "How to Report Bugs Effectively"~~]~~. ''Please do not report Xen bugs to Simon Tatham!''~~	+	Issues with XCP and user questions are better addressed to the [mailto:xen-api@lists.xen.org xen-api] list rather than ''xen-users'' or ''xen-devel''. See [http://lists.xen.org/mailman/listinfo/xen-api list info] for more details

-	Before posting you should check your favourite [http://www.google.com search engine] and the list archives for both [http://lists.~~xensource~~.~~com~~/archives/html/xen-users/ xen-users] and [http://lists.~~xensource~~.~~com~~/archives/html/xen-devel/ xen-devel] to see if your issue has been reported (and perhaps solved) already.	+
		+	Before posting a bug report you are strongly encouraged to read Simon Tatham's excellent [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html "How to Report Bugs Effectively"]. ''Please do not report Xen bugs to Simon Tatham!''
		+
		+	Before posting you should check your favourite [http://www.google.com search engine] and the list archives for both [http://lists.xen.org/archives/html/xen-users/ xen-users] and [http://lists.xen.org/archives/html/xen-devel/ xen-devel] to see if your issue has been reported (and perhaps solved) already.

	== List Etiquette ==		== List Etiquette ==

-	[mailto:xen-devel@lists.~~xensource~~.~~com~~ xen-devel], like many open-source mailing lists, keeps to a set of conventions established in the '80s and '90s. They may seem a bit archaic these days, but breaking them is considered bad form and may cause people to skip over your bug report. There are a number of guides on the web, but some particular points that seem to show up on xen-devel are:	+	[mailto:xen-devel@lists.xen.org xen-devel], like many open-source mailing lists, keeps to a set of conventions established in the '80s and '90s. They may seem a bit archaic these days, but breaking them is considered bad form and may cause people to skip over your bug report. There are a number of guides on the web, but some particular points that seem to show up on xen-devel are:
-	* Please post in plain text (i.e. not HTML), word-wrapped to ~~somewehere~~ around 72 characters.	+	* Please post in plain text (i.e. not HTML), word-wrapped to somewhere around 72 characters.
	* Please don't top-post.		* Please don't top-post.
	* Please start a new thread for a new bug (don't just reply to a random email from the list).		* Please start a new thread for a new bug (don't just reply to a random email from the list).
Line 30:		Line 33:
	=== General ===		=== General ===

-	First and foremost please provide a clear description of the issue you are seeing. What ''~~exacly~~'' happened and what did you expect. Try to be as clear as you can, properly explaining your issue is key to us being able to help. See [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html "How to Report Bugs Effectively"] (which you have already read, right?) for examples of the sorts of bug reports which are not likely to garner a response from developers, as well as advice on how to produce a good bug report.	+	First and foremost please provide a clear description of the issue you are seeing. What ''exactly'' happened and what did you expect. Try to be as clear as you can, properly explaining your issue is key to us being able to help. See [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html "How to Report Bugs Effectively"] (which you have already read, right?) for examples of the sorts of bug reports which are not likely to garner a response from developers, as well as advice on how to produce a good bug report.
-		+	u
-	Also please always include the precise version of Xen you are running, i.e. a reference to the particular mercurial tree and a changeset number or the name of the ~~distribtion~~ which provided the packages you are using along with the version of those packages.	+	Also please always include the precise version of Xen you are running, i.e. a reference to the particular mercurial tree and a changeset number or the name of the distribution which provided the packages you are using along with the version of those packages.

	Where possible, please include precise steps to reproduce the issue. An issue which can be reproduced by a developer is an order of magnitude more likely to get fixed quickly.		Where possible, please include precise steps to reproduce the issue. An issue which can be reproduced by a developer is an order of magnitude more likely to get fixed quickly.

← Older revision		Revision as of 09:36, 10 May 2012
Line 46:		Line 46:
	[[Category:Developers]]		[[Category:Developers]]
	[[Category:Index]]		[[Category:Index]]
		+	[[Category:Fedora]]