openkylin
/
libvirt
mirror of https://gitee.com/openkylin/libvirt.git
9
0
Fork 0
Code Issues Projects Releases Wiki Activity

virsh: Tweak attach-* documentation 

as we are missing:
attach-disk: --type can accept 'lun' too, not just cdrom or floppy.
attach-disk: --target specify logical device name, not path
attach-interface: --target silently drops strings with vnet* prefix
This commit is contained in:
Michal Privoznik 2012-06-18 13:14:49 +02:00
parent d97a234c62
commit cc75fcc90f
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
tools/virsh.pod
View File

@ -1586,10 +1586,11 @@ needed if the device does not use managed mode.
[I<--multifunction>] [I<--multifunction>]
Attach a new disk device to the domain. Attach a new disk device to the domain.
I<source> and I<target> are paths for the files and devices. I<source> is path for the files and devices. I<target> controls the bus or
I<driver> can be I<file>, I<tap> or I<phy> for the Xen hypervisor depending on device under which the disk is exposed to the guest OS. It indicates the
the kind of access; or I<qemu> for the QEMU emulator. "logical" device name. I<driver> can be I<file>, I<tap> or I<phy> for the Xen
I<type> can indicate I<cdrom> or I<floppy> as alternative to the disk default, hypervisor depending on the kind of access; or I<qemu> for the QEMU emulator.
I<type> can indicate I<lun>, I<cdrom> or I<floppy> as alternative to the disk default,
although this use only replaces the media within the existing virtual cdrom or although this use only replaces the media within the existing virtual cdrom or
floppy device; consider using B<update-device> for this usage instead. floppy device; consider using B<update-device> for this usage instead.
I<mode> can specify the two specific mode I<readonly> or I<shareable>. I<mode> can specify the two specific mode I<readonly> or I<shareable>.
@ -1614,7 +1615,8 @@ Attach a new network interface to the domain.
I<type> can be either I<network> to indicate a physical network device or I<type> can be either I<network> to indicate a physical network device or
I<bridge> to indicate a bridge to a device. I<bridge> to indicate a bridge to a device.
I<source> indicates the source device. I<source> indicates the source device.
I<target> allows to indicate the target device in the guest. I<target> allows to indicate the target device in the guest. Names starting
with 'vnet' are considered as auto-generated an hence blanked out.
I<mac> allows to specify the MAC address of the network interface. I<mac> allows to specify the MAC address of the network interface.
I<script> allows to specify a path to a script handling a bridge instead of I<script> allows to specify a path to a script handling a bridge instead of
the default one. the default one.