search for: qemu_monitor

...Yes you're right, I just blindly started looking for 30s constants in the code and that one seemed the most obvious but I had not tried to trace it all the way back to the domain start job or checked the debug logs yet, sorry. So looking a bit more carefully I see the real issue is in src/qemu/qemu_monitor.c: 321 static int 322 qemuMonitorOpenUnix(const char *monitor, pid_t cpid) 323 { 324 struct sockaddr_un addr; 325 int monfd; 326 int timeout = 30; /* In seconds */ Is this safe to increase? Is there any reason to keep it at 30s given (from what I'm seeing on a fast 2-socket Haswel...

Hi folks, I need to trace how libvirt talk with qemu monitor, log everything when give command, but does anyone know what the format, and how to read the log file? for example: 2014-07-22 17:25:22.984+0000: 18571: debug : qemuMonitorIOProcess:356 : QEMU_MONITOR_IO_PROCESS: mon=0x7f733c000a40 buf={"timestamp": {"seconds": 1406049922, "microseconds": 983916}, "event": "STOP"} where to find the qemuMonitorIOProcess function, and what :356 means? Thanks very much! Best, Yuanzhen

...arted looking for 30s constants in > > the code and that one seemed the most obvious but I had not tried to > > trace it all the way back to the domain start job or checked the debug > > logs yet, sorry. So looking a bit more carefully I see the real issue > > is in src/qemu/qemu_monitor.c: > > > > 321 static int > > 322 qemuMonitorOpenUnix(const char *monitor, pid_t cpid) > > 323 { > > 324 struct sockaddr_un addr; > > 325 int monfd; > > 326 int timeout = 30; /* In seconds */ > > > > Is this safe to increase? Is th...

...915: warning : qemuProcessEventHandler:4886 : vm: active, event: 6, cost 31.830 secs The threads backtraces is as follows: [Switching to thread 17 (Thread 0x7f12fddf5700 (LWP 32580))] #2 0x00007f12eb26df21 in qemuMonitorSend (mon=mon@entry=0x7f12d0013af0, msg=msg@entry=0x7f12fddf46e0) at qemu/qemu_monitor.c:1075 1075 if (virCondWait(&mon->notify, &mon->parent.lock) < 0) { (gdb) l 1070 PROBE(QEMU_MONITOR_SEND_MSG, 1071 "mon=%p msg=%s fd=%d", 1072 mon, mon->msg->txBuffer, mon->msg->txFD); 1073 1074 while (mon &am...

Hi, all. I want to know when I press run button. start a domain. What is the procedure of libvirt internal. I know it will call virDomainCreate(),then qemuDomainStart() -> qemuDomainStartWithFlags(). what is the next? xuanmao_001 -------------- next part -------------- An HTML attachment was scrubbed... URL:

...t; Hi folks, > > > I need to trace how libvirt talk with qemu monitor, log everything when > give command, but does anyone know what the format, and how to read the log > file? > > for example: > 2014-07-22 17:25:22.984+0000: 18571: debug : qemuMonitorIOProcess:356 : > QEMU_MONITOR_IO_PROCESS: mon=0x7f733c000a40 buf={"timestamp": {"seconds": > 1406049922, "microseconds": 983916}, "event": "STOP"} > > where to find the qemuMonitorIOProcess function, and what :356 means? > Thanks very much! If you have libvirt.git...

...t, I just blindly started looking for 30s constants in > the code and that one seemed the most obvious but I had not tried to > trace it all the way back to the domain start job or checked the debug > logs yet, sorry. So looking a bit more carefully I see the real issue > is in src/qemu/qemu_monitor.c: > > 321 static int > 322 qemuMonitorOpenUnix(const char *monitor, pid_t cpid) > 323 { > 324 struct sockaddr_un addr; > 325 int monfd; > 326 int timeout = 30; /* In seconds */ > > Is this safe to increase? Is there any reason to keep it at 30s given > (...

Hi, Excuse me, I have watched qemu_driver.c where most of the libvirt API is overrided in order to connect qemu. But I am confused which functions then call those qemu_driver API? I mean where is the qemu_driver implementation? Libvirt.c? But how does the qemu_driver connect and control qemu? Thanks a lot! Regards, Corey -------------- next part -------------- An HTML

...ibpthread.so.0 No symbol table info available. #1 0x00007f69c9ee884a in virCondWait (c=<optimized out>, m=<optimized out>) at util/threads-pthread.c:117 ret = <optimized out> #2 0x000000000049c749 in qemuMonitorSend (mon=0x7f69ac0ec0c0, msg=<optimized out>) at qemu/qemu_monitor.c:826 ret = -1 __func__ = "qemuMonitorSend" __FUNCTION__ = "qemuMonitorSend" #3 0x00000000004ac8ed in qemuMonitorJSONCommandWithFd (mon=0x7f69ac0ec0c0, cmd=0x7f6998028280, scm_fd=-1, reply=0x7f69c57829f8) at qemu/qemu_monitor_json.c:230 ret =...

...r 30s constants in >> > the code and that one seemed the most obvious but I had not tried to >> > trace it all the way back to the domain start job or checked the debug >> > logs yet, sorry. So looking a bit more carefully I see the real issue >> > is in src/qemu/qemu_monitor.c: >> > >> > 321 static int >> > 322 qemuMonitorOpenUnix(const char *monitor, pid_t cpid) >> > 323 { >> > 324 struct sockaddr_un addr; >> > 325 int monfd; >> > 326 int timeout = 30; /* In seconds */ >> > >> &g...

....14.x86_64) works just fine though (I also tried the qemu-rhev-packages for el6 from ovirt, but no change). I verified the changelog from libvirt 1.2.12 and the earlier suggested fix is in there (but doesn't seem to change anything): 2015-01-14 Pavel Hrdina <phrdina@redhat.com> qemu_monitor: introduce new function to get QOM path Now, I have activated libvirtd debug and these are the qom-list lines (I can provide the full logfile if wanted): 2015-02-11 14:10:33.259+0000: 13280: debug : virJSONValueToString:1528 : result={"execute":"qom-list","arguments&quot...

...port='1'/> </channel> ``` as requested per the doc (I tried with source=bind to no avail, btw the doc for `source` is not that great) my libvirtd.conf has the following setting ``` log_level = 1 # no filter for now log_filters="1:qemu.qemu_agent 1:qemu.qemu_monitor" # log_filters="3:remote 4:event 3:json 3:rpc" log_outputs="1:file:/var/log/libvirt/libvirtd.log" ``` `journalctl -b -u libvirtd.service` returns ``` avril 17 12:31:05 jedha libvirtd[22804]: 2018-04-17 03:31:05.482+0000: 22806: error : qemuDomainAgentAvailable...

Hi all, In IRC last night Dan helpfully confirmed my analysis of an issue we are seeing attempting to launch high memory KVM guests backed by hugepages... In this case the guests have 240GB of memory allocated from two host NUMA nodes to two guest NUMA nodes. The trouble is that allocating the hugepage backed qemu process seems to take longer than the 30s QEMU_JOB_WAIT_TIME and so libvirt then

.... > as requested per the doc (I tried with source=bind to no avail, btw > the doc for `source` is not that great) > > my libvirtd.conf has the following setting > > ``` > log_level = 1 > # no filter for now > log_filters="1:qemu.qemu_agent 1:qemu.qemu_monitor" > # log_filters="3:remote 4:event 3:json 3:rpc" > log_outputs="1:file:/var/log/libvirt/libvirtd.log" > ``` > > `journalctl -b -u libvirtd.service` returns > > ``` > avril 17 12:31:05 jedha libvirtd[22804]: 2018-04-17 03:31:05.482+0000:...