similar to: Dom0 boot failure with latest xen-unstable

(The list appears to have eaten my previous attempt to send this. Apologies if you receive multiple copies.) The attached patches allow you to use paravirtualised network and block interfaces from fully virtualised domains, based on Intel''s patches from a few months ago. These are significantly faster than the equivalent ioemu devices, sometimes by more than an order of magnitude.

Hi I have a couple of questions: 1. How do I exist from a domU console back to dom0 console (after issuing xm console [domU])? 2. How do I setup a dom0/domU in order to get a tty login? TIA Paolo _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, everyone, I installed the Xen3.1.0 based on Fedora8 and enter the Dom0 successfully. The kernel of dom0 is linux-2.6.18-xen0. But the Xorg could not start in the Dom0. When I use the "startx" command to start the X server, the error information is following: ......... (==) Using config file: "etc/X11/xorg.conf" (II) Module already built-in (II) Module already built-in

Hi, I have successfully installed Xen unstable binary on SuSE 9.3. I am trying to do a source install and I got the following error. Will be glad for any help or guidance. In file included from include/asm-xen/asm/processor.h:18, from include/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/spinlock.h:12, from include/linux/capability.h:45, from

Hi. I am trying to make initrd for xen0 but I am not successful. I receive error: #yaird error: Could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.16.33-xen0 evdev (fatal). If I do that just for xen kernel (not xen0) it goes without any problem. I guest I have to use initrd for xen0 otherwise it does not want to boot. Similarly, xen kernel without initrd will not

Hello guys Does anyone use lvm2 backends for domU storages ? I do and I wanted to use lvm''s snapshot feature to make backups of domUs in background but I got the following problem. When I create a snapshot LV and copy data from it to backup storage it works perfect. Then I do umount and then lvremove. lvremove asks me if I really want to remove the volume and then just hangs forever.

I''m experimenting with xen + iscsi, and I founded that under heavy stress domU''s can crash entire system, I''ve reproduced this many many times. My system is like this Software: - iSCSI Enterprise Target v0.4.13 - RedHat AS4 update 4 64bit + Xen 3.0.3-0 Kernel 2.6.16.29 + Open iSCSI v2.0.730 (Initiator) - Bonnie++ v1.03a VM: - Debian 3.1r3 + Open iSCSI v2.0.730

Hi, I just added 32GB memory in my system and wanted Xen to see that memory, so enabled PAE in xen0 and XenU. I did a make menuconfig in xen0 and xenU, then did a make in xen-unstable and a make install. Whilebooting this kernel, I get the above error PAE mode mismatch. I looked under xen/include/asm-x86/processor.h has #define X86_CR4_PAE defined and so does cpufeature.h have this defined.

Hello, I have a big startproblem with the dom0 kernel. I use the latest stable xen with the 2.6.10 kernel. menu.lst: --- title Xen 2.05 / XenLinux 2.6.10 kernel /boot/xen.gz dom0_mem=512M noreboot module /boot/vmlinuz-2.6.10-xen0 root=/dev/sda1 ro console=tty0 --- Starterror: --- (XEN) Initial guest OS requires too much space (XEN) (8MB is greater than 0MB limit) --- System: I use an fresh

Hi, I''m a newbie to Xen and I need some help. I saw user ''datto'' had a similar problem but changed to FC4 to resolve it. I''m currently running FC3 and Xen2.0.7. I did the usual ''make install'' and I can boot into Xen dom0. However, my network card is not working. The driver is found in the linux-2.6.11.12-xen0 tree but not selected. I

Hi, I just updated to xen 3.0.4 and linux-2.6.16.49-xen0 (gentoo linux). After reboot xen starts up just fine but instead of starting the dom0 kernel the machine just reboots. The last messages I see on my screen are: (XEN) Scrubbing Free RAM: .......done. (XEN) Xen trace buffers: disabled (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and

Cd /xen/xen-unstable/linux/2.6.12-xen0/ Then: make ARCH=xen xconfig Thomas Diederich ************************************************** * Boehringer Ingelheim Pharma GmbH & Co.KG * A Informationsverarbeitung / Diplomant Systemtechnik * * Mail: diederit@ing.boehringer-Ingelheim.com * Phone: +49 (0)6132/77-98151 -----Ursprüngliche Nachricht----- Von:

Hi Keir, This patch updates the ia64 buildconfigs, enabling pcifront for all kernels and pciback for -xen and -xen0. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 4833dc75ce4d buildconfigs/linux-defconfig_xen0_ia64 --- a/buildconfigs/linux-defconfig_xen0_ia64 Fri Jul 28 17:52:57 2006 +0100 +++ b/buildconfigs/linux-defconfig_xen0_ia64 Fri Jul 28

On Thu, 2005-06-16 at 06:17 +0100, Keir Fraser wrote: > > I suggested that we simply mmap /dev/kmem for the xenstored to access > > the domain0 page for the moment. That doesn''t work: we''ll do something > > else. > > Just use xc_map_foreign_range(), as you would for mapping any other > domain''s xenstore page. So here''s my patch

Hi there, I''ve just built xen & dom0 kernel from gentoo ebuilds (bugs.gentoo.org), but my dom0 kernel crashes during boot. Any help is appreciated. Console log, grub.conf and .config are included, machine is celeron/466, 128MB of RAM. Console log: Linux version 2.6.9-xen0 (root@zirafa) (gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)) #2 Sun Nov 14

I just cloned a xeno-unstable.bk tree ( < 30 minutes ago). autofs.ko didn''t get generated for some reason, so I did a separate make modules pass. Then I did a make modules_install from which I got a heap of unknown symbols warnings. I thought this might be fallout from the switch to 2.6.11. -Kip WARNING: /lib/modules/2.6.11-xen0/kernel/fs/fat/fat.ko needs unknown symbol _spi

I''ve been working on a xen-unstable tree from mid-April. I wanted to upgrade to the latest version, so here is what I did: - Clone a fresh copy of xeno-unstable.bk (1.1507) - "make world" - Change the .config of linux-2.6.11-xen0 to include my ethernet card (CONFIG_FORCEDETH=y) - Add localversion files to linux-2.6.11-xen0 and linux-2.6.11-xenU - rm -rf the existing dist

I''m struggling to get Xen to boot on a FC4 Opteron box. I''ve included the tail of the boot log below [1]. I suspect that the problems relates to the software RAID 1 root and boot partitions, and how it relates to the initrd image. The RAID volumes fail to mount. I compiled the Xen snapshot from the 23rd September, and the only change I''ve made is to enable the

Dear list, I''m trying to get Xen working on a P3-600E with 320 MB RAM. (256+64) It has suse linux 9.1 installed on it, and I tried to get xen running with both the binary download from the xen pages and the suse xen packages mentioned on this list some days ago. Both ''install packages/kernels'' lead to the same error: (XEN) Not enough memory for DOM0 memory

Hi, I''ve installed xen-2.0.5 from source on gentoo, but the xen dom0 kernel doesn''t find the root device: ############################# snip ###################################### Kernel panic: VFS: Unable to mount root fs on unknown-block (3,3) ############################# snap ###################################### grub.conf: ############################# snip