search for: shutoff

Hi Libvirt, Is there a command that performs the same operation as blockpull while a domain is shutoff? I have a backing chain base <-- A <-- B that I would like to shorten to base <-- B It seems like blockpull B, setting --base <path-to-base> does this, but only when the domain is running. Thanks! Sincerely, Roger Jin -------------- next part -------------- An HTML attachment...

hi alll.. i want to find the xen domain''s state using xm domstate command, domstate command works fine inside virish but when i try with xm like [xm domestate VM_NAME] its giving an error saying subcomand domestate not found. i just want to shutoff the xen virtual domains using a scrip to take backup. so i just want to make sure that the domain are shutdown successfully after the xm shutdown command. can anyone help me pls. thanks in Advance.

...cing an issue with libvirt w.r.t a guest's state and reason code. Precisely following are steps: 1. I have a running guest named *linux-test *on KVM 2. I do a * $> virsh save linux-test linux-saved.dat* 3. At this point * $> virsh domstate --reason linux-test *shows *shutoff(saved)* 4. I restarted the libvirtd daemon * $>systemctl restart libvirtd* 5. Now when I check for the domain state, * $> virsh domstate --reason linux-test *it reads *shutoff(unknown)* >From what I understand: The reason code for a particular state is maintained in-mem...

...t internally it is divided by 60, using integer division, to get the number of minutes. I said the following in a prior message about a different Cyber Power UPS model: === When I specify a 59 second delay on the command line, the UPS shuts off immediately. 59 second delay specified - immediate shutoff 60 second delay specified - exactly one minute delay, then shutoff 80 second delay specified - exactly one minute delay, then shutoff 115 second delay specified - exactly one minute delay, then shutoff 128 second delay specified - exactly two minute delay, then shutoff So if I had to guess,...

"Daniel P. Berrange" <berrange@redhat.com> writes: > On Fri, Mar 17, 2017 at 11:55:13AM +0100, Milan Zamazal wrote: >> Hi, we experienced a strange, non-reproducible error after a successful >> migration to another host. When we called virDomainDestroyFlags with >> VIR_DOMAIN_DESTROY_GRACEFUL flag after the migration on the source host, >> we got

...t internally it is divided by 60, using integer division, to get the number of minutes. I said the following in a prior message about a different Cyber Power UPS model: === When I specify a 59 second delay on the command line, the UPS shuts off immediately. 59 second delay specified - immediate shutoff 60 second delay specified - exactly one minute delay, then shutoff 80 second delay specified - exactly one minute delay, then shutoff 115 second delay specified - exactly one minute delay, then shutoff 128 second delay specified - exactly two minute delay, then shutoff So if I had to guess,...

...nd permissions of volume files in such a way that a standard user cannot access them, even if it is member of the 'libvirt' group. While the VM is running, volume file permissions are like this: -rw-r----- 1 libvirt-qemu kvm [...] /var/lib/libvirt/images/YourVmDisk.qcow2 When the VM is shutoff: -rw-r----- 1 root root [...] /var/lib/libvirt/images/YourVmDisk.qcow2 The trouble is, I want to access that .qcow2 file when the VM is shutoff. I would really like not to run my script as root. I could not find a way to specify the permissions for the .qcow2 files, so I tried editing the gro...

...issue is first deleting the snapshot and my understanding of what its saying. So here is some basic info: # virsh snapshot-list host1 Name Creation Time State ------------------------------------------------------------ snap1-host1 2014-01-19 16:59:10 +1100 shutoff # # virsh snapshot-info host1 --current Name: snap1-host1 Domain: host1 Current: yes State: shutoff Location: internal Parent: - Children: 0 Descendants: 0 Metadata: yes So I try and delete it: # virsh snapshot-delete host1 --curren...

