|
![](http://nl.training-info.ro/QUJGIx5AkQjn-K9AKb850p2jc4CKH6wpSR39G8DQlbfjddhxahB_jyeCzFONDn2O6O1F_b7o_iTAvA1nMI0tNJ8Sh5XbI351NnRbgaiYXwRHBey_iobnklMqWnys-7H2zvriuAcxBCJeSJp_kVJGUatSlOJxSJQWBItcqDGj4NNwE1diBHfzHNsAyNQ4vkkamrEwjDe2LcI8XgMAqWIH9yE9fqGOMVzgJ8VRsMuJRWh143fPpjjwPJ0zZeBo6ZNJWifC85dMj
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219343
--- Comment #2 from Chris Gordon ---
Thanks. My concern is more of the underlying issues requiring -w, not vmrun.sh
itself.
If I can provide any help, please let me know.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213814
--- Comment #9 from a.andersson@gmail.com ---
Any news on this? I would be happy to try out patches.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-virt