Xen project Mailing List

[Xen-changelog] [xen master] tools: remove xend and associated python modules

Date: Wed, 09 Apr 2014 10:44:53 +0000

Delivery-date: Wed, 09 Apr 2014 10:45:04 +0000

List-id: "Change log for Mercurial $receive only$" <xen-changelog.lists.xen.org>

commit 9e8672f1c36d7237508c537c0a1db6c473c2be37 Author: Ian Campbell <ian.campbell@xxxxxxxxxx> AuthorDate: Thu Sep 12 10:21:25 2013 +0100 Commit: Ian Campbell <ian.campbell@xxxxxxxxxx> CommitDate: Thu Apr 3 17:39:09 2014 +0100 tools: remove xend and associated python modules I've retained xen.lowlevel.{xc,xs} since they seem more widely useful. I also kept xen.lowlevel.xl even though it is disabled by default and IMHO useless in its current form. I've tried to clean up the various associated bits like example configs, init scripts, udev rules etc but no doubt I have missed something, those can easily be cleaned up later. I've also removed xm-test since although it could in theory be reworked to test xl it hasn't been touched for years. If someone wants to resurrect it then they could do so via the git history. This has been built but not runtime tested. Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> --- v2: Clean out some .*ignore cruft Remove some xm/xend docs. --- .gitignore | 14 - .hgignore | 12 - MAINTAINERS | 2 - config/Tools.mk.in | 1 - docs/man/xend-config.sxp.pod.5 | 158 - docs/man/xl.pod.1 | 1 - docs/man/xm.pod.1 | 1004 ----- docs/man/xmdomain.cfg.pod.5 | 358 -- tools/configure | 48 - tools/configure.ac | 13 - tools/examples/Makefile | 12 - tools/examples/xend-config.sxp | 304 -- tools/examples/xend-pci-permissive.sxp | 27 - tools/examples/xend-pci-quirks.sxp | 96 - tools/examples/xm-config.xml | 45 - tools/examples/xmexample.hvm | 373 -- tools/examples/xmexample.hvm-stubdom | 317 -- tools/examples/xmexample.nbd | 26 - tools/examples/xmexample.pv-grub | 172 - tools/examples/xmexample1 | 197 - tools/examples/xmexample2 | 232 - tools/examples/xmexample3 | 218 - tools/hotplug/Linux/Makefile | 5 - tools/hotplug/Linux/init.d/xend | 82 - tools/hotplug/Linux/xend.rules | 4 - tools/hotplug/NetBSD/Makefile | 3 +- tools/hotplug/NetBSD/rc.d/xend | 71 - tools/libxl/xl.c | 16 - tools/python/Makefile | 18 +- tools/python/logging/logging-0.4.9.2/PKG-INFO | 25 - tools/python/logging/logging-0.4.9.2/README.txt | 311 -- tools/python/logging/logging-0.4.9.2/default.css | 32 - .../python/logging/logging-0.4.9.2/liblogging.tex | 1281 ------ .../logging/logging-0.4.9.2/logging/__init__.py | 1225 ------ .../logging/logging-0.4.9.2/logging/config.py | 301 -- .../logging/logging-0.4.9.2/logging/handlers.py | 787 ---- .../logging/logging-0.4.9.2/python_logging.html | 1183 ------ tools/python/logging/logging-0.4.9.2/setup.py | 29 - tools/python/logging/logging-0.4.9.2/test/app.py | 5 - .../logging/logging-0.4.9.2/test/critical.ini | 60 - .../python/logging/logging-0.4.9.2/test/debug.ini | 60 - .../python/logging/logging-0.4.9.2/test/error.ini | 60 - .../python/logging/logging-0.4.9.2/test/events.xml | 31 - .../logging/logging-0.4.9.2/test/log_test.py | 158 - .../logging/logging-0.4.9.2/test/log_test0.py | 118 - .../logging/logging-0.4.9.2/test/log_test1.py | 85 - .../logging/logging-0.4.9.2/test/log_test10.py | 87 - .../logging/logging-0.4.9.2/test/log_test11.py | 72 - .../logging/logging-0.4.9.2/test/log_test12.py | 47 - .../logging/logging-0.4.9.2/test/log_test13.py | 106 - .../logging/logging-0.4.9.2/test/log_test14.py | 108 - .../logging/logging-0.4.9.2/test/log_test15.py | 70 - .../logging/logging-0.4.9.2/test/log_test16.py | 73 - .../logging/logging-0.4.9.2/test/log_test17.py | 111 - .../logging/logging-0.4.9.2/test/log_test18.py | 102 - .../logging/logging-0.4.9.2/test/log_test19.py | 57 - .../logging/logging-0.4.9.2/test/log_test2.py | 119 - .../logging/logging-0.4.9.2/test/log_test20.py | 84 - .../logging/logging-0.4.9.2/test/log_test21.py | 141 - .../logging/logging-0.4.9.2/test/log_test22.py | 50 - .../logging/logging-0.4.9.2/test/log_test3.ini | 95 - .../logging/logging-0.4.9.2/test/log_test3.py | 70 - .../logging/logging-0.4.9.2/test/log_test4.py | 168 - .../logging/logging-0.4.9.2/test/log_test5.py | 44 - .../logging/logging-0.4.9.2/test/log_test6.py | 47 - .../logging/logging-0.4.9.2/test/log_test7.py | 48 - .../logging/logging-0.4.9.2/test/log_test8.py | 69 - .../logging/logging-0.4.9.2/test/log_test9.py | 71 - .../logging/logging-0.4.9.2/test/logconf.ini | 180 - .../python/logging/logging-0.4.9.2/test/logconf.py | 1738 -------- .../logging/logging-0.4.9.2/test/logging.dtd | 19 - .../logging/logging-0.4.9.2/test/logging.xml | 5 - .../logging/logging-0.4.9.2/test/logrecv.ini | 36 - .../python/logging/logging-0.4.9.2/test/logrecv.py | 443 -- tools/python/logging/logging-0.4.9.2/test/myapp.py | 13 - .../logging/logging-0.4.9.2/test/mymodule.py | 8 - .../python/logging/logging-0.4.9.2/test/stderr.exp | 566 --- .../python/logging/logging-0.4.9.2/test/stdout.exp | 24 - tools/python/logging/logging-0.4.9.2/test/warn.ini | 60 - tools/python/logging/setup.py | 11 - tools/python/ptsname/ptsname.c | 44 - tools/python/setup.py | 95 +- tools/python/xen/lowlevel/checkpoint/checkpoint.c | 371 -- tools/python/xen/lowlevel/checkpoint/checkpoint.h | 61 - .../python/xen/lowlevel/checkpoint/libcheckpoint.c | 850 ---- tools/python/xen/lowlevel/flask/flask.c | 292 -- tools/python/xen/lowlevel/netlink/libnetlink.c | 585 --- tools/python/xen/lowlevel/netlink/libnetlink.h | 58 - tools/python/xen/lowlevel/netlink/netlink.c | 215 - tools/python/xen/lowlevel/process/process.c | 164 - tools/python/xen/lowlevel/scf/scf.c | 156 - tools/python/xen/remus/blkdev.py | 31 - tools/python/xen/remus/device.py | 397 -- tools/python/xen/remus/image.py | 227 - tools/python/xen/remus/netlink.py | 318 -- tools/python/xen/remus/profile.py | 56 - tools/python/xen/remus/qdisc.py | 189 - tools/python/xen/remus/save.py | 186 - tools/python/xen/remus/tapdisk.py | 4 - tools/python/xen/remus/util.py | 82 - tools/python/xen/remus/vbd.py | 9 - tools/python/xen/remus/vdi.py | 121 - tools/python/xen/remus/vif.py | 18 - tools/python/xen/remus/vm.py | 168 - tools/python/xen/util/Brctl.py | 186 - tools/python/xen/util/SSHTransport.py | 102 - tools/python/xen/util/__init__.py | 1 - tools/python/xen/util/acmpolicy.py | 1622 ------- tools/python/xen/util/asserts.py | 27 - tools/python/xen/util/auxbin.py | 47 - tools/python/xen/util/blkif.py | 107 - tools/python/xen/util/bootloader.py | 626 --- tools/python/xen/util/bugtool.py | 234 - tools/python/xen/util/diagnose.py | 185 - tools/python/xen/util/dictio.py | 50 - tools/python/xen/util/fileuri.py | 156 - tools/python/xen/util/ip.py | 121 - tools/python/xen/util/mac.py | 11 - tools/python/xen/util/mkdir.py | 44 - tools/python/xen/util/oshelp.py | 33 - tools/python/xen/util/pci.py | 1416 ------- tools/python/xen/util/rwlock.py | 137 - tools/python/xen/util/sxputils.py | 64 - tools/python/xen/util/utils.py | 78 - tools/python/xen/util/vscsi_util.py | 307 -- tools/python/xen/util/vusb_util.py | 338 -- tools/python/xen/util/xmlrpcclient.py | 129 - tools/python/xen/util/xmlrpclib2.py | 220 - tools/python/xen/util/xpopen.py | 182 - tools/python/xen/util/xsconstants.py | 115 - tools/python/xen/util/xsm/__init__.py | 2 - tools/python/xen/util/xsm/acm/__init__.py | 1 - tools/python/xen/util/xsm/acm/acm.py | 1627 ------- tools/python/xen/util/xsm/dummy/__init__.py | 1 - tools/python/xen/util/xsm/dummy/dummy.py | 136 - tools/python/xen/util/xsm/flask/__init__.py | 1 - tools/python/xen/util/xsm/flask/flask.py | 65 - tools/python/xen/util/xsm/xsm.py | 20 - tools/python/xen/util/xsm/xsm_core.py | 7 - tools/python/xen/util/xspolicy.py | 66 - tools/python/xen/web/SrvBase.py | 98 - tools/python/xen/web/SrvDir.py | 126 - tools/python/xen/web/__init__.py | 17 - tools/python/xen/web/connection.py | 333 -- tools/python/xen/web/http.py | 518 --- tools/python/xen/web/httpserver.py | 367 -- tools/python/xen/web/protocol.py | 40 - tools/python/xen/web/resource.py | 108 - tools/python/xen/web/static.py | 61 - tools/python/xen/web/tcp.py | 212 - tools/python/xen/web/unix.py | 69 - tools/python/xen/xend/Args.py | 166 - tools/python/xen/xend/MemoryPool.py | 118 - tools/python/xen/xend/PrettyPrint.py | 323 -- tools/python/xen/xend/Vifctl.py | 35 - tools/python/xen/xend/XendAPI.py | 2812 ------------- tools/python/xen/xend/XendAPIConstants.py | 82 - tools/python/xen/xend/XendAPIStore.py | 83 - tools/python/xen/xend/XendAPIVersion.py | 22 - tools/python/xen/xend/XendAuthSessions.py | 131 - tools/python/xen/xend/XendBase.py | 126 - tools/python/xen/xend/XendBootloader.py | 230 - tools/python/xen/xend/XendCPUPool.py | 910 ---- tools/python/xen/xend/XendCheckpoint.py | 425 -- tools/python/xen/xend/XendClient.py | 40 - tools/python/xen/xend/XendConfig.py | 2265 ---------- tools/python/xen/xend/XendConstants.py | 164 - tools/python/xen/xend/XendDPCI.py | 165 - tools/python/xen/xend/XendDSCSI.py | 299 -- tools/python/xen/xend/XendDevices.py | 85 - tools/python/xen/xend/XendDmesg.py | 41 - tools/python/xen/xend/XendDomain.py | 1958 --------- tools/python/xen/xend/XendDomainInfo.py | 4429 -------------------- tools/python/xen/xend/XendError.py | 252 -- tools/python/xen/xend/XendLocalStorageRepo.py | 93 - tools/python/xen/xend/XendLogging.py | 149 - tools/python/xen/xend/XendMonitor.py | 340 -- tools/python/xen/xend/XendNetwork.py | 238 -- tools/python/xen/xend/XendNode.py | 1173 ------ tools/python/xen/xend/XendOptions.py | 567 --- tools/python/xen/xend/XendPBD.py | 99 - tools/python/xen/xend/XendPIF.py | 390 -- tools/python/xen/xend/XendPIFMetrics.py | 59 - tools/python/xen/xend/XendPPCI.py | 160 - tools/python/xen/xend/XendPSCSI.py | 211 - tools/python/xen/xend/XendProtocol.py | 225 - tools/python/xen/xend/XendQCoWStorageRepo.py | 340 -- tools/python/xen/xend/XendSXPDev.py | 13 - tools/python/xen/xend/XendStateStore.py | 234 - tools/python/xen/xend/XendStorageRepository.py | 118 - tools/python/xen/xend/XendTask.py | 224 - tools/python/xen/xend/XendTaskManager.py | 110 - tools/python/xen/xend/XendVDI.py | 214 - tools/python/xen/xend/XendVMMetrics.py | 146 - tools/python/xen/xend/XendVnet.py | 181 - tools/python/xen/xend/XendXSPolicy.py | 305 -- tools/python/xen/xend/XendXSPolicyAdmin.py | 386 -- tools/python/xen/xend/__init__.py | 1 - tools/python/xen/xend/arch.py | 31 - tools/python/xen/xend/balloon.py | 244 -- tools/python/xen/xend/encode.py | 180 - tools/python/xen/xend/image.py | 1047 ----- tools/python/xen/xend/osdep.py | 268 -- tools/python/xen/xend/server/BlktapController.py | 313 -- tools/python/xen/xend/server/ConsoleController.py | 38 - tools/python/xen/xend/server/DevConstants.py | 49 - tools/python/xen/xend/server/DevController.py | 677 --- tools/python/xen/xend/server/SSLXMLRPCServer.py | 103 - tools/python/xen/xend/server/SrvDaemon.py | 420 -- tools/python/xen/xend/server/SrvDmesg.py | 52 - tools/python/xen/xend/server/SrvDomain.py | 329 -- tools/python/xen/xend/server/SrvDomainDir.py | 222 - tools/python/xen/xend/server/SrvNode.py | 64 - tools/python/xen/xend/server/SrvRoot.py | 43 - tools/python/xen/xend/server/SrvServer.py | 261 -- tools/python/xen/xend/server/SrvVnetDir.py | 128 - tools/python/xen/xend/server/SrvXendLog.py | 37 - tools/python/xen/xend/server/XMLRPCServer.py | 273 -- tools/python/xen/xend/server/__init__.py | 1 - tools/python/xen/xend/server/blkif.py | 221 - tools/python/xen/xend/server/iopif.py | 102 - tools/python/xen/xend/server/irqif.py | 95 - tools/python/xen/xend/server/netif.py | 218 - tools/python/xen/xend/server/netif2.py | 163 - tools/python/xen/xend/server/params.py | 46 - tools/python/xen/xend/server/pciif.py | 596 --- tools/python/xen/xend/server/pciquirk.py | 149 - tools/python/xen/xend/server/relocate.py | 173 - tools/python/xen/xend/server/tests/__init__.py | 1 - .../xen/xend/server/tests/test_controllers.py | 81 - tools/python/xen/xend/server/udevevent.py | 92 - tools/python/xen/xend/server/vfbif.py | 91 - tools/python/xen/xend/server/vscsiif.py | 246 -- tools/python/xen/xend/server/vusbif.py | 126 - tools/python/xen/xend/sxp.py | 765 ---- tools/python/xen/xend/tests/__init__.py | 1 - tools/python/xen/xend/tests/test_XendConfig.py | 42 - tools/python/xen/xend/tests/test_sxp.py | 39 - tools/python/xen/xend/tests/test_uuid.py | 30 - tools/python/xen/xend/tests/xend-config.sxp | 131 - tools/python/xen/xend/uuid.py | 69 - tools/python/xen/xend/xend | 110 - tools/python/xen/xend/xenstore/__init__.py | 16 - tools/python/xen/xend/xenstore/tests/__init__.py | 2 - tools/python/xen/xend/xenstore/tests/stress_xs.py | 121 - tools/python/xen/xend/xenstore/xstransact.py | 368 -- tools/python/xen/xend/xenstore/xsutil.py | 32 - tools/python/xen/xend/xenstore/xswatch.py | 80 - tools/python/xen/xm/XenAPI.py | 206 - tools/python/xen/xm/addlabel.py | 274 -- tools/python/xen/xm/console.py | 88 - tools/python/xen/xm/cpupool-create.py | 51 - tools/python/xen/xm/cpupool-new.py | 50 - tools/python/xen/xm/cpupool.py | 236 -- tools/python/xen/xm/create.dtd | 154 - tools/python/xen/xm/create.py | 1529 ------- tools/python/xen/xm/dry-run.py | 161 - tools/python/xen/xm/dumppolicy.py | 69 - tools/python/xen/xm/getenforce.py | 66 - tools/python/xen/xm/getlabel.py | 157 - tools/python/xen/xm/getpolicy.py | 135 - tools/python/xen/xm/help.py | 100 - tools/python/xen/xm/labels.py | 89 - tools/python/xen/xm/main.py | 4030 ------------------ tools/python/xen/xm/migrate.py | 87 - tools/python/xen/xm/new.py | 79 - tools/python/xen/xm/opts.py | 627 --- tools/python/xen/xm/resetpolicy.py | 106 - tools/python/xen/xm/resources.py | 65 - tools/python/xen/xm/rmlabel.py | 216 - tools/python/xen/xm/setenforce.py | 74 - tools/python/xen/xm/setpolicy.py | 181 - tools/python/xen/xm/shutdown.py | 164 - tools/python/xen/xm/tests/__init__.py | 2 - tools/python/xen/xm/tests/test_create.py | 206 - tools/python/xen/xm/xenapi_create.py | 1129 ----- tools/python/xen/xm/xm | 20 - tools/xcutils/Makefile | 10 +- tools/xcutils/xc_restore.c | 73 - tools/xcutils/xc_save.c | 227 - tools/xm-test/COPYING | 340 -- tools/xm-test/ChangeLog | 11 - tools/xm-test/Makefile.am | 18 - tools/xm-test/README | 310 -- tools/xm-test/TODO | 3 - tools/xm-test/Writing_Tests_HOWTO | 136 - tools/xm-test/autogen | 9 - tools/xm-test/configure.ac | 155 - tools/xm-test/grouptest/cpupool | 1 - tools/xm-test/grouptest/create | 1 - tools/xm-test/grouptest/default | 30 - tools/xm-test/grouptest/medium | 24 - tools/xm-test/grouptest/quick | 4 - tools/xm-test/grouptest/xapi | 1 - tools/xm-test/lib/XmTestLib/Console.py | 302 -- tools/xm-test/lib/XmTestLib/DomainTracking.py | 61 - tools/xm-test/lib/XmTestLib/NetConfig.py | 268 -- tools/xm-test/lib/XmTestLib/Test.py | 203 - tools/xm-test/lib/XmTestLib/XenAPIDomain.py | 183 - tools/xm-test/lib/XmTestLib/XenDevice.py | 275 -- tools/xm-test/lib/XmTestLib/XenDomain.py | 385 -- tools/xm-test/lib/XmTestLib/XenMemory.py | 68 - tools/xm-test/lib/XmTestLib/Xm.py | 245 -- tools/xm-test/lib/XmTestLib/__init__.py | 27 - tools/xm-test/lib/XmTestLib/arch.py | 118 - tools/xm-test/lib/XmTestLib/block_utils.py | 53 - tools/xm-test/lib/XmTestLib/config.py.in | 7 - tools/xm-test/lib/XmTestLib/network_utils.py | 60 - tools/xm-test/lib/XmTestLib/xapi.py | 54 - tools/xm-test/lib/XmTestReport/OSReport.py | 248 -- tools/xm-test/lib/XmTestReport/ProgReport.py | 119 - tools/xm-test/lib/XmTestReport/Report.py | 156 - tools/xm-test/lib/XmTestReport/ResultReport.py | 157 - tools/xm-test/lib/XmTestReport/arch.py | 42 - tools/xm-test/lib/XmTestReport/utils.py | 31 - tools/xm-test/lib/XmTestReport/xmtest.py.in | 15 - tools/xm-test/mergereport | 25 - tools/xm-test/mkreport | 71 - tools/xm-test/ramdisk/Makefile.am | 126 - .../ramdisk/README-XenSource-initrd-0.7-img | 42 - .../ramdisk/README-XenSource-initrd-0.8-img | 42 - .../ramdisk/README-XenSource-initrd-1.0-img | 46 - .../ramdisk/README-XenSource-initrd-1.1-img | 45 - tools/xm-test/ramdisk/bin/create_disk_image | 384 -- tools/xm-test/ramdisk/configs/buildroot-i386 | 346 -- tools/xm-test/ramdisk/configs/busybox | 465 -- tools/xm-test/ramdisk/configs/uClibc | 172 - tools/xm-test/ramdisk/make-release.sh | 44 - .../patches/buildroot/add_xvd_devices.patch | 13 - .../xm-test/ramdisk/patches/buildroot/hping.patch | 67 - tools/xm-test/ramdisk/skel/.profile | 3 - tools/xm-test/ramdisk/skel/etc/init.d/rcS | 19 - tools/xm-test/ramdisk/skel/etc/inittab | 5 - tools/xm-test/ramdisk/skel/root/.profile | 3 - tools/xm-test/runtest.sh | 337 -- tools/xm-test/tests/Makefile.am | 43 - tools/xm-test/tests/Makefile.am.template | 21 - tools/xm-test/tests/_sanity/01_domu_proc.py | 32 - tools/xm-test/tests/_sanity/Makefile.am | 21 - .../block-create/01_block_attach_device_pos.py | 49 - .../02_block_attach_file_device_pos.py | 49 - .../04_block_attach_device_repeatedly_pos.py | 46 - ...ock_attach_and_dettach_device_repeatedly_pos.py | 49 - .../block-create/06_block_attach_baddomain_neg.py | 18 - .../block-create/07_block_attach_baddevice_neg.py | 53 - .../08_block_attach_bad_filedevice_neg.py | 52 - ...ock_attach_and_dettach_device_check_data_pos.py | 66 - .../10_block_attach_dettach_multiple_devices.py | 100 - .../block-create/11_block_attach_shared_dom0.py | 38 - .../block-create/12_block_attach_shared_domU.py | 30 - tools/xm-test/tests/block-create/Makefile.am | 29 - .../block-destroy/01_block-destroy_btblock_pos.py | 44 - .../block-destroy/02_block-destroy_rtblock_pos.py | 41 - .../block-destroy/03_block-destroy_nonexist_neg.py | 17 - .../04_block-destroy_nonattached_neg.py | 33 - .../block-destroy/05_block-destroy_byname_pos.py | 43 - .../06_block-destroy_check_list_pos.py | 42 - tools/xm-test/tests/block-destroy/Makefile.am | 26 - .../block-integrity/01_block_device_read_verify.py | 62 - .../02_block_device_write_verify.py | 63 - tools/xm-test/tests/block-integrity/Makefile.am | 22 - .../xm-test/tests/block-list/01_block-list_pos.py | 42 - .../tests/block-list/02_block-list_attachbd_pos.py | 46 - .../block-list/03_block-list_anotherbd_pos.py | 54 - .../tests/block-list/04_block-list_nodb_pos.py | 28 - .../tests/block-list/05_block-list_nonexist_neg.py | 18 - .../block-list/06_block-list_checkremove_pos.py | 61 - tools/xm-test/tests/block-list/Makefile.am | 26 - .../xm-test/tests/console/01_console_badopt_neg.py | 21 - .../xm-test/tests/console/02_console_baddom_neg.py | 27 - tools/xm-test/tests/console/Makefile.am | 22 - .../xm-test/tests/cpupool/01_cpupool_basic_pos.py | 72 - .../xm-test/tests/cpupool/02_cpupool_manage_pos.py | 152 - tools/xm-test/tests/cpupool/03_cpupool_domain.py | 126 - tools/xm-test/tests/cpupool/04_cpupool_migrate.py | 84 - tools/xm-test/tests/cpupool/Makefile.am | 22 - tools/xm-test/tests/cpupool/pool1.cfg | 1 - tools/xm-test/tests/cpupool/pools.py | 78 - tools/xm-test/tests/create/01_create_basic_pos.py | 49 - tools/xm-test/tests/create/02_create_noparm_neg.py | 17 - .../xm-test/tests/create/03_create_badparm_neg.py | 19 - .../tests/create/04_create_conflictname_neg.py | 41 - tools/xm-test/tests/create/06_create_mem_neg.py | 53 - tools/xm-test/tests/create/07_create_mem64_pos.py | 49 - tools/xm-test/tests/create/08_create_mem128_pos.py | 49 - tools/xm-test/tests/create/09_create_mem256_pos.py | 49 - .../xm-test/tests/create/10_create_fastdestroy.py | 43 - .../tests/create/11_create_concurrent_pos.py | 78 - .../create/12_create_concurrent_stress_pos.py | 59 - .../xm-test/tests/create/13_create_multinic_pos.py | 27 - .../tests/create/14_create_blockroot_pos.py | 44 - .../xm-test/tests/create/15_create_smallmem_pos.py | 27 - .../xm-test/tests/create/16_create_smallmem_neg.py | 30 - tools/xm-test/tests/create/Makefile.am | 33 - .../xm-test/tests/destroy/01_destroy_basic_pos.py | 40 - .../xm-test/tests/destroy/02_destroy_noparm_neg.py | 16 - .../tests/destroy/03_destroy_nonexist_neg.py | 16 - .../tests/destroy/04_destroy_badparm_neg.py | 16 - tools/xm-test/tests/destroy/05_destroy_byid_pos.py | 33 - tools/xm-test/tests/destroy/06_destroy_dom0_neg.py | 14 - .../xm-test/tests/destroy/07_destroy_stale_pos.py | 133 - tools/xm-test/tests/destroy/Makefile.am | 27 - tools/xm-test/tests/dmesg/01_dmesg_basic_pos.py | 15 - tools/xm-test/tests/dmesg/02_dmesg_basic_neg.py | 17 - tools/xm-test/tests/dmesg/Makefile.am | 21 - tools/xm-test/tests/domid/01_domid_basic_pos.py | 16 - tools/xm-test/tests/domid/02_domid_basic_neg.py | 15 - tools/xm-test/tests/domid/Makefile.am | 21 - .../xm-test/tests/domname/01_domname_basic_pos.py | 17 - .../xm-test/tests/domname/02_domname_basic_neg.py | 15 - tools/xm-test/tests/domname/Makefile.am | 21 - .../01_enforce_dom0_cpus_basic_pos.py | 126 - tools/xm-test/tests/enforce_dom0_cpus/Makefile.am | 21 - tools/xm-test/tests/help/01_help_basic_pos.py | 14 - tools/xm-test/tests/help/02_help_basic_neg.py | 14 - tools/xm-test/tests/help/03_help_badparm_neg.py | 14 - tools/xm-test/tests/help/04_help_long_pos.py | 16 - tools/xm-test/tests/help/05_help_nonroot_pos.py | 17 - tools/xm-test/tests/help/06_help_allcmds.py | 44 - tools/xm-test/tests/help/Makefile.am | 26 - tools/xm-test/tests/info/01_info_basic_pos.py | 11 - .../xm-test/tests/info/02_info_compiledata_pos.py | 42 - tools/xm-test/tests/info/Makefile.am | 22 - tools/xm-test/tests/list/01_list_basic_pos.py | 14 - tools/xm-test/tests/list/02_list_badparm_neg.py | 16 - tools/xm-test/tests/list/03_list_nonexist_neg.py | 17 - tools/xm-test/tests/list/04_list_goodparm_pos.py | 28 - tools/xm-test/tests/list/05_list_long_pos.py | 22 - tools/xm-test/tests/list/06_list_nonroot.py | 15 - tools/xm-test/tests/list/Makefile.am | 27 - .../xm-test/tests/memmax/01_memmax_badparm_neg.py | 29 - tools/xm-test/tests/memmax/Makefile.am | 21 - tools/xm-test/tests/memset/01_memset_basic_pos.py | 82 - .../xm-test/tests/memset/02_memset_badparm_neg.py | 56 - tools/xm-test/tests/memset/03_memset_random_pos.py | 64 - .../xm-test/tests/memset/04_memset_smallmem_pos.py | 55 - tools/xm-test/tests/memset/Makefile.am | 24 - .../tests/migrate/01_migrate_localhost_pos.py | 86 - tools/xm-test/tests/migrate/Makefile.am | 20 - .../tests/network-attach/01_network_attach_pos.py | 43 - .../network-attach/02_network_attach_detach_pos.py | 49 - .../03_network_attach_detach_multiple_pos.py | 51 - .../04_network_attach_baddomain_neg.py | 15 - tools/xm-test/tests/network-attach/Makefile.am | 24 - .../tests/network/02_network_local_ping_pos.py | 71 - .../tests/network/03_network_local_tcp_pos.py | 75 - .../tests/network/04_network_local_udp_pos.py | 76 - .../tests/network/05_network_dom0_ping_pos.py | 54 - .../tests/network/06_network_dom0_tcp_pos.py | 57 - .../tests/network/07_network_dom0_udp_pos.py | 56 - .../tests/network/11_network_domU_ping_pos.py | 62 - .../tests/network/12_network_domU_tcp_pos.py | 64 - .../tests/network/13_network_domU_udp_pos.py | 76 - tools/xm-test/tests/network/Makefile.am | 34 - tools/xm-test/tests/pause/01_pause_basic_pos.py | 63 - tools/xm-test/tests/pause/02_pause_badopt_neg.py | 32 - tools/xm-test/tests/pause/03_pause_badname_neg.py | 18 - tools/xm-test/tests/pause/04_pause_badid_neg.py | 18 - tools/xm-test/tests/pause/Makefile.am | 22 - tools/xm-test/tests/reboot/01_reboot_basic_pos.py | 52 - tools/xm-test/tests/reboot/02_reboot_badopt_neg.py | 32 - .../xm-test/tests/reboot/03_reboot_badname_neg.py | 18 - tools/xm-test/tests/reboot/Makefile.am | 23 - .../xm-test/tests/restore/01_restore_basic_pos.py | 82 - .../tests/restore/02_restore_badparm_neg.py | 28 - .../tests/restore/03_restore_badfilename_neg.py | 28 - .../tests/restore/04_restore_withdevices_pos.py | 130 - tools/xm-test/tests/restore/Makefile.am | 24 - tools/xm-test/tests/save/01_save_basic_pos.py | 37 - tools/xm-test/tests/save/02_save_badparm_neg.py | 28 - tools/xm-test/tests/save/03_save_bogusfile_neg.py | 39 - tools/xm-test/tests/save/Makefile.am | 24 - .../sched-credit/01_sched_credit_weight_cap_pos.py | 72 - tools/xm-test/tests/sched-credit/Makefile.am | 20 - .../xm-test/tests/sedf/01_sedf_period_slice_pos.py | 62 - .../xm-test/tests/sedf/02_sedf_period_lower_neg.py | 44 - .../xm-test/tests/sedf/03_sedf_slice_lower_neg.py | 40 - .../xm-test/tests/sedf/04_sedf_slice_upper_neg.py | 48 - tools/xm-test/tests/sedf/05_sedf_extratime_pos.py | 63 - .../tests/sedf/06_sedf_extratime_disable_neg.py | 71 - tools/xm-test/tests/sedf/Makefile.am | 25 - .../tests/shutdown/01_shutdown_basic_pos.py | 54 - .../tests/shutdown/02_shutdown_badparm_neg.py | 39 - .../tests/shutdown/03_shutdown_nonexist_neg.py | 22 - tools/xm-test/tests/shutdown/Makefile.am | 21 - tools/xm-test/tests/sysrq/01_sysrq_basic_neg.py | 20 - tools/xm-test/tests/sysrq/02_sysrq_sync_pos.py | 52 - .../xm-test/tests/sysrq/03_sysrq_withreboot_pos.py | 40 - tools/xm-test/tests/sysrq/Makefile.am | 23 - .../xm-test/tests/unpause/01_unpause_basic_pos.py | 76 - tools/xm-test/tests/unpause/Makefile.am | 20 - .../vcpu-disable/01_vcpu-disable_basic_pos.py | 82 - tools/xm-test/tests/vcpu-disable/Makefile.am | 21 - .../tests/vcpu-pin/01_vcpu-pin_basic_pos.py | 50 - tools/xm-test/tests/vcpu-pin/Makefile.am | 21 - tools/xm-test/tests/xapi/01_xapi-vm_basic.py | 61 - tools/xm-test/tests/xapi/02_xapi-vbd_basic.py | 122 - tools/xm-test/tests/xapi/03_xapi-network_pos.py | 123 - .../tests/xapi/04_xapi-data_uri_handling.py | 65 - tools/xm-test/tests/xapi/20_xapi-cpu_pool_basic.py | 157 - tools/xm-test/tests/xapi/Makefile.am | 23 - 501 files changed, 7 insertions(+), 83858 deletions(-) diff --git a/.gitignore b/.gitignore index eb210ca..af1d826 100644 --- a/.gitignore +++ b/.gitignore @@ -245,8 +245,6 @@ tools/vtpm/tpm_emulator/* tools/vtpm/vtpm/* tools/vtpm_manager/manager/vtpm_managerd tools/xcutils/lsevtchn -tools/xcutils/xc_restore -tools/xcutils/xc_save tools/xcutils/readnotes tools/xenfb/sdlfb tools/xenfb/vncfb @@ -279,18 +277,6 @@ tools/xentrace/xentrace_setsize tools/xentrace/tbctl tools/xentrace/xenctx tools/xentrace/xentrace -tools/xm-test/ramdisk/buildroot -tools/xm-test/aclocal.m4 -tools/xm-test/autom4te -tools/xm-test/install-sh -tools/xm-test/mkinstalldirs -tools/xm-test/missing -tools/xm-test/config(ure|.log|.status|.guess|.sub) -tools/xm-test/Makefile(.in)* -tools/xm-test/*/Makefile(.in)* -tools/xm-test/lib/XmTestLib/config.py -tools/xm-test/lib/XmTestReport/xmtest.py -tools/xm-test/tests/*.test tools/ocaml-xenstored* xen/.banner xen/System.map diff --git a/.hgignore b/.hgignore index 9c9421e..6d09b09 100644 --- a/.hgignore +++ b/.hgignore @@ -278,18 +278,6 @@ ^tools/xentrace/tbctl$ ^tools/xentrace/xenctx$ ^tools/xentrace/xentrace$ -^tools/xm-test/ramdisk/buildroot -^tools/xm-test/aclocal.m4$ -^tools/xm-test/autom4te -^tools/xm-test/install-sh$ -^tools/xm-test/mkinstalldirs$ -^tools/xm-test/missing$ -^tools/xm-test/config(ure|.log|.status|.guess|.sub)$ -^tools/xm-test/Makefile(.in)*$ -^tools/xm-test/.*/Makefile(.in)*$ -^tools/xm-test/lib/XmTestLib/config.py$ -^tools/xm-test/lib/XmTestReport/xmtest.py$ -^tools/xm-test/tests/.*\.test$ ^tools/firmware/ovmf-remote ^tools/firmware/ovmf$ ^tools/qemu-xen-traditional-dir-remote diff --git a/MAINTAINERS b/MAINTAINERS index 3f8810b..19dd49f 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -255,8 +255,6 @@ REMUS M: Shriram Rajagopalan <rshriram@xxxxxxxxx> S: Maintained F: tools/remus/ -F: tools/python/xen/remus/ -F: tools/python/xen/lowlevel/checkpoint/ F: tools/blktap2/drivers/block-remus.c F: tools/blktap2/drivers/hashtable* diff --git a/config/Tools.mk.in b/config/Tools.mk.in index d9d3239..85379b2 100644 --- a/config/Tools.mk.in +++ b/config/Tools.mk.in @@ -54,7 +54,6 @@ CONFIG_ROMBIOS := @rombios@ CONFIG_SEABIOS := @seabios@ CONFIG_QEMU_TRAD := @qemu_traditional@ CONFIG_QEMU_XEN := @qemu_xen@ -CONFIG_XEND := @xend@ CONFIG_BLKTAP1 := @blktap1@ #System options diff --git a/docs/man/xend-config.sxp.pod.5 b/docs/man/xend-config.sxp.pod.5 deleted file mode 100644 index 9504c71..0000000 --- a/docs/man/xend-config.sxp.pod.5 +++ /dev/null @@ -1,158 +0,0 @@ -=head1 NAME - -xend-config.sxp - Xen daemon configuration file - -=head1 SYNOPSIS - -/etc/xen/xend-config.sxp - -=head1 DESCRIPTION - -The xend(1) program requires xend-config.sxp to specify operating -parameters which determine the behavior of the daemon at runtime. - -The parameters are specified in S-expression format. See the example -configuration file in I</etc/xen/xend-config.sxp> for details. - -=head1 OPTIONS - -The following lists the daemon configuration parameters: - -=over 4 - -=item I<logfile> - -The location of the file to record runtime log messages. Defaults to -I</var/log/xen/xend.log>. - -=item I<loglevel> - -Filters out messages below the specified level. Possible values are -DEBUG, INFO, WARNING, ERROR, CRITICAL. Defaults to I<DEBUG>. - -=item I<xend-http-server> - -A boolean value that tells xend whether or not to start the http -stream socket management server. Defaults to I<no>. - -=item I<xend-unix-server> - -A boolean value that tells xend whether or not to start the unix -domain socket management server. This is required for the CLI tools -to operate. Defaults to I<yes>. - -=item I<xend-relocation-server> - -A boolean value that tells xend whether or not to start the relocation -server. This is required for cross-machine migrations. Defaults to -I<no>. - -=item I<xend-unix-path> - -The location of the unix domain socket the xend-unix-server will use -to communicate with the management tools. Defaults to -I</var/lib/xend/xend-socket>. - -=item I<xend-port> - -The port that will be used by the http management server. Defaults to -I<8000>. - -=item I<xend-relocation-port> - -The port that will be used by the relocation server. Defaults to -I<8002>. - -=item I<xend-address> - -The address to which the http management server will bind. Defaults -to I<''> which means "all interfaces". - -=item I<xend-relocation-address> - -The address to which the relocation server will bind. Defaults to -I<''> which means "all interfaces". - -=item I<console-limit> - -The kilobyte buffer limit that will be enforced by the console server. -This limit is set per-domain, and is needed to prevent a single domain -from overwhelming the console server with massive amounts of data. -Defaults to I<1024>. - -=item I<network-script> - -The name of the script in I</etc/xen/scripts> that will be run to -setup the networking environment. This can be any name, but in -general is either I<network-bridge> or I<network-route>. - -=item I<vif-script> - -The name of the script in I</etc/xen/scripts> that will be run to -setup a virtual interface when it is created or destroyed. This needs -to (in general) work in unison with the I<network-script>. - -=item I<dom0-min-mem> - -This specifies the minimum number of megabytes that will be reserved -for Domain0. If this value is positive, Domain0 will be automatically -ballooned down to this limit to make space for new domains. If this -is set to 0, Domain0 will not be automatically ballooned. - -=item I<dom0-cpus> - -This specifies the number of CPUs that Domain0 will be allowed to use. -If the value is 0, all available CPUs will be used by Domain0. - -=item I<enable-dump> - -A boolean value that tells xend whether or not core dumps of guest -domains should be saved when a crash occurs. Defaults to I<no>. - -=item I<external-migration-tool> - -The name of an application or script that can handle external device -migration, such as for example virtual TPM migration. An example -script is I</etc/xen/scripts/external-device-migrate>. - -=item I<device-create-timeout> - -Integer value that tells xend how long it should wait for a new device -to be created. Defaults to I<100>. - -=item I<device-destroy-timeout> - -Integer value that tells xend how long it should wait for a device to -be destroyed. Defaults to I<100>. - -=back - -=head1 EXAMPLES - -An example configuration with relocation enabled for the local network: - -=over 4 - - (xend-relocation-server yes) - (xend-relocation-address 192.0.2.192) - (network-script network-bridge) - (vif-script vif-bridge) - (dom0-min-mem 0) - (dom0-cpus 0) - -=back - -=head1 CAVEATS - -Note that relocation is currently unsecured and is very dangerous if -left enabled. No authentication is performed, and very little sanity -checking takes place. Enable at your own risk. - -=head1 SEE ALSO - -B<xend>(1) - -=head1 AUTHOR - -Dan Smith <danms@xxxxxxxxxx> - diff --git a/docs/man/xl.pod.1 b/docs/man/xl.pod.1 index f7ceaa8..dae0718 100644 --- a/docs/man/xl.pod.1 +++ b/docs/man/xl.pod.1 @@ -12,7 +12,6 @@ The B<xl> program is the new tool for managing Xen guest domains. The program can be used to create, pause, and shutdown domains. It can also be used to list current domains, enable or pin VCPUs, and attach or detach virtual block devices. -The old B<xm> tool is deprecated and should not be used. The basic structure of every B<xl> command is almost always: diff --git a/docs/man/xm.pod.1 b/docs/man/xm.pod.1 deleted file mode 100644 index 973de95..0000000 --- a/docs/man/xm.pod.1 +++ /dev/null @@ -1,1004 +0,0 @@ -=head1 NAME - -xm - Obsolete xen management user interface - -=head1 SYNOPSIS - -B<xm> I<subcommand> [I<args>] - -=head1 DESCRIPTION - -This program is now superseded by B<xl>, which should be largely -backwards-compatible with B<xm>. - -The B<xm> program is the main interface for managing Xen guest domains -when the obsolete Xend toolstack is in use. The program can be used to -create, pause, and shutdown domains. It can also be used to list -current domains, enable or pin VCPUs, and attach or detach virtual -block devices. - -The basic structure of every B<xm> command is almost always: - -=over 2 - -B<xm> I<subcommand> I<domain-id> [I<OPTIONS>] - -=back - -Where I<subcommand> is one of the subcommands listed below, I<domain-id> -is the numeric domain id, or the domain name (which will be internally -translated to domain id), and I<OPTIONS> are subcommand specific -options. There are a few exceptions to this rule in the cases where -the subcommand in question acts on all domains, the entire machine, -or directly on the Xen hypervisor. Those exceptions will be clear for -each of those subcommands. - -=head1 NOTES - -All B<xm> operations rely upon the Xen control daemon, aka B<xend>. -For any B<xm> commands to run, xend must also be running. For this -reason you should start xend as a service when your system first boots -using Xen. - -Most B<xm> commands require root privileges to run due to the -communications channels used to talk to the hypervisor. Running as -non root will return an error. - -Most B<xm> commands act synchronously, except maybe create, shutdown, -mem-set and vcpu-set. The fact that the B<xm> command returned doesn't -necessarily mean that the action is complete and you must poll through -xm list periodically to detect that the operation completed. - -=head1 DOMAIN SUBCOMMANDS - -The following subcommands manipulate domains directly. As stated -previously, most commands take I<domain-id> as the first parameter. - -=over 4 - -=item B<console> I<domain-id> - -Attach to domain I<domain-id>'s console. If you've set up your domains to -have a traditional log in console this will look much like a normal -text log in screen. - -This uses the back end xenconsole service which currently only -works for para-virtual domains. - -The attached console will perform much like a standard serial console, -so running curses based interfaces over the console B<is not -advised>. Vi tends to get very odd when using it over this interface. - -Use the key combination Ctrl+] to detach the domain console. - -=item B<create> I<configfile> [I<OPTIONS>] [I<vars>].. - -The create subcommand requires a config file and can optionally take a -series of I<vars> that add to or override variables defined -in the config file. See L<xmdomain.cfg> for full details of that file -format, and possible options used in either the configfile or for I<vars>. - -I<configfile> can either be an absolute path to a file, or a relative -path to a file located in /etc/xen. - -Create will return B<as soon> as the domain is started. This B<does -not> mean the guest OS in the domain has actually booted, or is -available for input. - -B<OPTIONS> - -=over 4 - -=item B<--help_config> - -Print the available configuration variables I<vars>. These variables may be -used on the command line or in the configuration file I<configfile>. - -=item B<-q>, B<--quiet> - -No console output. - -=item B<--path> - -Search path for configuration scripts. The value of PATH is a -colon-separated directory list. - -=item B<-f=FILE>, B<--defconfig=FILE> - -Use the given Python configuration script. The configuration -script is loaded after arguments have been processed. Each -command-line option sets a configuration variable named after -its long option name, and these variables are placed in the -environment of the script before it is loaded. Variables -for options that may be repeated have list values. Other -variables can be set using name=value on the command line. -After the script is loaded, option values that were not set -on the command line are replaced by the values set in the script. - -=item B<-F=FILE>, B<--config=FILE> - -Use the given SXP formatted configuration script. -SXP is the underlying configuration format used by Xen. -SXP configuration scripts can be hand-written or generated -from Python configuration scripts, using the -n -(dryrun) option to print the configuration. An SXP formatted -configuration file may also be generated for a given I<domain-id> by -redirecting the output from the the B<xm list --long I<domain-id>> -to a file. - -=item B<-n>, B<--dryrun> - -Dry run - prints the resulting configuration in SXP -but does not create the domain. - -=item B<-x>, B<--xmldryrun> - -XML dry run - prints the resulting configuration in -XML but does not create the domain. - -=item B<-s>, B<--skipdtd> - -Skip DTD checking - skips checks on XML before -creating. Experimental. Can decrease create time. - -=item B<-p>, B<--paused> - -Leave the domain paused after it is created. - -=item B<-c>, B<--console_autoconnect> - -Attach console to the domain as soon as it has started. This is -useful for determining issues with crashing domains. - -=back - -B<EXAMPLES> - -=over 4 - -=item I<with config file> - - xm create Fedora4 - -This creates a domain with the file /etc/xen/Fedora4, and returns as -soon as it is run. - -=item I<without config file> - - xm create /dev/null ramdisk=initrd.img \ - kernel=/boot/vmlinuz-2.6.12.6-xenU \ - name=ramdisk vif='' vcpus=1 \ - memory=64 root=/dev/ram0 - -This creates the domain without using a config file (more specifically -using /dev/null as an empty config file), kernel and ramdisk as -specified, setting the name of the domain to "ramdisk", also disabling -virtual networking. (This example comes from the xm-test test suite.) - -=back - -=item B<delete> - -Remove a domain from Xend domain management. The B<xm list> command -shows the domain names. - -=item B<destroy> I<domain-id> - -Immediately terminate the domain I<domain-id>. This doesn't give the -domain OS any chance to react, and is the equivalent of ripping the -power cord out on a physical machine. In most cases you will want to -use the B<shutdown> command instead. - -=item B<domid> I<domain-name> - -Converts a domain name to a domain id using xend's internal mapping. - -=item B<domname> I<domain-id> - -Converts a domain id to a domain name using xend's internal mapping. - -=item B<dump-core> [I<OPTIONS>] I<domain-id> [I<filename>] - -Dumps the virtual machine's memory for the specified domain to the -I<filename> specified. The dump file will be written to a distribution -specific directory for dump files. Such as: /var/lib/xen/dump or -/var/xen/dump Defaults to dumping the core without pausing the domain -if no I<OPTIONS> are specified. - -B<OPTIONS> - -=over 4 - -=item B<-L>, B<--live> - -Dump core without pausing the domain. - -=item B<-C>, B<--crash> - -Crash domain after dumping core. - -=back - -=item B<help> [B<--long>] - -Displays the short help message (i.e. common commands). - -The B<--long> option prints out the complete set of B<xm> subcommands, -grouped by function. - -=item B<list> [I<OPTIONS>] [I<domain-id> ...] - -Prints information about one or more domains. If no domains are -specified it prints out information about all domains. - - -B<OPTIONS> - -=over 4 - -=item B<-l>, B<--long> - -The output for B<xm list> is not the table view shown below, but -instead presents the data in SXP format. - -=item B<--label> - -Security labels are added to the output of xm list and the lines -are sorted by the labels (ignoring case). -See the ACCESS CONTROL SUBCOMMAND section of this man page for more -information about labels. - -=item B<--state=<state>> - -Output information for VMs in the specified state. - -=back - -B<EXAMPLE> - -An example format for the list is as follows: - - Name ID Mem(MiB) VCPUs State Time(s) - Domain-0 0 98 1 r----- 5068.6 - Fedora3 164 128 1 r----- 7.6 - Fedora4 165 128 1 ------ 0.6 - Mandrake2006 166 128 1 -b---- 3.6 - Mandrake10.2 167 128 1 ------ 2.5 - Suse9.2 168 100 1 ------ 1.8 - -Name is the name of the domain. ID the numeric domain id. Mem is the -desired amount of memory to allocate to the domain (although it may -not be the currently allocated amount). VCPUs is the number of -virtual CPUs allocated to the domain. State is the run state (see -below). Time is the total run time of the domain as accounted for by -Xen. - -B<STATES> - -The State field lists 6 states for a Xen domain, and which ones the -current domain is in. - -=over 4 - -=item B<r - running> - -The domain is currently running on a CPU. - -=item B<b - blocked> - -The domain is blocked, and not running or runnable. This can be caused -because the domain is waiting on IO (a traditional wait state) or has -gone to sleep because there was nothing else for it to do. - -=item B<p - paused> - -The domain has been paused, usually occurring through the administrator -running B<xm pause>. When in a paused state the domain will still -consume allocated resources like memory, but will not be eligible for -scheduling by the Xen hypervisor. - -=item B<s - shutdown> - -FIXME: Why would you ever see this state? - -=item B<c - crashed> - -The domain has crashed, which is always a violent ending. Usually -this state can only occur if the domain has been configured not to -restart on crash. See L<xmdomain.cfg> for more info. - -=item B<d - dying> - -The domain is in process of dying, but hasn't completely shutdown or -crashed. - -FIXME: Is this right? - -=back - -B<NOTES> - -=over 4 - -The Time column is deceptive. Virtual IO (network and block devices) -used by domains requires coordination by Domain0, which means that -Domain0 is actually charged for much of the time that a DomainU is -doing IO. Use of this time value to determine relative utilizations -by domains is thus very suspect, as a high IO workload may show as -less utilized than a high CPU workload. Consider yourself warned. - -=back - -=item B<mem-max> I<domain-id> I<mem> - -Specify the maximum amount of memory the domain is able to use. I<mem> -is specified in megabytes. - -The mem-max value may not correspond to the actual memory used in the -domain, as it may balloon down its memory to give more back to the OS. - -=item B<mem-set> I<domain-id> I<mem> - -Set the domain's used memory using the balloon driver. - -Because this operation requires cooperation from the domain operating -system, there is no guarantee that it will succeed. This command will -definitely not work unless the domain has the required paravirt -driver. - -B<Warning:> There is no good way to know in advance how small of a -mem-set will make a domain unstable and cause it to crash. Be very -careful when using this command on running domains. - -=item B<migrate> I<domain-id> I<host> [I<OPTIONS>] - -Migrate a domain to another host machine. Xend must be running on -other host machine, it must be running the same version of Xen, it -must have the migration TCP port open and accepting connections from -the source host, and there must be sufficient resources for the domain -to run (memory, disk, etc). - -Migration is pretty complicated, and has many security implications. -Please read the Xen User's Guide to ensure you understand the -ramifications and limitations on migration before attempting it in -production. - -B<OPTIONS> - -=over 4 - -=item B<-l>, B<--live> - -Use live migration. This will migrate the domain between hosts -without shutting down the domain. See the Xen User's Guide for more -information. - -=item B<-r>, B<--resource> I<Mbs> - -Set maximum Mbs allowed for migrating the domain. This ensures that -the network link is not saturated with migration traffic while -attempting to do other useful work. - -=back - -=item B<new> I<configfile> [I<OPTIONS>] [I<vars>]... - -Adds a domain to Xend domain management. - -The new subcommand requires a config file and can optionally -take a series of I<vars> that add to or override variables -defined in the config file. See xmdomain.cfg for full details of that -file format, and possible options used in either the configfile or for -I<vars>. - -I<configfile> can either be an absolute path to a file, or a relative -path to a file located in /etc/xen. - -The new subcommand will return without starting the domain. The -domain needs to be started using the B<xm start> command. - -B<OPTIONS> - -=over 4 - -=item B<--help_config> - -Print the available configuration variables I<vars>. These variables may be -used on the command line or in the configuration file I<configfile>. - -=item B<-q>, B<--quiet> - -No console output. - -=item B<--path> - -Search path for configuration scripts. The value of PATH is a -colon-separated directory list. - -=item B<-f=FILE>, B<--defconfig=FILE> - - -Use the given Python configuration script. The configuration -script is loaded after arguments have been processed. Each -command-line option sets a configuration variable named after -its long option name, and these variables are placed in the -environment of the script before it is loaded. Variables -for options that may be repeated have list values. Other -variables can be set using name=value on the command line. -After the script is loaded, option values that were not set -on the command line are replaced by the values set in the script. - -=item B<-F=FILE>, B<--config=FILE> - -Use the given SXP formatted configuration script. -SXP is the underlying configuration format used by Xen. -SXP configuration scripts can be hand-written or generated -from Python configuration scripts, using the -n -(dryrun) option to print the configuration. An SXP formatted -configuration file may also be generated for a given I<domain-id> by -redirecting the output from the the B<xm list --long I<domain-id>> -to a file. - -=item B<-n>, B<--dryrun> - -Dry run - prints the resulting configuration in SXP -but does not create the domain. - -=item B<-x>, B<--xmldryrun> - -XML dry run - prints the resulting configuration in -XML but does not create the domain. - -=item B<-s>, B<--skipdtd> - -Skip DTD checking - skips checks on XML before -creating. Experimental. Can decrease create time. - -=item B<-p>, B<--paused> - -Leave the domain paused after it is created. - -=item B<-c>, B<--console_autoconnect> - -Attach console to the domain as soon as it has started. This is -useful for determining issues with crashing domains. - -=back - -=item B<pause> I<domain-id> - -Pause a domain. When in a paused state the domain will still consume -allocated resources such as memory, but will not be eligible for -scheduling by the Xen hypervisor. - -=item B<reboot> [I<OPTIONS>] I<domain-id> - -Reboot a domain. This acts just as if the domain had the B<reboot> -command run from the console. The command returns as soon as it has -executed the reboot action, which may be significantly before the -domain actually reboots. - -The behavior of what happens to a domain when it reboots is set by the -B<on_reboot> parameter of the xmdomain.cfg file when the domain was -created. - -B<OPTIONS> - -=over 4 - -=item B<-a>, B<--all> - -Reboot all domains. - -=item B<-w>, B<--wait> - -Wait for reboot to complete before returning. This may take a while, -as all services in the domain will have to be shut down cleanly. - -=back - -=item B<restore> I<state-file> - -Build a domain from an B<xm save> state file. See B<save> for more info. - -=item B<resume> I<domain-name> [I<OPTIONS>] - -Moves a domain out of the suspended state and back into memory. - -B<OPTIONS> - -=over 4 - -=item B<-p>, <--paused> - -Moves a domain back into memory but leaves the domain in a paused state. -The B<xm unpause> subcommand may then be used to bring it out of the -paused state. - -=back - -=item B<save> I<domain-id> I<state-file> - -Saves a running domain to a state file so that it can be restored -later. Once saved, the domain will no longer be running on the -system, thus the memory allocated for the domain will be free for -other domains to use. B<xm restore> restores from this state file. - -This is roughly equivalent to doing a hibernate on a running computer, -with all the same limitations. Open network connections may be -severed upon restore, as TCP timeouts may have expired. - -=item B<shutdown> [I<OPTIONS>] I<domain-id> - -Gracefully shuts down a domain. This coordinates with the domain OS -to perform graceful shutdown, so there is no guarantee that it will -succeed, and may take a variable length of time depending on what -services must be shutdown in the domain. The command returns -immediately after signally the domain unless that B<-w> flag is used. - -The behavior of what happens to a domain when it reboots is set by the -B<on_shutdown> parameter of the xmdomain.cfg file when the domain was -created. - -B<OPTIONS> - -=over 4 - -=item B<-a> - -Shutdown B<all> domains. Often used when doing a complete shutdown of -a Xen system. - -=item B<-w> - -Wait for the domain to complete shutdown before returning. - -=back - -=item B<start> I<domain-name> [I<OPTIONS>] - -Start a Xend managed domain that was added using the B<xm new> command. - - -B<OPTIONS> - -=over 4 - -=item B<-p>, B<--paused> - -Do not unpause domain after starting it. - -=item B<-c>, B<--console_autoconnect> - -Connect to the console after the domain is created. - -=back - -=item B<suspend> I<domain-name> - -Suspend a domain to a state file so that it can be later -resumed using the B<xm resume> subcommand. Similar to the B<xm save> -subcommand although the state file may not be specified. - -=item B<sysrq> I<domain-id> I<letter> - -Send a I<Magic System Request> signal to the domain. For more -information on available magic sys req operations, see sysrq.txt in -your Linux Kernel sources. - -=item B<unpause> I<domain-id> - -Moves a domain out of the paused state. This will allow a previously -paused domain to now be eligible for scheduling by the Xen hypervisor. - -=item B<vcpu-set> I<domain-id> I<vcpu-count> - -Enables the I<vcpu-count> virtual CPUs for the domain in question. -Like mem-set, this command can only allocate up to the maximum virtual -CPU count configured at boot for the domain. - -If the I<vcpu-count> is smaller than the current number of active -VCPUs, the highest number VCPUs will be hotplug removed. This may be -important for pinning purposes. - -Attempting to set the VCPUs to a number larger than the initially -configured VCPU count is an error. Trying to set VCPUs to < 1 will be -quietly ignored. - -Because this operation requires cooperation from the domain operating -system, there is no guarantee that it will succeed. This command will -not work with a full virt domain. - -=item B<vcpu-list> [I<domain-id>] - -Lists VCPU information for a specific domain. If no domain is -specified, VCPU information for all domains will be provided. - -=item B<vcpu-pin> I<domain-id> I<vcpu> I<cpus> - -Pins the the VCPU to only run on the specific CPUs. The keyword -B<all> can be used to apply the I<cpus> list to all VCPUs in the -domain. - -Normally VCPUs can float between available CPUs whenever Xen deems a -different run state is appropriate. Pinning can be used to restrict -this, by ensuring certain VCPUs can only run on certain physical -CPUs. - -=back - -=head1 XEN HOST SUBCOMMANDS - -=over 4 - -=item B<dmesg> [B<-c>] - -Reads the Xen message buffer, similar to dmesg on a Linux system. The -buffer contains informational, warning, and error messages created -during Xen's boot process. If you are having problems with Xen, this -is one of the first places to look as part of problem determination. - -B<OPTIONS> - -=over 4 - -=item B<-c>, B<--clear> - -Clears Xen's message buffer. - -=back - -=item B<info> - -Print information about the Xen host in I<name : value> format. When -reporting a Xen bug, please provide this information as part of the -bug report. - -Sample output looks as follows (lines wrapped manually to make the man -page more readable): - - host : talon - release : 2.6.12.6-xen0 - version : #1 Mon Nov 14 14:26:26 EST 2005 - machine : i686 - nr_cpus : 2 - nr_nodes : 1 - cores_per_socket : 1 - threads_per_core : 1 - cpu_mhz : 696 - hw_caps : 0383fbff:00000000:00000000:00000040 - total_memory : 767 - free_memory : 37 - xen_major : 3 - xen_minor : 0 - xen_extra : -devel - xen_caps : xen-3.0-x86_32 - xen_scheduler : credit - xen_pagesize : 4096 - platform_params : virt_start=0xfc000000 - xen_changeset : Mon Nov 14 18:13:38 2005 +0100 - 7793:090e44133d40 - cc_compiler : gcc version 3.4.3 (Mandrakelinux - 10.2 3.4.3-7mdk) - cc_compile_by : sdague - cc_compile_domain : (none) - cc_compile_date : Mon Nov 14 14:16:48 EST 2005 - xend_config_format : 3 - -B<FIELDS> - -Not all fields will be explained here, but some of the less obvious -ones deserve explanation: - -=over 4 - -=item B<hw_caps> - -A vector showing what hardware capabilities are supported by your -processor. This is equivalent to, though more cryptic, the flags -field in /proc/cpuinfo on a normal Linux machine. - -=item B<free_memory> - -Available memory (in MB) not allocated to Xen, or any other domains. - -=item B<xen_caps> - -The Xen version and architecture. Architecture values can be one of: -x86_32, x86_32p (i.e. PAE enabled), x86_64, ia64. - -=item B<xen_changeset> - -The Xen mercurial changeset id. Very useful for determining exactly -what version of code your Xen system was built from. - -=back - -=item B<log> - -Print out the xend log. This log file can be found in -/var/log/xend.log. - -=item B<top> - -Executes the B<xentop> command, which provides real time monitoring of -domains. Xentop is a curses interface, and reasonably self -explanatory. - -=item B<uptime> - -Prints the current uptime of the domains running. - -=back - -=head1 SCHEDULER SUBCOMMANDS - -Xen ships with a number of domain schedulers, which can be set at boot -time with the B<sched=> parameter on the Xen command line. By -default B<credit> is used for scheduling. - -FIXME: we really need a scheduler expert to write up this section. - -=over 4 - -=item B<sched-credit> [ B<-d> I<domain-id> [ B<-w>[B<=>I<WEIGHT>] | B<-c>[B<=>I<CAP>] ] ] - -Set credit scheduler parameters. The credit scheduler is a -proportional fair share CPU scheduler built from the ground up to be -work conserving on SMP hosts. - -Each domain (including Domain0) is assigned a weight and a cap. - -B<PARAMETERS> - -=over 4 - -=item I<WEIGHT> - -A domain with a weight of 512 will get twice as much CPU as a domain -with a weight of 256 on a contended host. Legal weights range from 1 -to 65535 and the default is 256. - -=item I<CAP> - -The cap optionally fixes the maximum amount of CPU a domain will be -able to consume, even if the host system has idle CPU cycles. The cap -is expressed in percentage of one physical CPU: 100 is 1 physical CPU, -50 is half a CPU, 400 is 4 CPUs, etc. The default, 0, means there is -no upper cap. - -NB: Many systems have features that will scale down the computing -power of a cpu that is not 100% utilized. This can be in the -operating system, but can also sometimes be below the operating system -in the BIOS. If you set a cap such that individual cores are running -at less than 100%, this may have an impact on the performance of your -workload over and above the impact of the cap. For example, if your -processor runs at 2GHz, and you cap a vm at 50%, the power management -system may also reduce the clock speed to 1GHz; the effect will be -that your VM gets 25% of the available power (50% of 1GHz) rather than -50% (50% of 2GHz). If you are not getting the performance you expect, -look at performance and cpufreq options in your operating system and -your BIOS. - -=back - -=item B<sched-sedf> I<period> I<slice> I<latency-hint> I<extratime> I<weight> - -Set Simple EDF (Earliest Deadline First) scheduler parameters. This -scheduler provides weighted CPU sharing in an intuitive way and uses -realtime-algorithms to ensure time guarantees. For more information -see docs/misc/sedf_scheduler_mini-HOWTO.txt in the Xen distribution. - -B<PARAMETERS> - -=over 4 - -=item I<period> - -The normal EDF scheduling usage in nanoseconds - -=item I<slice> - -The normal EDF scheduling usage in nanoseconds - -FIXME: these are lame, should explain more. - -=item I<latency-hint> - -Scaled period if domain is doing heavy I/O. - -=item I<extratime> - -Flag for allowing domain to run in extra time. - -=item I<weight> - -Another way of setting CPU slice. - -=back - -B<EXAMPLES> - -I<normal EDF (20ms/5ms):> - - xm sched-sedf <dom-id> 20000000 5000000 0 0 0 - -I<best-effort domains (i.e. non-realtime):> - - xm sched-sedf <dom-id> 20000000 0 0 1 0 - -I<normal EDF (20ms/5ms) + share of extra-time:> - - xm sched-sedf <dom-id> 20000000 5000000 0 1 0 - -I<4 domains with weights 2:3:4:2> - - xm sched-sedf <d1> 0 0 0 0 2 - xm sched-sedf <d2> 0 0 0 0 3 - xm sched-sedf <d3> 0 0 0 0 4 - xm sched-sedf <d4> 0 0 0 0 2 - -I<1 fully-specified (10ms/3ms) domain, 3 other domains share available -rest in 2:7:3 ratio:> - - xm sched-sedf <d1> 10000000 3000000 0 0 0 - xm sched-sedf <d2> 0 0 0 0 2 - xm sched-sedf <d3> 0 0 0 0 7 - xm sched-sedf <d4> 0 0 0 0 3 - -=back - -=head1 VIRTUAL DEVICE COMMANDS - -Most virtual devices can be added and removed while guests are -running. The effect to the guest OS is much the same as any hotplug -event. - -=head2 BLOCK DEVICES - -=over 4 - -=item B<block-attach> I<domain-id> I<be-dev> I<fe-dev> I<mode> [I<bedomain-id>] - -Create a new virtual block device. This will trigger a hotplug event -for the guest. - -B<OPTIONS> - -=over 4 - -=item I<domain-id> - -The domain id of the guest domain that the device will be attached to. - -=item I<be-dev> - -The device in the backend domain (usually domain 0) to be exported. -This can be specified as a physical partition (phy:sda7) or as a file -mounted as loopback (file://path/to/loop.iso). - -=item I<fe-dev> - -How the device should be presented to the guest domain. It can be -specified as either a symbolic name, such as /dev/hdc, for common -devices, or by device id, such as 0x1400 (/dev/hdc device id in hex). - -=item I<mode> - -The access mode for the device from the guest domain. Supported modes -are B<w> (read/write) or B<r> (read-only). - -=item I<bedomain-id> - -The back end domain hosting the device. This defaults to domain 0. - -=back - -B<EXAMPLES> - -=over 4 - -=item I<Mount an ISO as a Disk> - -xm block-attach guestdomain file://path/to/dsl-2.0RC2.iso /dev/hdc r - -This will mount the dsl ISO as /dev/hdc in the guestdomain as a read -only device. This will probably not be detected as a CD-ROM by the -guest, but mounting /dev/hdc manually will work. - -=back - -=item B<block-detach> I<domain-id> I<devid> [B<--force>] - -Detach a domain's virtual block device. I<devid> may be the symbolic -name or the numeric device id given to the device by domain 0. You -will need to run B<xm block-list> to determine that number. - -Detaching the device requires the cooperation of the domain. If the -domain fails to release the device (perhaps because the domain is hung -or is still using the device), the detach will fail. The B<--force> -parameter will forcefully detach the device, but may cause IO errors -in the domain. - -=item B<block-list> [B<-l>|B<--long>] I<domain-id> - -List virtual block devices for a domain. The returned output is -formatted as a list or as an S-Expression if the B<--long> option was given. - -=back - -=head2 NETWORK DEVICES - -=over 4 - -=item B<network-attach> I<domain-id> [B<script=>I<scriptname>] [B<ip=>I<ipaddr>] -[B<mac=>I<macaddr>] [B<bridge=>I<bridge-name>] [B<backend=>I<bedomain-id>] - -Creates a new network device in the domain specified by I<domain-id>. It -takes the following optional options: - -=back - -B<OPTIONS> - -=over 4 - -=item B<script=>I<scriptname> - -Use the specified script name to bring up the network. Defaults to -the default setting in xend-config.sxp for B<vif-script>. - -=item B<ip=>I<ipaddr> - -Passes the specified IP Address to the adapter on creation. - -FIXME: this currently appears to be B<broken>. I'm not sure under what -circumstances this should actually work. - -=item B<mac=>I<macaddr> - -The MAC address that the domain will see on its Ethernet device. If -the device is not specified it will be randomly generated with the -00:16:3e vendor id prefix. - -=item B<bridge=>I<bridge-name> - -The name of the bridge to attach the vif to, in case you have more -than one. This defaults to xenbr0. - -=item B<backend=>I<bedomain-id> - -The backend domain id. By default this is domain 0. - -=back - -=over 4 - -=item B<network-detach> I<domain-id> I<devid> - -Removes the network device from the domain specified by I<domain-id>. -I<devid> is the virtual interface device number within the domain -(i.e. the 3 in vif22.3). - -FIXME: this is currently B<broken>. Network devices aren't completely -removed from domain 0. - -=item B<network-list> [B<-l>|B<--long>]> I<domain-id> - -List virtual network interfaces for a domain. The returned output is -formatted as a list or as an S-Expression if the B<--long> option was given. - -=back - -=head1 SEE ALSO - -B<xmdomain.cfg>(5), B<xentop>(1) - -=head1 AUTHOR - - Sean Dague <sean at dague dot net> - Daniel Stekloff <dsteklof at us dot ibm dot com> - Reiner Sailer <sailer at us dot ibm dot com> - Stefan Berger <stefanb at us dot ibm dot com> - -=head1 BUGS diff --git a/docs/man/xmdomain.cfg.pod.5 b/docs/man/xmdomain.cfg.pod.5 deleted file mode 100644 index 2e73db4..0000000 --- a/docs/man/xmdomain.cfg.pod.5 +++ /dev/null @@ -1,358 +0,0 @@ -=head1 NAME - -xmdomain.cfg - xm domain config file format - -=head1 SYNOPSIS - - /etc/xen/myxendomain - /etc/xen/myxendomain2 - /etc/xen/auto/myxenautostarted - -=head1 DESCRIPTION - -The B<xm>(1) program uses python executable config files to define -domains to create from scratch. Each of these config files needs to -contain a number of required options, and may specify many more. - -Domain configuration files live in /etc/xen by default, if you store -config files anywhere else the full path to the config file must be -specified in the I<xm create> command. - -/etc/xen/auto is a special case. Domain config files in that -directory will be started automatically at system boot if the -xendomain init script is enabled. The contents of /etc/xen/auto -should be symlinks to files in /etc/xen to allow I<xm create> to be -used without full paths. - -Options are specified by I<name = value> statements in the -xmdomain.cfg files. - -=head1 OPTIONS - -The following lists the most commonly used options for a domain config -file. - -=over 4 - -=item B<kernel> - -The kernel image for the domain. The format of the parameter is the -fully qualified path to the kernel image file, -i.e. I</boot/vmlinuz-2.6.12-xenU>. - - -=item B<ramdisk> - -The initial ramdisk for the domain. The format of the parameter is -the fully qualified path to the initrd, i.e. I</boot/initrd.gz>. On -many Linux distros you will not need a ramdisk if using the default -xen kernel. - -=item B<memory> - -The amount of RAM, in megabytes, to allocate to the domain when it -starts. Allocating insufficient memory for a domain may produce -extremely bizarre behavior. If there isn't enough free memory left on -the machine to fulfil this request, the domain will fail to start. - -Xen does not support overcommit of memory, so the total memory of all -guests (+ 64 MB needed for Xen) must be less than or equal to the -physical RAM in the machine. - -=item B<name> - -A unique name for the domain. Attempting to create two domains with -the same name will cause an error. - -=item B<root> - -Specifies the root device for the domain. This is required for Linux -domains, and possibly other OSes. - -=item B<nics> - -The number of network interfaces allocated to the domain on boot. It -defaults to 1. - -=item B<disk> - -An array of block device stanzas, in the form: - - disk = [ "stanza1", "stanza2", ... ] - -Each stanza has 3 terms, separated by commas, -"backend-dev,frontend-dev,mode". - -=over 4 - -=item I<backend-dev> - -The device in the backend domain that will be exported to the guest -(frontend) domain. Supported formats include: - -I<phy:device> - export the physical device listed. The device can be -in symbolic form, as in sda7, or as the hex major/minor number, as in -0x301 (which is hda1). - -I<file://path/to/file> - export the file listed as a loopback device. -This will take care of the loopback setup before exporting the device. - -=item I<frontend-dev> - -How the device should appear in the guest domain. The device can be -in symbolic form, as in sda7, or as the hex major/minor number, as in -0x301 (which is hda1). - -=item I<mode> - -The access mode for the device. There are currently 2 valid options, -I<r> (read-only), I<w> (read/write). - -=back - -=item B<vif> - -An array of virtual interface stanzas in the form: - - vif = [ "stanza1", "stanza2", ... ] - -Each stanza specifies a set of I<name = value> options separated by -commas, in the form: "name1=value1, name2=value2, ..." - -B<OPTIONS> - -=over 4 - -=item I<bridge> - -The network bridge to be used for this device. This is especially -needed if multiple bridges exist on the machine. - -=item I<mac> - -The MAC address for the virtual interface. If mac is not specified, -one will be randomly chosen by xen with the 00:16:3e vendor id prefix. - -=back - -=item B<vfb> - -A virtual frame buffer stanza in the form: - - vfb = [ "stanza" ] - -The stanza specifies a set of I<name = value> options separated by -commas, in the form: "name1=value1, name2=value2, ..." - -B<OPTIONS> - -=over 4 - -=item I<type> - -There are currently two valid options: I<vnc> starts a VNC server that -lets you connect an external VNC viewer, and I<sdl> starts an internal -viewer. - -=item I<vncdisplay> - -The VNC display number to use, defaults to the domain ID. The -VNC server listens on port 5900 + display number. - -=item I<vnclisten> - -The listening address for the VNC server, default 127.0.0.1. - -=item I<vncunused> - -If non-zero, the VNC server listens on the first unused port above -5900. - -=item I<vncpasswd> - -Overrides the XenD configured default password. - -=item I<display> - -Display to use for the internal viewer, defaults to environment -variable I<DISPLAY>. - -=item I<xauthority> - -Authority file to use for the internal viewer, defaults to environment -variable I<XAUTHORITY>. - -=back - -=back - -=head1 ADDITIONAL OPTIONS - -The following options are also supported in the config file, though -are far more rarely used. - -=over 4 - -=item B<builder> - -Which builder should be used to construct the domain. This defaults -to the I<linux> if not specified, which is the builder for -paravirtualized Linux domains. - -=item B<cpu> - -Specifies which CPU the domain should be started on, where 0 specifies -the first cpu, 1 the second, and so on. This defaults to -1, which -means Xen is free to pick which CPU to start on. - -=item B<cpus> - -Specifies a list of CPUs on which the domains' VCPUs are allowed to -execute upon. The syntax supports ranges (0-3), and negation, ^1. -For instance: - - cpus = "0-3,5,^1" - -Will result in CPUs 0, 2, 3, 5 being available for use by the domain. - -=item B<extra> - -Extra information to append to the end of the kernel parameter line. -The format is a string, the contents of which can be anything that the -kernel supports. For instance: - - extra = "4" - -Will cause the domain to boot to runlevel 4. - -=item B<nfs_server> - -The IP address of the NFS server to use as the root device for the -domain. In order to do this you'll need to specify I<root=/dev/nfs>, -and specify I<nfs_root>. - -=item B<nfs_root> - -The directory on the NFS server to be used as the root filesystem. -Specified as a fully qualified path, i.e. I</full/path/to/root/dir>. - -=item B<vcpus> - -The number of virtual cpus to allocate to the domain. In order to use -this the xen kernel must be compiled with SMP support. - -This defaults to 1, meaning running the domain as a UP. - -=back - -=head1 DOMAIN SHUTDOWN OPTIONS - -There are 3 options which control domain shutdown (both planned and -unplanned) under certain events. The 3 events currently captured are: - -=over 4 - -=item B<on_shutdown> - -Triggered on either an I<xm shutdown> or graceful shutdown from inside -the DomU. - -=item B<on_reboot> - -Triggered on either an I<xm reboot> or graceful reboot from inside the -DomU. - -=item B<on_crash> - -Triggered when a DomU goes to the crashed state for any reason. - -=back - -All of them take one of 4 valid states listed below. - -=over 4 - -=item B<destroy> - -The domain will be cleaned up completely. No attempt at respawning -will occur. This is what a typical shutdown would look like. - -=item B<restart> - -The domain will be restarted with the same name as the old domain. -This is what a typical reboot would look like. - -=item B<preserve> - -The domain will not be cleaned up at all. This is often useful for -crash state domains which ensures that enough evidence is to debug the -real issue. - -=item B<rename-restart> - -The old domain will not be cleaned up, but will be renamed so a new -domain can be restarted in it's place. The old domain will be renamed with -a suffix -1, -2, etc, and assigned a new random UUID; the new domain will -keep the original name and UUID. The old domain will release the devices that -it holds, so that the new one may take them. - -=back - -Additionally, the "on_crash" event can also take: - -=over 4 - -=item B<coredump-destroy> - -Dump the crashed domain's core and then destroy it. - -=item B<coredump-restart> - -Dump the crashed domain's core and then restart it. - -=back - -=head1 EXAMPLES - -The following are quick examples of ways that domains might be -configured. They should not be considered an exhaustive set. - -=over 4 - -=item I<A Loopback File as Root> - - kernel = "/boot/vmlinuz-2.6-xenU" - memory = 128 - name = "MyLinux" - root = "/dev/hda1 ro" - disk = [ "file:/var/xen/mylinux.img,hda1,w" ] - -This creates a domain called MyLinux with 128 MB of memory using a -default xen kernel, and the file /var/xen/mylinux.img loopback mounted -at hda1, which is the root filesystem. - -=item I<NFS Root> - -FIXME: write me - -=item I<LVM Root> - -FIXME: write me - -=item I<Two Networks> - -FIXME: write me - -=back - -=head1 SEE ALSO - -B<xm>(1) - -=head1 AUTHOR - - Sean Dague <sean at dague dot net> - -=head1 BUGS - -Not all options are currently documented diff --git a/tools/configure b/tools/configure index 5c2fa14..7a44505 100755 --- a/tools/configure +++ b/tools/configure @@ -688,7 +688,6 @@ seabios_path qemu_xen qemu_traditional blktap1 -xend debug seabios rombios @@ -765,7 +764,6 @@ enable_ovmf enable_rombios enable_seabios enable_debug -enable_xend enable_blktap1 enable_qemu_traditional with_system_qemu @@ -1427,7 +1425,6 @@ Optional Features: --disable-rombios Disable ROM BIOS (default is ENABLED) --disable-seabios Disable SeaBIOS (default is ENABLED) --disable-debug Disable debug build of tools (default is ENABLED) - --enable-xend Enable xend toolstack (default is DISABLED) --enable-blktap1 Enable blktap1 tools (default is DISABLED) --enable-qemu-traditional Enable qemu traditional device model, (DEFAULT is on @@ -3747,29 +3744,6 @@ debug=$ax_cv_debug -# Check whether --enable-xend was given. -if test "${enable_xend+set}" = set; then : - enableval=$enable_xend; -fi - - -if test "x$enable_xend" = "xno"; then : - - ax_cv_xend="n" - -elif test "x$enable_xend" = "xyes"; then : - - ax_cv_xend="y" - -elif test -z $ax_cv_xend; then : - - ax_cv_xend="n" - -fi -xend=$ax_cv_xend - - - # Check whether --enable-blktap1 was given. if test "${enable_blktap1+set}" = set; then : enableval=$enable_blktap1; @@ -9480,25 +9454,3 @@ $as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2;} fi -if test "x$xend" = "xy" ; then : - - { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: You have enabled the xend toolstack. - -xend is deprecated and scheduled for removal. Please migrate to another -toolstack ASAP. - -See http://wiki.xen.org/wiki/Choice_of_Toolstacks for information on -other alternatives, including xl which is designed to be a drop in -replacement for xm (http://wiki.xen.org/wiki/XL). -" >&5 -$as_echo "$as_me: WARNING: You have enabled the xend toolstack. - -xend is deprecated and scheduled for removal. Please migrate to another -toolstack ASAP. - -See http://wiki.xen.org/wiki/Choice_of_Toolstacks for information on -other alternatives, including xl which is designed to be a drop in -replacement for xm (http://wiki.xen.org/wiki/XL). -" >&2;} - -fi diff --git a/tools/configure.ac b/tools/configure.ac index a62faf8..e1f7527 100644 --- a/tools/configure.ac +++ b/tools/configure.ac @@ -58,7 +58,6 @@ AX_ARG_DEFAULT_DISABLE([ovmf], [Enable OVMF]) AX_ARG_DEFAULT_ENABLE([rombios], [Disable ROM BIOS]) AX_ARG_DEFAULT_ENABLE([seabios], [Disable SeaBIOS]) AX_ARG_DEFAULT_ENABLE([debug], [Disable debug build of tools]) -AX_ARG_DEFAULT_DISABLE([xend], [Enable xend toolstack]) AX_ARG_DEFAULT_DISABLE([blktap1], [Enable blktap1 tools]) AC_ARG_ENABLE([qemu-traditional], @@ -245,15 +244,3 @@ AC_CHECK_HEADERS([yajl/yajl_version.h sys/eventfd.h]) AC_OUTPUT() -AS_IF([test "x$xend" = "xy" ], [ - AC_MSG_WARN( -[You have enabled the xend toolstack. - -xend is deprecated and scheduled for removal. Please migrate to another -toolstack ASAP. - -See http://wiki.xen.org/wiki/Choice_of_Toolstacks for information on -other alternatives, including xl which is designed to be a drop in -replacement for xm (http://wiki.xen.org/wiki/XL). -]) -]) diff --git a/tools/examples/Makefile b/tools/examples/Makefile index df24e38..86d9cc1 100644 --- a/tools/examples/Makefile +++ b/tools/examples/Makefile @@ -5,18 +5,6 @@ include $(XEN_ROOT)/tools/Rules.mk XEN_READMES = README XEN_READMES += README.incompatibilities -XEN_CONFIGS-$(CONFIG_XEND) += xend-config.sxp -XEN_CONFIGS-$(CONFIG_XEND) += xm-config.xml -XEN_CONFIGS-$(CONFIG_XEND) += xmexample1 -XEN_CONFIGS-$(CONFIG_XEND) += xmexample2 -XEN_CONFIGS-$(CONFIG_XEND) += xmexample3 -XEN_CONFIGS-$(CONFIG_XEND) += xmexample.hvm -XEN_CONFIGS-$(CONFIG_XEND) += xmexample.hvm-stubdom -XEN_CONFIGS-$(CONFIG_XEND) += xmexample.pv-grub -XEN_CONFIGS-$(CONFIG_XEND) += xmexample.nbd -XEN_CONFIGS-$(CONFIG_XEND) += xend-pci-quirks.sxp -XEN_CONFIGS-$(CONFIG_XEND) += xend-pci-permissive.sxp - XEN_CONFIGS += xlexample.hvm XEN_CONFIGS += xlexample.pvlinux XEN_CONFIGS += xl.conf diff --git a/tools/examples/xend-config.sxp b/tools/examples/xend-config.sxp deleted file mode 100644 index 0896a27..0000000 --- a/tools/examples/xend-config.sxp +++ /dev/null @@ -1,304 +0,0 @@ -# -*- sh -*- - -# -# Xend configuration file. -# - -# This example configuration is appropriate for an installation that -# utilizes a bridged network configuration. Access to xend via http -# is disabled. - -# Commented out entries show the default for that entry, unless otherwise -# specified. - -#(logfile /var/log/xen/xend.log) -#(loglevel DEBUG) - -# Uncomment the line below. Set the value to flask, acm, or dummy to -# select a security module. - -#(xsm_module_name dummy) - -# The Xen-API server configuration. -# -# This value configures the ports, interfaces, and access controls for the -# Xen-API server. Each entry in the list starts with either unix, a port -# number, or an address:port pair. If this is "unix", then a UDP socket is -# opened, and this entry applies to that. If it is a port, then Xend will -# listen on all interfaces on that TCP port, and if it is an address:port -# pair, then Xend will listen on the specified port, using the interface with -# the specified address. -# -# The subsequent string configures the user-based access control for the -# listener in question. This can be one of "none" or "pam", indicating either -# that users should be allowed access unconditionally, or that the local -# Pluggable Authentication Modules configuration should be used. If this -# string is missing or empty, then "pam" is used. -# -# The final string gives the host-based access control for that listener. If -# this is missing or empty, then all connections are accepted. Otherwise, -# this should be a space-separated sequence of regular expressions; any host -# with a fully-qualified domain name or an IP address that matches one of -# these regular expressions will be accepted. -# -# Example: listen on TCP port 9363 on all interfaces, accepting connections -# only from machines in example.com or localhost, and allow access through -# the unix domain socket unconditionally: -# -# (xen-api-server ((9363 pam '^localhost$ example\\.com$') -# (unix none))) -# -# Optionally, the TCP Xen-API server can use SSL by specifying the private -# key and certificate location: -# -# (9367 pam '' xen-api.key xen-api.crt) -# -# Default: -# (xen-api-server ((unix))) - - -#(xend-http-server no) -#(xend-unix-server no) -#(xend-tcp-xmlrpc-server no) -#(xend-unix-xmlrpc-server yes) -#(xend-relocation-server no) -(xend-relocation-server yes) -#(xend-relocation-ssl-server no) -#(xend-udev-event-server no) - -#(xend-unix-path /var/lib/xend/xend-socket) - - -# Address and port xend should use for the legacy TCP XMLRPC interface, -# if xend-tcp-xmlrpc-server is set. -#(xend-tcp-xmlrpc-server-address 'localhost') -#(xend-tcp-xmlrpc-server-port 8006) - -# SSL key and certificate to use for the legacy TCP XMLRPC interface. -# Setting these will mean that this port serves only SSL connections as -# opposed to plaintext ones. -#(xend-tcp-xmlrpc-server-ssl-key-file xmlrpc.key) -#(xend-tcp-xmlrpc-server-ssl-cert-file xmlrpc.crt) - - -# Port xend should use for the HTTP interface, if xend-http-server is set. -#(xend-port 8000) - -# Port xend should use for the relocation interface, if xend-relocation-server -# is set. -#(xend-relocation-port 8002) - -# Port xend should use for the ssl relocation interface, if -# xend-relocation-ssl-server is set. -#(xend-relocation-ssl-port 8003) - -# SSL key and certificate to use for the ssl relocation interface, if -# xend-relocation-ssl-server is set. -#(xend-relocation-server-ssl-key-file xmlrpc.key) -#(xend-relocation-server-ssl-cert-file xmlrpc.crt) - -# Whether to use ssl as default when relocating. -#(xend-relocation-ssl no) - -# Address xend should listen on for HTTP connections, if xend-http-server is -# set. -# Specifying 'localhost' prevents remote connections. -# Specifying the empty string '' (the default) allows all connections. -#(xend-address '') -#(xend-address localhost) - -# Address xend should listen on for relocation-socket connections, if -# xend-relocation-server is set. -# Meaning and default as for xend-address above. -# Also, interface name is allowed (e.g. eth0) there to get the -# relocation address to be bound on. -#(xend-relocation-address '') - -# The hosts allowed to talk to the relocation port. If this is empty (the -# default), then all connections are allowed (assuming that the connection -# arrives on a port and interface on which we are listening; see -# xend-relocation-port and xend-relocation-address above). Otherwise, this -# should be a space-separated sequence of regular expressions. Any host with -# a fully-qualified domain name or an IP address that matches one of these -# regular expressions will be accepted. -# -# For example: -# (xend-relocation-hosts-allow '^localhost$ ^.*\\.example\\.org$') -# -#(xend-relocation-hosts-allow '') -(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$') - -# The limit (in kilobytes) on the size of the console buffer -#(console-limit 1024) - -## -# To bridge network traffic, like this: -# -# dom0: ----------------- bridge -> real eth0 -> the network -# | -# domU: fake eth0 -> vifN.0 -+ -# -# use -# -# (network-script network-bridge) -# -# Your default ethernet device is used as the outgoing interface, by default. -# To use a different one (e.g. eth1) use -# -# (network-script 'network-bridge netdev=eth1') -# -# The bridge is named eth0, by default (yes, really!) -# - -# It is normally much better to create the bridge yourself in -# /etc/network/interfaces. network-bridge start does nothing if you -# already have a bridge, and network-bridge stop does nothing if the -# default bridge name (normally eth0) is not a bridge. See -# bridge-utils-interfaces(5) for full information on the syntax in -# /etc/network/interfaces, but you probably want something like this: -# iface xenbr0 inet static -# address [etc] -# netmask [etc] -# [etc] -# bridge_ports eth0 -# -# To have network-bridge create a differently-named bridge, use: -# (network-script 'network-bridge bridge=<name>') -# -# It is possible to use the network-bridge script in more complicated -# scenarios, such as having two outgoing interfaces, with two bridges, and -# two fake interfaces per guest domain. To do things like this, write -# yourself a wrapper script, and call network-bridge from it, as appropriate. -# -(network-script network-bridge) - -# The script used to control virtual interfaces. This can be overridden on a -# per-vif basis when creating a domain or a configuring a new vif. The -# vif-bridge script is designed for use with the network-bridge script, or -# similar configurations. -# -# If you have overridden the bridge name using -# (network-script 'network-bridge bridge=<name>') then you may wish to do the -# same here. The bridge name can also be set when creating a domain or -# configuring a new vif, but a value specified here would act as a default. -# -# If you are using only one bridge, the vif-bridge script will discover that, -# so there is no need to specify it explicitly. The default is to use -# the bridge which is listed first in the output from brctl. -# -(vif-script vif-bridge) - - -## Use the following if network traffic is routed, as an alternative to the -# settings for bridged networking given above. -#(network-script network-route) -#(vif-script vif-route) - - -## Use the following if network traffic is routed with NAT, as an alternative -# to the settings for bridged networking given above. -#(network-script network-nat) -#(vif-script vif-nat) - -# dom0-min-mem is the lowest permissible memory level (in MB) for dom0. -# This is a minimum both for auto-ballooning (as enabled by -# enable-dom0-ballooning below) and for xm mem-set when applied to dom0. -(dom0-min-mem 196) - -# Whether to enable auto-ballooning of dom0 to allow domUs to be created. -# If enable-dom0-ballooning = no, dom0 will never balloon out. -(enable-dom0-ballooning yes) - -# 32-bit paravirtual domains can only consume physical -# memory below 168GB. On systems with memory beyond that address, -# they'll be confined to memory below 128GB. -# Using total_available_memory (in GB) to specify the amount of memory reserved -# in the memory pool exclusively for 32-bit paravirtual domains. -# Additionally you should use dom0_mem = <-Value> as a parameter in -# xen kernel to reserve the memory for 32-bit paravirtual domains, default -# is "0" (0GB). -(total_available_memory 0) - -# In SMP system, dom0 will use dom0-cpus # of CPUS -# If dom0-cpus = 0, dom0 will take all cpus available -(dom0-cpus 0) - -# Whether to enable core-dumps when domains crash. -#(enable-dump no) - -# The tool used for initiating virtual TPM migration -#(external-migration-tool '') - -# The interface for VNC servers to listen on. Defaults -# to 127.0.0.1 To restore old 'listen everywhere' behaviour -# set this to 0.0.0.0 -#(vnc-listen '127.0.0.1') - -# The default password for VNC console on HVM domain. -# Empty string is no authentication. -(vncpasswd '') - -# The VNC server can be told to negotiate a TLS session -# to encryption all traffic, and provide x509 cert to -# clients enabling them to verify server identity. The -# GTK-VNC widget, virt-viewer, virt-manager and VeNCrypt -# all support the VNC extension for TLS used in QEMU. The -# TightVNC/RealVNC/UltraVNC clients do not. -# -# To enable this create x509 certificates / keys in the -# directory ${XEN_CONFIG_DIR} + vnc -# -# ca-cert.pem - The CA certificate -# server-cert.pem - The Server certificate signed by the CA -# server-key.pem - The server private key -# -# and then uncomment this next line -# (vnc-tls 1) - -# The certificate dir can be pointed elsewhere.. -# -# (vnc-x509-cert-dir vnc) - -# The server can be told to request & validate an x509 -# certificate from the client. Only clients with a cert -# signed by the trusted CA will be able to connect. This -# is more secure the password auth alone. Passwd auth can -# used at the same time if desired. To enable client cert -# checking uncomment this: -# -# (vnc-x509-verify 1) - -# The default keymap to use for the VM's virtual keyboard -# when not specififed in VM's configuration -#(keymap 'en-us') - -# Script to run when the label of a resource has changed. -#(resource-label-change-script '') - -# Rotation count of qemu-dm log file. -#(qemu-dm-logrotate-count 10) - -# Path where persistent domain configuration is stored. -# Default is /var/lib/xend/domains/ -#(xend-domains-path /var/lib/xend/domains) - -# Number of seconds xend will wait for device creation and -# destruction -#(device-create-timeout 100) -#(device-destroy-timeout 100) - -# 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, 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. -#(pci-passthrough-strict-check yes) - -# If we have a very big scsi device configuration, start of xend is slow, -# because xend scans all the device paths to build its internal PSCSI device -# list. If we need only a few devices for assigning to a guest, we can reduce -# the scan to this device. Set list list of device paths in same syntax like in -# command lsscsi, e.g. ('16:0:0:0' '15:0') -# (pscsi-device-mask ('*')) - diff --git a/tools/examples/xend-pci-permissive.sxp b/tools/examples/xend-pci-permissive.sxp deleted file mode 100644 index 1a3fb90..0000000 --- a/tools/examples/xend-pci-permissive.sxp +++ /dev/null @@ -1,27 +0,0 @@ -############################################################################### -# Configuration file for granting quiry PCI devices full write access to their -# configuration space. This file should only be used when you are unable to -# determine the exact registers required by your device. Even so, it should -# be used only temporarily. -# -# SEND A MESSAGE TO xen-devel@xxxxxxxxxxxxxxxxxxx IF YOU USE THIS FILE. -# -# Using this file should NOT be necessary. If you must use it to make some -# device work, send a message to the above list with as much information about -# your device as possible so the developers can make accomodations for it. -# Once developers make the necessary updates you can remove the corresponding -# entry for your device. -############################################################################### -# Entries are formated as follows: <vendor>:<device>[:<subvendor>:<subdevice>] -# -# Example: Appending to an existing list -# -# (unconstrained_dev_ids -# ('XXXX:XXXX:XXXX:XXXX' # existing entry -# 'YYYY:YYYY:YYYY:YYYY' # new entry 1 -# 'ZZZZ:ZZZZ') # new entry 2 -# ) -############################################################################### -(unconstrained_dev_ids - #('0123:4567:89AB:CDEF') -) diff --git a/tools/examples/xend-pci-quirks.sxp b/tools/examples/xend-pci-quirks.sxp deleted file mode 100644 index 6bce4b8..0000000 --- a/tools/examples/xend-pci-quirks.sxp +++ /dev/null @@ -1,96 +0,0 @@ -############################################################################### -# Configuration file for quirky PCI devices that require write-access to -# parts of the configuration space. Use this file to specific PCI device -# IDs and the configuration space fields to which those devices must be -# able to write. -# -# Length is important, so be sure to match new entries with the -# lengths of comparable existing entries. -# -# Additions to this file take effect as soon as a new domain with a -# matching device is started. However, to remove a field that was -# previously applied to a device you must unbind the device from -# pciback. -############################################################################### -# This is a bogus entry to show how a new device would be added to the list -# -# (new_quirky_dev_name -# (pci_ids -# ('0123:4567:890A:BCEF') -# ) -# -# (pci_config_space_fields -# ('12345678:1:00000000') -# ) -# ) -############################################################################### - -(tg3 - (pci_ids - # Entries are formated as follows: - # <vendor>:<device>[:<subvendor>:<subdevice>] - ('14e4:1644' # Broadcom Tigon3 5700 - '14e4:1645' # Broadcom Tigon3 5701 - '14e4:1646' # Broadcom Tigon3 5702 - '14e4:1647' # Broadcom Tigon3 5703 - '14e4:1648' # Broadcom Tigon3 5704 - '14e4:164d' # Broadcom Tigon3 5702FE - '14e4:1653' # Broadcom Tigon3 5705 - '14e4:1654' # Broadcom Tigon3 5705_2 - '14e4:165d' # Broadcom Tigon3 5705M - '14e4:165e' # Broadcom Tigon3 5705M_2 - '14e4:16a6' # Broadcom Tigon3 5702X - '14e4:16a7' # Broadcom Tigon3 5703X - '14e4:16a8' # Broadcom Tigon3 5704S - '14e4:16c6' # Broadcom Tigon3 5702A3 - '14e4:16c7' # Broadcom Tigon3 5703A3 - '14e4:1696' # Broadcom Tigon3 5782 - '14e4:169c' # Broadcom Tigon3 5788 - '14e4:169d' # Broadcom Tigon3 5789 - '14e4:170d' # Broadcom Tigon3 5901 - '14e4:1649' # Broadcom Tigon3 5704S_2 - '14e4:166e' # Broadcom Tigon3 5705F - '14e4:1658' # Broadcom Tigon3 5720 - '14e4:1659' # Broadcom Tigon3 5721 - '14e4:1676' # Broadcom Tigon3 5750 - '14e4:1677' # Broadcom Tigon3 5751 - '14e4:167c' # Broadcom Tigon3 5750M - '14e4:167d' # Broadcom Tigon3 5751M - '14e4:167e' # Broadcom Tigon3 5751F - '14e4:1600' # Broadcom Tigon3 5752 - '14e4:1601' # Broadcom Tigon3 5752M - '14e4:16f7' # Broadcom Tigon3 5753 - '14e4:16fd' # Broadcom Tigon3 5753M - '14e4:16fe' # Broadcom Tigon3 5753F - '14e4:1668' # Broadcom Tigon3 5714 - '14e4:1678' # Broadcom Tigon3 5715 - '14e4:166a' # Broadcom Tigon3 5780 - '14e4:166b' # Broadcom Tigon3 5780S - '14e4:16dd' # Broadcom Tigon3 5781 - '1148:4400' # Syskonnect 9DXX - '1148:4500' # Syskonnect 9MXX - '173b:03e8' # Altima AC1000 - '173b:03e9' # Altima AC1001 - '173b:03eb' # Altima AC1003 - '173b:03ea' # Altima AC9100 - '106b:1645') # Apple Tigon3 - ) - - (pci_config_space_fields - # Entries are formated as follows: - # <register>:<size>:<mask> - # size is measured in bytes (1,2,4 are valid sizes) - # mask is currently unused; use all zero's - ('00000078:4:00000000' # TG3PCI_REG_BASE_ADDR - '0000007c:4:00000000' # TG3PCI_MEM_WIN_BASE_ADDR - '00000080:4:00000000' # TG3PCI_REG_DATA - '00000084:4:00000000' # TG3PCI_MEM_WIN_DATA - '00000090:4:00000000' # TG3PCI_MISC_LOCAL_CTRL - '00000068:4:00000000' # TG3PCI_MISC_HOST_CTRL - '0000009C:4:00000000' # TG3PCI_STD_RING_PROD_IDX + TG3_64BIT_REG_LOW - '00000098:4:00000000' # TG3PCI_STD_RING_PROD_IDX + TG3_64BIT_REG_HIGH - '000000a4:4:00000000' # TG3PCI_RCV_RET_RING_CON_IDX + TG3_64BIT_REG_LOW - '000000a0:4:00000000' # TG3PCI_RCV_RET_RING_CON_IDX + TG3_64BIT_REG_HIGH - '00000070:4:00000000') # TG3PCI_PCISTATE - ) -) diff --git a/tools/examples/xm-config.xml b/tools/examples/xm-config.xml deleted file mode 100644 index 943b74d..0000000 --- a/tools/examples/xm-config.xml +++ /dev/null @@ -1,45 +0,0 @@ - - - - -<xm> -  -  -</xm> diff --git a/tools/examples/xmexample.hvm b/tools/examples/xmexample.hvm deleted file mode 100644 index 96b6cc4..0000000 --- a/tools/examples/xmexample.hvm +++ /dev/null @@ -1,373 +0,0 @@ -# -*- mode: python; -*- -#============================================================================ -# Python configuration setup for 'xm create'. -# This script sets the parameters used when a domain is created using 'xm create'. -# You use a separate script for each domain you want to create, or -# you can set the parameters for the domain on the xm command line. -#============================================================================ - -#---------------------------------------------------------------------------- -# Kernel image file. -kernel = "hvmloader" - -# The domain build function. HVM domain uses 'hvm'. -builder='hvm' - -# Initial memory allocation (in megabytes) for the new domain. -# -# WARNING: Creating a domain with insufficient memory may cause out of -# memory errors. The domain needs enough memory to boot kernel -# and modules. Allocating less than 32MBs is not recommended. -memory = 128 - -# Shadow pagetable memory for the domain, in MB. -# If not explicictly set, xend will pick an appropriate value. -# Should be at least 2KB per MB of domain memory, plus a few MB per vcpu. -# shadow_memory = 8 - -# Whether to transparently share this domain's memory with other domains. -# default = 0 -# memory_sharing = 0 - -# A name for your domain. All domains must have different names. -name = "ExampleHVMDomain" - -# 128-bit UUID for the domain. The default behavior is to generate a new UUID -# on each call to 'xm create'. -#uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9" - -#----------------------------------------------------------------------------- -# The number of cpus guest platform has, default=1 -#vcpus=1 - -# Enable/disable HVM guest PAE, default=1 (enabled) -#pae=1 - -# Enable/disable HVM guest ACPI, default=1 (enabled) -#acpi=1 - -# Enable/disable HVM APIC mode, default=1 (enabled) -# Note that this option is ignored if vcpus > 1 -#apic=1 - -# Enable/disable extended power management support within HVM guest, i.e., beyond -# S3, S4, S5 within guest like exposing battery meter. -# 0 (default option, extended power management support disabled) -# 1 (pass-through mode; uses pass-through as needed; efficient but limited in scope) -# 2 (non pass-through mode; extended scope, likely to work on all applicable environment -# but comparitively less efficient than pass-through mode) -# xen_extended_power_mgmt=0 - -# List of which CPUS this domain is allowed to use, default Xen picks -#cpus = "" # leave to Xen to pick -#cpus = "0" # all vcpus run on CPU0 -#cpus = "0-3,5,^1" # all vcpus run on cpus 0,2,3,5 -#cpus = ["2", "3"] # VCPU0 runs on CPU2, VCPU1 runs on CPU3 - -# Optionally define mac and/or bridge for the network interfaces. -# Random MACs are assigned if not given. -#vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci' ] -# type=ioemu specify the NIC is an ioemu device not netfront -vif = [ 'type=ioemu, bridge=xenbr0' ] - -#---------------------------------------------------------------------------- -# Define the disk devices you want the domain to have access to, and -# what you want them accessible as. -# Each disk entry is of the form phy:UNAME,DEV,MODE -# where UNAME is the device, DEV is the device name the domain will see, -# and MODE is r for read-only, w for read-write. - -#disk = [ 'phy:hda1,hda1,r' ] -disk = [ 'file:/var/images/min-el3-i386.img,hda,w', ',hdc:cdrom,r' ] - -#---------------------------------------------------------------------------- -# Configure the behaviour when a domain exits. There are three 'reasons' -# for a domain to stop: poweroff, reboot, and crash. For each of these you -# may specify: -# -# "destroy", meaning that the domain is cleaned up as normal; -# "restart", meaning that a new domain is started in place of the old -# one; -# "preserve", meaning that no clean-up is done until the domain is -# manually destroyed (using xm destroy, for example); or -# "rename-restart", meaning that the old domain is not cleaned up, but is -# renamed and a new domain started in its place. -# -# In the event a domain stops due to a crash, you have the additional options: -# -# "coredump-destroy", meaning dump the crashed domain's core and then destroy; -# "coredump-restart', meaning dump the crashed domain's core and the restart. -# -# The default is -# -# on_poweroff = 'destroy' -# on_reboot = 'restart' -# on_crash = 'restart' -# -# For backwards compatibility we also support the deprecated option restart -# -# restart = 'onreboot' means on_poweroff = 'destroy' -# on_reboot = 'restart' -# on_crash = 'destroy' -# -# restart = 'always' means on_poweroff = 'restart' -# on_reboot = 'restart' -# on_crash = 'restart' -# -# restart = 'never' means on_poweroff = 'destroy' -# on_reboot = 'destroy' -# on_crash = 'destroy' - -#on_poweroff = 'destroy' -#on_reboot = 'restart' -#on_crash = 'restart' - -#============================================================================ - -# Device Model to be used -device_model = 'qemu-dm' - -#----------------------------------------------------------------------------- -# boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d) -# default: hard disk, cd-rom, floppy -#boot="cda" - -#----------------------------------------------------------------------------- -# write to temporary files instead of disk image files -#snapshot=1 - -#---------------------------------------------------------------------------- -# enable SDL library for graphics, default = 0 -sdl=0 - -#---------------------------------------------------------------------------- -# enable OpenGL for texture rendering inside the SDL window, default = 1 -# valid only if sdl is enabled. -opengl=1 - -#---------------------------------------------------------------------------- -# enable VNC library for graphics, default = 1 -vnc=1 - -#---------------------------------------------------------------------------- -# address that should be listened on for the VNC server if vnc is set. -# default is to use 'vnc-listen' setting from -# auxbin.xen_configdir() + /xend-config.sxp -#vnclisten="127.0.0.1" - -#---------------------------------------------------------------------------- -# set VNC display number, default = domid -#vncdisplay=1 - -#---------------------------------------------------------------------------- -# try to find an unused port for the VNC server, default = 1 -#vncunused=1 - -#---------------------------------------------------------------------------- -# set password for domain's VNC console -# default is depents on vncpasswd in xend-config.sxp -vncpasswd='' - -#---------------------------------------------------------------------------- -# no graphics, use serial port -#nographic=0 - -#---------------------------------------------------------------------------- -# enable stdvga, default = 0 (use cirrus logic device model) -stdvga=0 - -#----------------------------------------------------------------------------- -# serial port re-direct to pty deivce, /dev/pts/n -# then xm console or minicom can connect -serial='pty' - -#---------------------------------------------------------------------------- -# tsc_mode : TSC mode (0=default, 1=native TSC, 2=never emulate, 3=pvrdtscp) -# emulate TSC provides synced TSC for all vcpus, but lose perfomrance. -# native TSC leverages hardware's TSC(no perf loss), but vcpu's TSC may lose -# sync due to hardware's unreliable/unsynced TSC between CPUs. -# default intelligently uses native TSC on machines where it is safe, but -# switches to emulated if necessary after save/restore/migration -# pvrdtscp is for intelligent apps that use special Xen-only paravirtualized -# cpuid instructions to obtain offset/scaling/migration info and maximize -# performance within pools of machines that support the rdtscp instruction -tsc_mode=0 - -#----------------------------------------------------------------------------- -# Qemu Monitor, default is disable -# Use ctrl-alt-2 to connect _______________________________________________ Xen-changelog mailing list Xen-changelog@xxxxxxxxxxxxx http://lists.xensource.com/xen-changelog

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.