- 03 8月, 2017 2 次提交
-
-
由 Daniel P. Berrange 提交于
The HTML5 doctype is simply <!DOCTYPE html> no DTD is present because HTML5 is no longer defined as an extension of SGML. XSL has no way to natively output a doctype without a public or system identifier, so we have to use an <xsl:text> hack instead. See also https://dev.w3.org/html5/html-author/#doctype-declarationSigned-off-by: NDaniel P. Berrange <berrange@redhat.com>
-
由 Daniel P. Berrange 提交于
The 'name' attribute on <a...> elements is deprecated in favour of the 'id' attribute which is allowed on any element. HTML5 drops 'name' support entirely. Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
-
- 29 6月, 2017 1 次提交
-
-
由 Roman Bogorodskiy 提交于
- Add a news entry - Update driver's page with information about the new vgaconf attribute and provide usage example; while here, fix a grammar mistake Signed-off-by: NRoman Bogorodskiy <bogorodskiy@gmail.com> Reviewed-by: NAndrea Bolognani <abologna@redhat.com>
-
- 01 4月, 2017 1 次提交
-
-
由 Roman Bogorodskiy 提交于
USB tables -> USB tablet.
-
- 30 3月, 2017 1 次提交
-
-
由 Roman Bogorodskiy 提交于
- Add a news entry - Update the driver page with documentation of the new options and some examples
-
- 14 3月, 2017 1 次提交
-
-
由 Roman Bogorodskiy 提交于
Add an entry about virt-host-validate bhyve support and update the driver's page.
-
- 13 2月, 2017 1 次提交
-
-
由 Roman Bogorodskiy 提交于
* Add bhyve e1000 support entry to release notes * Update the bhyve driver page with usage sample
-
- 14 11月, 2016 1 次提交
-
-
由 Michal Privoznik 提交于
The <pre/> section is rendered as-is on the page. That is, if all the lines are prefixed with 4 spaces the rendered page will also have them. Problem is if we put a box around such <pre/> because the content might not fix into it. Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
-
- 23 7月, 2015 1 次提交
-
-
由 Roman Bogorodskiy 提交于
-
- 13 11月, 2014 1 次提交
-
-
由 Conrad Meyer 提交于
Rather than just picking the first CD (or failing that, HDD) we come across, if the user has picked a boot device ordering with <boot order=''>, respect that (and just try to boot the lowest-index device). Adds two sets of tests to bhyve2xmlargv; 'grub-bootorder' shows that we pick a user-specified device over the first device in the domain; 'grub-bootorder2' shows that we pick the first (lowest index) device.
-
- 12 11月, 2014 1 次提交
-
-
由 Conrad Meyer 提交于
We still default to bhyveloader(1) if no explicit bootloader configuration is supplied in the domain. If the /domain/bootloader looks like grub-bhyve and the user doesn't supply /domain/bootloader_args, we make an intelligent guess and try chainloading the first partition on the disk (or a CD if one exists, under the assumption that for a VM a CD is likely an install source). Caveat: Assumes the HDD boots from the msdos1 partition. I think this is a pretty reasonable assumption for a VM. (DrvBhyve with Bhyveload already assumes that the first disk should be booted.) I've tested both HDD and CD boot and they seem to work.
-
- 18 9月, 2014 1 次提交
-
-
由 Roman Bogorodskiy 提交于
- docs/formatstorage.html.in: document 'zfs' pool type, add it to a list of pool types that could use source physical devices - docs/storage.html.in: update a ZFS pool example XML with source physical devices, mention that starting from 1.2.9 a pool could be created from this devices by libvirt and in earlier versions user still has to create a pool manually - docs/drvbhyve.html.in: add an example with ZFS pools
-
- 30 7月, 2014 1 次提交
-
-
由 Roman Bogorodskiy 提交于
- mention that one disk and one network limitation is no longer current for 1.2.6 and newer - add 'cdrom' device to the sample domain XML
-
- 02 6月, 2014 1 次提交
-
-
由 Roman Bogorodskiy 提交于
- Document 'domxml-to-native' command - Mention that the nmdm console support needs an appropriate kernel module loaded
-
- 24 4月, 2014 1 次提交
-
-
由 Roman Bogorodskiy 提交于
* Add nmdm type device to domain format documnetation * Add a section about nmdm console usage to the bhyve driver documentation
-
- 02 3月, 2014 1 次提交
-
-
由 Roman Bogorodskiy 提交于
-