Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TODO: Libvirt: virsh snapshot-create test #152

Closed
chuanchang opened this issue Jan 8, 2013 · 5 comments
Closed

TODO: Libvirt: virsh snapshot-create test #152

chuanchang opened this issue Jan 8, 2013 · 5 comments
Assignees

Comments

@chuanchang
Copy link
Contributor

$ virsh help snapshot-create
NAME
snapshot-create - Create a snapshot from XML

SYNOPSIS
snapshot-create [] [--redefine] [--current] [--no-metadata] [--halt] [--disk-only] [--reuse-external] [--quiesce] [--atomic] [--live]

DESCRIPTION
Create a snapshot (disk and RAM) from XML

OPTIONS
[--domain] domain name, id or uuid
[--xmlfile] domain snapshot XML
--redefine redefine metadata for existing snapshot
--current with redefine, set current snapshot
--no-metadata take snapshot but create no metadata
--halt halt domain after snapshot is created
--disk-only capture disk state but not vm state
--reuse-external reuse any existing external files
--quiesce quiesce guest's file systems
--atomic require atomic operation
--live take a live snapshot

@chuanchang
Copy link
Contributor Author

@cevich, please assign the issue to me firstly.

@chuanchang
Copy link
Contributor Author

@cevich, I just saw we had a virsh_snapshot.py test case, and it has covered many snapshot commands, but it's incompleted not what we want, we need to test and verify more things such as each options and more checkpoints.

@cevich
Copy link
Member

cevich commented Jan 9, 2013

@chuanchang Sure, please feel free to make an additional test or enhance the existing one.

@cevich
Copy link
Member

cevich commented Jan 9, 2013

Adding to tracking issue #64

@ghost ghost assigned chuanchang Jan 10, 2013
@cevich
Copy link
Member

cevich commented May 24, 2013

Since moving to pull-request model, these topic issues are no-longer needed. Thanks.

@cevich cevich closed this as completed May 24, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants