similar to: Bug#795330: Suggests noapic but doesn't support it

Control: tag -1 upstream Jan/Andy & David, Is there anything we can improve here on either the Xen or kernel side do you think? On Thu, 2015-08-13 at 00:59 +0200, Guido G?nther wrote: > Package: xen-hypervisor-4.5-amd64 > Severity: normal > > Hi, > when running xen inside of kvm the hypervisor fails to set up the proper > IRQ routing and suggests to use noapic. FTR, it

On Fri, 2015-09-04 at 15:04 +0100, David Vrabel wrote: > On 04/09/15 14:38, Ian Campbell wrote: > > Control: tag -1 upstream > > > > Jan/Andy & David, > > > > Is there anything we can improve here on either the Xen or kernel side > > do > > you think? > > > > On Thu, 2015-08-13 at 00:59 +0200, Guido G?nther wrote: > > >

On 04/09/15 15:13, Ian Campbell wrote: > On Fri, 2015-09-04 at 15:04 +0100, David Vrabel wrote: >> On 04/09/15 14:38, Ian Campbell wrote: >>> Control: tag -1 upstream >>> >>> Jan/Andy & David, >>> >>> Is there anything we can improve here on either the Xen or kernel side >>> do >>> you think? >>> >>> On

Adding apic_verbosity=debug gives me that (hope nothing miss-typed as I have no serial console on this box). I found a lot of suggested workarounds: - noapic as suggested in output gives an noapic isn''t support - acpi_skip_timer_override has no effect at all Thx, Florian (XEN) Initing memory sharing. (XEN) AMD-Vi: IOMMU not found! (XEN) I/O virtualisation disabled (XEN) Getting

Adding apic_verbosity=debug gives me that (hope nothing miss-typed as I have no serial console on this box). I found a lot of suggested workarounds: - noapic as suggested in output gives an noapic isn''t support - acpi_skip_timer_override has no effect at all Thx, Florian (XEN) Initing memory sharing. (XEN) AMD-Vi: IOMMU not found! (XEN) I/O virtualisation disabled (XEN) Getting

I just installed CentOS 4.6 (because I had 4.6 media handy) on a new system, which has a SuperMicro PDSMi mobo with an E4600 CPU. I then did yum update to get to 4.7, although I don't think that's relevant to my query. I wondered why "shutdown -h" would not power down the system. I then also discovered that the soft power button did not initiate a switch to runlevel 0 to do a

