Bug 834561 - Ability to apply changes made by virt-manager by restarting vm using virsh
Ability to apply changes made by virt-manager by restarting vm using virsh
Status: CLOSED NOTABUG
Product: Virtualization Tools
Classification: Community
Component: libvirt (Show other bugs)
unspecified
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Libvirt Maintainers
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-22 08:28 EDT by karaluh
Modified: 2012-06-25 05:05 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-22 09:58:50 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description karaluh 2012-06-22 08:28:36 EDT
Description of problem:
As in summary. When changes requiring vm restart are made in virt-manager, they should also be applied when restarting the machine using virsh.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Dave Allan 2012-06-22 09:58:50 EDT
Restarting a VM using virsh or virt-manager happens through the same mechanism, so restarting the VM with virsh or virt-manager will have the same effect.  Without more information I can't say why you aren't seeing the results you expect.  You should try describing your situation on the libvirt-users mailing list which will get you the most visibility to people who may be able to offer suggestions.
Comment 2 karaluh 2012-06-25 05:05:37 EDT
(In reply to comment #1)
> Without more information I can't say why you aren't seeing the
> results you expect.

VM is running. I change cache type of the VM's HDD in virt-manager. Dialog box saying, that the change will be applied on the next restart is displayed. I restart the machine using virsh. The change isn't applied.

Note You need to log in before you can comment on or make changes to this bug.