aboutsummaryrefslogtreecommitdiffstats
path: root/tools/examples
Commit message (Collapse)AuthorAgeFilesLines
* tools: drop VT-i exampleJan Beulich2013-08-272-181/+0
| | | | | | ... as being another IA64 leftover. Signed-off-by: Jan Beulich <jbeulich@suse.com>
* tools: make building xend configurable.Ian Campbell2013-08-201-17/+16
| | | | | | | | | | | | | xend has been deprecated for 2 releases now. Lets make it possible to not even build it. For now I'm leaving the default of on but I would like to change that before the 4.4 release. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com> Acked-by: Matt Wilson <msw@amazon.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
* libxl: Add vif.default.backend to xl.confGeorge Dunlap2013-07-221-0/+4
| | | | | | | | | This will allow a user to default to a network driver domain system-wide. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> Acked-by: Roger Pau Monné <roger.pau@citrix.com> Acked-by: Ian Campbell <ian.campbell@citrix.com>
* xl: Enable by default claim mode.Konrad Rzeszutek Wilk2013-07-221-1/+1
| | | | | | | | | | During the Xen 4.3 release we discussed that this feature could be turned on by default - as it benefits all of the guests - not just tmem related. Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Acked-by: George Dunlap <george.dunlap@eu.citrix.com> Acked-by: Ian Campbell <ian.campbell@citrix.com>
* xl: Update example xl.conf with correct name for default script optionGeorge Dunlap2013-05-301-3/+3
| | | | | | | | | | We've changed the config option from "vifscript" to "vif.default.script". This was changed in the manpage but not in the example xl.conf. Also move the option down to be with the other vif options. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> Acked-by: Ian Campbell <ian.campbell@citrix.com>
* xl: Implement XENMEM_claim_pages support via 'claim_mode' global configKonrad Rzeszutek Wilk2013-04-161-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The XENMEM_claim_pages hypercall operates per domain and it should be used system wide. As such this patch introduces a global configuration option 'claim_mode' that by default is disabled. If this option is enabled then when a guest is created there will be an guarantee that there is memory available for the guest. This is an particularly acute problem on hosts with memory over-provisioned guests that use tmem and have self-balloon enabled (which is the default option for them). The self-balloon mechanism can deflate/inflate the balloon quickly and the amount of free memory (which 'xl info' can show) is stale the moment it is printed. When claim is enabled a reservation for the amount of memory ('memory' in guest config) is set, which is then reduced as the domain's memory is populated and eventually reaches zero. If the reservation cannot be meet the guest creation fails immediately instead of taking seconds/minutes (depending on the size of the guest) while the guest is populated. Note that to enable tmem type guests, one needs to provide 'tmem' on the Xen hypervisor argument and as well on the Linux kernel command line. There are two boolean options: (0) No claim is made. Memory population during guest creation will be attempted as normal and may fail due to memory exhaustion. (1) Normal memory and freeable pool of ephemeral pages (tmem) is used when calculating whether there is enough memory free to launch a guest. This guarantees immediate feedback whether the guest can be launched due to memory exhaustion (which can take a long time to find out if launching massively huge guests) and in parallel. [v1: Removed own claim_mode type, using just bool, improved docs, all per Ian's suggestion] [v2: Updated the comments] [v3: Rebase on top 733b9c524dbc2bec318bfc3588ed1652455d30ec (xl: add vif.default.script)] [v4: Fixed up comments] [v5: s/global_claim_mode/claim_mode/] [v6: Ian Jackson's feedback: use libxl_defbool, better comments, etc] Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
* xl: extend autoballoon xl.conf option with an "auto" optionDavid Vrabel2013-04-081-3/+4
| | | | | | | | | | | | | | | | | | autoballoon=1 is not recommened if dom0_mem was used to reduce the amount of dom0 memory. Instead of requiring users to change xl.conf if they do this, extend the autoballoon option with a new choice: "auto". With autoballoon="auto", autoballooning will be disabled if dom0_mem was used on the Xen command line. For consistency, accept "on" and "off" as valid autoballoon options (1 and 0 are still accepted). The default remains "on" for now. Signed-off-by: David Vrabel <david.vrabel@citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
* xl: add vif.default.bridgeRoger Pau Monne2013-03-151-0/+3
| | | | | | | | | | | This is a replacement for defaultbridge xl.conf option. The now deprecated defaultbridge is still supported. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: George Dunlap <George.Dunlap@eu.citrix.com> Cc: Ian Campbell <ian.campbell@citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* xl: allow specifying a default gatewaydev in xl.confRoger Pau Monne2013-03-151-0/+3
| | | | | | | | | | | | | | This adds a new global option in the xl configuration file called "vif.default.gatewaydev", that is used to specify the default gatewaydev to use when none is passed in the vif specification. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Acked-by: Ian Campbell <ian.campbell@citrix.com> Tested-by: Ulf Kreutzberg <ulf.kreutzberg@hosteurope.de> Cc: Ulf Kreutzberg <ulf.kreutzberg@hosteurope.de> Cc: Ian Campbell <ian.campbell@citrix.com> Cc: George Dunlap <george.dunlap@citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
* tools: Remove the vtpm process modelMatthew Fioravante2012-11-135-63/+1
| | | | | | | | | Remove the old vtpm process model. It doesn't work very well and is no longer supported. Signed-off-by: Matthew Fioravante <matthew.fioravante@jhuapl.edu> Acked-by: Ian Campbell <ian.campbell@citrix.com> Committed-by: Ian Campbell <ian.campbell@citrix.com>
* libxl: add option to choose who executes hotplug scriptsRoger Pau Monne2012-07-261-0/+5
| | | | | | | | | | | | | | | | | Add and option to xl.conf file to decide if hotplug scripts are executed from the toolstack (xl) or from udev as it used to be in the past. This option is only introduced in this patch, but it has no effect since the code to call hotplug scripts from libxl is introduced in a latter patch. This choice will be saved in "libxl/disable_udev", as specified in the DISABLE_UDEV_PATH constant. Signed-off-by: Roger Pau Monne <roger.pau@citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Campbell <ian.campbell@citrix.com>
* xl/libxl: add a blkdev_start parameterStefano Stabellini2012-05-291-0/+3
| | | | | | | | | | | | | | | | Introduce a blkdev_start in xl.conf and a corresponding string in libxl_domain_build_info. Add a blkdev_start parameter to libxl__device_disk_local_attach: it is going to be used in a following patch. blkdev_start specifies the first block device to be used for temporary block device allocations by the toolstack. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Acked-by: Ian Campbell <ian.campbell@citrix.com> Committed-by: Ian Campbell <ian.campbell@citrix.com>
* tools/examples: mention output_format= in examples/xl.confOlaf Hering2012-02-201-0/+3
| | | | | Signed-off-by: Olaf Hering <olaf@aepfle.de> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* xl.cfg: fix gfx_passthru stringOlaf Hering2012-02-201-1/+1
| | | | | | | Use correct string for gfx_passthru, and fix comment typo in xmexample.hvm Signed-off-by: Olaf Hering <olaf@aepfle.de> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* tools/examples: Add the xl configuration examples to the makefileFabio Fantoni2012-02-201-0/+2
| | | | | | Signed-off-by: Fabio Fantoni <fabio.fantoni@heliman.it> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* docs: xlexample.hvm: mention the viridian setting.Ian Campbell2011-11-291-0/+5
| | | | | | | | Turning this on for Windows guests is recommended. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Committed-by: Ian Jackson <ian.jackson.citrix.com> Acked-by: Ian Jackson <ian.jackson.citrix.com>
* docs: add a document describing the xl cfg file syntaxIan Campbell2011-11-292-2/+2
| | | | | | | | | | | | | | | | | | Based on an initial version by Ian Jackson. I believe that all keys are now present in the document although there are are various omissions in the actual documentation of them. Hopefully however this covers the majority of the most interesting keys. Spice section: Signed-off-by: Zhou Peng <zhoupeng@nfs.iscas.ac.cn> Committed-by: Ian Jackson <ian.jackson.citrix.com> Acked-by: Ian Jackson <ian.jackson.citrix.com> The rest: Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Committed-by: Ian Jackson <ian.jackson.citrix.com> Acked-by: Ian Jackson <ian.jackson.citrix.com>
* docs: xlexample.hvm is missing "builder = 'hvm'"Ian Campbell2011-11-291-0/+3
| | | | | | | | This is rather critical... Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Committed-by: Ian Jackson <ian.jackson.citrix.com> Acked-by: Ian Jackson <ian.jackson.citrix.com>
* xl: add some example configuration filesIan Campbell2011-10-272-0/+83
| | | | | | | | | | | | | These are much more minimal than the equivalent xmexamples but should eventually reference a more complete document describing the available options. These are based on the guest configuration files that I actually use day-to-day. There is an unresolved reference to a document describing the complete syntax. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Acked-by: Ian Jackson <ian.jackson.citrix.com> Committed-by: Ian Jackson <ian.jackson.citrix.com>
* build: Make XEN_ROOT an absolute path.Keir Fraser2011-03-171-1/+1
| | | | | | | | Otherwise make can search the path relative to certain standard paths such as /usr/include (e.g., the line '-include $(XEN_ROOT)/.config' in Config.mk suffers from this). Signed-off-by: Keir Fraser <keir@xen.org>
* libxl/xl: enable support for routed network configurations.Ian Campbell2011-02-181-0/+3
| | | | | | | | | | | | | Add "vifscript" option to xl.conf which configures the default vif script to use (default remains "vif-bridge") Write each VIFs "ip" option to xenstore so the vif-route script can pick it up. Reported-by: W. Michael Petullo <mike@flyn.org>. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* tools/examples: Remove obsolete bochsrc example file.Keir Fraser2011-02-171-20/+0
| | | | Signed-off-by: Keir Fraser <keir@xen.org>
* tools: Include cpupool example in /etc/xenGeorge Dunlap2011-02-151-0/+1
| | | | | | | | | xl cpupool-create at the moment requires a config file. Make sure to include the example config file in the install. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* tools: cpupools: add example cpupool config fileJuergen Gross2010-10-212-0/+18
| | | | | | | Adds an example configuration file for xm/xl pool-create Signed-off-by: juergen.gross@ts.fujitsu.com Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
* xl: fix spelling mistake in xl.confIan Campbell2010-10-211-1/+1
| | | | | Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
* xl: free memory before building a domainStefano Stabellini2010-09-221-0/+3
| | | | | | | | | | | Free the needed amount of memory before proceeding with the domain build. Use a filelock to prevent other xl instances from conflicting during this operation. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
* xl: Change default global config not to contain uncommented defaultIan Jackson2010-09-221-1/+1
| | | | | | | [mistakenly applied v4 of patch 7/12 rather than v4b -iwj] Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
* xl: add a global configuration fileStefano Stabellini2010-09-222-0/+6
| | | | | | | | | | Add a global configuration file: /etc/xen/xl.conf; the only option currently parsed is autoballoon that is 1 by default. [fixed up for conflicts with libxl__ naming policy changes -iwj] Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
* tools/xend: Fix performance of xend with more than 10000 FC device paths"Dube, Lutz"2010-07-231-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On server startup xend start or a later xend restart needs approx. 30 min to start/restart. Without attached FC devices xend start/restart needs only some seconds. server type: Fujitsu Primergy RX600-S5 The time gets lost in xen/xend/XendNode.py line 329 while calling vscsi_util.get_all_scsi_device(). 329 for pscsi_record in vscsi_util.get_all_scsi_devices(): 330 scsi_id = pscsi_record['scsi_id'] 331 if scsi_id: 332 saved_HBA_uuid = None I think, in most cases we don't need all the PSCSI devices registered in xend, but only a few of it. So a good solution for this perforamce issue is to scan only the SCSI device paths we need, controlled by a new option in xend-config.sxp. I have made a patch to allow specification of scsi devices we need in xend in the config file xend-config.sxp. The new options pscsi-device-mask expects a list of device ids oder partial device ids like the option of lsscsi, e.g. (pscsi-device-mask ('<partial-dev-id1' 'partial-dev-id2' ...)) Without this option set in xend-config.sxp or if lsscsi is not support, all device paths are process like today. Signed-off-by: Lutz Dube Lutz.Dube@ts.fujitsu.com Comment from Masaki Kanno <kanno.masaki@jp.fujitsu.com>: "Well done" Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
* xend: Do not mess with bridge if admin has set one up alreadyKeir Fraser2010-06-151-2/+17
| | | | | | | | | | | | | | | | | | | | | | | | | Previously, the default "network-script", /etc/xen/scripts/network-bridge, would attempt to do its horrid work even if you had already set everything up in /etc/network/interfaces. Setting up your bridge in /etc/network/interfaces is: * easy * required for libxl since libxl never does it for you * not a fragile piece of lunacy * properly documented * the way everyone would expect it to work In this small patch we make it so that the default config for xend doesn't mess about on startup if you already have a bridge, and doesn't mess about on shutdown unless your first-named bridge (eth0 or xenbr0, normally) doesn't also have a physical interface named p<whatever> (peth0 or pxenbr0) enslaved to it. The latter test is not ideal but will hopefully do from now until the time xend finally dies. We also fix the "documentation" - ie, the comments in the default xend-config.sxp - to correspond to reality. Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
* xend: Add interface name definition support for xend-relocation-addressKeir Fraser2010-05-251-0/+2
| | | | | | | | | | | | | | | | | | | Add a new feature for xend-relocation-address option to support definition by interface name which can be useful for people having e.g. a cluster environment with multiple network interfaces on all of the machines with only one reserved to be registered to a private cluster network. This way they won't need to specify the relocation address manually on all the machines but just simple providing the interface name to get the IP address from would do the job (all the machines have to have this interface named the same to make it working, of course). Technically it reads the interface name and gets its IP address using ioctl call of SIOCGIFADDR and if the interface doesn't have the address, i.e. if non-existing interface or hostname was provided the original ifname is returned to preserve the old behaviour. Signed-off-by: Michal Novotny <minovotn@redhat.com>
* VT-d, tools: Intel IGD passthrough 2/2: hvm config file exampleKeir Fraser2010-02-041-0/+6
| | | | | | | | | Add an option into hvm config file to enable graphics passthrough including discrete and IGD. To passthrough graphics to guest, need to set gfx_passthru=1, and also specify graphics device BDF in pci passthrough option, like pci=['xx:xx.x'] in hvm config file. Signed-off-by: Weidong Han <weidong.han@intel.com>
* tools: Do not append trailing slash to XEN_ROOT in MakefilesKeir Fraser2010-02-041-1/+1
| | | | Signed-off-by: Keir Fraser <keir.fraser@citrix.com>
* Adds 'memory_sharing' option to domain config scripts. It passes domain id toKeir Fraser2009-12-171-0/+4
| | | | | | | the tapdisk2 process if sharing is enabled (tapdisk2 is not normally aware what domain it is working for). Signed-off-by: Grzegorz Milos <Grzegorz.Milos@citrix.com>
* xend: Memory pool for pv guest on systems with >128G memoryKeir Fraser2009-12-021-0/+10
| | | | | | | | | | | | | | | | | | | | | | | The main idea of this patch is: 1) The admin sets aside some memory below 128G for 32-bit paravirtual domain creation (via dom0_mem=-<value> in kernel comand line). 2) The admin also explicitly states to the tools (i..e xend) how much memory is supposed to be left untouched by 64-bit domains 3) If a 32-bit pv DomU gets created, no ballooning ought to be necessary (since if it is, no guarantee can be made about the address range of the memory ballooned out), and memory gets allocated from the reserved range. 4) Upon 64-bit (or 32-bit HVM or HVM) DomU creation, the tools determine the amount of memory to be ballooned out of Dom0 by adding the amount needed for the new guest and the amount still in the reserved pool (and then of course subtracting the total amount of memory the hypervisor has available for guest use). Signed-off-by: james song (wei) <jsong@novell.com>
* Replace tsc_native config option with tsc_mode config optionKeir Fraser2009-11-251-3/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (NOTE: pvrdtscp mode not finished yet, but all other modes have been tested so sooner seemed better than later to submit this fairly major patch so we can get more mileage on it before next release.) New tsc_mode config option supercedes tsc_native and offers a more intelligent default and an additional option for intelligent apps running on PV domains ("pvrdtscp"). For PV domains, default mode will determine if the initial host has a "safe"** TSC (meaning it is always synchronized across all physical CPUs). If so, all domains will execute all rdtsc instructions natively; if not, all domains will emulate all rdtsc instructions but providing the TSC hertz rate of the initial machine. After being restored or live-migrated, all PV domains will emulate all rdtsc instructions. Hence, this default mode guarantees correctness while providing native performance in most conditions. For PV domains, tsc_mode==1 will always emulate rdtsc and tsc_mode==2 will never emulate rdtsc. For tsc_mode==3, rdtsc will never be emulated, but information is provided through pvcpuid instructions and rdtscp instructions so that an app can obtain "safe" pvclock-like TSC information across save/restore and live migration. (Will be completed in a follow-on patch.) For HVM domains, the default mode and "always emulate" mode do the same as tsc_native==0; the other two modes do the same as tsc_native==1. (HVM domains since 3.4 have implemented a tsc_mode=default-like functionality, but also can preserve native TSC across save/restore and live-migration IFF the initial and target machines have a common TSC cycle rate.) ** All newer AMD machines, and Nehalem and future Intel machines have "Invariant TSC"; many newer Intel machines have "Constant TSC" and do not support deep-C sleep states; these and all single-processor machines are "safe". Signed-off-by: Dan Magenheimer <dan.magenheimer@oracle.com>
* x86: document tsc_native configuration option in xmexample.hvm.Keir Fraser2009-10-161-0/+6
| | | | | | Set the default value to 1 Signed-off-by: Xiantao Zhang <xiantao.zhang@intel.com>
* xend: passthrough: add an option pci-passthrough-strict-checkKeir Fraser2009-09-071-0/+7
| | | | | | | | | | | | | | | | | Currently when assigning device to HVM guest, we use the strict check for HVM guest by default.(For PV guest we use loose check automatically if necessary.) When we assign device to HVM guest, if we meet with the co-assignment issues or the ACS issue (see changeset 20081: 4a517458406f), we could try changing the option to 'no' -- however, we have to realize this may incur security issue and we can't make sure the device assignment could really work properly even after we do this. The option is located in /etc/xen/xend-config.sxp: (pci-passthrough-strict-check yes) Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
* Fix a couple of comment typos.Keir Fraser2009-07-151-1/+1
| | | | Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
* xend: get rid of hardcoded path in xend config fileKeir Fraser2009-06-301-7/+7
| | | | | | | | * Change default settings to relative pathes. * Make xend to prepend install directory if entries have no absolute * path Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
* tools: remove hard coded paths in example config filesKeir Fraser2009-06-245-16/+11
| | | | Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
* stubdom: update config example to reflect that the serial option canKeir Fraser2009-06-171-3/+5
| | | | | | now be used. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
* xend: Make hotplug script timeouts configurableKeir Fraser2009-05-191-0/+6
| | | | | | | | | | | | | | In some configurations, when dom0 is busy with I/O, it may take several minutes to complete all hotplug scripts required when a new domain is being created. As device create timeout is set to 100 seconds, users get "hotplug scripts not working" error instead of a new domain. This patch makes both DEVICE_CREATE_TIMEOUT and DEVICE_DESTROY_TIMEOUT configurable in xend-config.sxp to allow users to easily adapt hotplug timeouts to their environment. Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
* tools: clean up handling of xen config and scripts directories.Keir Fraser2009-05-191-1/+0
| | | | | | | For now hardcode /etc w/o a prefix as there are hardcoded config paths in the code which would break otherwise. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
* stubdom docs: Update to reflect the new way of configuring stubdom domains.Keir Fraser2009-05-113-26/+5
| | | | Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
* xmexample: fix cpuid exampleKeir Fraser2009-03-201-2/+2
| | | | Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
* Disable xen platform PCI device when xen_platform_pci=0 is specifiedKeir Fraser2009-03-181-0/+4
| | | | | | | | | | - Change guest firmware to use new fixed byte port 0x10. - Add "xen_platform_pci" option into guest config file and APIs. xen_platform_pci=0: Disable xen platform device. xen_platform_pci=1: Enable xen platform device. (default) - Add "disable_pf" entry into xenstore. Signed-off-by: Yuji Shimada <shimada-yxb@necst.nec.co.jp>
* xend: Accept udev events and update physical resource informationKeir Fraser2009-03-171-0/+1
| | | | | | | | | When a udev event is received, udevevent.py parses the udev data and tells XendNode.py to update the physical resource information. This patch also add a boolean parameter 'xend-udev-event-server', to let users indicate whether we should enable this function or not. Signed-off-by: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>
* [IA64] fix issue of can not find the qemu-dm in ia64Keir Fraser2009-03-091-2/+0
| | | | | | | | | IA64 uses the /usr/lib/ for xen. We do not=20 need to check the arch_libdir in ia64. It will return the wrong value to arch_libdir. And guest can not boot. Signed-off-by: Yang Zhang <yang.zhang@intel.com>
* xend: allow VM configuration with both sdl=1 and vnc=1Keir Fraser2009-03-065-25/+25
| | | | | | | | | | | | | | | | | In the stubdom case you can now specify sdl=1 and vnc=1 (again, both can be selected at the same time) in the vfb configuration. So instead of: vfb = [ 'type=vnc' ] now you have: vfb = [ 'vnc=1,sdl=1' ] the former configuration option is deprecated but still supported for backward compatibility. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-19 06:40:22 +0000