Re: stable/13, vm page counts do not add up

On Tue, 13 Apr 2021 17:18:42 -0400 Mark Johnston wrote: > > P.S. > > I have not been running any virtual machines. > > I do use nvidia graphics driver. > In past I had report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238698 Now I switch to AMD and got only ~1Gb memory allocated by

Re: stable/13, vm page counts do not add up

On 14/04/2021 16:32, Mark Johnston wrote: On Wed, Apr 14, 2021 at 02:21:44PM +0300, Andriy Gapon wrote: On 14/04/2021 00:18, Mark Johnston wrote: fbt::vm_page_unwire:entry /args[0]->oflags & 0x4/ { @unwire[stack()] = count(); } Unrelated report, dtrace complains about this probe on

Re: stable/13, vm page counts do not add up

On Wed, Apr 14, 2021 at 02:21:44PM +0300, Andriy Gapon wrote: > On 14/04/2021 00:18, Mark Johnston wrote: > > fbt::vm_page_unwire:entry > > /args[0]->oflags & 0x4/ > > { > > @unwire[stack()] = count(); > > } > > Unrelated report, dtrace complains about this probe on my stable/13 system: >

Re: stable/13, vm page counts do not add up

On 14/04/2021 00:18, Mark Johnston wrote: fbt::vm_page_unwire:entry /args[0]->oflags & 0x4/ { @unwire[stack()] = count(); } Unrelated report, dtrace complains about this probe on my stable/13 system: failed to resolve translated type for args[0] And I do not have any idea why...

Re: stable/13, vm page counts do not add up

On Tue, Apr 13, 2021 at 05:01:49PM +0300, Andriy Gapon wrote: > On 07/04/2021 23:56, Mark Johnston wrote: > > I don't know what might be causing it then. It could be a page leak. > > The kernel allocates wired pages without adjusting the v_wire_count > > counter in some cases, but the ones I know

Re: stable/13, vm page counts do not add up

On 07/04/2021 23:56, Mark Johnston wrote: > I don't know what might be causing it then. It could be a page leak. > The kernel allocates wired pages without adjusting the v_wire_count > counter in some cases, but the ones I know about happen at boot and > should not account for such a large

RE: stable/13, vm page counts do not add up

> -Original Message- > From: owner-freebsd-curr...@freebsd.org curr...@freebsd.org> On Behalf Of Mark Johnston > Sent: Wednesday, April 7, 2021 10:57 PM > To: Andriy Gapon > Cc: freebsd-stable List ; FreeBSD Current > > Subject: Re: stable/13, vm page counts d

Re: stable/13, vm page counts do not add up

On 8/04/2021 2:59 pm, Helge Oldach wrote: > On Wed, Apr 07, 2021 at 10:42:57PM +0300, Andriy Gapon wrote: >> >> I regularly see that the top's memory line does not add up (and by a >> lot). >> That can be seen with vm.stats as well. >> >> For example: >> $ sysctl

Re: stable/13, vm page counts do not add up

On 8/04/2021 6:56 am, Mark Johnston wrote: > On Wed, Apr 07, 2021 at 11:22:41PM +0300, Andriy Gapon wrote: >> On 07/04/2021 22:54, Mark Johnston wrote: >>> On Wed, Apr 07, 2021 at 10:42:57PM +0300, Andriy Gapon wrote: I regularly see that the top's memory line does not add up (and by a

Re: stable/13, vm page counts do not add up

On Wed, Apr 07, 2021 at 11:22:41PM +0300, Andriy Gapon wrote: > On 07/04/2021 22:54, Mark Johnston wrote: > > On Wed, Apr 07, 2021 at 10:42:57PM +0300, Andriy Gapon wrote: > >> > >> I regularly see that the top's memory line does not add up (and by a lot). > >> That can be seen with vm.stats as

Re: stable/13, vm page counts do not add up

On 07/04/2021 22:54, Mark Johnston wrote: > On Wed, Apr 07, 2021 at 10:42:57PM +0300, Andriy Gapon wrote: >> >> I regularly see that the top's memory line does not add up (and by a lot). >> That can be seen with vm.stats as well. >> >> For example: >> $ sysctl vm.stats | fgrep count >>

