search for: qemudomainobjtaint

hello all, my vm (windows server 2008) keep crashing? 2011-09-21 15:00:45.924: 1355: info : libvirt version: 0.9.6 2011-09-21 15:00:45.924: 1355: error : virSysinfoRead:465 : internal error Failed to find path for dmidecode binary 2011-09-21 15:05:43.873: 1349: warning : qemuDomainObjTaint:1128 : Domain id=1 name='IIS' uuid=a02e41a9-9f4d-d94f-43a6-995b1ca6d37d is tainted: high-privileges 2011-09-21 16:07:10.593: 1344: error : qemuMonitorIO:541 : internal error End of file from monitor Any help would be much appreciated. -- Sincerely, falazemi

...I have trouble starting a VM using virsh start $vm. I do this as root, because as non-root user it did not work at all (especially it failed attaching to the networks). So, when I run the command (with sudo), I get the following error in libvirtd.log: 2014-01-15 07:51:00.423+0000: 16158: warning : qemuDomainObjTaint:1573 : Domain id=5 name='vader' uuid=f5b8c05b-9c7a-3211-49b9-2bd635f7e2aa is tainted: high-privileges 2014-01-15 07:51:00.428+0000: 16158: error : virDBusCallMethod:1173 : Launch helper exited with unknown return code 1 At the same time I get an error in /var/log/messages which seems relat...

when i send a reboot command to libvirtd to reboot a domain, it does not receive and print the following warn: 2013-04-10 06:01:39.080+0000: 2908: warning : qemuDomainObjTaint:1311 : Domain id=56 name='69751ca7-3198-4f3c-8265-cb8cb70ad750' uuid=69751ca7-3198-4f3c-8265-cb8cb70ad750 is tainted: high-privileges what's the problem??? thanks a lot.:) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman....

...result : Migration: [ 61 %]error: operation failed: migration job: unexpectedly failed os/kernel version: centos 6.7 / kernel 2.6.32 qemu-kvm version : 0.12.1.2 libvirt version : 0.10.2-54 the libvirt.log on target host: 2018-05-22 11:45:38.603+0000: 32314: warning : qemuDomainObjTaint:1459 : Domain id=30 name='instance-00001959' uuid=41975d30-2490-473e-be7b-9d2d08bf66d2 is tainted: high-privileges 2018-05-22 11:45:38.883+0000: 32314: warning : qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async job owner; entering monitor without asking for a n...

when i send a reboot command to libvirtd to reboot a domain, it does not receive and print the following warn:2013-04-10 06:01:39.080+0000: 2908: warning : qemuDomainObjTaint:1311 : Domain id=56 name='69751ca7-3198-4f3c-8265-cb8cb70ad750' uuid=69751ca7-3198-4f3c-8265-cb8cb70ad750 is tainted: high-privileges what's the problem??? thanks a lot. > From: libvirt-users-request at redhat.com > Subject: libvirt-users Digest, Vol 40, Issue 24 > To: libvirt...

...less than 2 seconds on other machines. This is not normal, so I turned on the debug log for libvirtd. I analyzed the log and found that the time was spent on libvirtd calling qemu. Thread 95225 calls the qemuProcessLaunch interface at 14:22:30.129 and then builds the emulator command line, but the qemuDomainObjTaint method is called after 10 seconds. I tried to analyze the qemuProcessLaunch function to find the reason, but nothing was found. What is the cause? Below some information about my hypervisor: [root@node1 datapool]# virsh -v 3.4.0 [root@node1 datapool]# qemu-x86_64 --version qemu-x86_64 version 2.9.0...

...el 2.6.32 > qemu-kvm version : 0.12.1.2 > libvirt version : 0.10.2-54 These are very ancient versions. I wouldn't be surprised if you upgrade and find out the problem is fixed. > > the libvirt.log on target host: > 2018-05-22 11:45:38.603+0000: 32314: warning : qemuDomainObjTaint:1459 > : Domain id=30 name='instance-00001959' > uuid=41975d30-2490-473e-be7b-9d2d08bf66d2 is tainted: high-privileges > 2018-05-22 11:45:38.883+0000: 32314: warning : > qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async > job owner; entering monit...

