http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=807

------- Comment #4 from stij...@gmail.com 2006-12-11 17:10 ------- I've been seeing a similar problem with Xen 3.0.3-1-i386, also from Debian Etch.

After shutting down a domU, I get this output from xm list on dom0:

typhoon:~# xm list Error: Device 0 not connected Usage: xm list [options] [Domain, ...]

List information about all/some domains. -l, --long Output all VM details in SXP --label Include security labels

After that, there were two "hanging processes":

root 8494 0.0 0.0 0 0 ? S< 01:43 0:00 [xvd 6 fd:03] root 8495 0.0 0.0 0 0 ? S< 01:43 0:00 [xvd 6 fd:07]

Because of these hanging processes, I could not start the domU that I had halted before again, without rebooting dom0 - at least, that was the only way I knew until know.

After some testing I discovered that the cause of my problem was quagga, which is running on dom0. Simply restarting quagga made the hanging processes go away, and after that I could boot all the domU's again without a reboot of dom0.