similar to: what's wrong with using the qemu monitor with kvm/libvirt?

On Mon, Nov 10, 2014 at 06:54:58PM -0700, Min Du wrote: > Hi Kashyap, > > Thanks for the reply. > > >> > >> Now for some reason, I need to add “ -qmp tcp:127.0.0.1:1235” when > >> creating a KVM VM using libvirt. > > > > You might need to elaborate how exactly you're doing this. > > I wanted to add “-qmp tcp:127.0.0.1:1235” when

On Fri, Nov 07, 2014 at 03:28:57PM -0700, Min Du wrote: > Hi, > > Now for some reason, I need to add “ -qmp tcp:127.0.0.1:1235” when > creating a KVM VM using libvirt. You might need to elaborate how exactly you're doing this. > This command meaning in “qemu-kvm --help” is: -qmp dev like > -monitor but opens in 'control' mode. The above is used if you want

Hi Daniel, Thanks. The debugger program I used is a multi-level debugging tool called StackDB developed in our department. It was developed for Xen initially, and KVM support was only added recently. I've forwarded your email to the developer and hopefully it should be pretty straightforward to do so. Best Regards, Min On Nov 11, 2014, at 2:32 AM, Daniel P. Berrange

Hi Kashyap, Thanks for the reply. >> >> Now for some reason, I need to add “ -qmp tcp:127.0.0.1:1235” when >> creating a KVM VM using libvirt. > > You might need to elaborate how exactly you're doing this. I wanted to add “-qmp tcp:127.0.0.1:1235” when creating VM because I was using a multi-level debugger which needs this option to get more information of the VM

On Tuesday, 27 November 2018 12:17:52 CET Richard W.M. Jones wrote: > On Tue, Nov 27, 2018 at 11:13:12AM +0000, Daniel P. Berrangé wrote: > > On Tue, Nov 27, 2018 at 11:59:08AM +0100, Pino Toscano wrote: > > > We ship our own copy of it, so we do not need the external version. > > > (Also, the latest upstream version of ocaml-libvirt was already not > > > usable

Hi, Now for some reason, I need to add “ -qmp tcp:127.0.0.1:1235” when creating a KVM VM using libvirt. This command meaning in “qemu-kvm --help” is: -qmp dev like -monitor but opens in 'control' mode. I added command-line equivalent options into the xml file, like below format: <qemu:commandline> <qemu:arg value="-s"/> <qemu:arg

Hi, are some days that i'm searching for a possible bug in libvirt. I use Solusvm control panel to manage my kvm VM. If i start a vm it will be shown correctly as Running. After some days i found that libvirt show same vm as shut off, but this is not true. I still see login to vm, join in ssh, join in vnc etc. If i want to show correct state i need to power off the VM and boot it again. this

On Sun, May 05, 2019 at 02:23:22PM +0300, Pasi K?rkk?inen wrote: > Hello, Thanks for the bug report. > While testing Virt-SIG Xen 4.12 rpms on CentOS7 I noticed the following problem with libvirt/virt-manager when manually installing a new HVM guest from virt-manager GUI.. basicly the VM installation won't start, because libvirt/virt-manager is not able to start the VM, due to

System: CentOS Linux release 6.0 (final) Kernel: 2.6.32-71.23.1.el6.x86_64 KVM: QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2) Libvirt: ibvirtd (libvirt) 0.8.1 Hi everyone, I only recently subscribed to this list and hope you can shed some light on the following error. I created a VM on my Centos 6 KVM machine, used a qcow2 image and wanted to create a snapshot via 'virsh

Figured I'd test qemu-kvm-1.0.1 and libvirt-0.9.12, but the result after default compiles is: root at black:/usr/local/sbin# ./libvirtd 2012-06-12 19:53:41.894+0000: 6076: info : libvirt version: 0.9.12 2012-06-12 19:53:41.894+0000: 6076: warning : ebiptablesDriverInit:4084 : Could not find 'ebtables' executable 2012-06-12 19:53:42.675+0000: 6076: error : qemuCapsComputeCmdFlags:1209

There was an interesting note in a recent fedoraproject.org newsletter regarding Redhat's legal views on referring to others' trademarks. Since the comments are lengthy, they are not reproduced here and are available at the links below. FWN/Issue161: http://fedoraproject.org/wiki/FWN/Issue161#Legal Callaway note:

(I'm sorry, I didn't find my original message but I provide the archive link: https://www.redhat.com/archives/libvirt-users/2015-January/msg00069.html ) I just tried the latest libvirt release (1.2.12), combined with the following qemu EL6 package from centos: qemu-kvm-0.12.1.2-2.448.el6_6.x86_64 Using 1.2.12 and this version of qemu-kvm, I still get the following error when trying to

Kashyap Chamarthy <kchamart@redhat.com> schreef op 19 januari 2015 19:00:23 CET: >[Dropping libvir list and adding libvir-users list.] > >On Mon, Jan 19, 2015 at 04:12:46PM +0100, liedekef@telenet.be wrote: >> Hi all, >> >> I had libvirt 1.2.10 running without issues together with the qemu >package >> qemu-kvm-0.12.1.2-2.415.el6_5.14.x86_64.rpm >

Hello, While testing Virt-SIG Xen 4.12 rpms on CentOS7 I noticed the following problem with libvirt/virt-manager when manually installing a new HVM guest from virt-manager GUI.. basicly the VM installation won't start, because libvirt/virt-manager is not able to start the VM, due to "missing" qemu-system-i386 binary: Unable to complete install: 'unsupported configuration:

Hi everyone, I've had instances where qemu-kvm process dies and become a zombie. At that state, libvirtd reports the instance to be running and I can't restart the VM because libvirtd fails to kill the qemu-kvm process. Finding the root cause of that is a topic for another day. I also see this line in logs: Jun 15 13:36:57 d12566 libvirtd: 10424: warning : virKeepAliveTimerInternal:156 :

On 04/20/2015 08:45 PM, Matthew Schumacher wrote: > List, > > I was under the impression that I could restart libvirtd without it > destroying my VMs, but am not finding that to be true. If not, then something is wrong. > When I killall > libvirtd then my VM's keep running, but then when I start libvirtd it > calls qemuDomainObjEndJob:1542 : Stopping job: modify

On 04/21/2015 05:53 PM, Matthew Schumacher wrote: > On 04/20/2015 05:42 PM, Laine Stump wrote: >> Well, this is when the qemu process is killed (I'm pretty clever, eh? :-) >> >> I have 3 questions: >> >> 1) what version of libvirt are you running and on what distro? >> >> 2) can you reproduce this reliably? >> >> 3) If the answer to 2 is

Hi, I currently have a couple of Debian KVM servers with all a different version of kvm or qemu-kvm. I can live migrate a guest OS from one server to the other just fine, as long as the version of qemu-kvm is the same. However, when I try to migrate a guest to a server running a newer (or older) version of qemu-kvm, I run into problems. I think this is because the xml configuration differs

On 04/28/2015 06:03 PM, Matthew Schumacher wrote: > > On 04/22/2015 08:19 AM, Laine Stump wrote: >> If you're compiling yourself, then you should be all set to run under >> gdb. libvirt-debuginfo is just a separate subpackage that contains all >> the symbol and line number info from the build so that backtraces in >> gdb make sense. Try attaching gdb to the

Hi, can anyone give an example for a pointopoint routed setup? i.e. each virtual machine has one ip with pointopoint config to the host machine, on a private interface - thus the virtual machines can only talk to the host, which routes them and can use normal iptables for filtering all traffic. with xen this was a simple script doing ifconfig ${vif} ${main_ip} netmask 255.255.255.255 up ip