search for: overnetdata

I am getting a series of IOAPIC errors in xl dmesg on a Dell OptiPlex GX100 machine (bought in 2000). I also get an error from traps.c which is very similar to the one in the ''Getting mm.c errors from xl dmesg on certain hardware'' thread. This happens during system startup with no DomUs running. I have attached the xl dmesg log. _______________________________________________

I''m having problems with my Dom0 kernel command lines being truncated, and I want to increase the command line size. They currently default to a maximum size of 256 bytes and I want to increase that to 1024 bytes. I changed the #defined variable COMMAND_LINE_SIZE in 3 places in the 2.6.18 kernel from 256 to 1024, but it had no effect. I''m aware that I''m actually

I understand that VGA passthrough isn''t officially supported on paravirtualized VMs, but it will work with certain video cards. Does anybody have any information about which video cards/chipsets are/are not supported for paravirtualization, what the criteria for being supported/unsupported is etc.? I''m also interested in understanding the technical problems to getting VGA

As far as I work out the version of the Dom0 linux kernel has to be 2.6.18. This is causing me a lot of problem, because the driver support in 2.6.18 is slowly falling behind, and I finding that more modern hardware isn''t supported by the 2.6.18 drivers. Is it possible to use a more recent version of the kernel for Dom0, or am I stuck with 2.6.18? Is there another way I can use more

I have a custom built system based on LFS 6.6 with xen 4.1.0 & linux 2.6.39 built from source. The system boots correctly on one system (after a problem with the USB disk has been worked around), however when I try to boot the same system on another machine the screen corrupts shortly after handover from the bootloader. This happens on 2 out of the 3 machines I have tried it on. I was

I''ve just had my first attempt at getting VGA passthrough to work, and it crashed the machine. I''m trying to understand whether this is a problem with my hardware, configuration or a software problem. I''m running Xen 4.1.2 with Linux 3.1.2 The CPU is an Intel Core i5-650 http://ark.intel.com/products/43546/Intel-Core-i5-650-Processor-%284M-Cache-3_20-GHz%29 The Video

I have a xen 4.1.1 with a 3.0.4 linux kernel running on a Supermicro Supermicro X8DTL-iF motherboard with 16GB of RAM. If I run the 3.0.4 kernel on the bare metal dmidecode works fine. If I run it under xen dmidecode fails to work. On other systems with different hardware but identical software dmidecode works correctly under xen. On this hardware with xen 3.4.1 & linux 2.6.18, dmidecode