bhyve a no on rootbsd

Outback Dingo outbackdingo at gmail.com
Mon Sep 9 16:51:20 UTC 2013


On Mon, Sep 9, 2013 at 12:37 PM, Julian Elischer <julian at elischer.org>wrote:

> RootBSD virtual hosts are already virtualised (Xen). I doubt you can run
> bhyve on Xen.
>
>
> On 9/9/13 4:47 PM, Aryeh Friedman wrote:
>
>> The host:
>>
>> CPU: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz (2400.06-MHz K8-class
>> CPU)
>>    Origin = "GenuineIntel"  Id = 0x206c2  Family = 0x6  Model = 0x2c
>>   Stepping = 2
>>
>> Features=0x1781fbff<FPU,VME,**DE,PSE,TSC,MSR,PAE,MCE,CX8,**
>> APIC,SEP,MTRR,PGE,MCA,CMOV,**PAT,MMX,FXSR,SSE,SSE2,HTT>
>>    Features2=0x80982201<SSE3,**SSSE3,CX16,SSE4.1,SSE4.2,**POPCNT,HV>
>>    AMD Features=0x20100800<SYSCALL,**NX,LM>
>>    AMD Features2=0x1<LAHF>
>>
>> Kldstat:
>>
>> Id Refs Address            Size     Name
>>   1   10 0xffffffff80200000 1695318  kernel
>>   2    1 0xffffffff81896000 a6c8     if_tap.ko
>>   3    1 0xffffffff818a1000 12f60    if_bridge.ko
>>   4    2 0xffffffff818b4000 8c90     bridgestp.ko
>>   5    1 0xffffffff81c12000 16d947   vmm.ko
>>
>> Attempted script:
>>
>> truncate -s 80G /vms/test
>> ifconfig tap0 destroy
>> ifconfig tap0 create
>> ifconfig tap0 up
>> sleep 5
>> ifconfig bridge0 addm tap0 up
>> /usr/sbin/bhyvectl --vm=firstPublicInstance --destroy
>> /usr/sbin/bhyveload -m 512 -d /vms/cds/release.iso firstPublicInstance
>> /usr/sbin/bhyve -c 1 -m 512 -AI -H -P -g 0 -s 0:0,hostbridge -s
>> 1:0,virtio-net,tap0 -s 2:0,virtio-blk,/vms/test -s
>> 3:0,virtio-blk,/vms/cds/**release.iso -S 31,uart,stdio
>> firstPublicInstance
>> ifconfig tap0 destroy
>> ifconfig tap0 create
>> ifconfig tap0 up
>> sleep 5
>> ifconfig bridge0 addm tap0 up
>> /usr/sbin/bhyvectl --vm=firstPublicInstance --destroy
>> /usr/sbin/bhyveload -m 512 -d /vms/test firstPublicInstance
>> /usr/sbin/bhyve -c 1 -m 512 -AI -H -P -g 0 -s 0:0,hostbridge -s
>> 1:0,virtio-net,tap0 -s 2:0,virtio-blk,/vms/test -S 31,uart,stdio
>> firstPublicInstance*
>> *
>>
>
thats correct unless hes got a dedicated box......



> ______________________________**_________________
>> freebsd-virtualization@**freebsd.org <freebsd-virtualization at freebsd.org>mailing list
>> http://lists.freebsd.org/**mailman/listinfo/freebsd-**virtualization<http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>
>> To unsubscribe, send any mail to "freebsd-virtualization-**
>> unsubscribe at freebsd.org <freebsd-virtualization-unsubscribe at freebsd.org>"
>>
>
> ______________________________**_________________
> freebsd-virtualization@**freebsd.org <freebsd-virtualization at freebsd.org>mailing list
> http://lists.freebsd.org/**mailman/listinfo/freebsd-**virtualization<http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>
> To unsubscribe, send any mail to "freebsd-virtualization-**
> unsubscribe at freebsd.org <freebsd-virtualization-unsubscribe at freebsd.org>"
>


More information about the freebsd-virtualization mailing list