Date: Sat, 2 Jul 2016 00:29:33 -0700 From: Peter Grehan <grehan@freebsd.org> To: Jan Beich <jbeich@vfemail.net> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: VirtIO Ethernet driver in DragonFlyBSD under FreeBSD bhyve Message-ID: <d236f01b-7318-8619-66a0-1eb4ed827468@freebsd.org> In-Reply-To: <ziq5-vuhz-wny@vfemail.net> References: <9893747.yFCcEWVR7f@gizmo.my.domain> <56ABFE12.4060805@freebsd.org> <60sv-b0so-wny@vfemail.net> <b790cba6-dc86-aa51-2058-33525a6b4bd6@freebsd.org> <ziq5-vuhz-wny@vfemail.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Jan,
> I've used a daily snapshot where the installer still doesn't support
> GPT/EFI yet. Tested as
>
> $ bhyve -l com1,stdio -l bootrom,BHYVE_UEFI.fd -m 4G -s 0,hostbridge \
> -s 31,lpc -s 4,virtio-blk,/dev/md0 -s 5,virtio-net,tap0 vm0
Thanks for the info. There's definitely an interrupt issue with virtio
on bhyve and DFly. The MSI capability confuses DFly, but when I took
that out, interrupt storms resulted in hanging the VM.
Using ahci-hd instead of virtio-blk will give you a working boot,
though without networking until the interrupt situation is debugged :(
On this:
> Does it crash with less than 4G of RAM for you as well?
>
> $ bhyve -m 1G ...
> Unhandled memory access to 0x100000000
> Failed to emulate instruction [0x81 0x3c 0x8f 0x5f 0x4d 0x50 0x5f
0x75 0x0e 0xeb 0x05 0xb9 0x00 0x00 0x00] at 0xffffffff80a2e0a7
From DFly kgdb, the RIP is
(kgdb) x/i 0xffffffff80a2e217
0xffffffff80a2e217 <mptable_search_sig+108>:
cmpl $0x5f504d5f,(%rdi,%rcx,4)
.. so it's the MPTable scan that is failing. I'll look into this one
as well.
later,
Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d236f01b-7318-8619-66a0-1eb4ed827468>