From: Fabien Hermenier <Fabien.Hermenier@emn.fr>
To: Xen-devel@lists.xensource.com
Subject: xenbus api
Date: Thu, 15 Jun 2006 10:30:01 +0200 [thread overview]
Message-ID: <1150360202.21177.7.camel@localhost.localdomain> (raw)
Hello
I have a lot of problem using the xenbus api (in xen-3.0-testing).
I had to modify the network backend driver (file netback.c), and each
call to a xenbus function in a virtual machine make my machine reboot
(not the virtual, the real machine).
for example, I 've add this line of code (wich is useless):
printk("%d",xenbus_exists(XBT_NULL,"/local/domain/0/","domid"));
after a network packet reception.
When I launch my virtual machine, the station reboot after the virtual
machine console log is stopped after this block:
TCP: Hash tables configured (established 8192 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
What do I wrong ? Could I use the xenbus API in the backend (I have same
problem in the frontend) ? Any tips/advice would be appreciate
Regards.
Fabien
next reply other threads:[~2006-06-15 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 8:30 Fabien Hermenier [this message]
2006-06-15 21:01 ` xenbus api Anthony Liguori
2006-06-20 12:22 ` Fabien Hermenier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1150360202.21177.7.camel@localhost.localdomain \
--to=fabien.hermenier@emn.fr \
--cc=Xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.