VMTN_Admin
Enthusiast
Enthusiast

X-M0n0wall

http://www.vmware.com/vmtn/appliances/directory/150

all-in-one firewall package upgraded with VMXnet, heartbeat and MUI-control

0 Kudos
142 Replies
brugh
Enthusiast
Enthusiast

you could try this; go to http://your.ip/exec.php and type 'ps -aux'. see if there's a 'vmware-guestd' running or not. if not, you can type 'vmware-guestd --background /var/run/guestd.pid', see if it comes back.

can be a problem with the guestd too though. i put the same guestd in as in 1.233 but it seems that they changed something with the library set in 1.234 so i heard more people complain about this. i'll have a look into it soon.

0 Kudos
martinwa
Contributor
Contributor

Hi,

This is the output, the process seams to be running, but no vmware-tools detected Smiley Sad

-


$ ps -aux

USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND

root 121 99.1 0.3 668 348 ?? Rs Tue04PM 8062:43.24 /sbin/vmware-gues

root 166 0.0 0.8 1332 876 ?? SN 7:36AM 0:00.01 sh -c ps -aux

root 165 0.0 1.6 2380 1812 ?? S 7:36AM 0:00.01 /usr/local/sbin/m

root 163 0.0 5.8 7156 6608 ?? SN 7:36AM 0:00.20 /usr/local/bin/ph

root 129 0.0 0.7 1104 804 ?? I Fri03PM 0:00.04 /usr/local/bin/ms

root 123 0.0 0.8 1336 888 ?? I Tue04PM 0:00.01 /bin/sh /etc/rc.i

root 107 0.0 0.8 1332 840 con- I Tue04PM 0:00.04 /bin/sh /usr/loca

root 103 0.0 1.3 1816 1492 ?? Is Tue04PM 0:00.25 /usr/local/sbin/d

nobody 100 0.0 0.7 1044 824 ?? I Tue04PM 0:00.08 /usr/local/sbin/d

root 96 0.0 1.5 2296 1648 ?? Ss Tue04PM 0:00.05 /usr/local/sbin/m

root 93 0.0 0.7 1004 736 ?? Is Tue04PM 0:06.73 /usr/sbin/syslogd

root 88 0.0 1.1 1456 1224 ?? Ss Tue04PM 0:55.84 /sbin/ipmon -sD

root 7 0.0 0.0 0 0 ?? DL Tue04PM 0:17.07 (syncer)

root 6 0.0 0.0 0 0 ?? DL Tue04PM 0:06.91 (vnlru)

root 5 0.0 0.0 0 0 ?? DL Tue04PM 0:14.52 (bufdaemon)

root 4 0.0 0.0 0 0 ?? DL Tue04PM 0:02.87 (pagedaemon)

root 3 0.0 0.0 0 0 ?? DL Tue04PM 0:00.00 (taskqueue)

root 2 0.0 0.0 0 0 ?? DL Tue04PM 0:00.00 (cryptoret)

root 1 0.0 0.6 1060 696 ?? ILs Tue04PM 0:00.05 /sbin/init --

root 0 0.0 0.0 0 0 ?? DLs Tue04PM 0:00.00 (swapper)

root 167 0.0 0.6 1076 676 ?? RN 7:36AM 0:00.00 ps -aux

root 164 0.0 0.0 0 0 ?? Z 7:36AM 0:00.00 (mini_httpd)

-


$ vmware-guestd --background /var/run/guestd.pid

Guestd is already running, exiting.

0 Kudos
brugh
Enthusiast
Enthusiast

the guestd is using 99% cpu. might be looping or something. try killing it (kill -9 121 in exec.php) and restart it.

0 Kudos
martinwa
Contributor
Contributor

Same result Smiley Sad

$ ps -aux

USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND

root 206 92.9 0.3 668 368 ?? RNs 11:02AM 0:07.51 vmware-guestd --b

root 207 4.0 5.8 7156 6608 ?? SN 11:02AM 0:00.19 /usr/local/bin/ph