Re: stable/13, vm page counts do not add up

On Wed, Apr 07, 2021 at 10:42:57PM +0300, Andriy Gapon wrote: > > I regularly see that the top's memory line does not add up (and by a lot). > That can be seen with vm.stats as well. > > For example: > $ sysctl vm.stats | fgrep count > vm.stats.vm.v_cache_count: 0 >

stable/13, vm page counts do not add up

I regularly see that the top's memory line does not add up (and by a lot). That can be seen with vm.stats as well. For example: $ sysctl vm.stats | fgrep count vm.stats.vm.v_cache_count: 0 vm.stats.vm.v_user_wire_count: 3231 vm.stats.vm.v_laundry_count: 262058 vm.stats.vm.v_inactive_count:

HD audio problem on FreeBSD 12.1 bhyve VM

, the default sound device on my system. I see the following relevant errors: pcm0: chn_write(): pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead pcm0: chn_write(): pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead pin dump from FreeBSD 12.1 VM. -- hdaa0

VM laundry size is always 0

Hello! I’ve got strange values for vm laundry size on -STABLE. And these values do not change even under load. vm.domain.0.stats.laundry: 0 vm.stats.vm.v_laundry_count: 0 I cannot complete buildworld on this box, compiler throughs segmentation core at some random points. I tested RAM and hard

PCI express hotplug in FreeBSD11.2 VM

Hi, I am working on a driver for a PCI express device. And have been trying to get hotplug feature working on a FreeBSD 11.2 VM using both PFs and VFs. (host is Fedora 26) But I am having many issues in relation to this. I am encountering issues with both scenarios, For PF -> 1. Cre

Re: Passing through USB serial to bhyve VM

FWIW, I’ve opened a bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229712 > Am 11.07.2018 um 23:41 schrieb Stefan Bethke : > > It’s been a while since I last dealt with serial devices. Apparently, when > passing through a serial device on the host to a COM port in the

Re: Passing through USB serial to bhyve VM

It’s been a while since I last dealt with serial devices. Apparently, when passing through a serial device on the host to a COM port in the VM, CTS/RTS are not (correctly) passed through. With set ctsrts off in ppp.conf I could get ppp to dial successfully. Stefan > Am 11.07.2018 um 19

Passing through USB serial to bhyve VM

I’m trying to access a Huawei USB LTE stick from a Bhyve VM like so: # cat /var/vm/mgmt/mgmt.conf loader="bhyveload" cpu=1 memory=256M network0_type="virtio-net" network0_switch="lan" disk0_type="virtio-blk" disk0_name="disk0" disk0_dev="

VM image for 11.1-STABLE exhibiting same problem as 12.0-CURRENT. MFC?

VM image for 11.1-STABLE began exhibiting same dislike for USB 3.0 ports as problem reported in PR 225794 for 12.0-CURRENT. Prior to FreeBSD-11.1-STABLE-amd64-20180215-r329320.vmdk.xz no such problem was observed. ___ freebsd-stable@freebsd.org mailing

Re: Unkillable process in "vm map (user)"

eird but also not too puzzling. > > The vmdaemon (pid 41) is running, it tries to reduce the count of resident > pages in some pmap, most likely the one from the pid 20655. This process > seems to be huge: according to the v_stats, there is 15681264 inactive pages, > and the pagedae

Re: Unkillable process in "vm map (user)"

count of resident pages in some pmap, most likely the one from the pid 20655. This process seems to be huge: according to the v_stats, there is 15681264 inactive pages, and the pagedaemon tries to obtain a vm object lock which is owned by vmdaemon, resident count for that object is 15897170 (~64Gb). So bas

Re: Unkillable process in "vm map (user)"

oroutines", and the Go version has no problems with 100 > > goroutines on a much smaller system). > > > > According to SIGINFO, it's blocked on "vm map (user)" but I can't kill > > it. Can anyone suggest a way to unwedge it? > > > > This

Re: Unkillable process in "vm map (user)"

