On 4/26/21 2:07 PM, Matt Churchyard wrote:
What does /etc/fstab look like inside the guest?
# cat /etc/fstab
# DeviceMountpoint FStype Options DumpPass#
/dev/vtbd0a / ufs rw 1 1
/dev/vtbd0b noneswapsw 0 0
bye &
Hello.
I've asked about this in the past (around January) and somehow I got
some suggestions.
Either that helped me solve the problem, but now it's back, or I never
rebooted the host and simply forgot about it.
In any case...
Due to a 12.x specific bug, I run a 11.3 guest using vm-bhyve.
This
On 1/14/21 10:04 PM, Jason Tubnor wrote:
We clearly define volmode=dev on the zvol for all guests to prevent the
host geom activities taking hold of the volume. Setting it to 'dev'
will make the host ignore it and won't cause issues when bhyve goes to
use it.
This should fix the problem you
On 1/14/21 5:47 AM, Jason Tubnor wrote:
Is your guest running within a zvol?
Yes!
I've got disk0_dev="sparse-zvol" in my vm-bhyve config file.
What is the volmode parameter set to on that zvol?
# zfs get volmode zroot/vm/f11b/disk0
NAME PROPERTY VALUESOURCE
zroot/vm
On 1/13/21 7:30 PM, Allan Jude wrote:
Do you happen to have a ZFS partition?
Not sure what you mean:
_ the host is all ZFS based;
_ the guest has only an UFS partition.
I think some changes to some of the bootstrap (pre-loader) code that is
shared with bhyve-load, means it always prefers Z
Hello.
Due to a 12.x specific bug, I run a 11.3 guest using vm-bhyve.
This is its config:
loader="bhyveload"
cpu=1
memory=512M
network0_type="virtio-net"
network0_switch="public"
disk0_type="virtio-blk"
disk0_name="disk0"
disk0_dev="sparse-zvol"
uuid="..."
network0_mac="..."
On monday I upgrad
On 1/8/21 7:58 PM, Andrea Venturoli wrote:
Hello.
I'm tracking the quarterly port branches and building my packages with
poudriere.
Today I switched from 2020Q4 to 2021Q1 and upgraded VirtualBox from
5.2.44_3 to 5.2.44_4.
After that I can no longer start any guest.
What I get:
VDI:
Hello.
I'm tracking the quarterly port branches and building my packages with
poudriere.
Today I switched from 2020Q4 to 2021Q1 and upgraded VirtualBox from
5.2.44_3 to 5.2.44_4.
After that I can no longer start any guest.
What I get:
VDI: error reading pre-header in 'vdi' (VERR_DEV_IO_ER
On 2020-07-14 10:34, Peter Grehan wrote:
You may need a recent Windows viostor driver. A working configuration
was reported in
https://github.com/virtio-win/kvm-guest-drivers-windows/issues/392
Thanks.
I saw that page and hoped the binary version I downloaded already had
that change a
On 2020-07-12 15:13, Felix Palmen wrote:
* Andrea Venturoli [20200707 18:18]:
I have yet to try this, but, as I said, I switched temporaly to ahci-hd and
used the instructions at the following link to reclaim space (without the
need to start a new zvol):
https://winaero.com/blog/trim-ssd
On 2020-07-13 15:26, D'Arcy Cain wrote:
Am I missing something?
No idea, really.
It works for me, but I always specify
graphics_listen and graphics_port in config file. Give it a try, eventually.
What version of FreeBSD are you using?
bye
av.
___
On 2020-07-07 17:40, Felix Palmen wrote:
As I don't have background knowledge how TRIM works exactly: Should
guests that support it automatically free unused space when running on
the updated bhyve? Or would I have to do a "clean restart", by creating
a new zvol and copying everything over in th
Hello.
I'm running zvol-backed Windows guests in bhyve on FreeBSD 12.1.
Over time, I see the zvol effectively used space grow in size: a sign
that Windows isn't trimming it.
I'm using virtio-blk: I guess this driver does not support trim?
I see reports that this support was added, but it's not
On 2020-04-20 12:06, Jason Tubnor wrote:
On Mon., 20 Apr. 2020, 7:09 pm Felix Palmen, wrote:
Xeon are not affected, since they have vAPIC, so they should be already
running as fast as possible. Correct?
I don't know the details, but on my Xeon E3-1240L v5, it did have a huge
effect.
I co
On 2020-04-19 19:23, Michael Reifenberger wrote:
Hi,
r358848 has been MFC'd to stable/12
Hello.
Can I ask some questions about this?
First: this patch seems to apply cleanly to 12.1. Is it safe? At least
worth testing?
Second.
IIUIC it's useless to test this on an AMD system, since the pat
On 2020-03-02 10:26, Matt Churchyard wrote:
This is likely caused by an issue in the way vm-bhyve handled stdio, which only
worked correctly with older builds of bhyve.
I would recommend installing vm-bhyve from ports (you should get version
1.4.2), which hopefully will boot using bhyveload w
On 2020-03-01 16:58, Rodney W. Grimes wrote:
THis again looks very much like the "lost console" issue of the system
flipping to a serial console and your trying to access it via a
graphical console interface.
Thanks for your suggestion.
One thing to try is to stop in the loader and do this
Hello.
I'd like to run a FreeBSD 11.3 VM under FreeBSD 12.1.
As I'm already using vm-bhyve to run a Windows guest, I think the best
(or possibly only) choice is to use bhyve for the FreeBSD guest too.
I've got the following conf file:
guest="freebsd"
loader="bhyveload"
cpu=1
memory=512M
netw
On 2019-04-29 09:45, Patrick M. Hausen wrote:
What’s keeping you from increasing that timeout for your
particular requirements? IMHO 2 minutes are a reasonable
default for a system that does not run hypervisor VMs -
which is probably the vast majority.
Anyone with the knowledge to implement a v
On 10/26/18 12:05 PM, Andrea Venturoli wrote:
I'm trying sysctl net.link.bridge.inherit_mac=1, to see if it makes any
difference.
It looks like this does the trick, although I'm not sure yet; however,
it breaks other things.
In fact, in order to get a more deterministic behaviour
On 10/26/18 10:03 AM, Harry Schmalzbauer wrote:
Have you checked inside the guest that it really uses the defined MAC
with the interface?
Yes, IPCONFIG /ALL shows the MAC address I specificed in the vmbhyve
config file.
Other than that I don't have an idea. Gateway MAC is also taken into
Hello.
I've got a FreeBSD 11.2/amd64 + vm-bhyve + Windows 10 pro.
I'm building the network bridge statically, i.e., I have the following
in /etc/rc.conf:
cloned_interfaces="bridge0 tap0"
ifconfig_bridge0="up addm igb0"
I'm using virtio network drivers and I'm also fixing the MAC address;
i.e
Hello.
I've got a FreeBSD 11.2 box running vm-bhyve with two Windows virtual
machines, each with an instance of MS SQL server.
Everything works fine normally, but there's a specific operation which
will impose an high CPU load on the machine and last several minutes,
when it's expected to ge
On Thu, 16 Feb 2017 11:37:44 +1030, Shane Ambler wrote:
CC'ing to freebsd-virtualization as a better place to ask this.
Thanks, I hadn't noticed this list; I subscribed now.
I might be in need to permanently run a Windows 64b VM (with SQL server)
on a new FreeBSD box, so...
Permanently a
On Thu, 16 Feb 2017 10:46:34 +0100, Harry Schmalzbauer wrote:
Hello,
it depends on the features you need.
Not much, really.
Running SQL Server Express (for now) with decent performance.
· virtio-blk and jumbo frames (e1000 works with jumbo frames but
performance is not comparaable with ES
25 matches
Mail list logo
