XenFAQ: Difference between revisions

From Xen
Jump to navigationJump to search
(Migrated)
 
(Split this page into several pages in the FAQ category. Redirecting this page to the FAQ category.)
 
Line 1: Line 1:
#REDIRECT [[:Category:FAQ]]
<!-- MoinMoin name: XenFaq -->
<!-- Comment: Added link to XenFAQ2 -->
<!-- WikiMedia name: XenFaq -->
<!-- Page revision: 00000096 -->
<!-- Original date: Wed Sep 14 11:36:18 2011 (1316000178000000) -->

<!-- #pragma section-numbers on -->
<!-- ! TOC here -->

{{Needs_Refactor|This document may benefit from being broken into separate FAQs by section, maybe merged with [[XenFAQ2]].}}

= General Information =

Also note that there is a page called [[XenFAQ2]], which needs to be formatted as well as merged with this page.

== What is Xen? ==
Xen is a virtual machine monitor (VMM) for x86-compatible computers. Xen can securely execute multiple virtual machines, each running its own OS, on a single physical system with close-to-native performance.

== How is Xen licensed? ==
Xen is Open Source, and is released under terms of the [http://www.gnu.org/licenses/gpl-2.0.html GNU General Public License v2]. Some Xen projects may contain licensing exceptions or a small number of files which are licensed under a GPL compatible license. If so, the source repository contains a '''COPYING''' file providing more information (see [http://lxr.xensource.com/lxr/source/COPYING here] for the COPYING file for the hypervisor).

Xen projects do not come with an End User License as the GPL suffices. There is however a trademark policy that restricts the use of the Xen brand to ensure that all Xen branded hypervisors are compatible and will run the same guest VMs. You can find the [http:/www.xen.org/files/XenTMPolicy2008June.pdf trademark policy here].

Operating systems or other applications written to use Xen's hypercall interface are not derived works of Xen, hence may be licensed differently.

== Which OSes run on Xen? ==
To achieve such high performance, Xen requires that OSes are ported to run on it.

See [[XenDom0Kernels|Xen Dom 0 Kernels]] and [[XenDomUSupport|Xen Dom U support]]
*
== Does Xen support Microsoft Windows? ==
The paravirtualized approach we use to get such high performance has not been usable directly for Windows to date. However Xen 3.0 added [[IntelVT|Intel VT-x]] support to enable the running of unmodified guest operating systems, including Windows XP & 2003 Server, using hardware virtualization technology. Xen 3.0.2 and later support AMD Pacifica technology as well. Check to see if your CPU is among the list of [[HVM Compatible Processors]], and if your motherboard is among the list of [[HVM Compatible Motherboards]].

''(Note: This does not necessarily mean, that just about _any_ OS runs in HVM Mode! Reports vary about getting *BSD to work in HVM mode, on the Mailing List there's only 1 success for OpenBSD (http://www.openbsd-france.org/ml/archives/msg02494.html), no success message for the others, but some problem reports)''

== Does Xen run on laptops? ==
Xen will typically run on laptops.

== Which architectures does Xen support? ==
Xen currently runs on the x86, x86_64, IA64 (Itanium) and ARM architectures. On x86 Xen requires a "P6" or newer processor (that's any Intel or AMD x86 CPU purchased in the last seven years). Multiprocessor and multicore machines are supported, including support for Hyper-Threading (SMT). Support for x86/64 is available since Xen 3.0. We hope to add other architectures such as PPC.

== 32bit and 64bit ==
The 32bit and 64bit questions are many and more complex than you might think. Things can be 32bit, 32bit PAE or 64bit. There is the hardware, the xen hypervisor, the dom0 kernel and userland and the domU kernel and userland.
{| border="1" cellpadding="2" cellspacing="0"
|
| '''32bit PAE Hypervisor'''
|-
| '''32bit PAE PV DomU'''
| Yes
|-
| '''64bit PV DomU'''
| No
|-
| '''32bit HVM DomU'''
| Yes
|-
| '''64bit HVM DomU'''
| No
|}

= Booting Xen =
== I get an error from Xen... (console output starting "(XEN)") ==

<pre><nowiki>
(XEN) Initial guest OS requires too much space
(XEN) (8MB is greater than 0MB limit)
</nowiki></pre>

Check that you are correctly specifying the <code><nowiki>dom0_mem</nowiki></code> command line option for starting Xen. Note that: <code><nowiki>dom0_mem=512M</nowiki></code> should work in recent versions while older versions such as 2.0.5 require the memory specification to be in kilobytes, e.g. <code><nowiki>dom0_mem=524288</nowiki></code>.

(Note: you need to leave some memory for Xen, so the above assumes you have more than 512M total in the system; if you still have problems, reduce the amount further).

== How do I hide a pci device from dom0? ==
In Xen 2.x, you can add the <code><nowiki>physdev_dom0_hide</nowiki></code> parameter (see [[XenBooting]] for more parameters) to hide one or more pci devices to Dom0, so you can affect them to domU.

Pci slots MUST be formatted like this:

* '''(nn:nn.n)'''
so

* <code><nowiki>(03:06.1)</nowiki></code> is correct
* <code><nowiki>(03:6.1)</nowiki></code> is NOT correct
You can get the pci bus address on a Linux system by using the lspci command (only the last bits are relevant):


<pre><nowiki>
lspci | grep Ethernet
0000:02:03.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
0000:02:03.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
</nowiki></pre>

Then:

* to hide the second network interface from dom0, you can then append <code><nowiki>physdev_dom0_hide=(02:03.1)</nowiki></code> to your <code><nowiki>kernel /boot/xen-2.0.gz</nowiki></code>.
* to hide multiple pci devices, simply concatenate all the pci slots address like this: <code><nowiki>physdev_dom0_hide=(02:03.0)(02:03.1)</nowiki></code>
If everything went ok, you should see the following lines after a reboot:


<pre><nowiki>
(XEN) Hiding PCI device 02:03.0 from DOM0
(XEN) Hiding PCI device 02:03.1 from DOM0
</nowiki></pre>

== Error about root device still mounted when it's not mounted, zombie domU that can't be killed, domU hangs under heavy I/O (e.g disk) access ==
This is an unresolved problem with Xen 3.0.

You may try to [http://lists.xensource.com/archives/html/xen-users/2006-03/msg00651.html pass nousb to dom0 kernel command line], or [http://lists.xensource.com/archives/html/xen-devel/2005-07/msg00436.html pass ignorebiostables], or try to [http://lists.xensource.com/archives/html/xen-devel/2005-07/msg00468.html disable software IRQ affinity for 1850/2850 systems].

* [http://lists.xensource.com/archives/html/xen-users/2006-02/msg00851.html Discussion in xen-users mailing list]
= Networking Issues =
== What is veth, vif or xenbr0? ==
You should read [[XenNetworking]] http://wiki.xensource.com/xenwiki/XenNetworking

== Why can't I ssh into or ping a newly created domain? ==
In the default configuration we rely on the Linux bridge-utils in domain 0 to set up virtual networking. After you've created a new domain (e.g., domain 1) you should be able to run <code><nowiki>ifconfig</nowiki></code> in domain 0 and see an interface with a name like vif1.0; you should also be able to check that bridging is working by typing <code><nowiki>brctl show xen-br0</nowiki></code>. Finally, you can check the IP confiuration in the new domain by logging into it via the console (<code><nowiki>xm console</nowiki></code>) and running standard tools such as <code><nowiki>ifconfig</nowiki></code> and <code><nowiki>route</nowiki></code>.

== Why does my new domain receive no network traffic until after it initiates an outgoing connection? ==
This is an issue that occurs under the following circumstances:

* You do not specify the domain's MAC address, causing a random MAC address to be selected at domain creation time
* The upstream router has a local ARP cache
When a domain is destroyed, the host system's ARP cache is purged of addresses for the defunct virtual NIC. If the domain is recreated it is likely to be allocated a different random MAC address. This is no problem for the host machine, but the external switch/router still knows the "old" MAC address. The switch/router requires an outbound packet to the outside world to implicitly eradicate the old ARP-cache entry. This is not really Xen's fault at all, just a property of the implementation of ARP resolution.

Fixes: Either manually declare the MAC address in your VM config file, or upgrade to the 2.0-testing tree where the problem is fixed. This fix will also find its way into the forthcoming 2.0.4 maintenance release.

== How do I fix MTU issues resulting in "Received packet needs 8 bytes more headroom" in dmesg or /var/log/message output ? ==
See: http://lists.xensource.com/archives/html/xen-devel/2005-12/msg00226.html

You can work around the bug by reducing the MTU of eth0 in the dom0 e.g. "ifconfig eth0 mtu 1400". Put this in your networking scripts (e.g.: /etc/sysconfig/network/ifcfg-eth0 for RH/RPM systems or /etc/network/interfaces for Debian/Deb systems). See: http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/ref-guide/s1-networkscripts-interfaces.html for RH syntax, 'man interfaces' for Debian.

This bug is understood and a fix has been applied to the testing tree.

It only effects dom0 kernels built with the -xen config rather than -xen0.

Basically, the -xen kernel config turns on so much stuff that the area reserved for the max possible header length is too big. This causes a netfront slow-path to be exercised that copies the SKB. Unfortunately, this path hadn't been exercised before, and guess what, it was subtly broken for checksum-offloaded packets.

== TCP and UDP checksum errors, ping but nothing else, ipsec tunnels don't form, DNAT translation doesn't work ==
Try running the following command in each domU:


<pre><nowiki>
ethtool -K eth0 tx off
</nowiki></pre>

This command disable TX checksumming

To check checksum problems, you can use tcpdump:


<pre><nowiki>
tcpdump -vv -n -i eth0</nowiki></pre>

Read http://lists.xensource.com/archives/html/xen-users/2006-04/msg00032.html

This may or may not work.

[http://lists.xensource.com/archives/html/xen-users/2006-02/msg00747.html Patch for network-bridge]

== Xen and Shorewall ==
There is a document about configuring Shorewall in Dom0 at http://www.shorewall.net/Xen.html

http://www1.shorewall.net/XenMyWay.html can be useful also.

== Too many vethX and vif0.X ==
By default, 8 <code><nowiki>vethX</nowiki></code> and <code><nowiki>vif0.X</nowiki></code> are created. These interfaces are "cheap" but clutter list of interfaces. If you want to allocate only the necessary number, pass <code><nowiki>netloop.nloopbacks=NUMBER</nowiki></code> parameter to kernel command line.

== I can't use more than 3 network interfaces in domU ==
This is a limitation in Xen 3. Xen 3.1 supports 8 network interfaces.

= Running Linux on Xen =
== A large warning message is displayed when I boot Linux, saying something about '/lib/tls'. What should I do? ==
Do as the message advises! Some modern distributions ship with a 'TLS' version of glibc that is not fully compatible with Xen. To use Xen reliably and with maximum performance you must disable the incompatible glibc. You can easily do this by moving the /lib/tls directory (e.g., <code><nowiki>mv /lib/tls /lib/tls.disabled</nowiki></code>).

Alternatively, install a Xen-specific GLIBC, see [[XenSpecificGlibc]].

== Lots of programs crash with 'Segmentation fault' when I boot my system. What's going wrong? ==
See the answer to the previous question. In some environments (for example, when running Xen within a VMware product) you may experience severe problems with TLS libraries. If these are so severe that you cannot even log in to your system, you can obtain a command prompt by temporarily adding the boot parameter <code><nowiki>init=/bin/bash</nowiki></code> to your Linux command line.

== I can not export block device as /dev/sdaX in DomU ==
You have errors like


<pre><nowiki>
Registering block device major 8
register_blkdev: cannot get major 8 for sd
xen_blk: can't get major 8 with name sd
</nowiki></pre>

all you need to do is disable the entire scsi subsystem, ie:


<pre><nowiki>
CONFIG_SCSI=n
</nowiki></pre>

This allows the xen block frontend to register on device ID's normally occupied by the scsi subsystem.

== When I start a 9th domain using a loop-back file as its virtual disk why do I get "Error: vbd: Segment not found: uname=file:/path/to/image"? ==
By default, Linux only allows up to 8 loop-back devices to be active. You can increase this number by setting max_loop=32 (etc) on the domain 0 kernel command line in Grub. You also need to create new loop[n] device nodes in /dev.

== I'm trying to get X working in domain 0 but the server seems to hang (or domain 0 panics). What's going on? ==
It's likely your X server is trying to use agpgart, support for which is currently included only in the 2.0-testing and unstable trees. Try downloading a new tarball, or clone one of the BK repositories.

== I get "Badness in local_bh_enable at kernel/softirq.c" messages, why is this? ==
This is fairly likely to be caused by a module compiled for native i386 rather than Xen. When building modules outside of the Xen build tree, use <code><nowiki>make ARCH=xen ...</nowiki></code>.

Alternative, this may be a driver that uses interrupt en/disabling instructions directly rather than the proper API....

<span id="loadruninitrd"></span>

== How do I load and run an initial ram disk (initrd)? ==
To specify an initrd file for domain 0 add an extra "module" line to your GRUB config, after your kernel-module line (e.g., <code><nowiki>module /boot/initrd-2.6-xen0.img</nowiki></code>). To use an initrd file for other domains, set the "ramdisk" variable in your domain configuration file (e.g., <code><nowiki>ramdisk = path/to/initrd-2.6-xenU.img</nowiki></code>).

<span id="distroinitrd"></span>

== The initrd file that came with my distro doesn't work well with Xen. How do I edit it? ==
There are various forms of initrd image, but the two most common formats are a gzip'ed filesystem and a gzip'ed cpio file. In either case you can take the following steps to modify a file <code><nowiki>initrd.img</nowiki></code> (when running as root):


<pre><nowiki>
# mkdir initrd.mnt
# gzip -d -S ".img" /path/to/initrd.img
# mount -o loop /path/to/initrd initrd.mnt OR (cd initrd.mnt && cpio -ic <../path/to/initrd)
# ...edit files in directory initrd.mnt....
# umount initrd.mnt OR (cd initrd.mnt && find . | cpio -oc --quiet >../path/to/initrd)
# gzip -9 -S ".img" /path/to/initrd
</nowiki></pre>

If you use cpio then you may get warnings about truncated inode numbers. These can be ignored. Some distros (notably SLES 9) have a mkinitrd that generates initrd files with garbage at the end of them. Xen will not load this initrds. You can work around this problem by gunzip'ing and gzip'ing the initrd again.

== When I use the balloon driver, why do tools like 'top' and 'free' not show a change in memory usage? ==
The balloon driver requests memory from the system allocator which it then directly gives back to Xen. From the kernel's perspective, however, that memory is still part of the system and is being used by the balloon driver. Hence the unintuitive memory statistics.

== I increased the memory (RAM) in a domain and rebooted it, but it still shows the old memory value? ==
You need to "re-create" the domain using the

xm create <domU>

command again. Simply rebooting the domain does not cause it to read the new value from the domain definition file.

== Booting a guest complains about trying to use an already-mounted block device, but it isn't mounted?! ==
This is a bug to do with Xen incorrectly freeing guest resources. Take a look at the last line in /var/log/xen-hotplug.log, something like:


<pre><nowiki>
xenstore-read: couldn't read path /local/domain/9/vm
</nowiki></pre>

Take a note of that number, and run <code><nowiki>xenstore-rm backend/vbd/9</nowiki></code>, replacing 9 with the number you read. The guest machine should then boot happily.

Be careful when doing this that there are no guests effectively using the device in question, damage will probably be incurred in that case!

= Building Linux for Xen =
== How do I configure a Linux domain 0 kernel for my hardware? ==
You should be able to edit the .config file and then just type <code><nowiki>make</nowiki></code> at the top level. For example, to use Linux's graphical config editor:


<pre><nowiki>
# cd linux-2.6-xen0
# make xconfig (configure however you want) (on old version you need to specify ARCH=xen after make)
# cd ..
# make
</nowiki></pre>

If there's already a .config present in the kernel tree we leave it well alone. If there's none present and a <code><nowiki>./dist/install/boot/config-2.6-xen0</nowiki></code> exists then we copy that to .config. As a last resort, we select one of the arch/xen/configs/defconfig files.

== Why does my build fail with "error: isa_virt_to_bus_is_UNSUPPORTED undeclared"? ==
Certain drivers (primarily for ISA devices) do not work with Xen due to the restricted memory addresses that the device can access. For most of these drivers we report the error you have seen, in preference to failing weirdly at run time. We aim for Xen to support all modern x86 hardware: this restriction applies only to a few old NICs and disc controllers.

== How do I build Xen from source with a more recent kernel? ==
Modifying a kernel source tree to run Xen is not a simple task. It might seem that one should be able to run a few patches on any kernel and make it a Xen kernel but this not the case.

Currently, the best option is to look to the distribution vendors. For instance, Fedora 7 ships with Xen 3.1.0 and kernel 2.6.20. Fedora provides source RPMS that might be of interest to anyone who wants to build their own 2.6.20 Xen kernel.

= Linux Distributions =
== What Debian packages do I need for Xen? ==
To run Xen and a single OS from a binary release you need install no extra packages. To build Xen, XenLinux and documentation from source you will need: '''make''', '''libncurses5-dev''', '''libncurses5''', '''gcc''', '''libc6-dev''', '''zlib1g-dev''', '''python''', '''python-dev''', '''python-twisted''', '''openssl''', '''openssl-dev''', '''bridge-utils''', '''iproute''', '''libcurl3''', '''libcurl3-dev''', '''bzip2''', '''module-init-tools''', '''latex''', '''latex2html''', '''transfig''', and '''tgif'''.

== Why does Fedora Core 3 stop working after printing the line "Freeing unused kernel memory: ..."? ==
FC3 uses the new udev system for managing device nodes in <code><nowiki>/dev</nowiki></code>. To successfully boot, and to get any console output from <code><nowiki>init</nowiki></code>, you either need to manually create some device nodes or you need to load and run a suitable initrd. The former solution requires you to mount the root filesystem and then:


<pre><nowiki>
# mknod /path/to/dev/null c 1 3
# mknod /path/to/dev/console c 5 1
</nowiki></pre>

If you instead wish to load an initrd file then you can use one provided in the <code><nowiki>/boot</nowiki></code> directory of your FC3 filesystem, or you can use the slightly-modified one that [http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/initrd-fc3.img we supply]. To load and run your initrd file, or to modify it, see [[#loadruninitrd|this]] and [[#distroinitrd|this]] above.

You may also want to disable X by editing <code><nowiki>/etc/inittab</nowiki></code> if you do not use X, or if X is configured incorrectly and is causing your boot to fail. To do this, change "id:5:initdefault:" to "id:3:initdefault:".

== Why can't I save VM instances or migrate with Fedora Core 3 or Debian Sarge? I get a connection refused error from twisted referring to port 111. ==
<br><br> Fedora Core 3 and [[DebianSarge]] are missing <code><nowiki>/usr/lib/libcurl.so.2</nowiki></code> (they come with <code><nowiki>libcurl.so.3.0.0</nowiki></code> instead when updated to the latest RPMs as of 5/2/2005). This causes <code><nowiki>/usr/sbin/xfrd</nowiki></code> to fail and it is required for save (and other) operations. A workaround tried on both FC3 and Sarge is to just set up a symlink for <code><nowiki>libcurl.so.2</nowiki></code> which points at <code><nowiki>libcurl.so.3.0.0</nowiki></code>. With Debian, you can instead try installing [ftp://ftp.debian.org/debian/pool/main/c/curl/libcurl2_7.9.5-1_i386.deb the libcurl2 package from oldstable], though this workaround is untested and may cause you other problems.

The problem does not occur in xen-testing, which uses curl3.

== How do I fix the 4gb seg fixup messages in my syslog? ==
<br><br> These messages are from a glibc that was built with negative GS register offsets. Xen can run with negative GS register references, but it must "trap and emulate" this condition, which is relatively resource intensive, and quite slow. <br><br> If you don't have a patched glibc, see the no-tls-direct-seg-refs patch mentioned in [[XenSpecificGlibc]]. <br><br> Most newer distributions are shipped with a "-mno-tls-direct-seg-refs" compiled glibc, but it might not be enabled by default. <br><br> Some newer distributions like the RHEL5 Beta1/Beta2 require the ld.so.conf.d trick below to refer to the patched glibc. <br><br> Some slightly older distributions like Ubuntu Dapper can be fixed with a simple rebuild of glibc: (see [[UbuntuDapperHowTo]]).


<pre><nowiki>
echo 'hwcap 0 nosegneg' > /etc/ld.so.conf.d/libc6-xen.conf && ldconfig
</nowiki></pre>

Reference Link: http://lists.xensource.com/archives/html/xen-users/2006-11/msg00026.html and http://www.mail-archive.com/fedora-xen@redhat.com/msg00041.html <br><br>

= Using XEN =
== How do I connect to or detach from a console? ==
You can connect to a console directly when starting a domU:


<pre><nowiki>
# xm create -c your-DomU-config
</nowiki></pre>

This command will start a domU and connect to it's console immediately.

If you want to connect to a domU console that is already running you first have to find the domU id using:


<pre><nowiki>
# xm list
Name Id Mem(MB) CPU State Time(s) Console
Domain-0 0 123 0 r---- 2482.9
testXM1 30 127 1 -b--- 4.9 9630
testXM2 32 127 1 -b--- 4.7 9632
testXM3 34 128 1 -b--- 0.3 9634
</nowiki></pre>

Now you can connect to for example the testXM2 domU with Id 32 using:


<pre><nowiki>
# xm console 32
</nowiki></pre>

You can detach from a console using the escape character: <CTRL> ']'.

On a German keyboard try <CTRL> '5' if the above doesn't work. This works both in Putty and gnome-terminal. On a Swedish keyboard (mac running iTerm) <CTRL> 'Ã¥' works.

== In 3.0, how can I expose a console on a TCP port like in 2.0 ==
Xen 3.0 no longer exposes consoles on TCP ports to provide stronger security out of the box. If this feature is desired (and you're on an isolated network), you can achieve the same results using inetd or xinetd. The following is an xinetd service that can be enabled by placing it in /etc/xinetd.d/xen:


<pre><nowiki>
# default: on
# description: Xen console port
service xen1
{
disable = yes
type = UNLISTED
socket_type = stream
protocol = tcp
user = root
wait = no
port = 9001
server = /usr/sbin/xm
server_args = console 1
}
service xen2
{
disable = yes
type = UNLISTED
socket_type = stream
protocol = tcp
user = root
wait = no
port = 9002
server = /usr/sbin/xm
server_args = console 2
}
</nowiki></pre>

Adding entries for each domid that you want to expose (and the port you want to expose it on). In the above example, entries are only made for domain IDs 1 and 2. Any additional xinetd parameters can be used to limit where the connections come from and to implement logging.

== In Xen VM, how can I use 3D graphics. ==
See [[XenVGAPassthrough:]] wiki page for more information how to give a VM direct/full access (including video and 3d acceleration) to a graphics (VGA) card.

= Help With Xen =
== Where do I find documentation on Xen? ==
There's a [[XenDocs|list of pages on this wiki]] which might be helpful.

== What support is available for Xen? ==
There is both paid and volunteer support available for Xen. Commercial support is provided by Citrix Systems, Inc. ([[XenSource]], Inc.), the proprietors of this wiki. Volunteer support is available via the Xen [http://lists.xensource.com/ mailing lists] and on Internet Relay Chat (IRC):

# channel #xen on [http://www.oftc.net/ irc.oftc.net] is frequented by Xen developers
# channel ##xen ("about Xen") on [http://freenode.net/ irc.freenode.net] is a slightly larger, unofficial channel which also provides support
A search tool is available to search all [http://xen.markmail.org/ Xen mailing lists].

== Where can I find a list of available Xen dom0 kernels? ==
Take a look at the [[[XenDom0Kernels]]] wiki page.

== Where can I find answers to some common questions and problems about Xen? ==
Take a look at the [[[XenCommonProblems]]] wiki page.

== Where can I find Best Practices about running Xen? ==
Take a look at the [[[XenBestPractices]]] wiki page.

== I'm interesting in being a Xen developer, is there a list of projects to work with? ==
Yes! Please check out the [[XenDevelopmentProjects:]] wiki page for more information!
== Where and how can i report a bug? ==
This information will need an upgrade, but by now, as reported by [http://lists.xensource.com/archives/html/xen-devel/2007-01/msg01049.html Ewan Mellor] and [http://lists.xensource.com/archives/html/xen-devel/2007-01/msg01050.html Keir Fraser], is to:

# Place question in [http://lists.xensource.com/xen-users xen-users] mailing list, just to be sure that this is not a faq or something like that
# If it is not resolved in [http://lists.xensource.com/xen-users xen-users] mailing list, and it IS a bug, you have to:
## Place bug in [http://bugzilla.xensource.com bugzilla]
## Flag the problem (with link to bugzilla, and all that you think is necessary) in [http://lists.xensource.com/xen-devel xen-devel] mailing list
== Where and how can I submit a patch? ==
To submit a patch, put it in [http://lists.xensource.com/xen-devel xen-devel] mailing list, as reported by [http://lists.xensource.com/archives/html/xen-devel/2007-01/msg01191.html Keir Fraser], in plain-text unified diff format inline in the main body or as an attachment. Also, please add


<pre><nowiki>
Signed-off-by: Name Surname <email@domain>
</nowiki></pre>

to your email with patch, as reported by [http://lists.xensource.com/archives/html/xen-devel/2007-01/msg01051.html Ewan Mellor].

If there is a bug in bugzilla report the id of the bug, but by now do not expect anything from bugzilla (see above: "Where and how can i report a bug?").

[[Category:Xen]]
[[Category:FAQ]]
[[Category:Users]]
[[Category:Beginners]]

Latest revision as of 16:35, 12 November 2011

Redirect to:

Retrieved from "https://wiki.xenproject.org/index.php?title=XenFAQ&oldid=561"