root 209 0.0 1.6 2380 1812 ?? S 11:02AM 0:00.00 /usr/local/sbin/m

root 123 0.0 0.8 1336 888 ?? I 7:42AM 0:00.01 /bin/sh /etc/rc.i

root 109 0.0 0.7 1104 772 con- I 7:42AM 0:00.03 /usr/local/bin/ms

root 107 0.0 0.8 1332 840 con- I 7:42AM 0:00.02 /bin/sh /usr/loca

root 103 0.0 1.3 1812 1488 ?? Is 7:42AM 0:00.14 /usr/local/sbin/d

nobody 100 0.0 0.7 1044 824 ?? I 7:42AM 0:00.04 /usr/local/sbin/d

root 96 0.0 1.5 2296 1648 ?? Ss 7:42AM 0:00.10 /usr/local/sbin/m

root 93 0.0 0.7 1004 736 ?? Ss 7:42AM 0:00.21 /usr/sbin/syslogd

root 88 0.0 1.1 1456 1224 ?? Ss 7:42AM 0:01.31 /sbin/ipmon -sD

root 7 0.0 0.0 0 0 ?? DL 7:42AM 0:00.50 (syncer)

root 6 0.0 0.0 0 0 ?? DL 7:42AM 0:00.12 (vnlru)

root 5 0.0 0.0 0 0 ?? DL 7:42AM 0:00.32 (bufdaemon)

root 4 0.0 0.0 0 0 ?? DL 7:42AM 0:00.07 (pagedaemon)

root 3 0.0 0.0 0 0 ?? DL 7:42AM 0:00.00 (taskqueue)

root 2 0.0 0.0 0 0 ?? DL 7:42AM 0:00.00 (cryptoret)

root 1 0.0 0.6 1060 696 ?? SLs 7:42AM 0:00.07 /sbin/init --

root 0 0.0 0.0 0 0 ?? DLs 7:42AM 0:00.00 (swapper)

root 211 0.0 0.6 1076 676 ?? RN 11:02AM 0:00.00 ps -aux

root 208 0.0 0.0 0 0 ?? Z 11:02AM 0:00.00 (mini_httpd)

root 210 0.0 0.8 1332 876 ?? SN 11:02AM 0:00.01 sh -c ps -aux

0 Kudos
pascuzzi
Contributor
Contributor

I may be having the same problem running on ESX. The ps command shows that the vmware-tools is running. I can kill it and restart it. I then see that Virtual Center says that the tools are OK. Withinga few seconds, the tool status on virtual center changes to not installed.

IT may be partially caused from having the workstation verions of the VMware Tools installed on the VM. But I haven't had this problem with other VMs.

0 Kudos
martinwa
Contributor
Contributor

The ESX 3,5 also have the problem not only ESXi...

Best regards

Martin

0 Kudos
brugh
Enthusiast
Enthusiast

i just noticed there's a new version out. i'll look into it. 1.234 has vmware tools from workstation 6 in them. i'll try another version, see if that helps.

0 Kudos
martinwa
Contributor
Contributor

Thank you brugh Smiley Happy

But where can your new version be downloaded ?

Best regards

Martin

0 Kudos
brugh
Enthusiast
Enthusiast

the new version isn't built yet Smiley Happy i hope to get around to it next week or something. way too busy preparing for presentation and seminars.

0 Kudos
toddcrow
Contributor
Contributor

Does the X-MonoWall work on ESX3.5?

I am having excessive CPU usage and lockups when I try the 1.234

Thanks

Todd

0 Kudos
brugh
Enthusiast
Enthusiast

it works on esx 3.5 but the guestdaemon disagrees with it somehow. just disable it for now (backup configuration, remove 'shellcmd', restore configuration and reboot). i'll upgrade x-monowall real soon to 1.235 and will have a look at the new libraries and hopefully find a new guestdaemon that will fit. i'll post a msg here when it's done.

0 Kudos
brugh
Enthusiast
Enthusiast

