similar to: paravirt_ops xen booting

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__

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

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

Hi, I am trying to install Xen/Xenolinux v1.1 on my workstation which has 2 SCSI disks. The first disk has WinXP installed, and the second disk has Redhat 8.0. I copied the images into /boot and modified grub.conf accordingly: title Xen / XenoLinux 2.4.22 root (hd1,0) kernel /xen.gz dom0_mem=131072 ser_baud=115200 noht noreboot module /xenolinux.gz root=/dev/sdb2 ro

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

Mails to chrisw at sous-sol.org are not deliverable since several months. Drop him as PARAVIRT_OPS maintainer. Signed-off-by: Juergen Gross <jgross at suse.com> --- MAINTAINERS | 1 - 1 file changed, 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index d85c08956875..af0cb69f6a3e 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -10179,7 +10179,6 @@ F: Documentation/parport*.txt

Mails to chrisw at sous-sol.org are not deliverable since several months. Drop him as PARAVIRT_OPS maintainer. Signed-off-by: Juergen Gross <jgross at suse.com> --- MAINTAINERS | 1 - 1 file changed, 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index d85c08956875..af0cb69f6a3e 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -10179,7 +10179,6 @@ F: Documentation/parport*.txt

Hi, This is my setting: I have a Logical Volume /dev/VG/suse with Suse installed. I have added it to the grub and I can boot it and works perfectly fine. Now I am running /dev/VG/root which is running Xen0. I have created a Xen config file to boot a VM with disk: /dev/VG/suse. In other words I want to boot /dev/VG/suse as a virtual machine. Below is what I am getting at boot time :

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

Hi list, I am running a virtualized server. Dom0 uses Xen 3.2.1 with Debian Etch and a custom kernel 2.6.21 created by my webhosting company. I install my domU using debootstrap for a Debian Etch with 2.6.18-6-xen-amd64 kernel. Everything works well except the fact that once the VM is started I cannot "xm console" into it. It only works while it is booting and while it is shutting

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 all, I have a question on /etc/inittab for DomU booted with xencons parameter. I saw the following error messages when I appended xencons=ttyS to DomU boot option. INIT: Id "1" respawning too fast: disabled for 5 minutes INIT: Id "2" respawning too fast: disabled for 5 minutes INIT: Id "4" respawning too fast: disabled for 5 minutes INIT: Id

Hi, This patch series is an update of my previous paravirt_ops patches. They are loosely based on Ingo's original paravirt_ops implementation for KVM. Some of the changes since the last series include: 1) Switch to using CPUID 0x40000000 instead of using MSR writes to discover shared memory area 2) Attempt to deal with SMP guests 3) Support for generic CR read caching 4) Support for

Hi, This patch series is an update of my previous paravirt_ops patches. They are loosely based on Ingo's original paravirt_ops implementation for KVM. Some of the changes since the last series include: 1) Switch to using CPUID 0x40000000 instead of using MSR writes to discover shared memory area 2) Attempt to deal with SMP guests 3) Support for generic CR read caching 4) Support for

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 Andi, This series of patches updates paravirt_ops in various ways. Some of the changes are plain cleanups and improvements, and some add some interfaces necessary for Xen. The brief overview: add-MAINTAINERS.patch - obvious remove-CONFIG_DEBUG_PARAVIRT.patch - no longer needed paravirt-nop.patch - mark nop operations consistently paravirt-pte-accessors.patch - operations to pack/unpack

Hi Andi, This series of patches updates paravirt_ops in various ways. Some of the changes are plain cleanups and improvements, and some add some interfaces necessary for Xen. The brief overview: add-MAINTAINERS.patch - obvious remove-CONFIG_DEBUG_PARAVIRT.patch - no longer needed paravirt-nop.patch - mark nop operations consistently paravirt-pte-accessors.patch - operations to pack/unpack

Hi Andi, Here's a repost of the paravirt_ops update series I posted the other day. Since then, I found a few potential bugs with patching clobbering, cleaned up and documented paravirt.h and the patching machinery. Overview: add-MAINTAINERS.patch obvious remove-CONFIG_DEBUG_PARAVIRT.patch No longer meaningful or needed. paravirt-nop.patch Clean up nop paravirt_ops functions, mainly to

Hi Andi, Here's a repost of the paravirt_ops update series I posted the other day. Since then, I found a few potential bugs with patching clobbering, cleaned up and documented paravirt.h and the patching machinery. Overview: add-MAINTAINERS.patch obvious remove-CONFIG_DEBUG_PARAVIRT.patch No longer meaningful or needed. paravirt-nop.patch Clean up nop paravirt_ops functions, mainly to