search for: xh4

...ore serious. I found this message after disappearance of virtual machine created early. I restart XAPI tool stack and machine was killed (not shutdowned, but completely removing). Here log (from machine where domain was resident) Main line in log file I suspect: [20101026T14:50:09.639Z|debug|cvt-xh4|0 thread_zero|dbsync (update_env) D:634f731b810a|dbsync] killing umanaged domain: 4e118da2-8485-23c9-de75-a6c6862df33c Full log part: [20101026T14:50:09.518Z|debug|cvt-xh4|0 thread_zero|dbsync (update_env) D:634f731b810a|dbsync] updating VM states [20101026T14:50:09.523Z|debug|cvt-xh4|0 thread_z...

Got following message in /var/log/daemon.log: Jul 30 19:45:11 cvt-xh4 xapi: [error|cvt-xh4|5|Starting periodic scheduler D:7c5d1d776763|backgroundscheduler] Logrotate executed with error code: stdout='''' stderr=''error: error renaming /var/log/openvswitch/ovs-vswitchd.log.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1...

Good day. Few month ago I reported bug when vif was added as PIF to database. Now I found way to reproduce this: xe vif-create network-uuid=$NET_UUID vm-uuid=$DOM0_UUID device=1 mac=f4:03:02:01:00:01 xe vif-plug uuid=$NEWVIF_UUID xe pif-scan host-uuid=$HOST_UUID xe pif-list root at lab-xh4:~# xe pif-list uuid ( RO) : 62cdddc5-89ad-38e0-e9af-879df66e409d device ( RO): eth0 currently-attached ( RO): true VLAN ( RO): -1 network-uuid ( RO): 7c83b83f-c356-a22f-3e94-36361d769853 uuid ( RO) : b953d1a0-60...