similar to: linux-2.6-xen.hg: Selecting "Xen-compatible" subarchitecture makes most of the drivers unselectable

Hi! I`m trying to install xen 3.0.2 on my Debian system! But, the "make ARCH=xen menuconfig" don`t work! debian:/home/peso/xen-3.0.2/xen-3.0.2/linux-2.6.16-xen0# make ARCH=xen menuconfig Makefile:439: /home/peso/xen-3.0.2/xen-3.0.2/linux-2.6.16-xen0/arch/xen/Makefile: No such file or directory make: *** No rule to make target `/home/peso/xen-3.0.2/xen-3.0.2/linux-

No need to get into the submenu to disable all VIRTIO-related config entries. This makes it easier to disable all VIRTIO config options without entering the submenu. It will also enable one to see that en/dis-abled state from the outside menu. This is only intended to change menuconfig UI, not change the config dependencies. v2: add "default y" to avoid breaking existing configs

No need to get into the submenu to disable all VIRTIO-related config entries. This makes it easier to disable all VIRTIO config options without entering the submenu. It will also enable one to see that en/dis-abled state from the outside menu. This is only intended to change menuconfig UI, not change the config dependencies. v2: add "default y" to avoid breaking existing configs

No need to get into the submenu to disable all VIRTIO-related config entries. This makes it easier to disable all VIRTIO config options without entering the submenu. It will also enable one to see that en/dis-abled state from the outside menu. This is only intended to change menuconfig UI, not change the config dependencies. Signed-off-by: Vincent Legoll <vincent.legoll at gmail.com> ---

No need to get into the submenu to disable all VIRTIO-related config entries. This makes it easier to disable all VIRTIO config options without entering the submenu. It will also enable one to see that en/dis-abled state from the outside menu. This is only intended to change menuconfig UI, not change the config dependencies. Signed-off-by: Vincent Legoll <vincent.legoll at gmail.com> ---

Michael Ellerman <mpe at ellerman.id.au> writes: > Vincent Legoll <vincent.legoll at gmail.com> writes: > >> Hello, >> >> thanks for the help, and sorry for the poor patch, >> >> On Thu, Dec 21, 2017 at 11:53 AM, Michael Ellerman <mpe at ellerman.id.au> wrote: >>> This breaks all existing .configs *and* defconfigs that use VIRTIO.

Hi, I am writing a small doc for people new to Xen. to be able to compile Xen from sources on Ubuntu. Please suggest some improvements for this how to or mistakes that you can point out. There is a technique of virtualization known as Xen and a hypervisor known as Xen. Like you have Firefox,Open Office,VLC and other softwares on your computer similary there is a software known as Xen.

Is there any way (short of not patching it into the kernel) to turn KDB off on a given machine? There are some machines I do not want dropping into kdb when/if it oopses. Thanx, b.

No need to get into the submenu to disable all VIRTIO-related config entries. This makes it easier to disable all VIRTIO config options without entering the submenu. It will also enable one to see that en/dis-abled state from the outside menu. This is only intended to change menuconfig UI, not change the config dependencies. v2: Added "default y" to avoid breaking existing configs v3:

Hi there, I've done an apt-get source linux-image-2.6.18-4-xen-686 and would very much like to build a package with NFS root enabled. From what I've read, I need to run split-config, which I got from SVN (it doesn't seem to exist anywhere else) I've fooled around with split-config to produce a config to my spec but this doesn't seem to actually work. Usage:

I thought I read somewhere that you no longer have to do a special make command for the 2.6 kernel. Is this true, or should I still make linux26? I'm having problems getting anything zaptel to load properly. ---- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi all, where I can set acl support in the menuconfig? "make O=/home/name/build/kernel menuconfig" Thanks! Regards, Roland

Hi list, I am starting a academic security related project and I was wondering if there is any documentation on compiling xen/dom0 with a recent kernel? I''ve seen a few good intentioned threads, but no real documentation so far. Any helpful pointers will be greatly appreciated! Thanks in advance, - SDG P.S: First mail, not sure if I should post it here...let me know if I am on the

HI, I am trying to install xen through yum. Here is what I did. [root@localhost Kishore]# yum install kernel-xen xen Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package kernel.x86_64 0:2.6.31.9-174.fc12 set to be installed --> Processing Dependency: kernel-firmware >= 2.6.31.9-174.fc12 for package: kernel-2.6.31.9-174.fc12.x86_64

(Unless there are complaints, I'll push this as part of the lguest patches for 2.6.24, since there are lguest config changes there too). Andi points out that PARAVIRT is an option best selected when needed. We introduce PARAVIRT_GUEST for the menu itself, and select PARAVIRT if the user turns on anything which needs it. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> ---

(Unless there are complaints, I'll push this as part of the lguest patches for 2.6.24, since there are lguest config changes there too). Andi points out that PARAVIRT is an option best selected when needed. We introduce PARAVIRT_GUEST for the menu itself, and select PARAVIRT if the user turns on anything which needs it. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> ---

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

I installed Xen using the binary release on debian sarge and got it to boot no problem but when I check if dma is enabled with ''hdparm /dev/hda'' it''s not. I can''t enable it either with ''hdparm -d1 /dev/hda''. Says operation not permited. Using my debian default kernel dma works just fine. How can I enable dma with the Xen Kernel? Thanks!