similar to: Re: Feature request? Auto start vm upon next shutdown

Displaying 20 results from an estimated 10000 matches similar to: "Re: Feature request? Auto start vm upon next shutdown"

2020 Jun 21
0
Feature request? Auto start vm upon next shutdown
Sometimes when you change the configuration, this configuration change will only be available after a shutdown. Not to have to monitor when the vm shuts down, to start it again. It could be nice to have libvirt start it one time. Something like: 1. change the network interface of a running guest 2. at the prompt of the virt-manager "Some changes may require a guest shutdown to take
2020 Jun 22
0
RE: Feature request? Auto start vm upon next shutdown
It is not a destroy. With some hardware changes you require the host to shutdown down and then start. The shutdown down is manually given either via some acpi request or from within the guest. When the guest is down, the 'host' recognizes this guest requires a one time start, and starts it. This should 'solve' that if you change hardware you have to wait for the guest to
2018 Jan 11
0
Re: VM migration upon shutdown in centos 7
[Please keed the list CCed] On 01/10/2018 04:43 PM, Raman Gupta wrote: >> Does this command alone succeed? > Yes. I have used this command to migrate VMs successfully, without even > knowing that spelling has changed. > > >> I don't know enough about systemd but maybe it's not waiting for virsh to > finish? > Yes I also think virsh or libvirtd or related
2013 Sep 30
2
Unable to start libvirt_lxc domain a second time after shutdown
Hi, I'm unable to start a lxc domain again after shutting it down. Something doesn't seem to "clean up" the socket file (and probably more), as the error message says "Unable to start Domain: Failed to connect socket to '/var/run/libvirt/lxc/test.sock': Connection refused." I can create a domain with the same config as the one thats shutted down, but with
2018 Jan 12
1
Re: VM migration upon shutdown in centos 7
Hi, > I don't see your service being called. It started when system started, see logs: Jan 12 14:59:42 desktop4 systemd: systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN) Jan 12 14:59:42 desktop4 systemd: Detected architecture x86-64. Jan 12 14:59:42 desktop4
2010 May 15
1
XML-Created domain vanishes after shutdown
Hi, im migrating existing kvm-images into libvirt domains, by creating a domain in virsh from a xml file. The domain starts, is working fine, but after shutdown it is lost, and I have to recreate it. BTW, can I reset the domain count somewhere? Any ideas? thx and kind regards Alexander virsh # version Compiled against library: libvir 0.4.6 Using library: libvir 0.4.6 Using API: QEMU 0.4.6
2018 Jan 05
4
VM migration upon shutdown in centos 7
Hi, I have CentOS 7, two node system which allows live VM migration between them. Live migration triggered from virsh is happily happening. I am using GlusterFS for replicating VM disk files. Now I want to automatically do the live migration at the time of reboot/shutdown/halt of the host node and for this I have written a systemd service unit [vPreShutdownHook.service] and placed the live
2017 Feb 27
2
shutdown -r now hangs in qemu-/kvm-vm
Since updating app-emulation/libvirt and/or app-emulation/qemu (both were updated at the same time) I have a problem executing "shutdown -r now" in the vm ("shutdown -h now" works fine). When I execute "shutdown -r now" in the vm the shutdown process runs perfect until "Remounting root-filesystem readonly" and than it hangs and I have to "Force Power
2009 May 27
0
VM start failed - How to debug?
Hello List, when i try to create a domU i get: xm create www1.cfg Using config file "/etc/xen/www1.cfg". Error: Creating domain failed: name=www1 Error Log: ---------------- [2009-05-27 15:00:31 5237] DEBUG (XendDomainInfo:92) XendDomainInfo.create([''vm'', [''name'', ''www1''], [''memory'', ''1024''],
2019 Apr 26
1
Re: 5.2.0 xen and maxGrantFrames
error: Failed to create domain from /etc/libvirt/libxl/satan_pvh.xml error: internal error: libxenlight failed to create new domain 'satan.chao5.int' and with an other domU with this config: <domain type='xen'> <name>abaddon.chao5.int</name> <uuid>2ebe8981-b443-4052-a996-22f377c19cc6</uuid> <memory
2017 Jul 22
2
Increasing video memory available to Windows
Hi, I have a fedora25 system with a Windows10 host and would like to use it for photoshop. However, it complains the video memory is too low. I'm using the QXL driver and it appears to be limited to 256MB? I've installed the Red Hat QXL driver in Windows. I have 4GB of memory allocated overall, and could allocate more if necessary. How do I increase the available video memory? Photoshop
2011 May 01
2
can't up the eth in the vm and access to network
Hi, I encounter a problem that the eth can't be up in the VM by using VT-d. I boot the VM using "virsh create vt_d.xml". The VM could recongize the NIC which was assigned .then I do in VM as follows: #cat /sys/class/net/eth0/operstate down #ifconfig eth0 up #cat /sys/class/net/eth0/operstate down #ficonfig eth 10.100.0.5 #cat /sys/class/net/eth0/operstate down more system
2012 Jan 09
0
KVM VM crash under I/O load (e1000 and virtio)
I'm pretty consistently getting crashed KVM VMs under network I/O load when using the e1000 and virtio NIC models, with the follow message in dmesg: qemu-kvm[8785]: segfault at d0 ip 00000031e3200a08 sp 0000000047784080 error 4 in libnvidia-tls.so.285.05.23[31e3200000+3000] qemu-kvm[8791]: segfault at d0 ip 00000031e3200a08 sp 0000000049f89080 error 4 in
2011 Mar 12
1
Issue creating vm channel
Hello, I am trying to create a lucid guest VM with a vmchannel between the guest and the hypervisor. Details below: KERNEL: # uname -a Linux saurav-desktop 2.6.38-2-generic #29~lucid1-Ubuntu SMP Mon Feb 7 13:35:14 UTC 2011 i686 GNU/Linux QEMU: # /usr/bin/qemu --version QEMU emulator version 0.13.0, Copyright (c) 2003-2008 Fabrice Bellard LIBVIRT: # /usr/sbin/libvirtd --version
2008 Jul 03
1
VM does not reboot
Hello, yesterday a coworker had to reboot one VM, the Vm did shutdown but never came back up. We are USing CentOS 5.1 and XEN xen-3.0-x86_64. What can be the reason of this behavior? Here ist the part of the logfile: [2008-07-02 15:04:18 xend.XendDomainInfo 31150] INFO (XendDomainInfo:947) Domain has shutdown: name=auto-input-vm1 id=26 reason=reboot. [2008-07-02 15:04:18 xend.XendDomainInfo
2009 Sep 30
1
Problems with creating VM
Hi. I try to create VM in oVirt interface. New VM failed to start In oVirt interface Tasks log: Error creating virtual machine: Error: Error creating new domain (virDomainCreate). Subsystem qemu: internal error unable to start guest: bind(unix:/var/lib/libvirt/qemu/test.monitor): Permission denied qemu: could not open monitor device 'unix:/var/lib/libvirt/qemu/
2016 Mar 01
0
Re: which is the config file for a vm ?
On 01.03.2016 14:57, Lentes, Bernd wrote: > Hi, > > i have a weird problem. I have a vm (KVM) which seems to run fine. I believe the respective config file for this vm is /etc/libvirt/qemu/MausDB.xml. This is it: > > ========================================================= > <domain type='kvm'> > <name>MausDB</name> >
2012 Aug 16
0
vm pxe fail
Hallo I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips. on the physical
1998 Oct 20
0
Auto-restart/auto-shutdown feature idea
Here are some thoughts about a possible enhancement to samba. Let me know what yuou think. Whenever I want to re-start samba, for example to upgrade it, there always seem to be people logged in with files open. It occured to me therefore that an auto-restart feature may be useful. To implement this though we need to know when it is safe to re-start samba: 1. When there are no locked
2010 Aug 15
2
trouble launching vm''s
Hello, I must be missing something very very basic. Because I am having trouble launching some vm''s that I recently built whereas I don''t have any problem at all launching some older images I made in very much the same way! First there is vm01 which works just fine: [root@lcent5-1:/etc/xen]$:xm create vm01 Using config file "./vm01". Started domain vm01