I have just installed openSUSE 12.03 in a virtual machine box under Microsoft Hyper-V on Windows 8 Pro.
I attempted to change the resolution from 800x600 to something more acceptable, but under Display and Monitor configuration, there are no other options than 800x600.
Microsoft’s website says that openSUSE 12.1 is a supported operating system with their Integration Services built in. This should, I would think allow me to utilize the full range of resolutions for the display adapter in my machine. I say this because all my other guest operating system installations work fine with the complete range of resolutions available for my display.
I have also installed Ubuntu 12.04 and CentOS 6.4 as well as Windows XP, Vista and 7 and none of these other installs gives me similar problems.
Is there an alternate way to alter the display resolution, perhaps using a command line utility? Are the integration services still supported in 12.3 as the apparently are in 12.1?
Note that I am running an Intel Core i3-3220 with an Intel B75 chipset motherboard that uses the Intel default graphics available through that board/cpu on the physical system.
Thanks for the pointers. BTW, I put the version wrong - it is version 12.3 of openSUSE.
Here is the output of xrandr:
scott@TW100-BRF214:~> xrandrxrandr: Failed to get size of gamma for output default
Screen 0: minimum 800 x 600, current 800 x 600, maximum 800 x 600
default connected 800x600+0+0 0mm x 0mm
800x600 75.0*
If this sheds further light, please let me know. Someone on the Microsoft Server Hyper-V forum suggested I try version 12.1 of openSUSE since this is on the compatibility list. 12.3 is not. I just assumed if 112.1 were compatible 12.3 would be also.
The output shows that the display resolution is limited by the ‘detected’ hardware in use. The driver is not shown in your output, but probably the X.Org vesa driver is in use, and that is being determined by the virtual graphics card presented by the Microsoft host. You could examine /var/log/Xorg.0.log from openSUSE to discover more detail, including the driver loaded. If you want to share that info here, please cut/paste, and upload it to SUSE Paste, then post the link to it here. Once, we know this info more definitively, it may be possible to manually configure the X-server to proved better display resolution. However, I’m also thinking that you will need to configure the host graphics configuration in order for the guest to provide optimal graphics performance. Now, I’m not familiar with using this VM, so you’ll have to research this further yourself.
I will google around for ways to change the settings for the virtual card using the Hyper-V manager, but I have a sneaking feeling there is very little I can do there.
Display Adapter / Video The Xorg server uses vesa driver (since Microsoft has developed a weird proprietary device PCI:1414:5353).
It works quite well under both Etch and Lenny (Xorg 7.3). However:
Using xrandr causes the Xserver to restart.
vga= works, but you can’t switch between X11 and the console (it causes the system to crash).
Under Lenny, the Emulated screen always pretend to be 1600x1200… which is anoying if you have a smaller screen (you can force it in xorg-lenny.conf.txt )
Actually, your xorg log shows that the more primitive framebuffer (fbdev) driver is in use, which explains the low resolution. (The vesa module is loaded then later unloaded).
17.398] (--) FBDEV(0): Virtual size is 800x600 (pitch 800)
17.398] (**) FBDEV(0): Built-in mode "current": 48.0 MHz, 46.9 kHz, 75.1 Hz
17.398] (II) FBDEV(0): Modeline "current"x0.0 48.00 800 832 928 1024 600 604
608 624 -hsync -vsync -csync (46.9 kHz b)
17.398] (==) FBDEV(0): DPI set to (96, 96)
17.398] (II) Loading sub module "fb"
17.398] (II) LoadModule: "fb"
17.398] (II) Loading /usr/lib64/xorg/modules/libfb.so
17.403] (II) Module fb: vendor="X.Org Foundation"
17.403] compiled for 1.13.2, module version = 1.0.0
17.403] ABI class: X.Org ANSI C Emulation, version 0.4
17.403] (**) FBDEV(0): using shadow framebuffer
17.403] (II) Loading sub module "shadow"
17.403] (II) LoadModule: "shadow"
17.403] (II) Loading /usr/lib64/xorg/modules/libshadow.so
17.412] (II) Module shadow: vendor="X.Org Foundation"
17.412] compiled for 1.13.2, module version = 1.1.0
17.412] ABI class: X.Org ANSI C Emulation, version 0.4
17.412] (II) UnloadModule: "vesa"
17.412] (II) Unloading vesa
Thanks for the information. Is there any way to change the driver that is loaded? Can you shed any light, if you happen to know, on why it would behave in this manner?
They’re probably managing to load the vesa driver. You could try editing /etc/X11/xorg.conf.d/50-device.conf so that it loads the vesa driver explicitly
Section Device
Driver vesa
EndSection
A higher display resolution may be able to be coaxed via an edit to /etc/X11/xorg.conf.d/50-screen.conf (using a supported VESA resolution) eg
Microsoft’s Hyper-V does not support USB devices and there are other limitations that has been discussed in various news articles and blogs. To run a guest operating system in a virtualized session, you cannot run the guest OS at the host OS screen size resolution. For instance, on a laptop the guest OS will not adapt to the host OS video settings. This feature is important to me as it affects how I work with and use the guest OS.
Thanks so much for all your help so far - I appreciate the “extra mile” in finding those comparison articles.
I am just about to try your suggestions on openSUSE to see if it works. If your suggestions do not work, I will try 12.1 as a guest OS to see if that works.
I will report back as soon as I do.
I will also report to the Microsoft Server Hyper-V forum any successes so I can pass along the help if it all works out.
Now everything works hunky dory! I am not sure if I should mark yours as the answer though because it has errors - if you can edit it, I will mark it as an answer. Is that OK?
Now everything works hunky dory! I am not sure if I should mark yours as the answer though because it has errors - if you can edit it, I will mark it as an answer. Is that OK?
Ah, sorry about that. I forgot the quotes around ‘Device’… and driver too Doh!..Yes, one has to be very careful about the syntax with these files to prevent X-server crashing.
Section "Device"
Driver "vesa"
EndSection
The 50-screen.conf should have been okay though.
No need to mark it solved. We don’t generally do that around here.
On 2013-05-28 03:36, deano ferrari wrote:
>
> Some comparisons between the two:
>
> ‘Why is hyper-v better than virtualbox?’ (http://tinyurl.com/oh7s8cx)
>
> ‘My Windows 8 Experiences: Hyper-V or VirtualBox in Windows 8’
> (http://tinyurl.com/nzdej9x)
>
> and you’ll be interested to note
>> Microsoft’s Hyper-V does not support USB devices and there are other
>> limitations that has been discussed in various news articles and blogs.
>> To run a guest operating system in a virtualized session, you cannot
>> run the guest OS at the host OS screen size resolution. For instance,
>> on a laptop the guest OS will not adapt to the host OS video settings.
>> This feature is important to me as it affects how I work with and use
>> the guest OS.
I notice that this is a virtualized system, so this thread should be
moved to the virtualization subforum.
The issue has been solved, but it occurs to me that both virtualbox or
vmware use a set of “guest tools” that, amongst many other things, they
serve to adjust the guest size, or resolution. In vmplayer, for
instance, you simply resize the player window and the guest inside
automatically changes resolution. Without the tools running, you get a
black border, the resolution does not change.
Without the tools, you can manually change the guest resolution, using
the gadget in the panel, if available.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
I appreciate the info … I will have to try other virtualization solutions also. I am just getting my feet wet so far, and it is an amazing type of technology … operating systems research and learning with (practical) impunity!
Please not in my post above that you have to give a name to the section in the configuration files - it explicitly failed on that as well as the other stuff.
