https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229167
--- Comment #14 from commit-h...@freebsd.org ---
A commit references this bug:
Author: dexuan
Date: Sat Jul 7 00:41:05 UTC 2018
New revision: 336054
URL: https://svnweb.freebsd.org/changeset/base/336054
Log:
hyperv: Fix boot-up after ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220453
--- Comment #19 from Dexuan Cui ---
(In reply to scorpionmage from comment #18)
Let's track the vmbus_msghc_exec() panic in bug 229167. I'm going to commit a
fix soon.
--
You are receiving this mail because:
You are the assignee for the b
hi there - this is in relation to this ticket:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791
"ena driver causing kernel panics on AWS EC2"
reading through the thread, and Colin's blog post on the new M5 instance
types, it looks like the issues people are running into are related to
On 06/07/2018 18:32, Rodney W. Grimes wrote:
Untested, but since memstick is actually a "disk" image and not
a "cdrom" image you should be able to do something like
vmrun.sh -c 2 -m 4096M -t tap0 -d memstick.img -d guest.img guestname
Your memstick should show up as ada0,
and your guest.img shou
> Hello,
>
> context: freebsd-12-current server, amd64
>
> I usually install a freebsd guest like this:
>
> sh /usr/share/examples/bhyve/vmrun.sh -c 2 -m 4096M -t tap0 -d guest.img
> -i -I FreeBSD-installation-dvd1.iso guestname
>
> I only have memstick.img - how do I either:
>
> 1. convert t
Hello,
context: freebsd-12-current server, amd64
I usually install a freebsd guest like this:
sh /usr/share/examples/bhyve/vmrun.sh -c 2 -m 4096M -t tap0 -d guest.img
-i -I FreeBSD-installation-dvd1.iso guestname
I only have memstick.img - how do I either:
1. convert the memstick to dvd1.is
Hello,
I have configured passthrough of two different PCI Express network
interface cards. I can't get neither OpenBSD nor NetBSD to work with these
NICs.
I get this in dmesg when booting the NetBSD install:
wm0 at pci0 dev 5 function 0: 82576 quad-1000BaseT Ethernet (rev. 0x01)
pci_intr_map: no
Normally I would be using virtio-net, and advise as much with vm-bhyve.
It is sometimes useful to use e1000 briefly in order to have Internet access to
download drivers…
This machine is just for testing and I hadn’t bothered going through the
process of finding and installing virtio drivers, mini
Thanks for the replies guys. I've increased memory and switched to virtio-net.
Been running for an hour or two so far. Windows just complains about the boot
device if I try to move to virtio-blk.
I might set up another test using different settings during installation and
see how that goes.
Onl
Dave,
you got working Windows guest with virtio-blk?
I thought it was still unstable. I've tested virtio storage (on bhyve) +
virtio storage drivers on several windows guest ~ 2 months ago and they
were crashing all the time.
So I use ahci-hd with every windows guest we run (from 7 to Win S
On Fri, 6 Jul 2018, at 10:22, Matt Churchyard wrote:
> Hello,
>
> I have a server 2016 virtual machine which I only created for testing
> and don't use much. Booting it up recently I've found that it locks up
> consistently within a few minutes of booting. What can I do to try and
> figure out
Hi sorry on mobile so replying top.
I've got some 2016 guests running close to 12 months uptime. Just some
ideas below:
RAM allocation a little low for 2016 so bump that a little.
I use zvol for ahci storage with 4k blocks but have run 8k blocks as well.
MSSQL doesn't like anything more than 4k.
Hello,
I have a server 2016 virtual machine which I only created for testing and don't
use much. Booting it up recently I've found that it locks up consistently
within a few minutes of booting. What can I do to try and figure out what's
causing the problem?
Host was recently updated to 11.2
#
13 matches
Mail list logo
