Installation guide

unix_sock_group = <g ro up>

unix_sock_ro_perms = <perms>

unix_sock_rw_perms = <perms>

Note

The user running vi rsh must be a member of the g ro up specified in the

uni x_so ck_g ro up option.

B.2.3. Ot her connect ivit y errors

Un ab le t o co n n ect t o server at server: po rt: Co n n ect io n ref u sed

The daemon is not running on the server or is configured not to listen, using configuration

option l i sten_tcp or l i sten_tl s.

En d o f f ile wh ile read in g d at a: n c: u sin g st ream so cket : In p u t /ou t pu t erro r

If you specified ssh transport, the daemon is likely not running on the server. Solve this

error by verifying that the daemon is running on the server.

B.3. T he guest virt ual machine cannot be st art ed: i nternal erro r g uest

C P U i s no t co mpati bl e wi th ho st C P U

Symp t o m

Running on an Intel Core i7 processor (which virt - man ag er refers to as Nehal em, or the

older Core 2 Duo, referred to as P enryn), a KVM guest (or domain) is created using virt -

manag er. After installation, the guest's processor is changed to match the host's CPU. The

guest is then unable to start and reports this error:

2012-02-06 17:49:15.985+0000: 20757: error :

qemuBuildCpuArgStr:3565 : internal error guest CPU is not

compatible with host CPU

Additionally, clicking C o py ho st C P U co nfi g urati o n in virt - man ag er shows

Pentium III instead of Nehal em or P enryn.

In vest ig at io n

The /usr/share/l i bvi rt/cpu_map. xml file lists the flags that define each CPU model.

The Nehal em and P enryn definitions contain this:

As a result, the NX (or No eXecute) flag needs to be presented to identify the CPU as

Nehal em or P enryn. However, in /pro c/cpui nfo , this flag is missing.

So lu t io n

Red Hat Ent erp rise Linux 6 Virt ualiz at ion Host Configurat ion and G uest Inst allat ion G uide

132