Xen Errors
From OptionC
| Table of contents |
Error: Error creating domain: (12, ' Cannot allocate memory')
- Versions: 2.0
- Occurs when: trying to start domain
- Probable cause
- allocated memory for "dom0 + running domUs + domU that you are trying to start" exceeds physical memory
- Solution
- Reduce the amount of memory required for the new domU, or balloon down the memory of the running domUs
Error: Error creating domain: vbd: Segment not found: uname=file:/path/to/image.img
- Versions: 2.0
- Occurs when: trying to start domain
- Probable causes
- Path to image or image name incorrect
- For a file-backed VBD, no more available loopback devices
Error: Adding extent to vbd failed: device (vbd (uname phy:/dev/hdc) (dev hdc) (mode r)), error 8
- Versions: 2.0
- Occurs when: trying to start domain
- Probable cause
- Trying to mount a physical device that's currently not accessible (Example, a CD-drive that doesn't have a CD, or a USB device that's not inserted.)
- Solution
- Insert a CD (or the USB device) and try again
Error: Error creating domain: vbd: Segment phy:/dev/sda1 is in writable use
- Versions: 2.0
- Occurs when: trying to start domain
- Probable cause
- An attempt was made to mount a physical device (USB drive) inside a DomU when it's already mounted in the Dom0
- Solution
- Unmount the device in the Dom0 and try again
(XEN) (8MB is greater than 0MB limit)
- Versions: 2.0
- Occurs when: booting
- Detailed message
(XEN) Initial guest OS requires too much space (XEN) (8MB is greater than 0MB limit) ******************************************************** Could not set up DOM0 guest OS Aieee! CPU0 is toast... ******************************************************** Reboot in five seconds...
- Probably cause
- Not enough memory allocated to the dom0
- Solution
- Check the value of dom0_mem. On a "normal" system, "dom0_mem=65536" should be adequate. Try to specify the value in kilobytes although 3.0 understands "dom0_mem=64M", 2.0 does not
(XEN) (FATAL ERROR: Require at least one Multiboot module.)
- Versions: 2.0
- Occurs when: booting
- Probably cause
- No appropriate dom0 line in grub/menu.lst
- Solution
- Check and or add a line like the following in the Xen entry for grub/menu.lst (change to suit your setup
module /boot/vmlinuz-2.6.11-xen0 root=/dev/hda1 ro console=tty0
Kernel panic: VFS: Unable to mount root fs on unknown-block(2,0)
- Versions: 2.0
- Occurs when: booting dom0
- Detailed message
Root-NFS: No NFS server available, giving up. VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "sda9" or unknown-block(2,0) Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(2,0)
- Probable cause
- Support for root device not in kernel/modules
- Possible solutions
- Check dmesg output from a successful boot and check what drivers are used for your hard drive. If they aren't included in the version of the kernel you are using (configs usually live in /boot), you may need to compile your own.
- I'v resolved recently this problem using the default xen ( /usr/src/linux/arch/xen/configs/ ) configuration as base and rebuilding the Dom0 and DomU kernel. I hope to understand which was the bad option/s !
ADDED: installing under VMWare Workstation 5, the default drive type is SCSI, and the kernel doesn't support this. Just change to IDE and it should work.
Error 15: File not found
This is actually a grub error. The complete message looks something like this:
Booting command-list root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/xen-2.0.6.gz dom0_mem=65536 noreboot Error 15: File not found Press any key to continue...
- Versions: All
- Occurs when: booting
- Probably causes
- Typos in the grub menu list
- Bad root information
- Possible solutions
- If /boot is its own partition then it should be /xen-2.0.6.gz not /boot/xen-2.0.6.gz
Error: errors: transfer daemon (xfrd) error: 1
- Versions: 2.0
- Occurs when: trying to migrate a domain
- Probable causes
- Path to configuration, image or image name on the destination machine is incorrect
- Inconsistencies between file system images
- Possible solutions
- Check to see if the configuration and the associated files/paths exist on the destination machine. If they are NFS mounted, check the NFS mount is working.
