Re: fatal; loader returned error 139

2021-02-07 Thread KIRIYAMA Kazuhiko
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

fatal; loader returned error 139

2021-02-04 Thread KIRIYAMA Kazuhiko
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

To late to build packages in arm64/aarch64 on qemu

2020-08-27 Thread KIRIYAMA Kazuhiko
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

Re: Why qemu-system-aarch64 so late to process ?

2020-08-16 Thread KIRIYAMA Kazuhiko
(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

Why qemu-system-aarch64 so late to process ?

2020-08-10 Thread KIRIYAMA Kazuhiko
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

Re: Can't system_powerdown in qemu-system-aarch64 monitor

2020-06-29 Thread KIRIYAMA Kazuhiko
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 >

Can't system_powerdown in qemu-system-aarch64 monitor

2020-06-18 Thread KIRIYAMA Kazuhiko
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

Re: Bhyve and QEMU

2020-01-07 Thread KIRIYAMA Kazuhiko
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

Can't boot arm64 image by qemu-system-aarch64

2019-11-28 Thread KIRIYAMA Kazuhiko
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.or

Re: VM freezed at booting of FreeBSD-13.0-CURRENT-amd64-20191011-r353427-memstick.img

2019-10-15 Thread KIRIYAMA Kazuhiko
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 ) > >

Re: VM freezed at booting of FreeBSD-13.0-CURRENT-amd64-20191011-r353427-memstick.img

2019-10-15 Thread KIRIYAMA Kazuhiko
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/fre

VM freezed at booting of FreeBSD-13.0-CURRENT-amd64-20191011-r353427-memstick.img

2019-10-15 Thread KIRIYAMA Kazuhiko
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 --- KIRIYAM

Re: bhyve manager

2018-02-25 Thread 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" > --- KIRIYAMA Kazuhiko