Hi All,
I've just committed an update to the emulators/open-vm-tools port which updates
it to the 9.2.3 release of open-vm-tools and fixes the build on FreeBSD
11-CURRENT. I'm still having trouble with the 9.4.0 release of open-vm-tools,
but this at least gets us closer to the latest and greatest.
Hi,
I experienced a bhyve VM crash with this message:
vm exit[1]
reason VMX
rip 0x80c7490b
inst_length 3
status 0
exit_reason 2
qualification 0x
inst_type 0
The host is running FreeBSD 11.0-CURRENT r264056.
The guest is running FreeBSD 10.0-RELEASE r260789.
Steve
On Tue, Apr 08, 2014 at 02:39:00PM -0400, Aryeh Friedman wrote:
> What was the guest OS?
>
>
> On Tue, Apr 8, 2014 at 2:28 PM, Steve Wills wrote:
>
> > Hi,
&g
On Tue, Apr 08, 2014 at 11:43:27AM -0700, Peter Grehan wrote:
> Hi Steve,
>
> > I experienced a bhyve VM crash with this message:
> >
> > vm exit[1]
> > reason VMX
> > rip 0x80c7490b
> > inst_length 3
> > status 0
> >
Yep,
/usr/sbin/bhyveload -m 12G -d /vm/100amd64/disk.img -c /dev/nmdm1A 100amd64
Steve
On Wed, Apr 09, 2014 at 04:54:36AM +0900, Takuya ASADA wrote:
> Did you execute bhyveload before bhyve?
>
>
> 2014-04-09 4:26 GMT+09:00 Steve Wills :
>
> > On Tue, Apr 08, 2014 at 11
On Tue, Apr 08, 2014 at 02:14:32PM -0700, Peter Grehan wrote:
> Hi Steve,
>
> > The VM was building ports. I could try to deduce which ports, but I
> > wouldn't be 100% sure.
>
> Probably no need, unless this can be repro'd by building that
> particular port.
Ok, I'll keep an eye out for that.
Hi,
I'm trying to install FreeBSD 8.4 in bhyve, but running into some issues.
Sysinstall doesn't seem to like the disk. In the partition editor, I get:
Disk name: vtbd1 FDISK Partition Editor
DISK Geometry: 0 cyls/0 heads/0 sectors = 0 sectors (0MB)
Offset
On Thu, Apr 10, 2014 at 12:07:22PM -0700, Peter Grehan wrote:
> Hi Steve,
>
> > I'm trying to install FreeBSD 8.4 in bhyve, but running into some issues.
> > Sysinstall doesn't seem to like the disk. In the partition editor, I get:
> >
> > Disk name: vtbd1 FDI
Hi,
Can someone help me understand the cpu pinning feature in bhyve? I'm afraid the
docs have confused me:
-p pinnedcpu
Force guest virtual CPUs to be pinned to host CPUs. Virtual CPU n is pinned
to host CPU pinnedcpu+n.
What would the arg looks like? Something like -p 0,1,2,3 ?
Also, is
Hi,
A bhyve VM I run had this:
pid 79784 (bhyve), uid 0: exited on signal 6 (core dumped)
and the only thing on the console was this:
ahcich0: Timeout on slot 27 port 0
ahcich0: is cs ss rs tfd 50 serr
cmd 1000c017
(ada0:ahcich0:0:0:0): READ_FPDMA_Q
Hi,
Currently it seems bhyve has a max of 16 virtual CPUs, is that right? Or am I
misunderstanding something? And if so, can we get that increased to 32 at
least?
Thanks,
Steve
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org
Hi,
I'm running a FreeBSD guest in bhyve on a FreeBSD host. Both are running
FreeBSD CURRENT, r266947. I've gotten this message about 12 times since boot:
interrupt storm detected on "irq268:"; throttling interrupt source
vmstat -i shows:
irq268: ahci1 236514222839
ahc
On Sat, Jun 07, 2014 at 02:53:05PM -0700, Neel Natu wrote:
> Hi Steve,
>
> On Sat, Jun 7, 2014 at 2:28 PM, Peter Grehan wrote:
> > Hi Steve,
> >
> >
> >> I'm running a FreeBSD guest in bhyve on a FreeBSD host. Both are running
> >> FreeBSD CURRENT, r266947. I've gotten this message about 12 times
On Sat, Jun 07, 2014 at 02:53:05PM -0700, Neel Natu wrote:
> Hi Steve,
>
> On Sat, Jun 7, 2014 at 2:28 PM, Peter Grehan wrote:
> > Hi Steve,
> >
> >
> >> I'm running a FreeBSD guest in bhyve on a FreeBSD host. Both are running
> >> FreeBSD CURRENT, r266947. I've gotten this message about 12 times
On Wed, Jun 11, 2014 at 09:18:17AM +, Steve Wills wrote:
> On Sat, Jun 07, 2014 at 02:53:05PM -0700, Neel Natu wrote:
> > Hi Steve,
> >
> > On Sat, Jun 7, 2014 at 2:28 PM, Peter Grehan wrote:
> > > Hi Steve,
> > >
> > >
> > >> I&#x
Hi,
Just had a bhyve crash on 11-CURRENT. The host is r267362. The guest is
r266947. The crash was:
pid 38256 (bhyve), uid 0: exited on signal 6 (core dumped)
(The formatting of this may be off a bit)
vmexit[12]
reason VMX
rip 0x80d9e11d
inst_length 3
status
on %p held by
%p",
435 __func__, m, owner);
(kgdb)
I'm told that MTX_CONTESTED was set on the unlocked mtx and that MTX_CONTENDED
is spuriously left behind, and to ask how lock prefix is handled in bhyve. Any
of that make sense to anyone?
Thanks,
Steve
On Sun, Jul 0
On Sun, Jul 06, 2014 at 12:28:07PM -0400, Ryan Stone wrote:
> On Sun, Jul 6, 2014 at 11:46 AM, Steve Wills wrote:
> > I should have noted this system is running in bhyve. Also I'm told this
> > panic
> > may be related to the fact that the system is running in bhyv
On Sun, Jul 06, 2014 at 01:49:04PM -0700, Neel Natu wrote:
> Hi Steve,
>
> On Sun, Jul 6, 2014 at 8:46 AM, Steve Wills wrote:
> > I should have noted this system is running in bhyve. Also I'm told this
> > panic
> > may be related to the fact that the system is r
Hi,
I'd like anyone possible to test an updated version of
emulators/open-vm-tools{,-nox11}. I have the patch here for those who
wish to build themselves:
https://people.freebsd.org/~swills/open-vm-tools/open-vm-tools-10.1.0.diff
And for those who wish to test using packages, I've built packages
Hi,
On 01/21/2017 09:13, Kurt Jaeger wrote:
> Hi!
>
>> I'd like anyone possible to test an updated version of
>> emulators/open-vm-tools{,-nox11}. I have the patch here for those who
>> wish to build themselves:
>>
>> https://people.freebsd.org/~swills/open-vm-tools/open-vm-tools-10.1.0.diff
>
>
tream is looking at that.
This is likely the final change before I commit this, which currently I
plan to do on 3/15. So if you use it, now is your chance to test and
report issues.
Steve
On 01/19/2017 16:59, Steve Wills wrote:
> Hi,
>
> I'd like anyone possible to test an
Hi,
On 03/01/2017 05:14, Julian Elischer wrote:
> On 1/3/17 1:57 pm, Steve Wills wrote:
>> Hi All,
>>
>> Thanks to everyone who tested.
> Hi I haven't tested your new tools but I needed to do the following in
> the previous version.
> (otherwise I coudl have
Hello Everyone,
It's that time again, time to test another open-vm-tools update.
Everything is in basically the same place as last time.
The patch is here:
https://people.freebsd.org/~swills/open-vm-tools/open-vm-tools-10.1.5.diff
Note there are a good number of patches being renamed, so be sur
Hmm, I think I saw this when using the -W flag to bhyve and removing
that avoided it.
Steve
On 8/31/20 8:38 AM, Peter Grehan wrote:
This appears to be an MP issue: if the number of vCPUs in the win10
guest is set to 1, I'm unable to trigger this. However, it happens
almost immediately with vC
25 matches
Mail list logo
