Curent Centos 7 and bhyve
Victor Sudakov
vas at mpeks.tomsk.su
Mon Aug 13 09:53:10 UTC 2018
Matt Churchyard wrote:
> > Rodney W. Grimes wrote:
>
> [dd]
>
>
> I've already commented on the bug, although I'll reply here as well.
> If "-S" is found in bhyve_options it does currently affect both
> commands.
Sorry, this is not working for me (vm-bhyve 1.1.8_2 from official packages):
Aug 13 16:43:09: bhyve exited with status 1
Aug 13 16:43:09: destroying network device tap0
Aug 13 16:43:09: stopped
Aug 13 16:43:12: initialising
Aug 13 16:43:12: [loader: bhyveload]
Aug 13 16:43:12: [uefi: no]
Aug 13 16:43:12: [cpu: 1]
Aug 13 16:43:12: [memory: 1G]
Aug 13 16:43:12: [hostbridge: standard]
Aug 13 16:43:12: [com ports: com1]
Aug 13 16:43:12: [uuid: e148afdb-d4af-11e6-9a94-5404a6b49a66]
Aug 13 16:43:12: [utctime: yes]
Aug 13 16:43:12: [debug mode: no]
Aug 13 16:43:12: [primary disk: disk0.img]
Aug 13 16:43:12: [primary disk dev: file]
Aug 13 16:43:12: initialising network device tap0
Aug 13 16:43:12: adding tap0 -> bridge0 (main)
Aug 13 16:43:12: booting
Aug 13 16:43:12: bhyveload -c /dev/nmdm0A -m 1G -e autoboot_delay=3 -d /d02/vm/fido/disk0.img fido
Aug 13 16:43:17: [bhyve options: -c 1 -m 1G -AHP -S -U e148afdb-d4af-11e6-9a94-5404a6b49a66 -u]
Aug 13 16:43:17: [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,virtio-blk,/d02/vm/fido/disk0.img -s 5:0,virtio-net,tap0,mac=58:9c:fc:01:f6:ac]
Aug 13 16:43:17: [bhyve console: -l com1,/dev/nmdm0A]
Aug 13 16:43:17: starting bhyve (run 1)
Aug 13 16:43:17: bhyve exited with status 1
Aug 13 16:43:17: destroying network device tap0
Aug 13 16:43:17: stopped
Here is my complete config:
guest="freebsd"
loader="bhyveload"
cpu=1
memory=1G
network0_type="virtio-net"
network0_switch="main"
disk0_type="virtio-blk"
disk0_name="disk0.img"
utctime="yes"
uuid="e148afdb-d4af-11e6-9a94-5404a6b49a66"
network0_mac="58:9c:fc:01:f6:ac"
bhyve_options="-S"
--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
AS43859
More information about the freebsd-virtualization
mailing list