...oRead:767 : internal > error Failed to find path for dmidecode binary > 2012-07-08 22:45:17.710+0000: 3764: error : > virConnectNumOfInterfaces:10466 : this function is not supported by the > connection driver: virConnectNumOfInterfaces > 2012-07-08 22:46:13.494+0000: 3764: warning : qemuDomainObjTaint:1371 : > Domain id=1 name='AED-VM' uuid=8f2892d8-df3c-6e75-0fe5-42c1ecd7835d is > tainted: high-privileges > 2012-07-08 22:46:13.725+0000: 3762: error : qemuMonitorIORead:526 : Unable > to read from monitor: Connection reset by peer > 2012-07-08 22:46:13.725+0000: 3762: error...

...a VM using virsh start $vm. I do this as root, > because as non-root user it did not work at all (especially it failed > attaching to the networks). So, when I run the command (with sudo), I > get the following error in libvirtd.log: > > 2014-01-15 07:51:00.423+0000: 16158: warning : qemuDomainObjTaint:1573 > : Domain id=5 name='vader' uuid=f5b8c05b-9c7a-3211-49b9-2bd635f7e2aa > is tainted: high-privileges This usually means that libvirt has been configured to run the qemu process as root, which introduces the possibility that a guest exploiting some theoretical security exploit in...

...is is relevant, but I also noticed this warning when creating the VM through the test scripts mentioned above: --------------------------------------------------------------------------------------------------------------------------------------------- 2014-01-31 05:41:44.018+0000: 1351: warning : qemuDomainObjTaint:1134 : Domain id=1 name='control-test' uuid=95f2d398-6b98-5359-7597-b0f596aae996 is tainted: high-privileges --------------------------------------------------------------------------------------------------------------------------------------------- I assumed this was a permissions issue,...

...such file or directory Ending snapshot test Wed Apr 29 09:34:37 AKDT 2015 At this point libvirt is confused about which file is the backing store because the first run did pivot after blockcommit, but didn't update the block file. From the logs: 2015-04-29 17:33:41.052+0000: 25192: warning : qemuDomainObjTaint:1972 : Domain id=2 name='test' uuid=4b9cc25b-68d1-4ce8-8a65-2a378e255e36 is tainted: high-privileges 2015-04-29 17:34:37.322+0000: 25191: error : virDomainSnapshotAlignDisks:609 : unsupported configuration: source for disk 'vda' is not a regular file; refusing to generate external s...

...t; EOF Domain ceph defined from /dev/stdin 3. Try to start the guest by virsh # virsh start ceph error: Failed to start domain ceph error: internal error: process exited while connecting to monitor: What I can see from libvirtd log is below: 2015-01-08 08:07:32.376+0000: 22552: warning : qemuDomainObjTaint:1890 : Domain id=19 name='ceph' uuid=e4412366-1f16-4c54-b121-dfb565672427 is tainted: high-privileges Detaching after fork from child process 23015. 2015-01-08 08:07:32.684+0000: 22552: error : qemuMonitorOpenUnix:309 : failed to connect to monitor socket: No such process 2015-01-08 08:0...

...edhat.com> > Content-Type: text/plain; charset=UTF-8 > > On 11.04.2013 10:04, ??? wrote: > > when i send a reboot command to libvirtd to reboot a domain, it does not > > receive and print the following warn: > > > > 2013-04-10 06:01:39.080+0000: 2908: warning : qemuDomainObjTaint:1311 : > > Domain id=56 name='69751ca7-3198-4f3c-8265-cb8cb70ad750' > > uuid=69751ca7-3198-4f3c-8265-cb8cb70ad750 is tainted: high-privileges > > > > with reboot you may choose what mode do you want to use: > 'acpi', 'agent', 'initctl' or...

Hi all: I create VM on most hypervisors very quickly, about 2 seconds. But some hypervisors are slow, taking more than 10 seconds. I started the debug log for libvirtd and found that some threads had timed out. Thread 95205 has two 5-second timeouts, but I don't know why? Below some information about my hypervisor: [root@node1 datapool]# virsh -v 3.4.0 [root@node1 datapool]# qemu-x86_64