search for: xenning

Hey, It looks like one of the patches that went in Xen 4.1 blows up. This used to work over the weekend, so I can only surmise it is one the three patches. This is with a debug=y build (which has been working nicely for the last month or more). It looks like one of the patches that went in Xen 4.1 blows up. This used to work a day ago - that is c/s 23551 worked nicely. ----- Forwarded message

In hvm enviroment, acpi failed. why? centos5.1 =================================================== [root@hvm001 ~]# xm dmesg __ __ _____ _ ____ ___ ____ _ ____ \ \/ /___ _ __ |___ / / | |___ \ / _ \___ \ ___| | ___| \ // _ \ \047_ \ |_ \ | | __) |_| (_) |__) | / _ \ |___ \ / \ __/ | | | ___) || |_ / __/|__\__, / __/ | __/ |___) | /_/\_\___|_| |_| |____(_)_(_)_____| /_/_____(_)___|_|____/

I do not seem to be able to get any where with the power management functions. I have had a look at the xenpm Wiki page, but it hasn''t helped. Its probably something completely obvious, but I can''t see it. I running Xen 3.4.0 on Centos 5.3 x86_64 using the gitco RPMs on an Intel S5000PSL motherboard with 2 x Xeon 5410s. Dom0 is running the latest Centos 5.3 kernel. My xm

Hi, I need a help with tracking down following issue: When trying to boot Xen on a system with Ivy Bridge stepping C0 CPU, it is stuck on CPU initialization. I''ve added some tracing to apic writes/reads and traced it so far to sending INIT IPI. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) Setting warm reset code and vector. (XEN) apic_wrmsr (0x280,0x0)

Hi, I''ve not tried pv_ops for a long time but just got a new system (Supermicro X9DRL-iF) so decided to try 3.5.0 with the latest Xen 4.2-unstable, unfortunately the system crashes immediately after loading dom0: traps.c:486:d0 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000] I''ve tried loading both bzImage and vmlinuz (gzip compressed vmlinuz) with the same

Like others on this list I am trying to employ the VTD-NEO patches in Xen 3.2 unstable to assign the internal graphics device to Dom1/Vista. I have removed the Cirrus Logic emulated device from qemu and replaced the Cirrus Logic vgabios with the the actual vgabios from my GPU. However I am hitting an xen assert and was hoping someone might be able to point me in the right direction. Below

Hi Folks: I run into a problem when enabling Xen in next generation server platforms with Xen c/s is 21380. Xen reported "CPU Not responding" when booting up 32 CPUs( 2 sockets with 8 cores/16threads total). The log files belonging showed something wrong with APCI. So I added x2apic=0 in the xen grub line, but the symptom remained. However, Native RHEL5.5 can

I am having reports of PCI passthrough problems with SR-IOV, in particular it looks like we are hitting the warning at msi:635 and msi:648 in xen; see the following log: (XEN) [VT-D]iommu.c:1785: VT-d page table not sharing with EPT table xenbus dev backend/vbd/1/5696 error 6 opening device (XEN) PCI add Virtual Function 04:1a.0 (XEN) HVM1: HVM Loader (XEN) HVM1: Detected Xen v4.1.0.rc2.pre (XEN)

If anyone is still interested in this old thread, I have a rh7.3 image running under hvm. It''s a hack, but here''s what I did: Install rh7.3 in a vmware machine with vmware server. Booted off a live cd, ( I used a gentoo installer CD, but any live cd should work) Created a lvm volume on my Xen dom0 >From the liveCD, I use dd to copy the disk image to the lvm image (dd

Package: xen-hypervisor-3.4-amd64 Version: 3.4.2-2 Severity: critical Justification: breaks the whole system -- Dump: (XEN) Xen version 3.4 (Debian 3.4.2-29 (XEN) Command line: com1=115200,8n1 console=com1,vga loglvl=all guest_loglvl=all noreboot (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 1 seconds (XEN) EDID info not

Package: xen-hypervisor-3.4-amd64 Version: 3.4.2-2 Severity: critical Justification: breaks the whole system -- Dump: (XEN) Xen version 3.4 (Debian 3.4.2-29 (XEN) Command line: com1=115200,8n1 console=com1,vga loglvl=all guest_loglvl=all noreboot (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16

Hi, I have successfully installed Xen unstable binary on SuSE 9.3. I am trying to do a source install and I got the following error. Will be glad for any help or guidance. In file included from include/asm-xen/asm/processor.h:18, from include/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/spinlock.h:12, from include/linux/capability.h:45, from

Hi, An APIC error continues happening. __ __ _ _ _ _ _ _ \ \/ /___ _ __ | || | / | _ _ _ __ ___| |_ __ _| |__ | | ___ \ // _ \ ''_ \ | || |_ | |__| | | | ''_ \/ __| __/ _` | ''_ \| |/ _ \ / \ __/ | | | |__ _|| |__| |_| | | | \__ \ || (_| | |_) | | __/ /_/\_\___|_| |_| |_|(_)_| \__,_|_|

I''ve got a new system with Dual Quad Core Intel E5520 processors and Intel 82576 NICs built on the motherboard (this is a Supermicro Nehalem based blade). I''m running Xen 3.4.2, but I''ve also tried 3.4.1 and had the same problem. Dom0''s network works flawlessly, but the DomU systems all have network issues. Whenever they transmit large packets, it is as if

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

Xen 3.2.1-rc1 64 bit Dom0: 2.6.16.33 PAE DomU: 2.6.18.8 (from a pull a few weeks ago) If you need the symbols, there from the same Xen I linked to in my post from a few days ago... (XEN) mm.c:3498:d4 ptwr_emulate: could not get_page_from_l1e() (XEN) Unhandled page fault in domain 4 on VCPU 0 (ec=0003) (XEN) Pagetable walk from 00000000c08187f0: (XEN) L4[0x000] = 00000004dfa38027

I have an installation of 32bit SLES 10.1 on 2 servers in my lab that I just rebuilt. I applied the files from xen-3.1.0-install-x86_32.tgz and broke all the virtman functions. The errors I got indicate some missing python classes, specifically xen.install. I''m not sure why. This is what I get when I try to run virtman from the command line. If I try to run it from yast i get nothing.

This issue I am encountering seems to only happen on multi-socket machines. It also does not help that the only multi-socket box I have is an Romley-EP (so two socket SandyBridge CPUs). The other SandyBridge boxes I''ve (one socket) are not showing this. Granted they are also a different model (42). The problem is that when I run ''perf top'' within an SMP PVHVM guest,

Not sure I did the xen log correctly. I have this in /etc/default/grub now: GRUB_CMDLINE_XEN_DEFAULT="loglvl=all" And now here is xen dmesg: root at xen-3:~# xl dmesg (XEN) Xen version 4.3.0 (Debian 4.3.0-3+b1) (buildd-binet at buildd.debian.org) (gcc (Debian 4.8.2-8) 4.8.2) debug=n Wed Dec 4 07:43:54 UTC 2013 (XEN) Bootloader: GRUB 2.00-22 (XEN) Command line: placeholder