- Community Home
- >
- Software
- >
- HPE Morpheus Software
- >
- HPE Morpheus VM Essentials Software
- >
- Changes Made via “virsh edit”
Categories
Company
Local Language
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
a week ago
Changes Made via “virsh edit”
Is directly modifying a virtual machine definition (XML) using “virsh edit” an acceptable practice for HVM?
Since I can’t make detailed changes via the Web UI, I’m considering using “virsh edit.” However, I’ve noticed that changes made with “virsh edit” sometimes get reverted when I run the reconfigure menu or similar operations.
I’d also like to know which changes are preserved and which are not—do you happen to know?
*Please note that this is machine translation, so I apologize if it’s unclear.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
a week ago
Re: Changes Made via “virsh edit”
We recommend against making any changes using "virsh edit" because the Morpheus Manager enforces the XML configuration after some operations are done. Examples of such operations could be linked to live migrating a VM or simply power cycling it.
The manager doesn't change every aspect of the XML, for example setting a manual MAC address is not changed.
What type of changes have you found to be reverted?
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
a week ago
Re: Changes Made via “virsh edit”
Thank you.
I had made the following changes, but they reverted when I changed the virtual machine plan.
■Changes made using `virsh edit`
<sound model='ac97'>
↓
<sound model='ich9'>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
Sunday
Re: Changes Made via “virsh edit”
so, if it's not supported/practical to run virsh edit. What's the supported way to edit the xml? persistently?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
yesterday
Re: Changes Made via “virsh edit”
There's no supported way to edit the VMs XML, if the change doesn't persist and it's not something present in the UI, there's no guarantee the change will persist.
What are the use cases you're looking at? I see the Audio device example, but why is something like this needed?
Asking so we can analyze the use cases and make informed decisions
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]