Search results

From Xen
  • * <code>--reroll-count|-v</code> (e.g. <code>-v 2</code>): If you store your patches in '''one directory''' with different V: xen-maintainers-1
    39 KB (6,315 words) - 10:01, 9 November 2022
  • # iptables -L -n -v # iptables -t nat -L -n -v
    17 KB (2,507 words) - 13:33, 24 September 2012
  • * '''Select ""RHEL Server Optional (v. 6 64-bit x86_64)" channel.''' Some required packages are '''only''' available in the "RHEL Server Optional (v. 6 64-bit x86_64)" channel. '''Failing to add that channel means you won't
    29 KB (4,239 words) - 03:45, 26 February 2015
  • After altering the file, run 'mkinitrd -v --depmod /boot/<initrd image name> <2.6.31-and-higher>' and verify
    5 KB (739 words) - 11:23, 30 January 2012
  • <pre>xl [-v] block-attach <Domain> <BackDev> <FrontDev> [<Mode>] [BackDomain]</pre> ...ach</code> to release the block device. Looking at the syntax - <code>xl [-v] block-detach <Domain> <DevId></code>, something like <code>xl block-detach
    5 KB (816 words) - 18:53, 27 November 2011
  • CPU hardware virtualization extensions (Intel VT, AMD-V) are required for running Xen HVM guests (=Windows). Xen PCI passhtru to H
    21 KB (3,184 words) - 14:37, 11 September 2012
  • ...[http://www.supermicro.nl/products/motherboard/xeon/c216/x9sae-v.cfm X9SAE-V] (BIOS >= 2.0a required.) ** ASUS Crosshair V Formula (reported working by Pavel Matěja)
    23 KB (3,519 words) - 23:32, 27 December 2023
  • * CPU Virtualization extensions are called Intel VT-x or AMD-V and they are required for running Xen HVM guests. Xen requires CPU virtualization support/extensions (Intel VT, AMD-V) for running HVM guests (=Windows). Virtualization support needs to be enab
    43 KB (7,072 words) - 03:05, 26 March 2015
  • (`v->processor`) and, if it was, we send a remote request to go through the ...iles/slides/Faggioli_XenSummit.pdf slides], [https://www.youtube.com/watch?v=c537IiKzw6U video])
    36 KB (6,041 words) - 08:23, 18 July 2017
  • wodim -v livecd-xen-3.2-0.8.2-i386.iso<br> wodim -v livecd-xen-3.2-0.8.2-amd64.iso<br>
    5 KB (851 words) - 22:29, 25 June 2012
  • ...fairly good estimate of aggregate usage for all VCPUs of a VM; pressing '''V''' reveals how many seconds were spent in which VM's VCPU. Running VCPU mea
    43 KB (7,032 words) - 14:21, 30 April 2014
  • ...opt/xensource/libexec/vncterm-wrapper, variable is export VNCTERM_LISTEN="-v 127.0.0.1:1".
    9 KB (1,475 words) - 12:48, 25 November 2016
  • ..." is the PCI ID of the VGA graphics adapter, you can check it with "lspci -v" in dom0.
    14 KB (2,251 words) - 18:07, 29 June 2022
  • ...In particular, it is preferable to use OCaml objects rather than building v-tables by hand.
    14 KB (2,379 words) - 13:09, 11 July 2013
  • The universal variable v would escape its scope
    10 KB (1,679 words) - 13:41, 5 January 2017
  • ...onsider running all xl commands with the global "-v" option e.g. <code>xl -v create <create-options></code>. Also please include the output of the follo
    7 KB (1,225 words) - 10:30, 27 October 2017
  • ...OS querying the CPUID's where the Xen signatures live, but then the Hyper-V signatures are there too and I don't know when Windows queries those. Possi
    12 KB (2,089 words) - 18:07, 2 February 2017
  • | do VTi, AMD-V run HVMs properly?
    10 KB (1,264 words) - 11:53, 28 May 2012
  • ...owiki>-d</nowiki></code> <code><nowiki>-i 6</nowiki></code> <code><nowiki>-v</nowiki></code> <code><nowiki>-b 256k</nowiki></code> <code><nowiki>1g</now
    4 KB (496 words) - 11:54, 28 May 2012
  • tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    8 KB (1,417 words) - 21:38, 21 June 2015

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)