Opened 14 years ago
Closed 14 years ago
#6923 closed defect (worksforme)
Setting VESA custom resolutions
| Reported by: | oxoocoffee | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 3.2.2 |
| Keywords: | Curton Video Mode Guest not detected problem | Cc: | |
| Guest type: | other | Host type: | Windows |
Description
I was trying to run (BoxManage setextradata global "CustomVideoMode1" "1400x800x16") does not take affect when guest is running VESA gfx driver. I was testing this with CentOS and Haiku-os.org. No guest tools were installed. How would one go and verify after starting vbox that vbox indeed reports such resolution to determine if this is a problem with on guest OS vs VBOX. My VirtualBox.xml has this
<ExtraData>
<ExtraDataItem name="CustomVideoMode1" value="1400x800x16"/> <ExtraDataItem name="CustomVideoMode2" value="1400x800x32"/>
Change History (4)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
| Version: | VirtualBox 3.2.4 → VirtualBox 3.2.2 |
|---|
comment:4 by , 14 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Please read the manual again. This is not a global setting but a per-VM setting so you have to specify the VM name when doing VBoxManage setextradata. Check if this works by starting a VM, make sure the GRUB menu pops up (pressing SHIFT during the BIOS logo should do this) then enter the grub command vbeprobe which should show you all available VESA BIOS resolutions.
This is in 3.2.2 NOT 3.2.4!!!! 3.2.4 is not available yet