I see this bug too on real hardware: Linux epib-genstat3 3.2.0-36-generic #57-Ubuntu SMP Tue Jan 8 21:44:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
This is on a server and showed up after 9 days of uptime. Furthermore, it doesn't only show up when running tail -f, but also keeps libvirt-bin in a restart loop. /var/log/libvirt/libvirtd.log keeps repeating (with a different pid each time of course):
2013-01-30 13:43:35.046+0000: 25431: info : libvirt version: 0.9.8
2013-01-30 13:43:35.046+0000: 25431: error : umlStartup:471 : cannot initialize inotify
2013-01-30 13:43:35.046+0000: 25431: error : virStateInitialize:854 : Initialization of UML state driver failed
2013-01-30 13:43:35.046+0000: 25431: error : daemonRunStateInit:1157 : Driver state initialization failed
Unfortunately, since this is a production server I can't easily reboot with a new kernel...
I see this bug too on real hardware: Linux epib-genstat3 3.2.0-36-generic #57-Ubuntu SMP Tue Jan 8 21:44:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux libvirt/ libvirtd. log keeps repeating (with a different pid each time of course): ize:854 : Initialization of UML state driver failed nit:1157 : Driver state initialization failed
This is on a server and showed up after 9 days of uptime. Furthermore, it doesn't only show up when running tail -f, but also keeps libvirt-bin in a restart loop. /var/log/
2013-01-30 13:43:35.046+0000: 25431: info : libvirt version: 0.9.8
2013-01-30 13:43:35.046+0000: 25431: error : umlStartup:471 : cannot initialize inotify
2013-01-30 13:43:35.046+0000: 25431: error : virStateInitial
2013-01-30 13:43:35.046+0000: 25431: error : daemonRunStateI
Unfortunately, since this is a production server I can't easily reboot with a new kernel...