Installation guide

PXE boot (or D HCP) on guest
failed
A guest virtual machine starts
successfully, but is unable to
acquire an IP address from
DHCP, boot using the PXE
protocol, or both. This is often
a result of a long forward delay
time set for the bridge, or when
the iptables package and kernel
do not support checksum
mangling rules.
Section B.8, “ PXE boot (or
DHCP) on guest failed”
Guest can reach outside
network, but cannot reach host
when using macvtap interface
A guest can communicate with
other guests, but cannot
connect to the host machine
after being configured to use a
macvtap (or type='direct')
network interface.
This is actually not an error —
it is the defined behavior of
macvtap.
Section B.9, “ Guest can reach
outside network, but cannot
reach host when using
macvtap interface”
C o ul d no t ad d rul e to
fi xup D HC P respo nse
checksums o n netwo rk
'default'
This warning message is
almost always harmless, but is
often mistakenly seen as
evidence of a problem.
Section B.10, “ Could not add
rule to fixup DHCP response
checksums on network 'default'”
Unabl e to ad d bri d g e
br0 po rt vnet0 : No such
d evi ce
This error message or the
similar Fai l ed to ad d tap
i nterface to bri dg e
'br0': No such d evi ce
reveal that the bridge device
specified in the guest's (or
domain's) <i nterface>
definition does not exist.
Section B.11, “Unable to add
bridge br0 port vnet0: No such
device”
Warni ng : co ul d no t
o pen /d ev/net/tun: no
vi rtual netwo rk
emul ati o n q emu-kvm: -
netd ev
tap,scri pt= /etc/my-
q emu-i fup,i d = ho stnet0 :
D evi ce ' tap' co ul d no t
be i ni ti al i zed
The guest virtual machine does
not start after configuring a
type= ' ethernet' (or 'generic
ethernet') interface in the host
system. This error or similar
appears either in
l i bvi rtd .l o g ,
/var/l o g /l i bvi rt/q emu/n
ame_of_guest. l o g , or in
both.
Section B.12, “ Guest is unable
to start with error: warni ng :
co ul d no t o pen
/d ev/net/tun”
Unabl e to reso l ve
ad dress name_of_host
servi ce ' 4 9155' : Name
o r servi ce no t kno wn
Q EMU guest migration fails
and this error message
appears with an unfamiliar
hostname.
Section B.13, “ Migration fails
with Erro r: unabl e to
reso l ve ad d ress”
Unabl e to al l o w access
fo r d i sk path
/var/l i b/l i bvi rt/i mag es
/q emu. i mg : No such
fi le o r d i recto ry
A guest virtual machine cannot
be migrated because lib virt
cannot access the disk
image(s).
Section B.14, “Migration fails
with Unabl e to al l o w
access fo r d i sk path:
No such fi le o r
d i recto ry”
Erro r Descrip t io n of p ro b lem 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
128