Backtrack 4 on VMWare Server on Vista 64 bit host
Hi All,
I need some support/help on getting Backtrack 4 running within VMWare Server which is running on a Windows Vista 64 bit OS.
The VMWare Backtrack 3 image is working fine!
But when starting the Backtrack 4 VMWare image the BT doesn't boot. Sometimes I only see a black screen and sometimes I see:
boot:
Loading BT4 .................................................
BIOS data check successful
And that is it, nothing else! And is stays like this for hours.
This is the vmware.log file content:
Apr 10 14:38:44.843: vmx| Log for VMware Server pid=6752 version=2.0.1 build=build-156745 option=Release
Apr 10 14:38:44.843: vmx| Hostname=XXXXXXXXXXXXX
Apr 10 14:38:44.874: vmx| IP=127.0.0.1
Apr 10 14:38:44.874: vmx| Command line: "C:\Program Files (x86)\VMware\VMware Server\x64\vmware-vmx.exe" "-#" "name=VMware Server;version=2.0.1;buildnumber=156745;licensenam e=VMware GSX Server for Win32;licenseversion=3.0 build-156745;" "-@" "pipe=\\.\pipe\vmxe0b2e67f68820efe;" "D:\VMWare Virtual Disks\bt4-beta-vm-6.5.1\BT4-Beta\BT4-Beta.vmx"
Apr 10 14:38:44.921: vmx| UI Connecting to pipe '\\.\pipe\vmxe0b2e67f68820efe' with user '(null)'
Apr 10 14:38:44.968: vmx| Transitioned vmx/execState/val to poweredOff
Apr 10 14:38:44.968: vmx| MStat: Creating Stat system.cpuusage
Apr 10 14:38:44.968: vmx| MStat: Creating Stat system.ram
Apr 10 14:38:44.968: vmx| MStat: Creating Stat system.uptime
Apr 10 14:38:44.968: vmx| MStat: Creating Stat system.load
Apr 10 14:38:44.968: vmx| HD: host version is 6.0.6001
Apr 10 14:38:44.968: vmx| HD: addr fffff80002b0af90
Apr 10 14:38:44.968: vmx| HD: fffff80002bc70e0, 0
Apr 10 14:38:44.968: vmx| VMMon_GetkHzEstimate: Calculated 2666761 kHz
Apr 10 14:38:44.968: vmx| VMMon_RememberkHzEstimate: Calculated 2666761 kHz
............................
I had to delete some logging because the text was to long.
............................
Apr 10 14:38:56.726: vcpu-0| Unknown int 10h func 0x0000
Apr 10 14:38:56.726: vcpu-0| Unknown int 10h func 0x0000
Apr 10 14:38:57.787: vcpu-0| Monitor64_PowerOn()
Apr 10 14:38:57.802: vcpu-0| vmm64-modules: [vmm.vmm64 .data:0xfffffffffc04b000-0xbe0 .sdata:0xfffffffffc04c000-0x9a8 .statvars:0xfffffffffc04d000-0x1e4 .peer:0xfffffffffc04e000-0x261c0 .shared:0xfffffffffc076000-0x12ac0 .bss:0xfffffffffc08a000-0xa080 .rodata:0xfffffffffc200000-0x12d80 .text:0xfffffffffc214000-0x5f67e .kstatvars:0x3000-0x0 .eh_frame:0xfffffffffc28b000-0x11da8, mmu-hwmmu.vmm64 .rodata:0xfffffffffc212d80-0xd2 .data:0xfffffffffc04bbe0-0x14 .peer:0xfffffffffc0741c0-0x16c0 .shared:0xfffffffffc088ac0-0x2c0 .bss:0xfffffffffc094080-0x930 .text:0xfffffffffc273680-0xa665 .statvars:0x2000-0x0 .kstatvars:0x2000-0x0 .scb:0x38a0-0x180 .shared_meta:0x3c00-0x390 .peer_meta:0x1020-0x210 .eh_frame:0xfffffffffc29cda8-0x1bb8 .comment:0xd4a-0x10e, sharedmmu-none.vmm64 .text:0xfffffffffc27dce8-0x1a .eh_frame:0xfffffffffc29e960-0x138 .comment:0xe58-0x12, pv-none.vmm64 .shared:0xfffffffffc088d80-0x180 .bss:0x1000-0x0 .text:0xfffffffffc27dd04-0x4 .shared_meta:0x3f90-0x90 .eh_frame:0xfffffffffc29ea98-0x48 .comment:0xe6a-0x48, vprobe-none.vmm64 .text:0xfffffffffc27dd08-0x6a .eh_frame:0xfffffffffc29eae0-0x2d0 .comment:0xeb2-0x12, hv-vt.vmm64 .rodata:0xfffffffffc212e60-0x6f4 .data:0xfffffffffc04bc00-0x20 .peer:0x2000-0x0 .shared:0x2000-0x0 .bss:0xfffffffffc0949c0-0x9d08 .text:0xfffffffffc27dd80-0xa6f2 .statvars:0x2000-0x0 .kstatvars:0x2000-0x0 .eh_frame:0xfffffffffc29edb0-0x17a0 .comment:0xec4-0x36, gphys-ept.vmm64 .rodata:0xfffffffffc213558-0x29 .data:0xfffffffffc04bc20-0x4 .peer:0xfffffffffc075880-0x40 .shared:0xfffffffffc088f00-0x200 .bss:0xfffffffffc09e6e0-0x79 .text:0xfffffffffc288480-0x1f14 .statvars:0x2000-0x0 .kstatvars:0x2000-0x0 .scb:0x3a20-0x60 .shared_meta:0x4020-0x2a0 .peer_meta:0x1230-0x60 .eh_frame:0xfffffffffc2a0550-0x650 .comment:0xefa-0x12, vassert-none.vmm64 .text:0xfffffffffc28a394-0xf .eh_frame:0xfffffffffc2a0ba0-0x78 .comment:0xf0c-0x12, vmsafe-none.vmm64 .text:0xfffffffffc28a3a4-0x6 .eh_frame:0xfffffffffc2a0c18-0x78 .comment:0xf1e-0x12, <MonSrcFile> .rodata:0xfffffffffc213581-0x389| 0x56000]
Apr 10 14:38:57.802: vcpu-0| APIC: version = 0x15, max LVT = 6
Apr 10 14:38:57.802: vcpu-0| APIC: LDR = 0x1000000, DFR = 0xffffffff
Apr 10 14:38:57.802: vcpu-0| HV enabled
Apr 10 14:38:57.818: vcpu-0| VMM64 initialized
Apr 10 14:38:57.818: vcpu-0| MonitorInitNumaUnmapVMM64
Apr 10 14:38:57.849: vcpu-0| DecoderIsInvalidInstruction:686 0xc091f6c5 #UD 830fffff sz=2 ct=0
Apr 10 14:38:57.865: vcpu-0| Msg_Hint: msg.monitorevent.halt (sent)
Apr 10 14:38:57.865: vcpu-0| The CPU has been disabled by the guest operating system. You will need to power off or reset the virtual machine at this point.
Apr 10 14:38:57.865: vcpu-0| ---------------------------------------
Apr 10 14:40:05.647: vmx| Stopping VCPU threads...
Apr 10 14:40:05.662: mks| MKSHostOps_Exit3D: 1, 0
Apr 10 14:40:05.662: mks| Async MKS thread is exiting
Apr 10 14:40:05.662: vmx| SOCKET 2 (1704) close VNC socket on VNCBackendDestroy
Apr 10 14:40:05.678: vmx| MKS local poweroff
Apr 10 14:40:05.678: vmx| scsi0:0: numIOs = 9203 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)
Apr 10 14:40:05.896: vmx| AIOWIN32C: asyncOps=1029 syncOps=76 bufSize=4Kb fixedOps=25 sgOps=1058 sgOn=1
Apr 10 14:40:05.896: aioCompletion| AIO thread processed 1029 completions
Apr 10 14:40:05.896: vmx| AIOWIN32: asyncOps=0 syncOps=0 bufSize=0Kb delayed=0 fixed=0 sgOp=0 sgOn=1
Apr 10 14:40:05.912: vmx| WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
Apr 10 14:40:05.927: vmx| Transitioned vmx/execState/val to poweredOff
Apr 10 14:40:06.193: vmx| vmdbPipe_Streams: Couldn't read
Apr 10 14:40:06.193: vmx| VMX idle exit
Apr 10 14:40:06.193: vmx| Flushing VMX VMDB connections
Apr 10 14:40:06.193: vmx| IPC_exit: disconnecting all threads
Apr 10 14:40:06.193: vmx| VMX exit (0).
Does somebody has an idea what is going on here? I really would like to get BT4 up and running!
Any suggestions/feedback is appreciated.
Thanks.
The vmware bt4 image was built for vmware workstation 6.5.1 and so needs that version or later.
I have heard about a tool to convert the image to other versions but cannot remember the name right now.
The easiest option will be to use the bt4 iso and install it using the method detailed in the bt4install.pdf
Try this
There's KB article at VMWare's self support site (won't let me post the link), but see below.Originally Posted by astein
I can't explain why BT3 wouldn't have the same problem, but this is what they said in the article:
"To be able to boot the guest operating system, you need to disable the SpeedStep applet before you run this operating system as a guest operating system. To do so, start the operating system natively and take the following steps:
1. In the Control Panel, double-click the Power Options icon. On Windows XP, you may need to click Classic View first.
2. Click the Intel SpeedStep technology tab.
3. Click the Advanced button.
4. Check the Disable Intel SpeedStep technology control check box.
5. Click OK twice to close the SpeedStep dialog boxes."
The above is for XP, so you may have to modify it a bit for win 2003 or vista. It doesn't hurt to try it, if it doesn't fix it you can re-enable it.
.
The red highlighted text are the important error messages.
The problem is the guest is trying to operate in 32bit mode with 64bit extensions and by itself this will not work.
You should try and do an install and see if that corrects the issue.
The guest OS selection does not affect the properties of the virtual CPU. On a 64-bit host, the virtual CPU will also be 64-bit, regardless of guest OS selection. You can still install a 32-bit guest OS in the VM, just as you can install a 32-bit OS on 64-bit hardware. You can also try adding the following to you vmware config file for the guest.
Let us know how it works out.Code:monitor_control.disable_longmode = TRUE
To be successful here you should read all of the following.
ForumRules
ForumFAQ
If you are new to Back|Track
Back|Track Wiki
Failure to do so will probably get your threads deleted or worse.
Hi Waydaws and balding_parrot,
Thanks for taking the time to provide some idea's and suggestions.
There was indeed a newer bios available for my motherboard and I've thus upgraded the bios. Unfortunately this didn't solve the problem. I'm still having the same problem as described in this thread. Below the last lines from the VMWare log file.
Additional intomation, I'm running on a Foxconn Renaissance motherboard 1366 socket and a Intel Core i7 (quad core) CPU.
Regarding the VMWare versions and conversion, all my VMWare images running "Virtual Hardware Version 7" (including BT4 Beta) so this is the latest if I'm correct.
I also have tried to install the VMWare Player but then I get a complain that the Server version is already installed. I'm my view the core of the VMWare Server and VMWare Player products are the same and thus I should not be neccessary to convert the vmware files, or am I wrong?
Apr 11 12:10:27.870: vcpu-0| pciBridge6:3: ISA/VGA decoding enabled (ctrl 0004)
Apr 11 12:10:27.870: vcpu-0| pciBridge6:4: ISA/VGA decoding enabled (ctrl 0004)
Apr 11 12:10:27.870: vcpu-0| pciBridge6:5: ISA/VGA decoding enabled (ctrl 0004)
Apr 11 12:10:27.870: vcpu-0| pciBridge6:6: ISA/VGA decoding enabled (ctrl 0004)
Apr 11 12:10:27.870: vcpu-0| pciBridge6:7: ISA/VGA decoding enabled (ctrl 0004)
Apr 11 12:10:27.870: vcpu-0| PCIBridge7: ISA/VGA decoding enabled (ctrl 0004)
Apr 11 12:10:27.870: vcpu-0| pciBridge7:1: ISA/VGA decoding enabled (ctrl 0004)
Apr 11 12:10:27.870: vcpu-0| pciBridge7:2: ISA/VGA decoding enabled (ctrl 0004)
Apr 11 12:10:27.870: vcpu-0| pciBridge7:3: ISA/VGA decoding enabled (ctrl 0004)
Apr 11 12:10:27.870: vcpu-0| pciBridge7:4: ISA/VGA decoding enabled (ctrl 0004)
Apr 11 12:10:27.870: vcpu-0| pciBridge7:5: ISA/VGA decoding enabled (ctrl 0004)
Apr 11 12:10:27.870: vcpu-0| pciBridge7:6: ISA/VGA decoding enabled (ctrl 0004)
Apr 11 12:10:27.870: vcpu-0| pciBridge7:7: ISA/VGA decoding enabled (ctrl 0004)
Apr 11 12:10:27.886: vcpu-0| DISKUTIL: scsi0:0 : geometry=1044/255/63
Apr 11 12:10:27.886: vcpu-0| SCSI0: RESET BUS
Apr 11 12:10:27.948: vcpu-0| BIOS-UUID is 56 4d 6c d4 c5 fe 59 b4-f8 26 30 23 33 93 42 4b
Apr 11 12:10:34.719: mks| SVGA: display status changed, using optimizations for local consoles.
Apr 11 12:10:37.324: vcpu-0| Unknown int 10h func 0x0000
Apr 11 12:10:37.324: vcpu-0| Unknown int 10h func 0x0000
Apr 11 12:10:38.400: vcpu-0| Monitor64_PowerOn()
Apr 11 12:10:38.400: vcpu-0| vmm64-modules: [vmm.vmm64 .data:0xfffffffffc04b000-0xbe0 .sdata:0xfffffffffc04c000-0x9a8 .statvars:0xfffffffffc04d000-0x1e4 .peer:0xfffffffffc04e000-0x261c0 .shared:0xfffffffffc076000-0x12ac0 .bss:0xfffffffffc08a000-0xa080 .rodata:0xfffffffffc200000-0x12d80 .text:0xfffffffffc214000-0x5f67e .kstatvars:0x3000-0x0 .eh_frame:0xfffffffffc28b000-0x11da8, mmu-hwmmu.vmm64 .rodata:0xfffffffffc212d80-0xd2 .data:0xfffffffffc04bbe0-0x14 .peer:0xfffffffffc0741c0-0x16c0 .shared:0xfffffffffc088ac0-0x2c0 .bss:0xfffffffffc094080-0x930 .text:0xfffffffffc273680-0xa665 .statvars:0x2000-0x0 .kstatvars:0x2000-0x0 .scb:0x38a0-0x180 .shared_meta:0x3c00-0x390 .peer_meta:0x1020-0x210 .eh_frame:0xfffffffffc29cda8-0x1bb8 .comment:0xd4a-0x10e, sharedmmu-none.vmm64 .text:0xfffffffffc27dce8-0x1a .eh_frame:0xfffffffffc29e960-0x138 .comment:0xe58-0x12, pv-none.vmm64 .shared:0xfffffffffc088d80-0x180 .bss:0x1000-0x0 .text:0xfffffffffc27dd04-0x4 .shared_meta:0x3f90-0x90 .eh_frame:0xfffffffffc29ea98-0x48 .comment:0xe6a-0x48, vprobe-none.vmm64 .text:0xfffffffffc27dd08-0x6a .eh_frame:0xfffffffffc29eae0-0x2d0 .comment:0xeb2-0x12, hv-vt.vmm64 .rodata:0xfffffffffc212e60-0x6f4 .data:0xfffffffffc04bc00-0x20 .peer:0x2000-0x0 .shared:0x2000-0x0 .bss:0xfffffffffc0949c0-0x9d08 .text:0xfffffffffc27dd80-0xa6f2 .statvars:0x2000-0x0 .kstatvars:0x2000-0x0 .eh_frame:0xfffffffffc29edb0-0x17a0 .comment:0xec4-0x36, gphys-ept.vmm64 .rodata:0xfffffffffc213558-0x29 .data:0xfffffffffc04bc20-0x4 .peer:0xfffffffffc075880-0x40 .shared:0xfffffffffc088f00-0x200 .bss:0xfffffffffc09e6e0-0x79 .text:0xfffffffffc288480-0x1f14 .statvars:0x2000-0x0 .kstatvars:0x2000-0x0 .scb:0x3a20-0x60 .shared_meta:0x4020-0x2a0 .peer_meta:0x1230-0x60 .eh_frame:0xfffffffffc2a0550-0x650 .comment:0xefa-0x12, vassert-none.vmm64 .text:0xfffffffffc28a394-0xf .eh_frame:0xfffffffffc2a0ba0-0x78 .comment:0xf0c-0x12, vmsafe-none.vmm64 .text:0xfffffffffc28a3a4-0x6 .eh_frame:0xfffffffffc2a0c18-0x78 .comment:0xf1e-0x12, <MonSrcFile> .rodata:0xfffffffffc213581-0x389| 0x56000]
Apr 11 12:10:38.416: vcpu-0| APIC: version = 0x15, max LVT = 6
Apr 11 12:10:38.416: vcpu-0| APIC: LDR = 0x1000000, DFR = 0xffffffff
Apr 11 12:10:38.416: vcpu-0| HV enabled
Apr 11 12:10:38.432: vcpu-0| VMM64 initialized
Apr 11 12:10:38.432: vcpu-0| MonitorInitNumaUnmapVMM64
Apr 11 12:10:38.463: vcpu-0| DecoderIsInvalidInstruction:686 0xc091f6c5 #UD 830fffff sz=2 ct=0
Apr 11 12:10:38.478: vcpu-0| Msg_Hint: msg.monitorevent.halt (sent)
Apr 11 12:10:38.478: vcpu-0| The CPU has been disabled by the guest operating system. You will need to power off or reset the virtual machine at this point.
Apr 11 12:10:38.478: vcpu-0| ---------------------------------------
Apr 11 12:10:59.601: mks| Create Memory BIO succeeded.
Apr 11 12:10:59.601: mks| Create Memory BIO succeeded.
Apr 11 12:11:15.482: mks| VNCENCODE 2 encoding mode change: (1024x768x16depth,16bpp,2048bytes/line)
Apr 11 12:11:15.497: mks| VNCENCODE 2 encoding mode change: (1024x768x16depth,16bpp,2048bytes/line)
Apr 11 12:11:21.597: mks| SVGA: display status changed, using optimizations for remote consoles.
Hi archangel.amael,
Thanks for the suggestion. I agree with you it has to do something with the 32 Bit Guest OS running on a 64 Bit Host. Other VMWare images Ubuntu 32 bit, Windows XP 32 bit, Vista 32 bit are all running fine. In those VMWare config files I do not find the monitor_control.disable_longmode configuration setting!
What do you mean with:
"You should try and do an install and see if that corrects the issue. "?
If added to following line to the BT4-Beta.vmx config file:
monitor_control.disable_longmode = TRUE
or
monitor_control.disable_longmode = "TRUE"
But this didn't solve the problem (unfortunately). Below the logging:
Apr 11 12:37:28.869: mks| SVGA: display status changed, using optimizations for local consoles.
Apr 11 12:37:31.537: vcpu-0| Unknown int 10h func 0x0000
Apr 11 12:37:31.537: vcpu-0| Unknown int 10h func 0x0000
Apr 11 12:37:32.597: vcpu-0| Monitor64_PowerOn()
Apr 11 12:37:32.613: vcpu-0| vmm64-modules: [vmm.vmm64 .data:0xfffffffffc04b000-0xbe0 .sdata:0xfffffffffc04c000-0x9a8 .statvars:0xfffffffffc04d000-0x1e4 .peer:0xfffffffffc04e000-0x261c0 .shared:0xfffffffffc076000-0x12ac0 .bss:0xfffffffffc08a000-0xa080 .rodata:0xfffffffffc200000-0x12d80 .text:0xfffffffffc214000-0x5f67e .kstatvars:0x3000-0x0 .eh_frame:0xfffffffffc28b000-0x11da8, mmu-hwmmu.vmm64 .rodata:0xfffffffffc212d80-0xd2 .data:0xfffffffffc04bbe0-0x14 .peer:0xfffffffffc0741c0-0x16c0 .shared:0xfffffffffc088ac0-0x2c0 .bss:0xfffffffffc094080-0x930 .text:0xfffffffffc273680-0xa665 .statvars:0x2000-0x0 .kstatvars:0x2000-0x0 .scb:0x38a0-0x180 .shared_meta:0x3c00-0x390 .peer_meta:0x1020-0x210 .eh_frame:0xfffffffffc29cda8-0x1bb8 .comment:0xd4a-0x10e, sharedmmu-none.vmm64 .text:0xfffffffffc27dce8-0x1a .eh_frame:0xfffffffffc29e960-0x138 .comment:0xe58-0x12, pv-none.vmm64 .shared:0xfffffffffc088d80-0x180 .bss:0x1000-0x0 .text:0xfffffffffc27dd04-0x4 .shared_meta:0x3f90-0x90 .eh_frame:0xfffffffffc29ea98-0x48 .comment:0xe6a-0x48, vprobe-none.vmm64 .text:0xfffffffffc27dd08-0x6a .eh_frame:0xfffffffffc29eae0-0x2d0 .comment:0xeb2-0x12, hv-vt.vmm64 .rodata:0xfffffffffc212e60-0x6f4 .data:0xfffffffffc04bc00-0x20 .peer:0x2000-0x0 .shared:0x2000-0x0 .bss:0xfffffffffc0949c0-0x9d08 .text:0xfffffffffc27dd80-0xa6f2 .statvars:0x2000-0x0 .kstatvars:0x2000-0x0 .eh_frame:0xfffffffffc29edb0-0x17a0 .comment:0xec4-0x36, gphys-ept.vmm64 .rodata:0xfffffffffc213558-0x29 .data:0xfffffffffc04bc20-0x4 .peer:0xfffffffffc075880-0x40 .shared:0xfffffffffc088f00-0x200 .bss:0xfffffffffc09e6e0-0x79 .text:0xfffffffffc288480-0x1f14 .statvars:0x2000-0x0 .kstatvars:0x2000-0x0 .scb:0x3a20-0x60 .shared_meta:0x4020-0x2a0 .peer_meta:0x1230-0x60 .eh_frame:0xfffffffffc2a0550-0x650 .comment:0xefa-0x12, vassert-none.vmm64 .text:0xfffffffffc28a394-0xf .eh_frame:0xfffffffffc2a0ba0-0x78 .comment:0xf0c-0x12, vmsafe-none.vmm64 .text:0xfffffffffc28a3a4-0x6 .eh_frame:0xfffffffffc2a0c18-0x78 .comment:0xf1e-0x12, <MonSrcFile> .rodata:0xfffffffffc213581-0x389| 0x56000]
Apr 11 12:37:32.613: vcpu-0| APIC: version = 0x15, max LVT = 6
Apr 11 12:37:32.613: vcpu-0| APIC: LDR = 0x40000000, DFR = 0xffffffff
Apr 11 12:37:32.613: vcpu-0| HV enabled
Apr 11 12:37:32.629: vcpu-0| VMM64 initialized
Apr 11 12:37:32.629: vcpu-0| MonitorInitNumaUnmapVMM64
Apr 11 12:37:32.660: vcpu-0| DecoderIsInvalidInstruction:686 0xc091f6c5 #UD 830fffff sz=2 ct=0
Apr 11 12:37:32.675: vcpu-0| Msg_Hint: msg.monitorevent.halt (sent)
Apr 11 12:37:32.675: vcpu-0| The CPU has been disabled by the guest operating system. You will need to power off or reset the virtual machine at this point.
Apr 11 12:37:32.675: vcpu-0| ---------------------------------------
Apr 11 12:37:54.422: mks| Create Memory BIO succeeded.
Apr 11 12:37:54.422: mks| Create Memory BIO succeeded.
Apr 11 12:38:10.178: mks| VNCENCODE 2 encoding mode change: (1024x768x16depth,16bpp,2048bytes/line)
Apr 11 12:38:10.256: mks| VNCENCODE 2 encoding mode change: (1024x768x16depth,16bpp,2048bytes/line)
Apr 11 12:38:15.716: mks| SVGA: display status changed, using optimizations for remote consoles.
Im just going to chime in here and say i have bt4 with vmware 6.5.2 running on 64bit win7
Using backtrack for the first time is like being 10 years old again with the keys to a Ferrari.
The image has been created for VMware Workstation with are not complate with Server or ESX.
You will need to use VMWare converter to downgrade the Image to a compatible one.
http://www.vmware.com/products/converter/
I am not sure about the ESX but as for server, I run server 2.0.1 and BT3 and 4beta and they work just fine for me.
To be successful here you should read all of the following.
ForumRules
ForumFAQ
If you are new to Back|Track
Back|Track Wiki
Failure to do so will probably get your threads deleted or worse.
Posting Permissions
