These are not very useful at all, and overly voluminous since the domain
builder switched to using XEN_DOMCTL_{get,set}hvmcontext to construct HVM
domains.
Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com>
---
CC: Jan Beulich <jbeul...@suse.com>
---
xen/common/hvm/save.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/xen/common/hvm/save.c b/xen/common/hvm/save.c
index dd2c547..26b7a4b 100644
--- a/xen/common/hvm/save.c
+++ b/xen/common/hvm/save.c
@@ -173,8 +173,6 @@ int hvm_save(struct domain *d, hvm_domain_context_t *h)
handler = hvm_sr_handlers[i].save;
if ( handler != NULL )
{
- printk(XENLOG_G_INFO "HVM%d save: %s\n",
- d->domain_id, hvm_sr_handlers[i].name);
if ( handler(d, h) != 0 )
{
printk(XENLOG_G_ERR
@@ -247,8 +245,6 @@ int hvm_load(struct domain *d, hvm_domain_context_t *h)
}
/* Load the entry */
- printk(XENLOG_G_INFO "HVM%d restore: %s %"PRIu16"\n", d->domain_id,
- hvm_sr_handlers[desc->typecode].name, desc->instance);
if ( handler(d, h) != 0 )
{
printk(XENLOG_G_ERR "HVM%d restore: failed to load entry %u/%u\n",
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
