VirtualBox

Ticket #6923 (closed defect: worksforme)

Opened 4 years ago

Last modified 4 years ago

Setting VESA custom resolutions

Reported by: OxOOCOFFEE Owned by:
Priority: major 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

comment:1 Changed 4 years ago by OxOOCOFFEE

This is in 3.2.2 NOT 3.2.4!!!! 3.2.4 is not available yet

comment:2 Changed 4 years ago by frank

  • Version changed from VirtualBox 3.2.4 to VirtualBox 3.2.2

comment:3 Changed 4 years ago by OxOOCOFFEE

Same problem with 3.2.4 after upgrade

comment:4 Changed 4 years ago by frank

  • Status changed from new to closed
  • Resolution set to worksforme

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.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use