netvm must be killed every time

[Axon]

Since upgrading to R2B3, I've noticed that my netvm must be "killed"
every time I wish to shut it down. In R2B2, it would take a long time to
shut down (which is a known issue), but it would eventually do so. Now,
when the normal "shut down" command is issued (by clicking the button in
QVMM), it just hangs forever (and repeatedly asks if I want to keep
waiting). Is this because I upgraded in-place from R2B2 to R2B3? Or are
people who did a clean install of R2B3 also experiencing this? What kind
of harm is caused by killing my netvm every time I shut it down? (What
does the "Kill VM" command actually do, anyway?) If the harm is not
great, perhaps I will just kill it right away every time (instead of
first attempting the normal "shut down" command), since it is much faster.

[cprise]

Since upgrading (fresh install) the showdowns have been the same (still
the 70-90 racing wait) but it does shut down on its own eventually.

However, the last time I tried to stop the netvm for an update, it
seemed to be in an endless loop of 'keep waiting 20 sec' and I after a
time I killed it.