On Wed, May 21, 2008 at 04:30:02PM +0100, Daniel P. Berrange wrote: > On Wed, May 21, 2008 at 10:59:28AM -0400, Daniel Veillard wrote: > > On Fri, May 16, 2008 at 10:47:40PM +0100, Daniel P. Berrange wrote: > > > If the KVM instance does not support the 'thread_id' data in 'info cpus', > > > we simply print out a suitable error message. We detect the mapping at > > > startup and cache it thereafter. > > > > Hum, okay, seems that should work just fine even if one migrates or > > save/restore. > > Is the error reported each time one starts a new VM ? > > Sorry, was slightly misleading. We detect the mapping at startup and > cache it, but don't print any errors at that point if it is not supported. > Only when someone runs virDomainPinVcpu()/virDomainGetVcpus() will they > get an error message. ah, okay, yeah makes more sense :-) Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard@xxxxxxxxxx | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list