If this has already been done, please forgive me. However, if not, I''d like to submit this as a mechanism for generating a bootable grub2 stanza for hypervisors. As the /etc/grub.d/* files rely on defaults in /etc/default/grub, I added the following Xen specific variable: GRUB_CMDLINE_XEN_DEFAULT="console=com1 115200,8n1 dom0_mem=512M dom0_max_vcpus=1 dom0_vcpus_pin=true

[Please send all questions and replies to the mailing list] On Mon, Jun 10, 2013 at 09:34:09PM -0400, Preetam Jinka wrote: > Hi Richard, > > I wanted to know how to set LIBGUESTFS_APPEND="noapic" through > /etc/libguestfs-tools.conf > but I'm not sure what the format of the file should be. > > Could you give me the exact line I should add which will work? >

--- Ryan Lane <ryanlane@gmail.com> wrote: > On Fri, 11 Mar 2005 07:21:39 -0800 (PST), Steven > Vishoot > <sir_funzone@yahoo.com> wrote: > > ok now i am frustrated. this is the third day in a > row > > that my server has crashed running centos4, i can > not > > ping or access the console but the hardware is > still > > running. it does not leave

I had been running CentOS 5 happily on my Sun Fire X4200 M2 systems, then I upgraded the BIOS and iLOM firmware. Now I'm running into what seems to be a fairly common problem with newer motherboards. I cannot boot unless I use the 'noapic' kernel option. If I try to boot the kernel normally, I get the error: "MP-BIOS bug: 8254 timer not connected to IO-APIC" I can

I am looking at using grubby. My command is: grubby --grub --title "CentOS (2.6.32.60)" --add-kernel=/boot/vmlinuz-2.6.32.60 --initrd=/boot/initrd-2.6.32.60.img --args="ro root=LABEL=/ noapic" --make-default my etc/grub.conf file after running the command is: title CentOS (2.6.32.60) kernel /boot/vmlinuz-2.6.32.60 ro root=LABEL=/ rhgb quiet noapic initrd

Hi all, I just upgraded my Debian/Etch with Xen3.3 machine to Debian/Squeeze Xen4.0 and now have problems with starting the Dom0 kernel. I always get the error message: Kernel panic not syncing: the kernel parameter noapic is incompatible with xen. My grub.cfg is: menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386'' --cl$ insmod part_msdos

>Thank you! It worked and I finally got a working kernel. Here is the kernel boot log: Sound great ! Though I ended with error from log below. Had no chance to fix it yet: ? CPU: AMD QEMU Virtual CPU version 2.5+ (family: 0x6, model: 0x6, stepping: 0x3) Performance Events: PMU not available due to virtualization, using software events only. ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1

The following error on a SMP x86_64 Centos 4.3 kernel 2.6.9-34 ELsmp appears at boot. and causes things to compute faster. Example, a wait(5) should wait for 5 seconds....it waits for 3 or 2. This was an open bug for that kernel. Has it been patched in the more recent kernel for Centos 2.6.9-34.0.1 ? dmseg output: Freeing unused kernel memory: 164k freed Losing some ticks... checking if CPU

While I wait for the Xen 3.0 Test CD to download, has anyone has luck using an Asus M2N32-SLI Deluxe motherboard (NVIDIA nForce 590 SLI MCP chipset)? The CPU is an AMD Athlon64 X2 3800+ AM2 w/ 2GB DDR2 533. The motherboard mostly works under Gentoo using kernel 2.6.18 with the "noapic" kernel boot option in my grub.conf file. The only major issue with the Gentoo kernel

I hope the CentOS people don't mind me cross-posting for their input. I've just done a clean, text-mode minimal WBEL4 install on an IBM Netfinity 4500, essentially the same hardware as an xSeries 340. The install went fine but now the box will boot, run through the initrd init sequence, perform its switchroot then hang here... SELinux: Initializing. SELinux: Starting in permissive mode

Summary: Changeset 10173 - 64bit UP and SMP guests boot cleanly - 32bit UP guests boot clean and 32bit SMP guests still fail to boot (see failure.7) - 32bit UP guests lockup under load with "ata1: command 0x25 timeout" (see failure.4) - 64bit SMP 2 CPU guests lockup under load with "ata1: command 0x25 timeout" (see failure.2) - 32bit UP guest crashed on user load test

> Like I just mentioned in a different thread, I need to use > the ''noapic'' > options on both the PowerEdge models I''ve tried.. I''ll try to > build up a Xen vs. non-Xen kernel tomorrow or Tuesday and > grab a diff for you. Which PE models are they? We have quite a few different Dell PowerEdge models running 24x7 in the test lab, and

Hello, We have a number of systems running KM400 chipsets from VIA (Socket A/462). Two different models have produced the same results -- DFI KM400-MLV and MSI KM4M-V. When a /sbin/reboot or /sbin/shutdown -r now is issued, the system does everything you would expect from a reboot, but when it gets to Rebooting System, it hangs and requires a power cycle. The logs do not indicate anything

Got some solutions myself. LAG is caused by : NETDEV WATCHDOG eth0 timeout this is caused bacause of problems with rtl8139 network card in kernel 2.6.x Solutions : 1.add in lilo.conf : append="noapic" 2.turn apic off in bios 3.if u have 2 rtl8139 cards, then exchange one with some other card type (chipset) btw. all above was found in various polish forums, but none has worked for