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: nbdkit on FreeBSD
> On Wed, Jun 17, 2020 at 9:53 PM Rodney W. Grimes < > freebsd-...@gndrsh.dnsmgr.net> wrote: > > > > Does anybody use nbdkit on FreeBSD? It's a fancy NBD (Network Block > > > Device) server. It runs fine on FreeBSD, but there's no port. If > > anybody > > > is interested, I'll make a port for it. However, if I'm the only one > > then > > > I won't bother. > > > > > > https://github.com/libguestfs/nbdkit/ > > > > I am not sure if this is what I looked at, but I was looking > > for a way to do old style sun "nd", and this looks to be 1/2 > > of that, in that I see a server, but no client for the kernel. > > > > I would be interested in NBD if we have both ends. > > > > There's lots of 'other ends' including qemu for this. I specifically meant native FreeBSD kernel. > This is really cool! > > Warner -- 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"
Re: nbdkit on FreeBSD
On Wed, Jun 17, 2020 at 9:53 PM Rodney W. Grimes < freebsd-...@gndrsh.dnsmgr.net> wrote: > > Does anybody use nbdkit on FreeBSD? It's a fancy NBD (Network Block > > Device) server. It runs fine on FreeBSD, but there's no port. If > anybody > > is interested, I'll make a port for it. However, if I'm the only one > then > > I won't bother. > > > > https://github.com/libguestfs/nbdkit/ > > I am not sure if this is what I looked at, but I was looking > for a way to do old style sun "nd", and this looks to be 1/2 > of that, in that I see a server, but no client for the kernel. > > I would be interested in NBD if we have both ends. > > > -Alan > -- > Rod Grimes > rgri...@freebsd.org In fact, Ryan Moeller wrote a ggate-based client for FreeBSD. I haven't tried it myself. The main motivation is to use it with Scaleway, a cloud hosting company that offers arm64 servers, but they need to boot from NBD. https://github.com/freqlabs/nbd-client -Alan ___ 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"
[Bug 246647] Request Errata Notice (EN) for bug 229852 and bug 245392 in releng/12.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246647 --- Comment #16 from Philip Paeps --- I think we can include this in our next batch of errata/advisories. I think we have everything we need. The merge looks straightforward. Thank you! -- You are receiving this mail because: You are on the CC list for the bug. ___ 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"
[Bug 246647] Request Errata Notice (EN) for bug 229852 and bug 245392 in releng/12.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246647 --- Comment #15 from Peter Grehan --- Ed/Philip - anything else that needs to be done here ? Would it help if I supplied a diff ? -- You are receiving this mail because: You are on the CC list for the bug. ___ 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: nbdkit on FreeBSD
On Thu, Jun 18, 2020 at 5:03 AM alan somers wrote: > > Does anybody use nbdkit on FreeBSD? It's a fancy NBD (Network Block > Device) server. It runs fine on FreeBSD, but there's no port. If anybody > is interested, I'll make a port for it. However, if I'm the only one then > I won't bother. > > https://github.com/libguestfs/nbdkit/ I would say just make a port if making it isn't that painful. Having a port might also attract more users, and it cloud save your upgrading time in the future. It would be nice to also let upstream know there is demand of using it on FreeBSD. Li-Wen ___ 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"
[Bug 244721] bhyve: Silence ACPI RTC error/warning in Linux guests
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244721 Peter Grehan changed: What|Removed |Added CC||gre...@freebsd.org --- Comment #2 from Peter Grehan --- I'd held off this until looking at Linux source to make sure there weren't any side-effects, but this doesn't appear to be any worse than the RTC's currently unimplemented calendar alarms, so I'll get this in. Thanks ! -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