Ok, finished the 1.235 version. I tried several versions of vmware-tools but every one of them made vmware-guestd hog the CPU. I finaly took a vmware-guestd from an early workstation version and that works fine so no more 100% cpu! Check it out on http://www.vmware.com/appliances/directory/150.

0 Kudos
martinwa
Contributor
Contributor

For some reason vmware-tools does not start with the vm.

In vmware infrastructure client:

vmware-tools: not running

If I start vmware-tools manually:

vmware tools: out of date (thats ok)

How do I configure monowall to run a command everytime it starts?

0 Kudos
martinwa
Contributor
Contributor

vmware-toos starts with the vm but for some reason it stops running after some time.

Can vmware-tools be restarted automatic?

0 Kudos
brugh
Enthusiast
Enthusiast

if you backup your configuration, check the <shellcmd> line. it should say /usr/bin/vmware-guestd.

0 Kudos
brugh
Enthusiast
Enthusiast

can you check the logs in /var/log through ? curious why it would stop..

to restart it automatically, change the shellcmd line in the configuration to <shellcmd>while true; do /usr/bin/vmware-tools; done</shellcmd>. without the --background option so it stays in the foreground.

0 Kudos
martinwa
Contributor
Contributor

How do I change the shellcmd line?

This is the system log after a powerup:

$ cat /var/log/system.log

Oct 7 07:37:10 m0n0wall /kernel: Waiting (max 60 seconds) for system process `vnlru' to stop...stopped

Oct 7 07:37:10 m0n0wall /kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped

Oct 7 07:37:10 m0n0wall /kernel: Waiting (max 60 seconds) for system process `syncer' to stop...stopped

Oct 7 07:37:10 m0n0wall /kernel:

Oct 7 07:37:10 m0n0wall /kernel: syncing disks...

Oct 7 07:37:10 m0n0wall /kernel: done

Oct 7 07:37:10 m0n0wall /kernel: Uptime: 15h48m18s

Oct 7 07:37:10 m0n0wall /kernel: Rebooting...

Oct 7 07:37:10 m0n0wall /kernel: Copyright (c) 1992-2005 The FreeBSD Project.

Oct 7 07:37:10 m0n0wall /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994

Oct 7 07:37:10 m0n0wall /kernel: The Regents of the University of California. All rights reserved.

Oct 7 07:37:10 m0n0wall /kernel: FreeBSD 4.11-RELEASE-p26 #0: Fri Aug 8 20:42:40 CEST 2008

Oct 7 07:37:10 m0n0wall /kernel: root@fb411.neon1.net:/usr/src/sys/compile/M0N0WALL_GENERIC

Oct 7 07:37:10 m0n0wall /kernel: Timecounter "i8254" frequency 1193182 Hz

Oct 7 07:37:10 m0n0wall /kernel: CPU: Quad-Core AMD Opteron(tm) Processor 2356 (2299.33-MHz 686-class CPU)

Oct 7 07:37:10 m0n0wall /kernel: Origin = "AuthenticAMD" Id = 0x100f23 Stepping = 3

Oct 7 07:37:10 m0n0wall /kernel: Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>

Oct 7 07:37:10 m0n0wall /kernel: AMD Features=0xe8400000<AMIE,<b27>,<b29>,DSP,3DNow!>

Oct 7 07:37:10 m0n0wall /kernel: real memory = 67108864 (65536K bytes)

Oct 7 07:37:10 m0n0wall /kernel: avail memory = 47595520 (46480K bytes)

Oct 7 07:37:10 m0n0wall /kernel: Preloaded elf kernel "kernel" at 0xc1110000.

Oct 7 07:37:10 m0n0wall /kernel: Preloaded elf module "vmxnet.ko" at 0xc111009c.

Oct 7 07:37:10 m0n0wall /kernel: Preloaded elf module "vmmemctl.ko" at 0xc111013c.

Oct 7 07:37:10 m0n0wall /kernel: Preloaded mfs_root "/mfsroot" at 0xc11101dc.

Oct 7 07:37:10 m0n0wall /kernel: VMware memory control driver initialized

