Changes

Jump to: navigation, search

Solving Common Xen Problems

1,026 bytes added, 18:50, 29 May 2016
m
Text replacement - "<google>BUY_XEN_ESSENTIALS</google>" to "<htmlet>xen</htmlet>"
<table border="0" cellspacing="0" width="100%">
<tr>
<td width="20%">[[Migrating Xen domainU Guests Between Host Systems|Previous]]<td align="center">[[Xen Virtualization Essentials|Table of Contents]]<td width="20%" align="right"></td>
<tr>
<td width="20%">Migrating Xen domainU Guests Between Host Systems<td align="center"><td width="20%" align="right"></td>
</table>
<hr>
 
 
<htmlet>xen</htmlet>
 
 
A number of different problems can occur during the boot process of the Xen guest system. Solutions to common Xen problems are as follows:
* [[Xen guest domainU migration fails with Error: can't connect: No route to host message]]
* [[Windows Server 2008 Xen HVM installation fails - Firmware (BIOS) is not ACPI compatible]]
* [[Xen mouse pointer appears in the wrong position in VNC console]]
* [[Device not visible in Xen domainU guest when using xm block-attach command to add a disk or CD-ROM/DVD drive]]
* [[Xen domainU Guest has an IP address on 192.168.122 subnet instead of the subnet to which the domain0 host belongs]]
* [[Ubuntu DomainU Fails to boot with "Error: Device 0 (vif) could not be connected. Could not find bridge, and none was specified".]]
* [[Ubuntu Xen Guest (DomU) Hangs after EXT3-fs: mounted filesystem with ordered data mode message]]
* [[Ubuntu Xen System Boot Hangs After Setting System Clock Message]]

Navigation menu