ery > cheap "thread" or "coroutine") joined by "channels" (think message > passing pipes). (The program ran basically instantaneously with 1 > or 10 "goroutines", and the Go version has no problems with 100 > goroutines on a much smaller sy

Unkillable process in "vm map (user)"

nnels" (think message passing pipes). (The program ran basically instantaneously with 1 or 10 "goroutines", and the Go version has no problems with 100 goroutines on a much smaller system). According to SIGINFO, it's blocked on "vm map (user)" but I can't kill it.

Call for testing VMware open-vm-tools update

VMware has been contributing to making FreeBSD a first class citizen for their open source vmware tools. As a continuing part of this contribution there's a new version of open-vm-tools in the works. The INO64 work in FreeBSD HEAD broke building open-vm-tools for HEAD/i386

Re: FreeBSD 11.1-R network slowness on Samba and Windows VM on VirtualBox

> I am compiling a new samba packet from ports, but that slow is weird >>> for >>> me, and I could not find any other cases on web search. >>> >>> thanks, >>> >>> matheus >> >> Hi guys, >> >> I got this still going, whe

Re: FreeBSD 11.1-R network slowness on Samba and Windows VM on VirtualBox

Windows VM and same problem. I reinstalled all ports and same problem. I use Windows shares from another sources (not a VirtualBox VM) and all works fine. Some help were said here https://forums.freebsd.org/threads/61813/, but unfortunately I have no leads so far. I will try to install some 10.3 box

Re: FreeBSD 11.1-R network slowness on Samba and Windows VM on VirtualBox

timeouts and > really slow connection. File copy never past kilobytes per second :( > > I am compiling a new samba packet from ports, but that slow is weird for > me, and I could not find any other cases on web search. > > thanks, > > matheus Hi guys, I got this still going

Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice

> > stable KBI, but in this case it is simpler to add padding than to follow > > > > principles. > > > > > > > > Fixed in 320889, will ask re for MFS permissions in a day. > > > > > > I think this is the commit: > > > https://sv

Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice

ne accessor. > > > > > > Thank you for noting. I do not consider vm_map part of the guaranteed > > > stable KBI, but in this case it is simpler to add padding than to follow > > > principles. > > > > > > Fixed in 320889, will ask re for MFS

Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice

guaranteed > > stable KBI, but in this case it is simpler to add padding than to follow > > principles. > > > > Fixed in 320889, will ask re for MFS permissions in a day. > > I think this is the commit: > https://svnweb.freebsd.org/base/stable/11/sys/vm/vm_ma

Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice

. I think this is the commit: https://svnweb.freebsd.org/base/stable/11/sys/vm/vm_map.h?view=log=320889 Do you think this will get picked up by/for RC3, which will begin on Friday? https://www.freebsd.org/releases/11.1R/schedule.html Thanks! ___ freebsd

Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice

On Mon, Jul 10, 2017 at 01:00:05PM -0700, Mark Johnston wrote: > I suspect that this is a result of r320763. That change removed a field > from struct vm_map_entry, which is embedded in struct vm_map. Virtualbox > does not reference the fields of struct vm_map directly, but it does > call

Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice

On Mon, Jul 10, 2017 at 09:47:50PM +0200, José G. Juanino wrote: > El Monday 10 de July a las 21:24:41 CEST, José G. Juanino escribió: > >El Sunday 09 de July a las 23:48:29 CEST, David Boyd escribió: > >>With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics. I haven't > &

[SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice

El Monday 10 de July a las 21:24:41 CEST, José G. Juanino escribió: El Sunday 09 de July a las 23:48:29 CEST, David Boyd escribió: With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics. I haven't been able to process the panic completely, but the backtrace looks mysteriously similar to those

Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice

El Sunday 09 de July a las 23:48:29 CEST, David Boyd escribió: With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics. I haven't been able to process the panic completely, but the backtrace looks mysteriously similar to those provided with PR219146. Initially, the VM-IMAGE booted just fine

[REVISED] Panic with FreeBSD 11.1-RC2 VM-IMAGE when starting vboxservice

With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics. I haven't been able to process the panic completely, but the backtrace looks mysteriously similar to those provided with PR219146. Initially, the VM-IMAGE booted just fine. The VM-IMAGE is then configured as a VirtualBox client

Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice

With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics. I haven't been able to process the panic completely, but the backtrace looks mysteriously similar to those provided with PR219146. Initially, the VM-IMAGE booted just fine. The VM-IMAGE is then configured as a VirtualBox client

[LOR] 11.1-BETA1 dev/md/md.c <-> vm/vm_pager.c - lost begnin matchlist

found a previous report about: lock order reversal: 1st 0xfe03bca22c10 bufwait (bufwait) @ /usr/local/share/deploy-tools/RELENG_11/src/sys/vm/vm_pager.c:370 2nd 0xf8001f9ff068 ufs (ufs) @ /usr/local/share/deploy-tools/RELENG_11/src/sys/dev/md/md.c:942 stack backtrace: #0 0x805e79b0

Re: Call for testing: VM bugs in 10.3

Hello I’ve run with this patch applied on two servers, on top of FreeBSD 10.3: 1) On a fast real server which was not experiencing the problem (skylake+c236+nvme) 2) On a slow virtual server (ESXi 5.5, running on 6 year old hardware) which I think was experiencing this problem when

Re: Call for testing: VM bugs in 10.3

xes object lifecycle r301436 do not leak the vm object lock, fixes overcommit disable r302243 avoid the active object marking for vm.vmtotal sysctl, fixes "vodead" hangs r302513 vm_fault() race with the vm_object_collapse(), fixes spurious SIGSEGV r303291 postpone BO_DEAD, fixes

Re: Call for testing: VM bugs in 10.3

I tested the patch on a 10.3-RELEASE-p7 system and so far no problems for last 2 days. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to

Re: Call for testing: VM bugs in 10.3

xes object lifecycle r301436 do not leak the vm object lock, fixes overcommit disable r302243 avoid the active object marking for vm.vmtotal sysctl, fixes "vodead" hangs r302513 vm_fault() race with the vm_object_collapse(), fixes spurious SIGSEGV r303291 postpone BO_DEAD, fixes

Re: Call for testing: VM bugs in 10.3

3291, then you already have that patches. The first sentence of my mail stated that the backport is from stable/10 to 10.3. Anyway, I put the patch at https://kib.kiev.ua/kib/vm-10.3-bp.1.patch . ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.o

Re: Call for testing: VM bugs in 10.3

andom SIGSEGV delivered to processes, hangs on "vodead" state > > on filesystem operations, and several others. > > > > List of the merged revisions: > > r301184 prevent parallel object collapses, fixes object lifecycle > > r301436 do not leak the vm object lo

Re: Call for testing: VM bugs in 10.3

of the merged revisions: > r301184 prevent parallel object collapses, fixes object lifecycle > r301436 do not leak the vm object lock, fixes overcommit disable > r302243 avoid the active object marking for vm.vmtotal sysctl, fixes > "vodead" hangs > r302513 vm_

Re: Call for testing: VM bugs in 10.3

d several others. > > List of the merged revisions: > r301184 prevent parallel object collapses, fixes object lifecycle > r301436 do not leak the vm object lock, fixes overcommit disable > r302243 avoid the active object marking for vm.vmtotal sysctl, fixes > "vodead"

Call for testing: VM bugs in 10.3

for the handling of radix insertion failures. Included fixes are for random SIGSEGV delivered to processes, hangs on "vodead" state on filesystem operations, and several others. List of the merged revisions: r301184 prevent parallel object collapses, fixes object lifecycle r301436 do not leak the

10.2-Stable crash when VirtualBox VM running on suspend?

I have twice had my laptop crash when I inadvertently had a Windows 7 VM running at the time of the suspend. I can certainly understand how this could happen, but should it? It's way too easy to forget to "Save the machine state" before "zzz" and it sure is annoying. I am run

RE: 10.2 Release seems to be crashing on Azure with "Standard DS" VM sizes

re dumps found. Clearing /tmp (X related). Updating motd:. Mounting late file systems:. Performing sanity check on sshd configuration. Scott -Original Message- From: Adrian Chadd [mailto:adrian.ch...@gmail.com] Sent: Sunday, February 7, 2016 12:08 AM To: Scott Otis <scott.o...@tandemcal.com>

Re: 10.2 Release seems to be crashing on Azure with "Standard DS" VM sizes

Hm, the runtime going backwards is a bit odd, maybe they fixed that in -HEAD recently. Other than that, yeah, you'll need a crash dump or at least some screenshot when it does reboot. -a ___ freebsd-stable@freebsd.org mailing list

Re: 10.2 Release seems to be crashing on Azure with "Standard DS" VM sizes

After setting crash dump settings correctly I'm still not seeing a dump in /var/crash/ - will try to get screenshot my of the boot screen after the crash and get back to you. Scott On Feb 7, 2016, at 12:08 AM, Adrian Chadd wrote: Hm, the runtime going backwards is a

10.2 Release seems to be crashing on Azure with "Standard DS" VM sizes

Been trying to get a FreeBSD VM server running on Azure on a "Standard DS" size VM (so I have access to SSD storage for PostgreSQL). The "Standard DS" series of VMs also have faster/newer CPUs than the original "Standard A" series of VMs. I am using the imag

Re: 10.2 Release seems to be crashing on Azure with "Standard DS" VM sizes

hiya, how much RAM does the VM have? Yes, you need to either run dumpon or reboot once you update /etc/rc.conf . -a On 5 February 2016 at 13:55, Scott Otis <scott.o...@tandemcal.com> wrote: > Been trying to get a FreeBSD VM server running on Azure on a "Standard DS" &

RE: 10.2 Release seems to be crashing on Azure with "Standard DS" VM sizes

d 1 (init) calcru: runtime went backwards from 1078465 usec to 545696 usec for pid 0 (kernel) Scott -Original Message- From: Adrian Chadd [mailto:adrian.ch...@gmail.com] Sent: Friday, February 5, 2016 4:46 PM To: Scott Otis <scott.o...@tandemcal.com> Cc: freebsd-stable@freebsd.o

Re: 10-STABLE live locks, looks like VM-related

Hello Lev, Monday, April 6, 2015, 11:55:09 AM, you wrote: I got several live locks of my server in a row (3 in one week). It is amd64 10-STABLE r277307. And again, rebuilded to r281159 http://lev.serebryakov.spb.ru/freebsd/ll/ I've tested memory with memtest86 for 12 hours without

10-STABLE live locks, looks like VM-related

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I got several live locks of my server in a row (3 in one week). It is amd64 10-STABLE r277307. Looks like live locks is VM related but manifest themselves under multi-threaded mixed CPU + I/O load (CrashPlan backup + torrents + openjdk8 rebuild

Re: 10-STABLE live locks, looks like VM-related

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 06.04.2015 11:55, Lev Serebryakov wrote: I have INVARIANTS and WITNESS in the kernel, but it doesn't help: only report is bufwait/dirhash right after booting. One more LOR: lock order reversal: 1st 0xf8011b9b82d8 ufs (ufs) @

FreeBSD 9.2 ahci under Parallels VM

Hi, I am trying to setup a FreeBSD 9.2 under Parallels and I find that I have to tell it to present IDE disks instead of SATA ones otherwise it gets timeouts probing for the disks. Is there some debugging I can enable to gather more information? -- Daniel O'Connor software and network engineer

Re: System doesn't resume with active vbox VM

with an active VirtualBox VM, in this case Windows XP/32. I didn't test any other systems. The system comes back to the console screen, but doesn't get back into X. After a couple of seconds (no dump occurs) I get the BIOS screen and the system reboots with unclean file systems. # uname

System doesn't resume with active vbox VM

My system doesn't resume with an active VirtualBox VM, in this case Windows XP/32. I didn't test any other systems. The system comes back to the console screen, but doesn't get back into X. After a couple of seconds (no dump occurs) I get the BIOS screen and the system reboots with unclean file

svn commit: r227420 - stable/9/sys/vm

Just out of curiosity or confusion maybe.. Will those commits be included to FreeBSD 9.0-RELEASE ? Thanks -- George Kontostanos aisecure.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To

Re: svn commit: r227420 - stable/9/sys/vm

On Thu, Nov 10, 2011 at 6:27 PM, George Kontostanos gkontos.m...@gmail.com wrote: Just out of curiosity or confusion maybe.. Will those commits be included to FreeBSD 9.0-RELEASE ? Almost certain of it, since releng/9.0-branch yet has to be created. -- chs,

Re: svn commit: r227420 - stable/9/sys/vm

On Thu, Nov 10, 2011 at 11:27 AM, George Kontostanos gkontos.m...@gmail.com wrote: Just out of curiosity or confusion maybe.. Will those commits be included to FreeBSD 9.0-RELEASE ? Thanks Yes, I believe so. Alan ___ freebsd-stable@freebsd.org

Re: svn commit: r227420 - stable/9/sys/vm

On Thu, Nov 10, 2011 at 8:46 PM, Alan Cox alan.l@gmail.com wrote: On Thu, Nov 10, 2011 at 11:27 AM, George Kontostanos gkontos.m...@gmail.com wrote: Just out of curiosity or confusion maybe.. Will those commits be included to FreeBSD 9.0-RELEASE ? Thanks Yes, I believe so. Alan

Is aio or vm broken for FreeBSD 7-STABLE ?

opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /usr/src/sys/vm/vm_unix.c /usr

Puzzling VM behavior in 6.3

hardware, we've observed that the disk is busier on the 6.3 system under the same load, but there shouldn't be much file activity other than logging and the swap usage stays at 0. In trying to track this down, we've found the most significant differences are in statistics from parts of the VM

Re: Open-vm-tools port available for testing

On Fri, Apr 18, 2008 at 10:32:22PM -0700, harshl wrote: I am an not great with BSD, how can I install this port without X? Sorry if this is easy but I don't really understand what I am seeing in the Makefile. There are several ways to do this. The easiest way is to just set WITHOUT_X11 in

Re: Open-vm-tools port available for testing

, and thanks for a much needed port!! -Lantard -- View this message in context: http://www.nabble.com/Open-vm-tools-port-available-for-testing-tp16341202p16770848.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable

Re: Open-vm-tools port available for testing

Hi Martin, On Thu, Mar 27, 2008 at 11:19:10PM +0100, Martin Blapp wrote: I've just made a port for FreeBSD 7 and FreeBSD 6 for the Open-vmware-tools. Any Feedback is welcome. I just installed your port on 6.3-p1/amd64 on ESX 3.5 (WITHOUT_X11, just guestd and vmmemctl) to see if VMotion works,

Re: Open-vm-tools port available for testing

Hi, Thanks for doing this, seems to be some problems with the downloading of the tarball though. See below: Just fixed that. The problem was the subdir name. -- Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] --

Open-vm-tools port available for testing

Hi, I've just made a port for FreeBSD 7 and FreeBSD 6 for the Open-vmware-tools. Any Feedback is welcome. http://antispam.imp.ch/patches/open-vmware-tools-freebsd-port.tgz -- Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]

Re: Open-vm-tools port available for testing

though. See below: [sugar-backup][~/open-vmware-tools]# make config === No options to configure [sugar-backup][~/open-vmware-tools]# make = open-vm-tools-2008.03.19-82724.tar.gz doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch from http://heanet.dl.sourceforge.net

Asus m2a-vm hdmi

FWIW, I have the almost the same motherboard (m2a-vm hdmi) with an AMD This is completely off topic, but which BIOS are you using ? I bought one of these today and it refuses to boot BSD at all from an IDE drive or a USB drive. The only thing which boots is the CD - all others complain

Re: Asus m2a-vm hdmi

On Tue, 12 Feb 2008 00:40:44 + Pete French [EMAIL PROTECTED] wrote: FWIW, I have the almost the same motherboard (m2a-vm hdmi) with an AMD This is completely off topic, but which BIOS are you using ? I bought I'm currently using the 1604 bios. When I bought it, the folks at the store

Re: mmap max size (qemu VM memsize limit)

On Mon, Nov 26, 2007 at 08:59:12AM -0600, Guy Helmer wrote: Gergely CZUCZY wrote: Hello, I'm trying to set up a qemu with 4G memory to the host system on a 7-BETA2, and I've hit some kind of limit in freebsd. When i give more then ~2000MB of memory to qemu, it returns an after trying to

Re: mmap max size (qemu VM memsize limit)

Guy Helmer wrote: Gergely CZUCZY wrote: Hello, I'm trying to set up a qemu with 4G memory to the host system on a 7-BETA2, and I've hit some kind of limit in freebsd. When i give more then ~2000MB of memory to qemu, it returns an after trying to mmap() it, saying Could not map physical

Re: mmap max size (qemu VM memsize limit)

Gergely CZUCZY wrote: Hello, I'm trying to set up a qemu with 4G memory to the host system on a 7-BETA2, and I've hit some kind of limit in freebsd. When i give more then ~2000MB of memory to qemu, it returns an after trying to mmap() it, saying Could not map physical memory. At the end of

mmap max size (qemu VM memsize limit)

Hello, I'm trying to set up a qemu with 4G memory to the host system on a 7-BETA2, and I've hit some kind of limit in freebsd. When i give more then ~2000MB of memory to qemu, it returns an after trying to mmap() it, saying Could not map physical memory. At the end of mmap(2) there's a note

Dubious VM behavior scanning large files

Inact, 439M Wired, 251M Cache, 214M Buf, 11M Free Swap: 10G Total, 12M Used, 10G Free, 232K Out cat(1), dd(1), par2, all result in the same sort of thing; I have well over over 4GB of memory used for nothing but disk cache, and the VM is somehow deciding it's cheaper to swap out fairly active

ASUS P5LD2-VM problem?

Hi! System: FreeBSD consulting 6.2-STABLE FreeBSD 6.2-STABLE #0: Fri Apr 27 00:46:01 EEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP-ECORYS i386 Motherboard: ASUS P5LD2-VM Socket775 BIOS version 1304 -- # dmesg Copyright (c) 1992-2007

Re: ASUS P5LD2-VM problem?

On Fri, Apr 27, 2007 at 04:50:53PM +0300, Andrei V. Lavreniyuk wrote: Motherboard: ASUS P5LD2-VM Socket775 BIOS version 1304 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR ?? Almost every system (workstation or server) i've seen which uses ACPI

/vm: mount pending error: blocks -7320419172370415403 files 4

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fresh install of 6-STABLE, upgraded to the latest RC ... ran for about 24 hours, and then crashed ... not a heavy load on it or anything ... And background FSCK shows: Dec 5 15:40:10 venus fsck: /dev/da0s1g: UNKNOWN FILE TYPE I=1626048 Dec 5

Re: systat -vm output showing negative total virtual memory

The change to vm_meter.c is ok. Could you please add a comment like that above the location of the patch. Alan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to

Re: systat -vm output showing negative total virtual memory

, the attached patch that includes a fix for vm_meter.c now prints the sane values for virtual memory. The huge contributions to vm total were from vnode objects representing mounted file systems (g_vfs_open()). Alan, could you please review this patch for me (the vm_meter.c portion at least) or suggest

systat -vm output showing negative total virtual memory

Hi all, this is on a two week old RELENG_6. The machine has 4GB RAM, SMP CPU: Intel(R) Xeon(TM) CPU 3.00GHz (3012.12-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf43 Stepping = 3 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUS

Re: systat -vm output showing negative total virtual memory

Memory: (Total: 815944K, Active 355288K) Real Memory:(Total: 2558540K Active 150424K) Shared Virtual Memory: (Total: 11460K Active: 7856K) Shared Real Memory: (Total: 6916K Active: 5044K) Free Memory Pages: 890092K If my reading of the sys/vm/vm_meter.c code

Re: systat -vm output showing negative total virtual memory

Ruslan Ermilov wrote: sysctl(8) knows that t_vm is in bytes, but for the other stats it thinks they are in pages. systat -vm thinks they are all in bytes. Here's a fix: Thanks!, I applied your patch to RELENG_6 # sysctl vm.vmtotal ; ./sysctl vm.vmtotal vm.vmtotal: System wide totals

Re: systat -vm output showing negative total virtual memory

On Thu, Nov 16, 2006 at 08:10:37PM +0100, Ulrich Spoerlein wrote: Ruslan Ermilov wrote: sysctl(8) knows that t_vm is in bytes, but for the other stats it thinks they are in pages. systat -vm thinks they are all in bytes. Here's a fix: Thanks!, I applied your patch to RELENG_6 22K

4.11 vm crash on Apr 28th kernel ...

(): page not found in hash) at /usr/src/sys/kern/kern_shutdown.c:595 #3 0x80217147 in vm_page_remove (m=0x80c3a3cc) at /usr/src/sys/vm/vm_page.c:461 #4 0x802177c8 in vm_page_free_toq (m=0x80c3a3cc) at /usr/src/sys/vm/vm_page.c:1104 #5 0x80216190 in vm_object_collapse (object=0xbb81e61c) at /usr

Re: panic: mutex vm object not owned

On Fri, 2005-03-11 at 13:20 -0600, Alan Cox wrote: I'm pretty sure that I understand the cause. Please apply and test the attached patch. Can this be committed please? Without it, my machine will still panic on starting X with BETA1. It's an MFC of src/sys/pci/agp.c 1.46 and

Re: panic: mutex vm object not owned

On Fri, 11 Mar 2005, Alan Cox wrote: I'm pretty sure that I understand the cause. Please apply and test the attached patch. [snip patch-agp] Sorry for the delay in getting back yo you, this patch does indeed fix the problem. Thanks! Gavin ___

panic: mutex vm object not owned

Hi, I'm tracking RELENG_5 and since my last update I can no longer start X without getting the following panic: panic: mutex vm object not owned at /usr/src/sys/vm/vm_page.c:334 cpuid = 0 KDB: enter: panic [ thread pid 2762 tid 100116 ] stopped at kdb_enter+0x2b: nop At which point

Re: panic: mutex vm object not owned

On Fri, Mar 11, 2005 at 06:59:02PM +, Gavin Atkinson wrote: Hi, I'm tracking RELENG_5 and since my last update I can no longer start X without getting the following panic: panic: mutex vm object not owned at /usr/src/sys/vm/vm_page.c:334 cpuid = 0 KDB: enter: panic [ thread pid

Re: panic: mutex vm object not owned

I'm pretty sure that I understand the cause. Please apply and test the attached patch. Regards, Alan Index: pci/agp.c === RCS file: /home/ncvs/src/sys/pci/agp.c,v retrieving revision 1.45 diff -u -r1.45 agp.c --- pci/agp.c 16 Aug

Re: panic: mutex vm object not owned

On Fri, 11 Mar 2005, Alan Cox wrote: I'm pretty sure that I understand the cause. Please apply and test the attached patch. Thanks! I'll start that compiling now, but won't be able to test it until I get physically back to the machine tomorrow. I'm not using the nVidia driver - the graphics

Re: Problems reclaiming VM cache = XFree86 startup annoyance

On Sat, 20 Dec 2003, Paul Mather wrote: Not being a Python programmer, I don't know exactly how BitTorrent is accessing the files (e.g., using mmap), though I do know some kind of random access is involved as the filesets are chunked and different chunks are served to different peers. I

Re: Problems reclaiming VM cache = XFree86 startup annoyance

... As you can probably gather, all this manual intervention is a bit of a hassle. So, my question is this: is there a way explicitly to force the kernel to flush its VM cache (to move it to Free). Failing that, are there any sysctls to tune to help alleviate the problem? The only sysctls I

Re: Problems reclaiming VM cache = XFree86 startup annoyance

:... : (Paul Mather) : As you can probably gather, all this manual intervention is a bit of a : hassle. So, my question is this: is there a way explicitly to force : the kernel to flush its VM cache (to move it to Free). Failing : that, are there any sysctls to tune to help alleviate

  1   2   >