Re: fatal; loader returned error 139
On Sat, 06 Feb 2021 05:14:52 +0900, Yuri Pankov wrote: > > KIRIYAMA Kazuhiko wrote: > > Hi, all > > > > Yesterday, I've updated 14.0-CURRENT and tried to start VM, > > filed to start with "loader returned error 139". VM log is > > as follows : > > > > root@vm:~ # tail -20 /vm/msrvkxb/vm-bhyve.log > > Feb 05 09:50:18: initialising > > Feb 05 09:50:18: [loader: bhyveload] > > Feb 05 09:50:18: [cpu: 2] > > Feb 05 09:50:18: [memory: 4GB] > > Feb 05 09:50:18: [hostbridge: standard] > > Feb 05 09:50:18: [com ports: com1] > > Feb 05 09:50:18: [uuid: c5ff2511-298f-11eb-9dae-0cc47ab3cfd4] > > Feb 05 09:50:18: [utctime: yes] > > Feb 05 09:50:18: [debug mode: no] > > Feb 05 09:50:18: [primary disk: disk0.img] > > Feb 05 09:50:18: [primary disk dev: file] > > Feb 05 09:50:19: initialising network device tap0 > > Feb 05 09:50:19: setting mtu of tap0 to 9000 > > Feb 05 09:50:19: adding tap0 -> vm-local (local addm) > > Feb 05 09:50:19: bring up tap0 -> vm-local (local addm) > > Feb 05 09:50:19: booting > > Feb 05 09:50:19: bhyveload -c /dev/nmdm-msrvkxb.1A -m 4GB -e > > autoboot_delay=3 -d /vm/msrvkxb/disk0.img msrvkxb > > Feb 05 09:50:19: fatal; loader returned error 139 > > That would normally mean process was killed by SIGSEGV (128 + 11 for > signal); was a core dumped somewhere? root@vm:~ # lldb -c bhyveload.core -- bhyveload (lldb) target create "bhyveload" --core "bhyveload.core" Core file '/root/bhyveload.core' (x86_64) was loaded. (lldb) thread backtrace all * thread #1, name = 'bhyveload', stop reason = signal SIGSEGV * frame #0: 0x000a4185c983 userboot.so`strlen + 31 frame #1: 0x000a418542c8 userboot.so`strdup + 24 frame #2: 0x000a4184e1d1 userboot.so`putenv + 12 frame #3: 0x000a4181c887 userboot.so`loader_main + 144 frame #4: 0x00203536 bhyveload`main(argc=, argv=) at bhyveload.c:853:2 frame #5: 0x00202f50 bhyveload`_start(ap=, cleanup=) at crt1_c.c:75:7 (lldb) > > > Feb 05 09:50:19: destroying network device tap0 > > Feb 05 09:50:19: stopped > > root@vm:~ # uname -a > > FreeBSD vm.truefc.org 14.0-CURRENT FreeBSD 14.0-CURRENT #0 > > main-n244626-cb7cc72c546e: Thu Feb 4 17:12:09 JST 2021 > > ad...@vm.truefc.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > root@vm:~ # > > > > > > Is there any suggetions ? > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscr...@freebsd.org" > ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
fatal; loader returned error 139
Hi, all Yesterday, I've updated 14.0-CURRENT and tried to start VM, filed to start with "loader returned error 139". VM log is as follows : root@vm:~ # tail -20 /vm/msrvkxb/vm-bhyve.log Feb 05 09:50:18: initialising Feb 05 09:50:18: [loader: bhyveload] Feb 05 09:50:18: [cpu: 2] Feb 05 09:50:18: [memory: 4GB] Feb 05 09:50:18: [hostbridge: standard] Feb 05 09:50:18: [com ports: com1] Feb 05 09:50:18: [uuid: c5ff2511-298f-11eb-9dae-0cc47ab3cfd4] Feb 05 09:50:18: [utctime: yes] Feb 05 09:50:18: [debug mode: no] Feb 05 09:50:18: [primary disk: disk0.img] Feb 05 09:50:18: [primary disk dev: file] Feb 05 09:50:19: initialising network device tap0 Feb 05 09:50:19: setting mtu of tap0 to 9000 Feb 05 09:50:19: adding tap0 -> vm-local (local addm) Feb 05 09:50:19: bring up tap0 -> vm-local (local addm) Feb 05 09:50:19: booting Feb 05 09:50:19: bhyveload -c /dev/nmdm-msrvkxb.1A -m 4GB -e autoboot_delay=3 -d /vm/msrvkxb/disk0.img msrvkxb Feb 05 09:50:19: fatal; loader returned error 139 Feb 05 09:50:19: destroying network device tap0 Feb 05 09:50:19: stopped root@vm:~ # uname -a FreeBSD vm.truefc.org 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-n244626-cb7cc72c546e: Thu Feb 4 17:12:09 JST 2021 ad...@vm.truefc.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 root@vm:~ # Is there any suggetions ? Regards --- Kazuhiko Kiriyama ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
To late to build packages in arm64/aarch64 on qemu
Hi, all I'm tring to build packages in arm64/aarch64 on qemu-system-aarch64. But it's too late in comparision to amd64 on bhyve. For example, `make package-recursive' of devel/binutils on qemu takes 67 times of bhyve [1]. I found that it's difference caused from disk geometry factors such as stripesize, cylinders according to firmware and heads according to firmware [2]. I also try to test in qcow2 format with cache-size 4 GB, but nothing progress: root@vm:/vm/test # qemu-system-aarch64 -machine virt -cpu cortex-a57 -smp 4 -m 8G,maxmem=8G -name test -blockdev driver=file,node-name=hd0,filename=FreeBSD-13.0-CURRENT-arm64-aarch64.qcow2 -blockdev driver=qcow2,node-name=hda,file=hd0,overlap-check=none,cache-size=4294967296 -device virtio-blk-device,drive=hda -nographic -monitor telnet::5045,server,nowait,nodelay -serial telnet::5044,server,nowait,nodelay -bios QEMU_EFI.fd root@vm:~ # telnet localhost 5044 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. FreeBSD/arm64 (freebsd) (ttyu0) login: root Aug 28 02:25:30 freebsd login[865]: ROOT LOGIN (root) ON ttyu0 Last login: Fri Aug 28 01:14:36 on ttyu0 FreeBSD 13.0-CURRENT (GENERIC) #0 r364182: Thu Aug 13 05:44:54 UTC 2020 Welcome to FreeBSD! Release Notes, Errata: https://www.FreeBSD.org/releases/ Security Advisories: https://www.FreeBSD.org/security/ FreeBSD Handbook: https://www.FreeBSD.org/handbook/ FreeBSD FAQ: https://www.FreeBSD.org/faq/ Questions List: https://lists.FreeBSD.org/mailman/listinfo/freebsd-questions/ FreeBSD Forums:https://forums.FreeBSD.org/ Documents installed with the system are in the /usr/local/share/doc/freebsd/ directory, or can be installed later with: pkg install en-freebsd-doc For other languages, replace "en" with a language code like de or fr. Show the version of FreeBSD installed: freebsd-version ; uname -a Please include that output and any error messages when posting questions. Introduction to manual pages: man man FreeBSD directory layout: man hier Edit /etc/motd.template to change this login announcement. root@freebsd:~ # df Filesystem 1K-blocksUsed Avail Capacity Mounted on /dev/ufs/rootfs 4053356 2727620 100146873%/ devfs 1 1 0 100%/dev root@freebsd:~ # diskinfo -tv /dev/ufs/rootfs /dev/ufs/rootfs 512 # sectorsize 4295020032 # mediasize in bytes (4.0G) 8388711 # mediasize in sectors 0 # stripesize 34091520# stripeoffset 8322# Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. # Disk descr. # Disk ident. # Attachment Yes # TRIM/UNMAP support Unknown # Rotation rate in RPM Seek times: Full stroke: 250 iter in 0.133557 sec =0.534 msec Half stroke: 250 iter in 0.136215 sec =0.545 msec Quarter stroke: 500 iter in 0.290992 sec =0.582 msec Short forward:400 iter in 0.204633 sec =0.512 msec Short backward: 400 iter in 0.246820 sec =0.617 msec Seq outer: 2048 iter in 1.149787 sec =0.561 msec Seq inner: 2048 iter in 1.162127 sec =0.567 msec Transfer rates: outside: 102400 kbytes in 0.499821 sec = 204873 kbytes/sec middle:102400 kbytes in 0.498121 sec = 205573 kbytes/sec inside:102400 kbytes in 0.488791 sec = 209496 kbytes/sec root@freebsd:~ # Is there any suggetions? Best regards [1] https://lists.freebsd.org/pipermail/freebsd-virtualization/2020-August/008753.html [2] https://lists.freebsd.org/pipermail/freebsd-virtualization/2020-August/008785.html --- Kazuhiko Kiriyama ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Why qemu-system-aarch64 so late to process ?
Hi Disk access performance is about 10 times between bhyve and qemu: root@jdtpkxb:~ # diskinfo -vt vtbd0p2 vtbd0p2 512 # sectorsize 31138512896 # mediasize in bytes (29G) 60817408# mediasize in sectors 131072 # stripesize 20480 # stripeoffset 3785# Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. # Disk descr. BHYVE-438B-D187-47E7# Disk ident. # Attachment No # TRIM/UNMAP support Unknown # Rotation rate in RPM Seek times: Full stroke: 250 iter in 0.019028 sec =0.076 msec Half stroke: 250 iter in 0.018842 sec =0.075 msec Quarter stroke: 500 iter in 0.032337 sec =0.065 msec Short forward:400 iter in 0.027096 sec =0.068 msec Short backward: 400 iter in 0.027531 sec =0.069 msec Seq outer: 2048 iter in 0.106816 sec =0.052 msec Seq inner: 2048 iter in 0.113622 sec =0.055 msec Transfer rates: outside: 102400 kbytes in 0.080248 sec = 1276044 kbytes/sec middle:102400 kbytes in 0.062225 sec = 1645641 kbytes/sec inside:102400 kbytes in 0.062555 sec = 1636959 kbytes/sec root@jdtpkxb:~ # gpart show vtbd0 => 40 67108784 vtbd0 GPT (32G) 40 1024 1 freebsd-boot (512K) 1064 60817408 2 freebsd-ufs (29G) 60818472 6290352 3 freebsd-swap (3.0G) root@jdtpkxb:~ # root@lpbkpkx:~ # diskinfo -vt vtbd0p2 vtbd0p2 512 # sectorsize 31138512896 # mediasize in bytes (29G) 60817408# mediasize in sectors 0 # stripesize 272650240 # stripeoffset 60334 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. # Disk descr. # Disk ident. # Attachment No # TRIM/UNMAP support Unknown # Rotation rate in RPM Seek times: Full stroke: 250 iter in 0.127904 sec =0.512 msec Half stroke: 250 iter in 0.126985 sec =0.508 msec Quarter stroke: 500 iter in 0.285858 sec =0.572 msec Short forward:400 iter in 0.206051 sec =0.515 msec Short backward: 400 iter in 0.201722 sec =0.504 msec Seq outer: 2048 iter in 1.050497 sec =0.513 msec Seq inner: 2048 iter in 1.019406 sec =0.498 msec Transfer rates: outside: 102400 kbytes in 0.505535 sec = 202558 kbytes/sec middle:102400 kbytes in 0.620144 sec = 165123 kbytes/sec inside:102400 kbytes in 0.615600 sec = 166342 kbytes/sec root@lpbkpkx:~ # gpart show vtbd0 => 40 67108784 vtbd0 GPT (32G) 40532480 1 freebsd-boot (260M) 532520 60817408 2 freebsd-ufs (29G) 61349928 5758896 3 freebsd-swap (2.7G) root@lpbkpkx:~ # Does it caused by disk cache ? On Tue, 11 Aug 2020 10:23:12 +0900, KIRIYAMA Kazuhiko wrote: > > Hi, all > > I'm working on qemu-system-aarch64 and try to build > packages, but it's too late to compile stuffs. I've compare > to bhyve package building procedure, then about 70 times > later than bhyve one. I don't know why so much late on > qemu-system-aarch64. > > Following results are devel/binutils package building > process between bhyve and qemu-system-aarch64. > > === devel/binutils package building (bhyve) === > > VM environments: > > root@vm:~ # cat /vm/jdtpkxb/jdtpkxb.conf > loader="bhyveload" > cpu=4 > memory=8GB > network0_type="virtio-net" > network0_switch="local" > disk0_type="virtio-blk" > disk0_name="disk0.img" > storage=32G > memory=8G > cpu=4 > uuid="200bdead-cd7e-11ea-8cb7-0cc47ab3cfd4" > network0_mac="58:9c:fc:02:0f:18" > root@vm:~ # tail -35 /vm/jdtpkxb/vm-bhyve.log > Jul 27 06:24:14: [primary disk dev: file] > Jul 27 06:24:14: initialising network device tap1 > Jul 27 06:24:14: setting mtu of tap1 to 9000 > Jul 27 06:24:14: adding tap1 -> vm-local (local addm) > Jul 27 06:24:14: bring up tap1 -> vm-local (local addm) > Jul 27 06:24:14: booting > Jul 27 06:24:14: bhyveload -c /dev/nmdm-jdtpkxb.1A -m 8GB -e autoboot_delay=3 > -d /vm/jdtpkxb/disk0.img jdtpkxb > Jul 27 06:24:18: [bhyve options: -c 4 -m 8GB -AHP -U > 200bdead-cd7e-11ea-8cb7-0cc47ab3cfd4 -u] > Jul 27 06:24:18: [bhyve devices: -s 0,hostbridge -s 31,lpc -s &g
Why qemu-system-aarch64 so late to process ?
Hi, all I'm working on qemu-system-aarch64 and try to build packages, but it's too late to compile stuffs. I've compare to bhyve package building procedure, then about 70 times later than bhyve one. I don't know why so much late on qemu-system-aarch64. Following results are devel/binutils package building process between bhyve and qemu-system-aarch64. === devel/binutils package building (bhyve) === VM environments: root@vm:~ # cat /vm/jdtpkxb/jdtpkxb.conf loader="bhyveload" cpu=4 memory=8GB network0_type="virtio-net" network0_switch="local" disk0_type="virtio-blk" disk0_name="disk0.img" storage=32G memory=8G cpu=4 uuid="200bdead-cd7e-11ea-8cb7-0cc47ab3cfd4" network0_mac="58:9c:fc:02:0f:18" root@vm:~ # tail -35 /vm/jdtpkxb/vm-bhyve.log Jul 27 06:24:14: [primary disk dev: file] Jul 27 06:24:14: initialising network device tap1 Jul 27 06:24:14: setting mtu of tap1 to 9000 Jul 27 06:24:14: adding tap1 -> vm-local (local addm) Jul 27 06:24:14: bring up tap1 -> vm-local (local addm) Jul 27 06:24:14: booting Jul 27 06:24:14: bhyveload -c /dev/nmdm-jdtpkxb.1A -m 8GB -e autoboot_delay=3 -d /vm/jdtpkxb/disk0.img jdtpkxb Jul 27 06:24:18: [bhyve options: -c 4 -m 8GB -AHP -U 200bdead-cd7e-11ea-8cb7-0cc47ab3cfd4 -u] Jul 27 06:24:18: [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,virtio-blk,/vm/jdtpkxb/disk0.img -s 5:0,virtio-net,tap1,mac=58:9c:fc:02:0f:18] Jul 27 06:24:18: [bhyve console: -l com1,/dev/nmdm-jdtpkxb.1A] Jul 27 06:24:18: starting bhyve (run 1) Jul 28 21:44:41: bhyve exited with status 1 Jul 28 21:44:41: destroying network device tap1 Jul 28 21:44:42: stopped Aug 10 09:58:51: initialising Aug 10 09:58:51: [loader: bhyveload] Aug 10 09:58:51: [cpu: 4] Aug 10 09:58:51: [memory: 8GB] Aug 10 09:58:51: [hostbridge: standard] Aug 10 09:58:51: [com ports: com1] Aug 10 09:58:51: [uuid: 200bdead-cd7e-11ea-8cb7-0cc47ab3cfd4] Aug 10 09:58:51: [utctime: yes] Aug 10 09:58:51: [debug mode: no] Aug 10 09:58:51: [primary disk: disk0.img] Aug 10 09:58:51: [primary disk dev: file] Aug 10 09:58:51: initialising network device tap2 Aug 10 09:58:51: setting mtu of tap2 to 9000 Aug 10 09:58:51: adding tap2 -> vm-local (local addm) Aug 10 09:58:51: bring up tap2 -> vm-local (local addm) Aug 10 09:58:51: booting Aug 10 09:58:51: bhyveload -c /dev/nmdm-jdtpkxb.1A -m 8GB -e autoboot_delay=3 -d /vm/jdtpkxb/disk0.img jdtpkxb Aug 10 09:58:54: [bhyve options: -c 4 -m 8GB -AHP -U 200bdead-cd7e-11ea-8cb7-0cc47ab3cfd4 -u] Aug 10 09:58:54: [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,virtio-blk,/vm/jdtpkxb/disk0.img -s 5:0,virtio-net,tap2,mac=58:9c:fc:02:0f:18] Aug 10 09:58:54: [bhyve console: -l com1,/dev/nmdm-jdtpkxb.1A] Aug 10 09:58:54: starting bhyve (run 1) root@vm:~ # Package building process in VM: root@jdtpkxb:~ # top -bd1 last pid: 54340; load averages: 2.91, 1.23, 0.61 up 0+05:28:5915:27:58 37 processes: 5 running, 32 sleeping CPU: 0.3% user, 0.0% nice, 0.2% system, 0.1% interrupt, 99.4% idle Mem: 208M Active, 125M Inact, 838M Wired, 692M Buf, 6749M Free Swap: 3071M Total, 3071M Free PID USERNAMETHR PRI NICE SIZERES STATEC TIMEWCPU COMMAND 54299 root 1 750 154M 108M RUN 0 0:01 10.99% cc 54315 root 1 740 124M84M CPU3 3 0:01 8.98% cc 54323 root 1 740 157M 113M CPU2 2 0:01 0.00% cc 16066 root 1 20021M 9828K select 0 0:01 0.00% sshd 624 ntpd 1 20021M 6420K select 2 0:01 0.00% ntpd 54339 root 1 730 132M87M CPU1 1 0:01 0.00% cc 17898 root 1 52019M 7540K wait 2 0:00 0.00% sh 16070 root 1 52019M 7372K wait 1 0:00 0.00% sh 665 root 1 20018M 7036K select 0 0:00 0.00% sendmail 52975 root 1 52013M 3596K select 0 0:00 0.00% gmake 672 root 1 20013M 2832K nanslp 0 0:00 0.00% cron 495 root 1 20013M 2836K select 1 0:00 0.00% syslogd 25104 root 1 52015M 4592K wait 3 0:00 0.00% gmake 25091 root 1 52015M 4332K wait 3 0:00 0.00% gmake 23169 root 1 52013M 3200K wait 2 0:00 0.00% make 761 root 1 20014M 4448K pause3 0:00 0.00% tcsh 52886 root 1 52013M 3492K wait 0 0:00 0.00% gmake 728 root 1 39021M 9440K select 3 0:00 0.00% sshd root@jdtpkxb:~ # uname -a FreeBSD jdtpkxb 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r363381M: Thu Jul 23 22:48:19 JST 2020 root@msrvkxb:/usr/obj/usr/src/amd64.amd64/sys/XIJ amd64 root@jdtpkxb:~ # svnlite info /usr/ports Path: /usr/ports Working Copy Root Path: /usr/ports URL: http://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: http://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 542063 Node Kind: directory Schedule:
Re: Can't system_powerdown in qemu-system-aarch64 monitor
On Fri, 19 Jun 2020 09:23:20 +0900, KIRIYAMA Kazuhiko wrote: > > Hi, all > > I'm wondering why system_powerdown can not be worked but > system_reset can work on qemu-system-aarch64. I set up > FreeBSD 13.0-CURRENT-arm64-aarch66 as follows: > > root@vm:~ # uname -a > FreeBSD vm.truefc.org 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r353025: Thu Oct > 3 19:38:47 JST 2019 > ad...@vm.truefc.org:/ds/obj/current/13.0/r353025/ds/src/current/13.0/r353025/amd64.amd64/sys/GENERIC > amd64 > root@vm:~ # qemu-system-aarch64 -version > QEMU emulator version 4.1.0 > Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers > root@vm:~ # ifconfig > igb0: flags=8943 metric 0 mtu > 9000 > > options=4a520b9 > ether 0c:c4:7a:b3:cf:d4 > inet 36.52.212.2 netmask 0xfff8 broadcast 36.52.212.7 > media: Ethernet autoselect (1000baseT ) > status: active > nd6 options=29 > igb1: flags=8943 metric 0 mtu > 9000 > > options=4e523bb > ether 0c:c4:7a:b3:cf:d5 > inet 192.168.1.17 netmask 0xff00 broadcast 192.168.1.255 > media: Ethernet autoselect (1000baseT ) > status: active > nd6 options=29 > lo0: flags=8049 metric 0 mtu 16384 > options=680003 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > inet 127.0.0.1 netmask 0xff00 > groups: lo > nd6 options=21 > vm-public: flags=8843 metric 0 mtu > 9000 > ether 9e:58:86:f8:e7:11 > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: tap0 flags=143 > ifmaxaddr 0 port 6 priority 128 path cost 200 > member: igb0 flags=143 > ifmaxaddr 0 port 1 priority 128 path cost 2 > groups: bridge vm-switch viid-4c918@ > nd6 options=1 > vm-local: flags=8843 metric 0 mtu 9000 > ether d6:e6:99:60:b6:a5 > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: igb1 flags=143 > ifmaxaddr 0 port 2 priority 128 path cost 2 > groups: bridge vm-switch viid-f5dda@ > nd6 options=1 > tap0: flags=8943 metric 0 mtu > 9000 > description: vmnet-mftpkx-0-public > options=8 > ether 58:9c:fc:10:ff:df > groups: tap vm-port > media: Ethernet autoselect > status: active > nd6 options=29 > Opened by PID 1427 > root@vm:~ # ifconfig tap create > tap1 > root@vm:~ # ifconfig tap1 mtu 9000 > root@vm:~ # ifconfig vm-local addm tap1 > root@vm:~ # ifconfig tap1 up > root@vm:~ # ifconfig > igb0: flags=8943 metric 0 mtu > 9000 > > options=4a520b9 > ether 0c:c4:7a:b3:cf:d4 > inet 36.52.212.2 netmask 0xfff8 broadcast 36.52.212.7 > media: Ethernet autoselect (1000baseT ) > status: active > nd6 options=29 > igb1: flags=8943 metric 0 mtu > 9000 > > options=4a520b9 > ether 0c:c4:7a:b3:cf:d5 > inet 192.168.1.17 netmask 0xff00 broadcast 192.168.1.255 > media: Ethernet autoselect (1000baseT ) > status: active > nd6 options=29 > lo0: flags=8049 metric 0 mtu 16384 > options=680003 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > inet 127.0.0.1 netmask 0xff00 > groups: lo > nd6 options=21 > vm-public: flags=8843 metric 0 mtu > 9000 > ether 9e:58:86:f8:e7:11 > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: tap0 flags=143 > ifmaxaddr 0 port 6 priority 128 path cost 200 > member: igb0 flags=143 > ifmaxaddr 0 port 1 priority 128 path cost 2 > groups: bridge vm-switch viid-4c918@ > nd6 options=1 > vm-local: flags=8843 metric 0 mtu 9000 > ether d6:e6:99:60:b6:a5 > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: tap1 flags=143 > ifmaxaddr 0 port 7 priority 128 path cost 200 &g
Can't system_powerdown in qemu-system-aarch64 monitor
Hi, all I'm wondering why system_powerdown can not be worked but system_reset can work on qemu-system-aarch64. I set up FreeBSD 13.0-CURRENT-arm64-aarch66 as follows: root@vm:~ # uname -a FreeBSD vm.truefc.org 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r353025: Thu Oct 3 19:38:47 JST 2019 ad...@vm.truefc.org:/ds/obj/current/13.0/r353025/ds/src/current/13.0/r353025/amd64.amd64/sys/GENERIC amd64 root@vm:~ # qemu-system-aarch64 -version QEMU emulator version 4.1.0 Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers root@vm:~ # ifconfig igb0: flags=8943 metric 0 mtu 9000 options=4a520b9 ether 0c:c4:7a:b3:cf:d4 inet 36.52.212.2 netmask 0xfff8 broadcast 36.52.212.7 media: Ethernet autoselect (1000baseT ) status: active nd6 options=29 igb1: flags=8943 metric 0 mtu 9000 options=4e523bb ether 0c:c4:7a:b3:cf:d5 inet 192.168.1.17 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (1000baseT ) status: active nd6 options=29 lo0: flags=8049 metric 0 mtu 16384 options=680003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 groups: lo nd6 options=21 vm-public: flags=8843 metric 0 mtu 9000 ether 9e:58:86:f8:e7:11 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: tap0 flags=143 ifmaxaddr 0 port 6 priority 128 path cost 200 member: igb0 flags=143 ifmaxaddr 0 port 1 priority 128 path cost 2 groups: bridge vm-switch viid-4c918@ nd6 options=1 vm-local: flags=8843 metric 0 mtu 9000 ether d6:e6:99:60:b6:a5 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: igb1 flags=143 ifmaxaddr 0 port 2 priority 128 path cost 2 groups: bridge vm-switch viid-f5dda@ nd6 options=1 tap0: flags=8943 metric 0 mtu 9000 description: vmnet-mftpkx-0-public options=8 ether 58:9c:fc:10:ff:df groups: tap vm-port media: Ethernet autoselect status: active nd6 options=29 Opened by PID 1427 root@vm:~ # ifconfig tap create tap1 root@vm:~ # ifconfig tap1 mtu 9000 root@vm:~ # ifconfig vm-local addm tap1 root@vm:~ # ifconfig tap1 up root@vm:~ # ifconfig igb0: flags=8943 metric 0 mtu 9000 options=4a520b9 ether 0c:c4:7a:b3:cf:d4 inet 36.52.212.2 netmask 0xfff8 broadcast 36.52.212.7 media: Ethernet autoselect (1000baseT ) status: active nd6 options=29 igb1: flags=8943 metric 0 mtu 9000 options=4a520b9 ether 0c:c4:7a:b3:cf:d5 inet 192.168.1.17 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (1000baseT ) status: active nd6 options=29 lo0: flags=8049 metric 0 mtu 16384 options=680003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 groups: lo nd6 options=21 vm-public: flags=8843 metric 0 mtu 9000 ether 9e:58:86:f8:e7:11 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: tap0 flags=143 ifmaxaddr 0 port 6 priority 128 path cost 200 member: igb0 flags=143 ifmaxaddr 0 port 1 priority 128 path cost 2 groups: bridge vm-switch viid-4c918@ nd6 options=1 vm-local: flags=8843 metric 0 mtu 9000 ether d6:e6:99:60:b6:a5 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: tap1 flags=143 ifmaxaddr 0 port 7 priority 128 path cost 200 member: igb1 flags=143 ifmaxaddr 0 port 2 priority 128 path cost 2 groups: bridge vm-switch viid-f5dda@ nd6 options=1 tap0: flags=8943 metric 0 mtu 9000 description: vmnet-mftpkx-0-public options=8 ether 58:9c:fc:10:ff:df groups: tap vm-port media: Ethernet autoselect status: active nd6 options=29 Opened by PID 1427 tap1: flags=8903 metric 0 mtu 9000 options=8 ether 58:9c:fc:10:86:31 groups: tap media: Ethernet autoselect status: no carrier nd6 options=29 root@vm:~ # qemu-system-aarch64 -machine virt -cpu
Re: Bhyve and QEMU
Hi, Julian On Wed, 08 Jan 2020 10:56:04 +0900, Julian Elischer wrote: > > I have been out of it for a while but I see that in Linux, KVM is used > as an emulation engine in QEMU. > > Do we have any plans to do the same with Bhyve? I really want to use defferent archtecture in bhyve. In order to use amd64/aarc64 with same user interface, I'm now re-constructing sysutils/vm-bhyve. > > Anyone have pointers as to how that combination works and if there are > reasons we would/would-not do the same? > > > Julian > > > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscr...@freebsd.org" > --- Kazuhiko Kiriyama ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Can't boot arm64 image by qemu-system-aarch64
Hi, all I've installed successfully by qemu-system-aarch64 below: root@vm:/vm/test # truncate -s 16g test.img root@vm:/vm/test # qemu-system-aarch64 -machine virt -m 4096M -cpu cortex-a57 -name test -bios QEMU_EFI.fd -nographic -hda test.img -hdc FreeBSD-13.0-CURRENT-arm64-aarch64-20191127-r355121-memstick.img and rebooted successfully and login with root: root@test:~ # uname -a FreeBSD test.tfc 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r355121: Wed Nov 27 03:49:21 UTC 2019 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 root@test:~ # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/vtbd0p2 14G1.3G 12G10%/ devfs 1.0K1.0K 0B 100%/dev root@test:~ # ifconfig vtnet0: flags=8843 metric 0 mtu 1500 options=80028 ether 52:54:00:12:34:56 inet 192.168.1.196 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet 10Gbase-T status: active nd6 options=29 lo0: flags=8049 metric 0 mtu 16384 options=680003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff00 groups: lo nd6 options=21 root@test:~ # So, I shutdowned and run by qemu-system-aarch64: root@vm:/vm/test # qemu-system-aarch64 -machine virt -m 4096M -cpu cortex-a57 -name test -bios QEMU_EFI.fd -nographic -drive if=none,format=raw,file=test.img,id=hd0 -device virtio-blk-device,drive=hd0 -device virtio-net-device,netdev=net0 -netdev tap,id=net0,ifname=tap2 But failed to boot: BdsDxe: failed to load Boot0001 "UEFI Misc Device" from VenHw(93E34C7E-B50E-11DF-9223-2443DFD72085,00): Not Found BdsDxe: failed to load Boot0002 "UEFI Misc Device 2" from VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A): Not Found >>Start PXE over IPv4. where, tap2 is ready to use: root@vm:/vm/test # ifconfig tap2 tap2: flags=8902 metric 0 mtu 1500 description: vmnet-test-0-local options=8 ether 58:9c:fc:10:ec:02 groups: tap qemu-port media: Ethernet autoselect status: no carrier nd6 options=21 root@vm:/vm/test # What's wrong ? Best regards. --- Kiriyama Kazuhiko ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: VM freezed at booting of FreeBSD-13.0-CURRENT-amd64-20191011-r353427-memstick.img
On Wed, 16 Oct 2019 07:17:04 +0900, KIRIYAMA Kazuhiko wrote: > > On Tue, 15 Oct 2019 19:35:23 +0900, > KIRIYAMA Kazuhiko wrote: > > > > On Tue, 15 Oct 2019 17:07:05 +0900, > > Simon wrote: > > > > > > > > > > > > Hi ) > > > May be the same problem. > > > I said about this here > > > https://forums.freebsd.org/threads/freebsd-12-0-release-amd64-freeze-boot-from-bhyve-uefi-bhyve_uefi-fd-uefi-gop-screen-goes-blank.69616/ > > > Solution. > > > Try this > > > Select > > > 3 - [Esc]ape to loader prompt > > > set boot_serial="NO" > > > boot > > > > `vm install' doesn't wait boot loader. So above > > manupulation could not work. I've specified it to the > > bhyveload `-e' option like with `-e boot_serial=NO': > > > > root@vm:~ # cat /vm/tbedfc/vm-bhyve.log > > Oct 15 19:27:55: initialising > > Oct 15 19:27:55: [loader: bhyveload] > > Oct 15 19:27:55: [cpu: 2] > > Oct 15 19:27:55: [memory: 8GB] > > Oct 15 19:27:55: [hostbridge: standard] > > Oct 15 19:27:55: [com ports: com1] > > Oct 15 19:27:55: [uuid: 737d1159-ef36-11e9-847a-0cc47ab3cfd4] > > Oct 15 19:27:55: [utctime: yes] > > Oct 15 19:27:55: [debug mode: no] > > Oct 15 19:27:55: [primary disk: disk0.img] > > Oct 15 19:27:55: [primary disk dev: file] > > Oct 15 19:27:55: generated static mac 58:9c:fc:02:46:e2 (based on > > 'tbedfc:0:1571135275:0') > > Oct 15 19:27:55: initialising network device tap0 > > Oct 15 19:27:55: adding tap0 -> vm-local (local addm) > > Oct 15 19:27:55: bring up tap0 -> vm-local (local addm) > > Oct 15 19:27:55: booting > > Oct 15 19:27:55: bhyveload -m 8GB -e autoboot_delay=3 -e boot_serial=NO -d > > /vm/.iso/FreeBSD-13.0-CURRENT-amd64-20191011-r353427-memstick.img tbedfc > > Oct 15 19:27:59: [bhyve options: -c 2 -m 8GB -AHP -U > > 737d1159-ef36-11e9-847a-0cc47ab3cfd4 -u] > > Oct 15 19:27:59: [bhyve devices: -s 0,hostbridge -s 31,lpc -s > > 4:0,virtio-blk,/vm/tbedfc/disk0.img -s > > 5:0,virtio-net,tap0,mac=58:9c:fc:02:46:e2] > > Oct 15 19:27:59: [bhyve console: -l com1,stdio] > > Oct 15 19:27:59: [bhyve iso device: -s > > 3:0,ahci-hd,/vm/.iso/FreeBSD-13.0-CURRENT-amd64-20191011-r353427-memstick.img] > > Oct 15 19:27:59: starting bhyve (run 1) > > Oct 15 19:29:54: bhyve exited with status 1 > > Oct 15 19:29:54: destroying network device tap0 > > Oct 15 19:29:55: stopped > > root@vm:~ # > > > > but also freezed ;-( > > I've listed all boot variables at loader prompt: > > > Type '?' for a list of commands, 'help' for more detailed help. > OK show > LINES=24 > ansi_caption[1]=^[1mB^[moot Multi User ^[1m[Enter]^[m > ansi_caption[2]=Boot ^[1mS^[mingle User > ansi_caption[3]=^[1mEsc^[mape to loader prompt > ansi_caption[5]=Kernel: default/kernel (1 of 2) > ansi_caption[5][0]=Kernel: default/kernel (1 of 2) > ansi_caption[5][1]=Kernel: kernel.old (2 of 2) > ansi_caption[6]=Configure Boot ^[1mO^[mptions... > autoboot_delay=NO > beansi_bootfs=^[1mbootfs: ^[m > beansi_current=^[1mActive: ^[m > beansi_page=^[1mP^[mage: > beansi_pageof= of > bemenu_bootfs=bootfs: > bemenu_current=Active: > bemenu_page=[P]age: > bemenu_pageof= of > boot_serial=NO > bootenv_autolist=YES > bootenv_root[2]= > bootenvmenu_command[1]=be_draw_screen 1 goto_menu > bootenvmenu_command[2]=set_bootenv > bootenvmenu_command[3]=set_be_page > beansi_bootfs=^[1mbootfs: ^[m > beansi_current=^[1mActive: ^[m > beansi_page=^[1mP^[mage: > beansi_pageof= of > bemenu_bootfs=bootfs: > bemenu_current=Active: > bemenu_page=[P]age: > bemenu_pageof= of > boot_serial=NO > bootenv_autolist=YES > bootenv_root[2]= > bootenvmenu_command[1]=be_draw_screen 1 goto_menu > bootenvmenu_command[2]=set_bootenv > bootenvmenu_command[3]=set_be_page > bootenvmenu_init=init_bootenv > bootenvmenu_keycode[1]=8 > bootenvmenu_keycode[2]=97 > bootenvmenu_keycode[3]=112 > bootenvmenu_options=4 > bootenvmenu_optionstext=Boot Environments: > bootfile=kernel > console=userboot > currdev=disk0s2a: > efi_max_resolution=1x1 > hint.acpi_throttle.0.disabled=1 > hint.atkbd.0.at=atkbdc > hint.atkbd.0.irq=1 > hint.atkbdc.0.at=isa > hint.atkbdc.0.port=0x060 > hint.atrtc.0.at=isa > hint.atrtc.0.irq=8 > hint.atrtc.0.port=0x70 > hint.attimer.0.at=isa > hint.attimer.0.irq=0 > hint.attimer.0.port=0x40 > hint.fd.0.at=fdc0 > hint.fd.0.drive=0 > efi_max_resolution=1x1 > hint.acpi_throttle.0.disabled=1 > hint.atkbd.0.at=atkbdc > hint.atkbd.0.irq=1 > hint.atk
Re: VM freezed at booting of FreeBSD-13.0-CURRENT-amd64-20191011-r353427-memstick.img
On Tue, 15 Oct 2019 19:35:23 +0900, KIRIYAMA Kazuhiko wrote: > > On Tue, 15 Oct 2019 17:07:05 +0900, > Simon wrote: > > > > > > > > Hi ) > > May be the same problem. > > I said about this here > > https://forums.freebsd.org/threads/freebsd-12-0-release-amd64-freeze-boot-from-bhyve-uefi-bhyve_uefi-fd-uefi-gop-screen-goes-blank.69616/ > > Solution. > > Try this > > Select > > 3 - [Esc]ape to loader prompt > > set boot_serial="NO" > > boot > > `vm install' doesn't wait boot loader. So above > manupulation could not work. I've specified it to the > bhyveload `-e' option like with `-e boot_serial=NO': > > root@vm:~ # cat /vm/tbedfc/vm-bhyve.log > Oct 15 19:27:55: initialising > Oct 15 19:27:55: [loader: bhyveload] > Oct 15 19:27:55: [cpu: 2] > Oct 15 19:27:55: [memory: 8GB] > Oct 15 19:27:55: [hostbridge: standard] > Oct 15 19:27:55: [com ports: com1] > Oct 15 19:27:55: [uuid: 737d1159-ef36-11e9-847a-0cc47ab3cfd4] > Oct 15 19:27:55: [utctime: yes] > Oct 15 19:27:55: [debug mode: no] > Oct 15 19:27:55: [primary disk: disk0.img] > Oct 15 19:27:55: [primary disk dev: file] > Oct 15 19:27:55: generated static mac 58:9c:fc:02:46:e2 (based on > 'tbedfc:0:1571135275:0') > Oct 15 19:27:55: initialising network device tap0 > Oct 15 19:27:55: adding tap0 -> vm-local (local addm) > Oct 15 19:27:55: bring up tap0 -> vm-local (local addm) > Oct 15 19:27:55: booting > Oct 15 19:27:55: bhyveload -m 8GB -e autoboot_delay=3 -e boot_serial=NO -d > /vm/.iso/FreeBSD-13.0-CURRENT-amd64-20191011-r353427-memstick.img tbedfc > Oct 15 19:27:59: [bhyve options: -c 2 -m 8GB -AHP -U > 737d1159-ef36-11e9-847a-0cc47ab3cfd4 -u] > Oct 15 19:27:59: [bhyve devices: -s 0,hostbridge -s 31,lpc -s > 4:0,virtio-blk,/vm/tbedfc/disk0.img -s > 5:0,virtio-net,tap0,mac=58:9c:fc:02:46:e2] > Oct 15 19:27:59: [bhyve console: -l com1,stdio] > Oct 15 19:27:59: [bhyve iso device: -s > 3:0,ahci-hd,/vm/.iso/FreeBSD-13.0-CURRENT-amd64-20191011-r353427-memstick.img] > Oct 15 19:27:59: starting bhyve (run 1) > Oct 15 19:29:54: bhyve exited with status 1 > Oct 15 19:29:54: destroying network device tap0 > Oct 15 19:29:55: stopped > root@vm:~ # > > but also freezed ;-( I've listed all boot variables at loader prompt: Type '?' for a list of commands, 'help' for more detailed help. OK show LINES=24 ansi_caption[1]=^[1mB^[moot Multi User ^[1m[Enter]^[m ansi_caption[2]=Boot ^[1mS^[mingle User ansi_caption[3]=^[1mEsc^[mape to loader prompt ansi_caption[5]=Kernel: default/kernel (1 of 2) ansi_caption[5][0]=Kernel: default/kernel (1 of 2) ansi_caption[5][1]=Kernel: kernel.old (2 of 2) ansi_caption[6]=Configure Boot ^[1mO^[mptions... autoboot_delay=NO beansi_bootfs=^[1mbootfs: ^[m beansi_current=^[1mActive: ^[m beansi_page=^[1mP^[mage: beansi_pageof= of bemenu_bootfs=bootfs: bemenu_current=Active: bemenu_page=[P]age: bemenu_pageof= of boot_serial=NO bootenv_autolist=YES bootenv_root[2]= bootenvmenu_command[1]=be_draw_screen 1 goto_menu bootenvmenu_command[2]=set_bootenv bootenvmenu_command[3]=set_be_page beansi_bootfs=^[1mbootfs: ^[m beansi_current=^[1mActive: ^[m beansi_page=^[1mP^[mage: beansi_pageof= of bemenu_bootfs=bootfs: bemenu_current=Active: bemenu_page=[P]age: bemenu_pageof= of boot_serial=NO bootenv_autolist=YES bootenv_root[2]= bootenvmenu_command[1]=be_draw_screen 1 goto_menu bootenvmenu_command[2]=set_bootenv bootenvmenu_command[3]=set_be_page bootenvmenu_init=init_bootenv bootenvmenu_keycode[1]=8 bootenvmenu_keycode[2]=97 bootenvmenu_keycode[3]=112 bootenvmenu_options=4 bootenvmenu_optionstext=Boot Environments: bootfile=kernel console=userboot currdev=disk0s2a: efi_max_resolution=1x1 hint.acpi_throttle.0.disabled=1 hint.atkbd.0.at=atkbdc hint.atkbd.0.irq=1 hint.atkbdc.0.at=isa hint.atkbdc.0.port=0x060 hint.atrtc.0.at=isa hint.atrtc.0.irq=8 hint.atrtc.0.port=0x70 hint.attimer.0.at=isa hint.attimer.0.irq=0 hint.attimer.0.port=0x40 hint.fd.0.at=fdc0 hint.fd.0.drive=0 efi_max_resolution=1x1 hint.acpi_throttle.0.disabled=1 hint.atkbd.0.at=atkbdc hint.atkbd.0.irq=1 hint.atkbdc.0.at=isa hint.atkbdc.0.port=0x060 hint.atrtc.0.at=isa hint.atrtc.0.irq=8 hint.atrtc.0.port=0x70 hint.attimer.0.at=isa hint.attimer.0.irq=0 hint.attimer.0.port=0x40 hint.fd.0.at=fdc0 hint.fd.0.drive=0 hint.fd.1.at=fdc0 hint.fd.1.drive=1 hint.fdc.0.at=isa hint.fdc.0.drq=2 hint.fdc.0.irq=6 hint.fdc.0.port=0x3F0 hint.p4tcc.0.disabled=1 hint.ppc.0.at=isa hint.ppc.0.irq=7 hint.psm.0.at=atkbdc hint.psm.0.irq=12 hint.sc.0.at=isa hint.sc.0.flags=0x100 hint.uart.0.at=isa hint.uart.0.flags=0x10 hint.uart.0.irq=4 hint.uart.0.port=0x3F8 hint.uart.1.at=isa hint.uart.1.irq=3 hint.uart.1.port=0x2F8 interpret=OK kernel=kernel kernel[0]=kernel hint.psm.0.at=atkbdc hint.psm.0.i
VM freezed at booting of FreeBSD-13.0-CURRENT-amd64-20191011-r353427-memstick.img
2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: igb0 flags=143 ifmaxaddr 0 port 1 priority 128 path cost 2 groups: bridge vm-switch viid-4c918@ nd6 options=1 vm-local: flags=8843 metric 0 mtu 1500 ether 8a:d0:25:7d:f7:51 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: tap0 flags=143 ifmaxaddr 0 port 6 priority 128 path cost 200 member: igb1 flags=143 ifmaxaddr 0 port 2 priority 128 path cost 2 groups: bridge vm-switch viid-f5dda@ nd6 options=1 tap0: flags=8943 metric 0 mtu 1500 description: vmnet-tbedfc-0-local options=8 ether 58:9c:fc:10:ff:df groups: tap vm-port media: Ethernet autoselect status: active nd6 options=29 Opened by PID 85496 root@vm:~ # Whats' wrong ? BTW 12.1-PRERELEASE(r352368) and 12.0-RELEASE-p10(r352368) are nothing happened. [1] https://github.com/TrueFC/ports/tree/master/sysutils/vm-bhyve-devel --- KIRIYAMA Kazuhiko ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve manager
At Sun, 25 Feb 2018 08:56:09 -0800 (PST), Rodney W. Grimes wrote: > > > Hi, > > > > What do folks use for their bhyve guest management? > > > > I have always spun bhyve guests up by hand but now I'm considering > > streamlining the process. What do you use? > > Personally I use vm-byve with some local hacking on it to remove things MeToo :) vm-bhyve is very simple and intuitive and also easy to modify. I've modified sevral parts as follows: (1) vm image name could be included blanks (2) can be treat with *.img images (3) add force options for destroy or rename I've created vm-bhyve-devel port including above diffs and it's tarball and package were up at [1] and [2]. [1] http://ds.truefc.org/~kiri/freebsd/ports/vm-bhyve-1.2b.tar.gz[ [2] http://ds.truefc.org/~kiri/freebsd/packages/vm-bhyve-devel-1.2b.txz > like 16 character VM names and to allow me to set wired memory from > the config file. Oh, and the CPU output column needs some hackery > after my cpu topology changes as that field can become very wide. > > -- > Rod Grimes rgri...@freebsd.org > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscr...@freebsd.org" > --- KIRIYAMA Kazuhiko ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