Oct 7 07:37:10 m0n0wall /kernel: Pentium Pro MTRR support enabled

Oct 7 07:37:10 m0n0wall /kernel: md0: Preloaded image </mfsroot> 12582912 bytes at 0xc050ec3c

Oct 7 07:37:10 m0n0wall /kernel: md1: Malloc disk

Oct 7 07:37:10 m0n0wall /kernel: Using $PIR table, 9 entries at 0xc00fdf30

Oct 7 07:37:10 m0n0wall /kernel: npx0: <math processor> on motherboard

Oct 7 07:37:10 m0n0wall /kernel: npx0: INT 16 interface

Oct 7 07:37:10 m0n0wall /kernel: pcib0: <Intel 82443BX (440 BX) host to PCI bridge> on motherboard

Oct 7 07:37:10 m0n0wall /kernel: pci0: <PCI bus> on pcib0

Oct 7 07:37:10 m0n0wall /kernel: pcib1: <Intel 82443BX (440 BX) PCI-PCI (AGP) bridge> at device 1.0 on pci0

Oct 7 07:37:10 m0n0wall /kernel: pci1: <PCI bus> on pcib1

Oct 7 07:37:10 m0n0wall /kernel: isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0

Oct 7 07:37:10 m0n0wall /kernel: isa0: <ISA bus> on isab0

Oct 7 07:37:10 m0n0wall /kernel: atapci0: <Intel PIIX4 ATA33 controller> at device 7.1 on pci0

Oct 7 07:37:10 m0n0wall /kernel: atapci0: ATA channel disabled by BIOS

Oct 7 07:37:10 m0n0wall /kernel: chip1: <Intel 82371AB Power management controller> port 0x1040-0x104f at device 7.3 on pci0

Oct 7 07:37:10 m0n0wall /kernel: pci0: <VGA-compatible display device> at 15.0

Oct 7 07:37:10 m0n0wall /kernel: bt0: <Buslogic Multi-Master SCSI Host Adapter> port 0x1060-0x107f mem 0xf4800000-0xf480001f irq 11 at device 16.0 on pci0

Oct 7 07:37:10 m0n0wall /kernel: bt0: BT-958 FW Rev. 5.07B Ultra Wide SCSI Host Adapter, SCSI ID 7, 192 CCBs

Oct 7 07:37:10 m0n0wall /kernel: lnc0: <PCNet/PCI Ethernet adapter> port 0x1080-0x10ff irq 9 at device 17.0 on pci0

Oct 7 07:37:10 m0n0wall /kernel: lnc0: PCnet-PCI II address 00:50:56:91:74:28

Oct 7 07:37:10 m0n0wall /kernel: lnc0: driver is using old-style compatibility shims

Oct 7 07:37:10 m0n0wall /kernel: lnc1: <PCNet/PCI Ethernet adapter> port 0x1400-0x147f irq 10 at device 18.0 on pci0

Oct 7 07:37:10 m0n0wall /kernel: lnc1: PCnet-PCI II address 00:50:56:91:5e:f3

Oct 7 07:37:10 m0n0wall /kernel: lnc1: driver is using old-style compatibility shims

Oct 7 07:37:10 m0n0wall /kernel: orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xca000-0xcafff,0xcb000-0xcbfff,0xdc000-0xdffff,0xe0000-0xe3fff on isa0

Oct 7 07:37:10 m0n0wall /kernel: pmtimer0 on isa0

Oct 7 07:37:10 m0n0wall /kernel: fdc0: <Intel 82077 or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0

Oct 7 07:37:10 m0n0wall /kernel: fdc0: FIFO enabled, 8 bytes threshold

Oct 7 07:37:10 m0n0wall /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0

Oct 7 07:37:10 m0n0wall /kernel: ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0

Oct 7 07:37:10 m0n0wall /kernel: ata1 at port 0x170-0x177,0x376 irq 15 on isa0

Oct 7 07:37:10 m0n0wall /kernel: atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0

