On Mon, Jul 13, 2015 at 1:22 PM, hw <[email protected]> wrote:
>
> So what happened to the 'hvm' USE flag of the "xen-tools" package?
>
Something is wrong with your repository. The flag is there.
I would suggest that you start by disabling any overlays, and run emerge --sync.
floppym@naomi ~ % equery uses xen-tools
[ Legend : U - final flag setting for installation]
[ : I - package is installed with flag ]
[ Colors : set, unset ]
* Found these USE flags for app-emulation/xen-tools-4.5.1-r1:
U I
- - api : Build the C libxenapi bindings
- - custom-cflags : Build with user-specified CFLAGS (unsupported)
- - debug : Enable extra debug codepaths, like
asserts and extra output. If you
want to get meaningful backtraces see
https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
- - doc : Add extra documentation (API, Javadoc,
etc). It is recommended to
enable per package instead of globally
- - flask : Enable the Flask XSM module from NSA
- - hvm : Enable support for hardware based
virtualization (VT-x,AMD-v)
- - ocaml : Enable support for the ocaml language
- - ovmf : Enable support to boot UEFI guest vm,
needed by hvm
+ + pam : Enable pam support
- - pygrub : Install the pygrub boot loader
- - python : Add optional support/bindings for the
Python language
+ + python_targets_python2_7 : Build with Python 2.7
- - qemu : Enable IOEMU support via the use of qemu-dm
- - screen : Enable support for running domain U
console in an app-misc/screen
session
- - static-libs : Build static versions of dynamic
libraries as well
- - system-qemu : Using app-emulation/qemu instead of
the bundled one
- - system-seabios : Using sys-firmware/seabios instead of
the bundled one
