I’ve applied Neel’s patch against r273182 and am currently abusively testing it 
on a mix of HP DL385s w/ dual Opteron 6378SE, & Single socket AMD G34s ( some 
with Opteron 6200s, some with 6300s ), about 15 boxes in total - so far so 
good. 

Seriously awesome work Gentlemen.

cheers,
-bp

> On Oct 15, 2014, at 8:30 PM, Matthew Grooms <[email protected]> wrote:
> 
> Fantastic news! Greatly appreciated.
> 
> -Matthew
> 
> On Oct 15, 2014 10:00 PM, Anish Gupta <[email protected]> wrote:
>> 
>> Hi all, 
>> 
>> The projects/bhyve_svm branch is ready to be merged to HEAD. 
>> 
>> This branch contains patches to bhyve to enable it to work on AMD 
>> processors with SVM/AMD-V hardware extensions[1]. Pretty much any AMD 
>> processor since 2010 will have the features required by bhyve. 
>> 
>> bhyve on AMD supports (almost) all the features available with Intel 
>> [2]. All guest OSes supported on Intel are supported on AMD. All the 
>> bhyve-related utilities function similarly on both Intel and AMD 
>> platforms [3]. 
>> 
>> The patch against HEAD revision 273066 is available for review and testing: 
>> https://people.freebsd.org/~neel/bhyve/bhyve_svm.diff [Neel’s web directory] 
>> 
>> [1]: http://en.wikipedia.org/wiki/X86_virtualization 
>> [2]: bhyve doesn't support PCI passthru on AMD at this time 
>> [3]: bhyvectl has grown some processor-specific options 
>> 
>> Thanks and regards, 
>> Peter, Neel & Anish[[email protected]] 
>> _______________________________________________ 
>> [email protected] mailing list 
>> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization 
>> To unsubscribe, send any mail to 
>> "[email protected]" 
> _______________________________________________
> [email protected] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to 
> "[email protected]"

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"[email protected]"

Reply via email to