Oct 7 07:37:10 m0n0wall /kernel: atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0

Oct 7 07:37:10 m0n0wall /kernel: kbd0 at atkbd0

Oct 7 07:37:10 m0n0wall /kernel: vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0

Oct 7 07:37:10 m0n0wall /kernel: sc0: <System console> at flags 0x100 on isa0

Oct 7 07:37:10 m0n0wall /kernel: sc0: VGA <16 virtual consoles, flags=0x300>

Oct 7 07:37:10 m0n0wall /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0

Oct 7 07:37:10 m0n0wall /kernel: sio0: type 16550A

Oct 7 07:37:10 m0n0wall /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0

Oct 7 07:37:10 m0n0wall /kernel: sio1: type 16550A

Oct 7 07:37:10 m0n0wall /kernel: BRIDGE 020214 loaded

Oct 7 07:37:10 m0n0wall /kernel: IPsec: Initialized Security Association Processing.

Oct 7 07:37:10 m0n0wall /kernel: IP Filter: v3.4.35 initialized. Default = block all, Logging = enabled

Oct 7 07:37:10 m0n0wall /kernel: Waiting 15 seconds for SCSI devices to settle

Oct 7 07:37:10 m0n0wall /kernel: da0 at bt0 bus 0 target 0 lun 0

Oct 7 07:37:10 m0n0wall /kernel: da0: <VMware Virtual disk 1.0> Fixed Direct Access SCSI-2 device

Oct 7 07:37:10 m0n0wall /kernel: da0: 3.300MB/s transfers, Tagged Queueing Enabled

Oct 7 07:37:10 m0n0wall /kernel: da0: 102MB (209716 512 byte sectors: 64H 32S/T 102C)

Oct 7 07:37:10 m0n0wall /kernel: Mounting root from ufs:/dev/md0c

Oct 7 07:37:10 m0n0wall dnsmasq[110]: started, version 2.45 cachesize 150

Oct 7 07:37:10 m0n0wall dnsmasq[110]: compile time options: IPv6 no-GNU-getopt BSD-bridge ISC-leasefile no-DBus no-I18N no-TFTP

Oct 7 07:37:10 m0n0wall dnsmasq[110]: setting --bind-interfaces option because of OS limitations

Oct 7 07:37:10 m0n0wall dnsmasq[110]: setting --bind-interfaces option because of OS limitations

Oct 7 07:37:10 m0n0wall dnsmasq[110]: reading /etc/resolv.conf

Oct 7 07:37:10 m0n0wall dnsmasq[110]: using nameserver 213.64.64.171#53

Oct 7 07:37:10 m0n0wall dnsmasq[110]: using nameserver 195.184.96.2#53

Oct 7 07:37:10 m0n0wall dhcpd: Internet Systems Consortium DHCP Server V3.0.5

Oct 7 07:37:10 m0n0wall dnsmasq[110]: read /etc/hosts - 2 addresses

Oct 7 07:37:10 m0n0wall dhcpd: Copyright 2004-2006 Internet Systems Consortium.

Oct 7 07:37:10 m0n0wall dhcpd: All rights reserved.

Oct 7 07:37:10 m0n0wall dhcpd: For info, please visit

CLOGX ìÿ

$ cat /var/log/dmesg.boot

Copyright (c) 1992-2005 The FreeBSD Project.

Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994

The Regents of the University of California. All rights reserved.

FreeBSD 4.11-RELEASE-p26 #0: Fri Aug 8 20:42:40 CEST 2008

root@fb411.neon1.net:/usr/src/sys/compile/M0N0WALL_GENERIC

Timecounter "i8254" frequency 1193182 Hz

CPU: Quad-Core AMD Opteron(tm) Processor 2356 (2299.33-MHz 686-class CPU)

Origin = "AuthenticAMD" Id = 0x100f23 Stepping = 3

Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>

AMD Features=0xe8400000<AMIE,<b27>,<b29>,DSP,3DNow!>

real memory = 67108864 (65536K bytes)

avail memory = 47595520 (46480K bytes)

