similar to: domU compilation failure on x86_64

plain text document attachment (xx-paravirt-boot.patch) Boot up code modifications to get paravirt ops running. Signed-off-by: Steven Rostedt srostedt@redhat.com Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com> Index: clean-start/arch/x86_64/kernel/head.S =================================================================== --- clean-start.orig/arch/x86_64/kernel/head.S +++

plain text document attachment (xx-paravirt-boot.patch) Boot up code modifications to get paravirt ops running. Signed-off-by: Steven Rostedt srostedt@redhat.com Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com> Index: clean-start/arch/x86_64/kernel/head.S =================================================================== --- clean-start.orig/arch/x86_64/kernel/head.S +++

Hi! I write this config line: kernel /boot/i386/vmlinuz ro ramdisk=32768 root=/dev/ram0 init=/linuxrc but when I try to boot I got this mesasge: Could not find kernel image: /boot/i.386/ Same symptomes are with slash and backslash too. I think, the parses don't understand the directory separator characters and count as the part of filename. ps Sorry for my english -- Gabor HALASZ

Hi! I discovered a bug in $subject. Next line caused a compilation error: auth_request_log_debug(auth_request, "vpopmail", "lookup user=%s domain=%s", vpop_user, vpop_domain); I think, te correct version is: auth_request_log_debug(request, "vpopmail", "lookup user=%s domain=%s",

I have succeeded in getting two tinc1.0pre3 hosts to connect, but I can't ping one from the other. I can ping the local tap interfaces. tcpdump shows that icmp echo requests are received by the other host, but no replies are sent. The two hosts are North and South. It is the same pinging North to South and South to North. The hosts are configured as follows: South: Debian 2.2

With the only bit in CR0 permitted to be changed by PV guests being TS, optimize the handling towards that: Keep a cached value in a per-CPU variable, and issue HYPERVISOR_fpu_taskswitch hypercalls for updates in all but the unusual case should something in the system still try to modify another bit (the attempt of which would then be logged by the hypervisor). This removes the need to have the

Hello all, Here's a new version of the paravirt_ops x86_64 patch. With this message, I'm sending an incremental patch. The complete patches can be found , from now on, at http://et.redhat.com/~gcosta/paravirt_ops/ The main aim of this new update, is to fix a critical bug, namely, Rusty's name. However, I took the opportunity to write some new less important pieces of code,

Hello all, Here's a new version of the paravirt_ops x86_64 patch. With this message, I'm sending an incremental patch. The complete patches can be found , from now on, at http://et.redhat.com/~gcosta/paravirt_ops/ The main aim of this new update, is to fix a critical bug, namely, Rusty's name. However, I took the opportunity to write some new less important pieces of code,

Hi! I tried to install xen-3.0.2 with 2.6.16 kernel, and got the next message (3 times) before crashing: DOM0: (file=mm.c, line=1729), unknown domain ''65535'' The hardware: ga-k8nf-9-4:~# cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 47 model name : AMD Athlon(tm) 64 Processor 3000+ The xen changeset:

Hi! I created a dedicated driver domain on my opteron machine (xen-3.0.2-3, changeset: 9762:1e225598ce82, 2.6.16.28, Debian Sid), and I discovered an interesting segfault at the last step of reboot: when the kernel flush out the md devices (raid1) the kernel prints the stack dump and reboot immidietly. After rebooting, the state of first md deveice is clean, but the second md device is dirty

Hi! Can I use my 2nd vga card (and 2nd keyboard and mouse) in domU? I tried to hide the additional card from dom0 and exported into domU, but I got console messages from domU in xen console, not on the 2nd monitor. What can I do? How can I disable the console redirection from domU? Thanks -- Gabor HALASZ <halasz.g@freemail.hu> _______________________________________________ Xen-users

Hi! I tried to boot dos from an USB drive, but only got one dot and six unreadable character after a syslinux welcome message. With memdisk, I got only syslinux welcome and one dot. Whats wrong? Thanks -- Gabor HALASZ <halasz.g at freemail.hu>

I just tried to setup another domain on a server running 1 domain. When i try to start the domain it gives me an error Error: Device 0 (vif) could not be connected. Backend device not found. The entry in my xen config file for the disks is disk = [''phy:/dev/xen001/xen2-fun,sda1,w'',''phy:/dev/xen001/xen2-fun-swap,sda2,w''] Looking at /var/log/xend.log, i found

Hi, I tried running xen3 (binary install) from xensource.com on an OpenSUSE box and it doesn´t work: I can not create any domUs: "Error: Device 0 (vif) could not be connected. Hotplug scripts not working." Same problems with a clone of xen-unstable from today (8439) The xen rpms shipped from suse aren´t that stable too (7608-2) Questions Has anybody running a stable xen3 box on

Kernel 2.6.12 contains a bad bug. So i need kernel 2.6.12.6. If i build Xen3 with make world it will still download/compile the old kernel 2.6.12. How can i build Xen3 with a newer kernel? Stephan <http://www.buchmesse.de/imperia/md/images/logos/fbm/2003/Logo100s150px.gif> 19. - 23. Oktober 2005 Halle 4.0 / Stand F1305 Reservieren Sie sich bereits heute über unsere Homepage

hello! i think i have an very common problem. i want to run a distro based on a 2.4 kernel (Scientific Linux 3/Centos 3/RHEL 3) in xen3 as domu. the dom0 is a 2.6 based and works fine. so i think the way to go is to "simply" use an 2.6 kernel. but now i see there are several things which don''t work for example module-init-tools are missing and i expect problems with the glibc.

Hello, we have the problem: We run 7 blades with a xen 3.0.1tha3 configuration (with the patches for debian from debianbase.de), which a is xenisied 2.6.12.6-kernel. Everything runs fine until we start producing heavy load on the network (e.g. multiple clients access our maxdb database), the dom0 and the domU network becomes unreachable (i.e. only every 100th-200th ping gets through).

Hi, I''ve been having troubles with bridge networking in Xen3. RHEL4 is running in dom0 and Debian sarge in domU. Both domains get their IPs from an external DHCP server. dom0 starts up OK and gets its IP from the server. (all networking services work fine; in and out) domU starts up OK and sometimes gets its IP while sometimes fails to get the IP. In any case, after logging into domU

idt_table is meaningless in paravirtualized guests, but there were still a couple of references to it left. The easiest way to locate them was to get rid of the variable altogether. It depends on the previously submitted patch cleaning up head.S (which, among other things, eliminated early_idt_handler). It also fixes the non-Xen cpu_gdt_init() handling (for easier later merging). Jan

I have built a dom 0 using a Gentoo Linux kernel. All is up and running with no errors. I downloaded a Centos 4.4 image from the web and when I rum xm I get an error 22. Does anyone know what I am doing wrong and/or where I can find more documentation on running unmodified VMX guest domains. The Xen 3.0 Users Manual is out of date. Here is the control file: sun temp # cat