similar to: Problem to boot Xenolinux.

The Xen boot option ''ser_baud=<baud>'' has been removed from the unstable tree. If you were still using this obsolete option then the effect is that you will get no serial output when you boot Xen, which may lead you to believe that there is a more serious problem. To fix this you must move to the new boot option: ''com1=<baud>,8n1'' -- Keir

Maybe this question is a little stupid, but please help me. I am a newbie to Xen. When I tried to create a new domain "domain 1", I followed the Yan-Ching CHU''s guide on :installing quick file systems for new domains in Xen 1.2". But when I do "xc_dom_create.py -Dvmid=1", Xen seems to start to boot with some normal bootup information, but right after several

resend to larger group: which one is the right one? I''m going thru some merge hell and a need some newer PPC code from kernel.org. is it: http://xenbits.xensource.com/linux-2.6-xen.hg (worked on) --or-- http://xenbits.xensource.com/ext/linux-2.6-merge.hg (six weeks of nothing) there is also linux-2.6.rc-xen.hg, linux-2.6.tip-xen.hg, linux-2.6- patchqueue.hg the PPC team

Hi all I am in the process of upgrading my XEN servers from 2.4 to 2.6 kernels as I am having better results on 2.6. However one machine (the big daddy) refuses to boot a 2.6.9 xenolinux kernel. It''s an IBM eSeries xServer x205. I have selected what i think are the appropriate options in menuconfig but it refuses to boot into dom0. By refuse I mean it initialises the hypervisor,

Hey everyone, Thanks for the quick help resonses once again, We got some mail saying that RAM disks were not the way to go. So we re-installed, made several partitions to use, and rebuilt xen. However, we''re still having trouble mounting partitions when xeno-linux boots. We give a physical grant of one of our newly made paritions (/dev/hda14 in particular) to the domain. But when

The system is Mandrake-9.1 Linux wih gcc-3.2.2. I am trying to compile xenolinux-2.4.24 (with vanilla sources from ftp.kernel.org for linux-2.4.24). The steps of mkbuildtree ARCH=xeno make menuconfig ARCH=xeno make dep produce no errors, but ARCH=xeno make bzImage results in following error messages. Any pointers will be appreciated. -ishwar --- gcc -D__KERNEL__

Hello, I''m trying to write a module to play with hypercall. So I wrote the following module: -------------------------xvifgetinfo.c---------------- /* * xvifgetinfo.c * * The routines in this file are used to get information about virtual * network interface provide by Xen. * */ #include <linux/module.h> #include <linux/init.h> #include <linux/kernel.h>

I know I have asked this before, but I am having trouble understanding the role of each component in the new 1.3 world: In 1.3 networking if Xen has no devices, and domain 0 owns and operates the NIC - does Xen have any role at all in networking for the guest OS''s? Which network device driver will a guest OS use? Do all the vnetif rules defined in Domain 0 now get interpreted by

Has anyone got Xen working with say, SELinux? Or vserver? Wesley Parish -- Clinesterton Beademung - in all of love. Mau e ki, "He aha te mea nui?" You ask, "What is the most important thing?" Maku e ki, "He tangata, he tangata, he tangata." I reply, "It is people, it is people, it is people." ------------------------------------------------------- This

Hi, I have used lmbench to test the performance of Xenolinux (HVM) CPU: Intel (R) Core (TM)2 T7400@2.16GHz Memory size: 1GB NIC: Intel PCIe Gigabit LAN chip HD: Samsung 80GB/7200rpm/8M Dom0: 2.6.19-1.2911.6.5.fc6xen DomU: 2.6.20-1.2944.fc6 The context switch time seems saturated along with increasement of processes? e.g. size of processes 64kB N=number of process t=context switch time when

Hi all, I am running the current xen-unstable and had the following error message when trying to create domain1. # ./xenctl script -f/etc/xen-mynewdom Domain defaults: name XenoLinux size 98304 vifs 1 domainImage /boot/xenolinux.gz domainInitRD null rootDevice /dev/hda5 rootArgs rw usrDevice null NWIP

Hi all, I have another problem with starting domainU (xenolinux). I took me pretty much quite some time and i can not figure out why starting a new domain is failing. I will really appreciate if somebody can help me with this error. The error I get when booting xen-domainU is: /======================= Red Hat nash version 4.1.18 starting Mounted /proc filesystem Mounting sysfs Creating /dev

I am trying to write a script to handle setup of domains using virtual block devices for their root FS and have been unable to get the virtual devices to work with any sort of consistency. This is using xen-1.1.bk on Redhat 7.3 (I had to rebuild all the tool binaries to run on 7.3). Anyway, I would first like to make sure I am using the vd/vbd stuff correctly. Here is an example of the problem I

Is there a particular reason for doing this unconditionally on both 32- and 64-bits in xenolinux? It would seem to me that this feature should be disabled at most in unprivileged kernels... Thanks, Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

hi, i''ve submitted a small patch to xen-unstable that makes the ''/dev/xx'' -> devicenumber lookup stuff work on my machine.. basically i''m using os.stat instead of os.popen() hacks. this is my first bitkeeper checkin ever, so please verify i did this correctly. thanks, paul ------------------------------------------------------- This SF.net email is

Just a note to let you know we've got domU booting with paravirt_ops XenoLinux. There's still some minor cleanups to do: - soft watchdog firing - inconsistent device probing - console on tty1 Then onto smp support, and removing the rest of the limitations of the current patchset. thanks, -chris

Hi everyone, I''m running Xen on an SMP machine. Couple of things: a) is dom0 pinned to a particular CPU? if so which? can I control the choice? b) with the 2.6.10 Xenolinux kernel, cat /proc/cpuinfo shows only a single CPU on my SMP machine. Is this a known problem/behavior? c) if I understand correctly, the BVT scheduler parameters are CPU specific -- they don''t aggregate

Hello, We''re curious about page fault handling in Xen-devel. In particular, during kernel boot-up, the kernel tests if the CPU "honours the WP bit". This causes a page fault with error code 3 (expected behavior). Does Xen still make a copy of the execution stack frame on the guest OS stack, as specified in the original "Xen and the Art of Virtualization" paper?

Just a note to let you know we've got domU booting with paravirt_ops XenoLinux. There's still some minor cleanups to do: - soft watchdog firing - inconsistent device probing - console on tty1 Then onto smp support, and removing the rest of the limitations of the current patchset. thanks, -chris

This patch uses the standard generic header for the definition of machine_emergency_restart() and reverses the call path for XenoLinux. Signed-off-by: Jimi Xenidis <jimix@watson.ibm.com> --- diff -r 7680b29c03a6 drivers/xen/core/reboot.c --- a/drivers/xen/core/reboot.c Sat Aug 05 11:33:24 2006 -0400 +++ b/drivers/xen/core/reboot.c Mon Aug 07 09:50:33 2006 -0400 @@ -9,6 +9,7 @@ #include