...h different versions of libvirt (0.7.5 and 0.7.7), with a kvm (WinXP), host running Ubuntu 9.10, and i would like to ask you two questions: - In virsh, after running the command "shutdown domainName", what should be the final state of the domain, if the shutdown finishes correctly: "shutoff", "no-state", "inactive", or the domain shouldn't show in "list --all" (full clean-up)? - After the command "shutdown domainName", should i be able to run the command "start domainName", without first defining the domain? (i.e.: does shutd...

...stand > that RHEL 6.x tends to not support internal snapshots. [ … ] >> # virsh snapshot-list host1 >> Name Creation Time State >> ------------------------------------------------------------ >> snap1-host1 2014-01-19 16:59:10 +1100 shutoff >> >> # >> # virsh snapshot-info host1 --current >> Name: snap1-host1 >> Domain: host1 >> Current: yes >> State: shutoff >> Location: internal > > So the fact that you created an internal snapshot may h...

On 12/8/2016 10:37 PM, Charles Lepple wrote: > On Dec 8, 2016, at 1:34 PM, Mike wrote: >> >> I didn't want to sign up for the nut-devs list or create a git account >> just to provide this information, so I hope posting this info here is OK... > > Not a problem. (Both lists go into the same mailbox on my end.) The important part is the "HCL" subject so I

...t know the actual setup, but if you have no UPC you shouldn't > > host email > > services anyway. > > I'm guessing you meant UPS, anyway, a UPS wont protect you from human > error. > > Also, most buildings, at least in this country, have a fire emergency > shutoff requirement, meaning mains is isolated from the building, and > the back up gennies are also forbidden to be engaged - UPS's dont last > forever. Guys, please don't argue on kindergarten level. The UPS is for backing a sudden death, but not for running five days. Of course you can...

>> I tested it by pulling the supply to the ups. It got the 'on and then >> the 'low battery' upsmon then shutdown my system. The ups however >> remained on. >the ups shutoff (hardware ups shutdown) seems not to be working. >Carlos might have more ideas on the cause... This might not be a bug - it could be that I reconnected the supply to soon. I say this because I now remember that after testing the shutdown worked the ups remained on so after some time I reconnec...

...f concurrency in libvirt. So it is conceivable that you would see OPERATION_INVALID for a transient guest if libvirt is part way through cleaning it up - it shouldn't be in that state for very long though You'll never see OPERATION_INVALID if the guest is truely running - it will either be shutoff, or in the process of becoming shutoff very soon. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://entangle-photo.org -o- http://search.cpan.org/~danber...

...I don't know if it > was created by a command gone amok or something else. > > # virsh snapshot-list serv1r2 > Name Creation Time State > ------------------------------------------------------------ > snap 2017-01-30 17:01:11 -0500 shutoff > > # virsh snapshot-delete serv1r2 snap --disk-only > error: command 'snapshot-delete' doesn't support option --disk-only > > # virsh snapshot-dumpxml serv1r2 snap > <domainsnapshot> > <name>snap</name> > <state>shutoff</state>...

...n, lvrenaming the storage devices and adjusting the storage path and vm name using "virsh edit". This works fine so far and "virsh list" shows them correctly however virt-manager has gone bonkers and still shows them with the old names and alternating between the status "Shutoff" and "Running" with every display refresh and CPU usage alternating between 0% and 100%. All other VMs on the host are fine and are displayed correctly by virt-manager. Does anybody know what the problem could be and how to fix it? While this issue seems to display related rather...

Hi， I tried QEMU on ARM/PPC platforms. If running poweroff command on guest, it should also shutoff the VM. But it shows the VM status still be 'running' instead of 'shutoff'. I guess it should be qemu issue, is it right? Best Regards, Olivia

...gt;> was created by a command gone amok or something else. >> >> # virsh snapshot-list serv1r2 >> Name Creation Time State >> ------------------------------------------------------------ >> snap 2017-01-30 17:01:11 -0500 shutoff >> >> # virsh snapshot-delete serv1r2 snap --disk-only >> error: command 'snapshot-delete' doesn't support option --disk-only >> >> # virsh snapshot-dumpxml serv1r2 snap >> <domainsnapshot> >> <name>snap</name> >> &lt...