The environment that I tested in when the virtualization support was put
into
the driver was using SRIOV, not pass-through, we have never validated the
latter, and whenever it crops up it seems to be having problems.
I can put it into my queue to look into, but I can't say how quickly I can
get
On 05/13/13 11:32, Roger Pau Monné wrote:
Right now the code is in a state where it can be tested by users, so we
would like to encourage FreeBSD and Xen users to test it and provide
feedback.
The code is available in the following git repository, under the branch
pvhvm_v5:
On 16/05/13 19:55, Colin Percival wrote:
On 05/13/13 11:32, Roger Pau Monné wrote:
Right now the code is in a state where it can be tested by users, so we
would like to encourage FreeBSD and Xen users to test it and provide
feedback.
The code is available in the following git repository,
Thanks a lot Jack.
According to my test, SRIOV works fine!
It's not the way we want, but this solution really helps.
So, we'll spend more time to solve the real problem, while we can use SRIOV as
a substitution.
--
Best wishes.
Jason Shi
-- Original
On 05/16/13 17:43, Roger Pau Monné wrote:
Thanks for testing this on EC2, could you post the full dmesg? So I can
see the hypervisor version and if the PV timer is loaded or not.
Here's what I get on a cc2.8xlarge with boot_verbose=YES:
Booting [/boot/kernel/kernel]...
