User Tools

Site Tools


unix:virtualization:virtlib:quickreference

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
unix:virtualization:virtlib:quickreference [2021/11/19 23:22] rodolicounix:virtualization:virtlib:quickreference [2022/03/05 14:58] rodolico
Line 127: Line 127:
  
 This also allows you to execute //qemu-agent-command// from within //virsh//, but this is strongly discouraged unless you have researched what is going on. Any changes you make can cause instability in libvirt, since they are bypassing virsh. Kind of like using hdparm, where you can do Really Bad Things to your hard disk if you don't know for sure what you are doing. Do what you want, but be careful. This also allows you to execute //qemu-agent-command// from within //virsh//, but this is strongly discouraged unless you have researched what is going on. Any changes you make can cause instability in libvirt, since they are bypassing virsh. Kind of like using hdparm, where you can do Really Bad Things to your hard disk if you don't know for sure what you are doing. Do what you want, but be careful.
 +
 +==== Using save/restore ====
 +
 +An alternative is to use //virsh save// to shut down and //virsh restore// to recover. In this case, use
 +<code bash>
 +virsh save domainname /path/to/save/image
 +</code>
 +to save the image. It will suspend the virtual, then save processor/memory/whatever to the file /path/to/save/image.
 +
 +Once this is done, you can do whatever you needed to do, then use the following command to restore it.
 +<code bash>
 +virsh restore /path/to/save/image
 +</code>
  
 ==== Windows servers will not restart ==== ==== Windows servers will not restart ====
unix/virtualization/virtlib/quickreference.txt · Last modified: 2023/02/26 17:12 by rodolico