[CentOS] KVM Linux Guest Resolution only 1024x768

[Chris]

Dear All,

I'm trying to install a Debian Wheezy KVM guest on a CentOS 6.4 Host.
The only resolutions supported are 1024x768 or 800x600.

I increased the video RAM to 500 MB, but the guest still says:

[10.321] (II) CIRRUS(0): Not using default mode "1920x1200"
(insufficient memory for mode)

Only 32 MB are recognized:

00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00 [VGA
controller])
Subsystem: Red Hat, Inc Device 1100
Physical Slot: 2
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
SERR- http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] KVM Linux Guest Resolution only 1024x768

[Nux!]

On 04.05.2014 08:39, Chris wrote:
> Dear All,
> 
> I'm trying to install a Debian Wheezy KVM guest on a CentOS 6.4 Host.
> The only resolutions supported are 1024x768 or 800x600.
> 
> I increased the video RAM to 500 MB, but the guest still says:
> 
> [10.321] (II) CIRRUS(0): Not using default mode "1920x1200"
> (insufficient memory for mode)
> 
> Only 32 MB are recognized:
> 
> 00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00 
> [VGA
> controller])
> Subsystem: Red Hat, Inc Device 1100
> Physical Slot: 2
> Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> SERR-  Region 0: Memory at f000 (32-bit, prefetchable) [size=32M]
> Region 1: Memory at f200 (32-bit, non-prefetchable) 
> [size=4K]
> Expansion ROM at f201 [disabled] [size=64K]
> 
> How can I increase the resolution? Are any guest modifications 
> necessary?

For better video performance switch from VNC to Spice display and QXL 
video card.

HTH
Lucian

-- 
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Disappearing Network Manager config scripts

[Evan Rowley]

When I started this thread a week ago, I certainly did not expect this many
replies. Without a doubt it seems Network Manager is a controversial topic.
I still haven't worked out my Network Manager woes and just lost an hour
troubleshooting a Golang webserver which wouldn't start.

Apparently in Golang's net package, there is a DNS resolver function that's
called whenever a server is started. That function depends on a working
/etc/resolv.conf - As per usual, the /etc/resolv.conf file turned out to be
the blank template NetworkManager always creates. The webserver starts now,
but this /etc/resolv.conf will certainly be blown away by NetworkManager
the next time the network service restarts.

I have one idea as to why this problem persists. This file:

ll /etc/sysconfig/network-scripts/ifcfg-eth0
...

-rw-r--r--. 1 root root44 Apr 26 22:21 ifcfg-eth0


Is it meant to be executable? Being a configuration file, I'm assuming it
doesn't need to be. Am I wrong?




On Thu, May 1, 2014 at 9:49 PM, Keith Keller <
kkel...@wombat.san-francisco.ca.us> wrote:

> On 2014-05-01, m.r...@5-cent.us  wrote:
> >
> > I think I need to check with my manager - we do have a few RH licenses -
> > and maybe I, or several of us, should put in an enhancement request for
> 7:
> > DO NOT INSTALL NM by default *EXCEPT* for either a desktop, or, better, a
> > laptop install. DO set network up by default in all other cases.
>
> I would suggest that it be installed and used by default for a
> ''beginner'' install, and specifically asked about in an ''expert''
> install.  I don't see the point in making a distinction between server,
> desktop, or laptop, because an expert setting up a laptop might prefer
> not to use NM, and a beginner setting up a server might need NM, or
> might not even know how to configure a network without it.  (I know,
> beginners probably shouldn't be installing servers, but they're going to
> do it anyway.)
>
> --keith
>
> --
> kkel...@wombat.san-francisco.ca.us
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>



-- 
 - EJR
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Disappearing Network Manager config scripts

[Matthew Miller]

On Sun, May 04, 2014 at 07:22:52PM -0400, Evan Rowley wrote:
> Apparently in Golang's net package, there is a DNS resolver function that's
> called whenever a server is started. That function depends on a working
> /etc/resolv.conf - As per usual, the /etc/resolv.conf file turned out to be
> the blank template NetworkManager always creates. The webserver starts now,
> but this /etc/resolv.conf will certainly be blown away by NetworkManager
> the next time the network service restarts.

Are you not getting a _correct_ resolv.conf from NetworkManager? Why not?

This doesn't seem like it is Go related at all -- if you want any DNS to be
working at all, pretty much all resolvers need that file.

> I have one idea as to why this problem persists. This file:
> ll /etc/sysconfig/network-scripts/ifcfg-eth0
> Is it meant to be executable? Being a configuration file, I'm assuming it
> doesn't need to be. Am I wrong?

You're not wrong. This is not your problem.

-- 
Matthew Miller   mat...@mattdm.org  
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Disappearing Network Manager config scripts

[Cliff Pratt]

That file is 'sourced' by other network scripts so doesn't have to be
executable, but the contents set environment variables for other scripts.
Or so I believe. No doubt someone will correct me if I am wrong. 8-)

Cheers,

Cliff


On Mon, May 5, 2014 at 11:27 AM, Matthew Miller  wrote:

> On Sun, May 04, 2014 at 07:22:52PM -0400, Evan Rowley wrote:
> > Apparently in Golang's net package, there is a DNS resolver function
> that's
> > called whenever a server is started. That function depends on a working
> > /etc/resolv.conf - As per usual, the /etc/resolv.conf file turned out to
> be
> > the blank template NetworkManager always creates. The webserver starts
> now,
> > but this /etc/resolv.conf will certainly be blown away by NetworkManager
> > the next time the network service restarts.
>
> Are you not getting a _correct_ resolv.conf from NetworkManager? Why not?
>
> This doesn't seem like it is Go related at all -- if you want any DNS to be
> working at all, pretty much all resolvers need that file.
>
> > I have one idea as to why this problem persists. This file:
> > ll /etc/sysconfig/network-scripts/ifcfg-eth0
> > Is it meant to be executable? Being a configuration file, I'm assuming it
> > doesn't need to be. Am I wrong?
>
> You're not wrong. This is not your problem.
>
> --
> Matthew Miller   mat...@mattdm.org  
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos