Solved Possible issue with VMware during upgrade to 13

circus78

Well-Known Member

Reaction score: 9
Messages: 264

Hi, I just started upgrade process from 12.2-RELEASE to 13-RELEASE on my virtual machine (VMware).
After first reboot, boot failed and I got this error:

Code:
mountroot: waiting for device /dev/da0p2...
WARNING: / was not properly dismounted
<118>Setting hostuuid: 421bc409-ba72-50bc-d06b-ce7728b82407.
<118>Setting hostid: 0x8924ff63.
Deprecated code (to be removed in FreeBSD 14): FreeBSD 12.x ABI compat
Deprecated code (to be removed in FreeBSD 14): FreeBSD 12.x ABI compat
<118>Starting file system checks:
<118>** SU+J Recovering /dev/da0p2
<118>** Reading 33554432 byte journal from inode 4.
<118>** Building recovery table.
<118>** Resolving unreferenced inode list.
<118>** Processing journal entries.
<118>** 16 journal records in 1024 bytes for 50.00% utilization
<118>** Freed 8 inodes (0 dirs) 0 blocks, and 3 frags.
<118>
<118>***** FILE SYSTEM MARKED CLEAN *****
<118>Mounting local filesystems:.
<118>ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/local/lib/compat /usr/local/lib/compat/pkg /usr/local/lib/
gcc10 /usr/local/lib/gcc8 /usr/local/lib/gcc9 /usr/local/lib/perl5/5.32/mach/CORE
<118>32-bit compatibility ldconfig path: /usr/lib32 /usr/local/lib32/compat
<118>Loading vmmemctl kernel module:
KLD vmmemctl.ko: depends on kernel - not available or version mismatch
linker_load_file: /usr/local/lib/vmware-tools/modules/drivers/vmmemctl.ko - unsupported file type
<118>kldload: an error occurred while loading module /usr/local/lib/vmware-tools/modules/drivers/vmmemctl.ko. Please check dmesg(8) for more details.
<118>failed.
<118>Loading vmblock kernel module:
KLD vmblock.ko: depends on kernel - not available or version mismatch
linker_load_file: /usr/local/lib/vmware-tools/modules/drivers/vmblock.ko - unsupported file type
<118>kldload: an error occurred while loading module /usr/local/lib/vmware-tools/modules/drivers/vmblock.ko. Please check dmesg(8) for more details.
<118>failed.
<118>Starting vmware_guestd.
<118>Autoloading module: intpm.ko
<118>Autoloading module: vmci.ko
intsmb0: <Intel PIIX4 SMBUS Interface> port 0x1040-0x104f at device 7.3 on pci0
intsmb0: intr SMI disabled revision 0
smbus0: <System Management Bus> on intsmb0
vmci0: <VMware Virtual Machine Communication Interface> port 0x1080-0x10bf irq 16 at device 7.7 on pci0
<3>vmci: Could not map: BAR1
<3>vmci: Failed to map PCI BARs.
<4>vmci: Failed to unsubscribe to event (type=0) with subscriber (ID=0xffffffff).
device_attach: vmci0 attach returned 6
vmci0: <VMware Virtual Machine Communication Interface> port 0x1080-0x10bf irq 16 at device 7.7 on pci0
<3>vmci: Could not map: BAR1
<3>vmci: Failed to map PCI BARs.


Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address   = 0x440
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff80be7b42
stack pointer           = 0x28:0xfffffe00085ed630
frame pointer           = 0x28:0xfffffe00085ed6b0
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 129 (devctl)
trap number             = 12
panic: page fault
cpuid = 1
time = 1620660990
KDB: stack backtrace:
#0 0xffffffff80c57345 at kdb_backtrace+0x65
#1 0xffffffff80c09d21 at vpanic+0x181
#2 0xffffffff80c09b93 at panic+0x43
#3 0xffffffff8108b187 at trap_fatal+0x387
#4 0xffffffff8108b1df at trap_pfault+0x4f
#5 0xffffffff8108a83d at trap+0x27d
#6 0xffffffff810617a8 at calltrap+0x8
#7 0xffffffff82329079 at vmci_qp_guest_endpoints_exit+0x19
#8 0xffffffff8232499e at vmci_detach+0x1e
#9 0xffffffff82324860 at vmci_attach+0x320
#10 0xffffffff80c4653d at device_attach+0x3dd
#11 0xffffffff80c46141 at device_probe_and_attach+0x41
#12 0xffffffff8085b9b6 at pci_driver_added+0xf6
#13 0xffffffff80c43fb9 at devclass_driver_added+0x39
#14 0xffffffff80c4baba at devctl2_ioctl+0x37a
#15 0xffffffff80aa9397 at devfs_ioctl+0xc7
#16 0xffffffff80cfa504 at vn_ioctl+0x1a4
#17 0xffffffff80aa9a4e at devfs_ioctl_f+0x1e
Uptime: 3s
Dumping 224 out of 4062 MB:..8%..15%..22%..36%..43%..58%..65%..72%..86%..93%
Dump complete

Other informations:
Code:
# camcontrol devlist
<NECVMWar VMware IDE CDR10 1.00>   at scbus1 target 0 lun 0 (cd0,pass0)
<VMware Virtual disk 1.0>          at scbus2 target 0 lun 0 (da0,pass1)

# uname -ar
FreeBSD mail.server 12.2-RELEASE-p6 FreeBSD 12.2-RELEASE-p6 GENERIC  amd64

# freebsd-version -k
13.0-RELEASE


I always use GENERIC kernel, I was able to boot fine only with /boot/kernel.old/kernel.
Any suggestion?
Thank you!
 

covacat

Well-Known Member

Reaction score: 226
Messages: 474

rebuild vmware guest additions ?
boot without vmware guest modules and rebuild them
 
OP
C

circus78

Well-Known Member

Reaction score: 9
Messages: 264

Hi, my loader.conf is empty, and rc.conf contains nothing about VMware or open-vm-tools-nox11.
I noticed the file /boot/kernel/vmci.ko, can I rename it?
Or is it a clean way to disable vmci.ko loading at boot?
Thank you
 

covacat

Well-Known Member

Reaction score: 226
Messages: 474

open-vm-tools seeems to start from somewhere so you may need to find out where (if not rc.conf) (might be rc.local or non standard script in /usr/local/etc/rc.d)
you can try to rename it (vmci.ko)
 
Top