Preloaded elf kernel "kernel" at 0xc1110000.

Preloaded elf module "vmxnet.ko" at 0xc111009c.

Preloaded elf module "vmmemctl.ko" at 0xc111013c.

Preloaded mfs_root "/mfsroot" at 0xc11101dc.

VMware memory control driver initialized

Pentium Pro MTRR support enabled

md0: Preloaded image </mfsroot> 12582912 bytes at 0xc050ec3c

md1: Malloc disk

Using $PIR table, 9 entries at 0xc00fdf30

npx0: <math processor> on motherboard

npx0: INT 16 interface

pcib0: <Intel 82443BX (440 BX) host to PCI bridge> on motherboard

pci0: <PCI bus> on pcib0

pcib1: <Intel 82443BX (440 BX) PCI-PCI (AGP) bridge> at device 1.0 on pci0

pci1: <PCI bus> on pcib1

isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0

isa0: <ISA bus> on isab0

atapci0: <Intel PIIX4 ATA33 controller> at device 7.1 on pci0

atapci0: ATA channel disabled by BIOS

chip1: <Intel 82371AB Power management controller> port 0x1040-0x104f at device 7.3 on pci0

pci0: <VGA-compatible display device> at 15.0

bt0: <Buslogic Multi-Master SCSI Host Adapter> port 0x1060-0x107f mem 0xf4800000-0xf480001f irq 11 at device 16.0 on pci0

bt0: BT-958 FW Rev. 5.07B Ultra Wide SCSI Host Adapter, SCSI ID 7, 192 CCBs

lnc0: <PCNet/PCI Ethernet adapter> port 0x1080-0x10ff irq 9 at device 17.0 on pci0

lnc0: PCnet-PCI II address 00:50:56:91:74:28

lnc0: driver is using old-style compatibility shims

lnc1: <PCNet/PCI Ethernet adapter> port 0x1400-0x147f irq 10 at device 18.0 on pci0

lnc1: PCnet-PCI II address 00:50:56:91:5e:f3

lnc1: driver is using old-style compatibility shims

orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xca000-0xcafff,0xcb000-0xcbfff,0xdc000-0xdffff,0xe0000-0xe3fff on isa0

pmtimer0 on isa0

fdc0: <Intel 82077 or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0

fdc0: FIFO enabled, 8 bytes threshold

fd0: <1440-KB 3.5" drive> on fdc0 drive 0

ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0

ata1 at port 0x170-0x177,0x376 irq 15 on isa0

atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0

atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0

kbd0 at atkbd0

vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0

sc0: <System console> at flags 0x100 on isa0

sc0: VGA <16 virtual consoles, flags=0x300>

sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0

sio0: type 16550A

sio1 at port 0x2f8-0x2ff irq 3 on isa0

sio1: type 16550A

BRIDGE 020214 loaded

IPsec: Initialized Security Association Processing.

IP Filter: v3.4.35 initialized. Default = block all, Logging = enabled

Waiting 15 seconds for SCSI devices to settle

da0 at bt0 bus 0 target 0 lun 0

da0: <VMware Virtual disk 1.0> Fixed Direct Access SCSI-2 device

da0: 3.300MB/s transfers, Tagged Queueing Enabled

da0: 102MB (209716 512 byte sectors: 64H 32S/T 102C)

Mounting root from ufs:/dev/md0c

0 Kudos
brugh
Enthusiast
Enthusiast

those logs wont help. show nothing special.

the shellcmd line can be changed by creating a backup, open the xml file in wordpad, then change, save and restore config.

0 Kudos
pascuzzi
Contributor
Contributor

This one works until you do a reset to factory defaults. After doing that the VMware tools do not communicate with VIrtual Center. ps -aux shows that vmware tools is running. I have killed and restarted it and it still doesn't communicate.

0 Kudos
brugh
Enthusiast
Enthusiast

hm strange. a factory default should 've removed the shellcmd line. do you have tools to do a quick compare of the default config file and the one from the appliance?

0 Kudos