Displaying 20 results from an estimated 2000 matches similar to: "pv_ops kernel 2.6.29-rc6 boot failure"
2009 Feb 13
12
VT-D RMRR is incorrect
I try pci pci passthrough with xen 3.3.1 and CentOS 5.2(64bit)
on a SUPERMICRO C7X58 board
I see the following the error in my boot log.
(XEN) [VT-D]dmar.c:372: RMRR is incorrect.
This problem is caused by this condition in dmr.c:372.
if ( rmrr->base_address >= rmrr->end_address )
{
dprintk(XENLOG_ERR VTDPREFIX, "RMRR is incorrect.\n");
return -EFAULT;
}
As an
2009 Feb 13
12
VT-D RMRR is incorrect
I try pci pci passthrough with xen 3.3.1 and CentOS 5.2(64bit)
on a SUPERMICRO C7X58 board
I see the following the error in my boot log.
(XEN) [VT-D]dmar.c:372: RMRR is incorrect.
This problem is caused by this condition in dmr.c:372.
if ( rmrr->base_address >= rmrr->end_address )
{
dprintk(XENLOG_ERR VTDPREFIX, "RMRR is incorrect.\n");
return -EFAULT;
}
As an
2008 Nov 29
24
pv_ops dom0 testing
I am trying to get a pv_ops dom0 working for testing,
but I am running into an elf_init error:
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_init: not an ELF binary
Full output attached.
>From what I have read on the mailing lists, it seems
that it is usually a problem with either grub or a
corrupt dom0 kernel.
Attached is my kernel config (2.6.28-rc6-tip).
I followed the instructions on:
2007 Dec 27
2
VT-d and the GPU
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
2010 Sep 17
27
Problem: Pattern with vertical colored lines on the dom0 screen
Hi list,
I have a problem with a new laptop (reproducable on other machines too) and the
xen hypervisor.
When the hypervisor gets booted with VESA mode 800x600 I see some messages and
then the screen contents is switched into a pattern of vertical colored lines
and never comes back.
In text mode all works well, but later the pattern appears when the X servers
starts.
I disabled VTd in the bios
2008 Oct 29
34
iommu: mapping reserved region failed - Q35 - VT-D Issue
Xen 3.4 xen-unstable.hg from yesterday with debian etch on 64bit arch
Intel/Lenovo Q35 Mainboard with VT-d enabled
Bootoptions iommu=1 vtd=1
pci.backhide for a PCI-E nvidia graphiccard
xm dmesg Error messages includes:
[VT-D] iommu.c: 1694:d32767 iommu: mapping reserved region failed
[VT-D] iommu.c: 1542:d0 intel_iommu_add_device: context mapping failed
If i try to start my HVM by xm create
2009 Aug 03
1
Cannot boot Dom0: Thread overran stack, or stack corrupted
Hi All,
I am trying to get the pv_ops Xen dom0 kernel working with Xen 3.4 but with no success. I have been at this for 2 weeks now with different problems. Initially I could not get dom0 to boot when using LVM, so I reinstalled and didn''t use LVM. Now I am getting stack overran or currupted errors. Here is the boot log; From <IRQ 0> to the last line keeps on repeating until
2010 Nov 24
18
System reboots after "Scrubbing free RAM" Xen 4.0.1 linux 2.6.37-rc3
Hi Everyone
I have sorted out the initial issues I''ve had and decided to give Xen
another go.
I''m trying to run Xen using kernel 2.6.37-rc3 (previous attempt with rc1
failed, and when I gave it a second go, rc3 was already out).
As previously, 2.6.37-rc3 boots fine natively. 2.6.32 boots natively and
under Xen as dom0, but I have reservations against running 2.6.32,
2010 Nov 24
18
System reboots after "Scrubbing free RAM" Xen 4.0.1 linux 2.6.37-rc3
Hi Everyone
I have sorted out the initial issues I''ve had and decided to give Xen
another go.
I''m trying to run Xen using kernel 2.6.37-rc3 (previous attempt with rc1
failed, and when I gave it a second go, rc3 was already out).
As previously, 2.6.37-rc3 boots fine natively. 2.6.32 boots natively and
under Xen as dom0, but I have reservations against running 2.6.32,
2008 Sep 17
7
Megaraid SAS driver failing in Xen-3.3.0 but was working in Xen-3.2.2-rc3
On Xen-3.3.0, domain0 Megaraid SAS (SAS 1068 controller) driver is not loading correctly if vtd support in Xen is enabled.
It fails at the point of initializing firmware.
I wasn''t seeing this error with Xen-3.2.2-rc3 (Unstable version), though with vtd disabled in Xen-3.3.0, it is working.
Looks like a degrade problem.
Any clues?
Thx,
Venkat
2009 Feb 27
8
Kernel build failure
Did a ''git pull'' a few minutes ago and tried to rebuild my kernel and
was given this error:
make
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86
CALL scripts/checksyscalls.sh
CHK include/linux/compile.h
CC drivers/acpi/acpica/hwsleep.o
drivers/acpi/acpica/hwsleep.c: In function
2013 Sep 12
3
[PATCH 1/1 V3] x86/AMD-Vi: Add additional check for invalid special->handle
From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
This patch handle additional cases for IVRS bugs where special->handle
is not correctly initialized for IOAPIC and HPETS due to firmware bugs.
Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Provide logic in "is_ioapic_overidden()"
Signed-off-by: Jan Beulich <JBeulich@suse.com>
---
2010 Jan 26
1
Bug#567025: xen-hypervisor-3.4-amd64: unhandled page fault while initializing dom0
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
2010 Jan 26
1
Bug#567026: xen-hypervisor-3.4-amd64: unhandled page fault while initializing dom0
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
2010 May 12
44
Xen4 / Intel DX58SO Mobo / VT-d not working
Hello,
I''ve previously been successful with Xen4 and VT-d on other systems. I
am having trouble getting VT-d passthrough working to a WinXP domain
with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios,
xm info shows hvm_directio capability, I have iommu=1 set, I have the
devices bound to pciback on dom0 cmdline, xm
pci-list-assignable-devices shows the devices as
2010 May 12
44
Xen4 / Intel DX58SO Mobo / VT-d not working
Hello,
I''ve previously been successful with Xen4 and VT-d on other systems. I
am having trouble getting VT-d passthrough working to a WinXP domain
with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios,
xm info shows hvm_directio capability, I have iommu=1 set, I have the
devices bound to pciback on dom0 cmdline, xm
pci-list-assignable-devices shows the devices as
2012 Aug 17
2
Bug#684661: Xen BUG at pci_amd_iommu.c:33
Hi Wei,
A Debian user has hit this message and reported it in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684661
I think it is the BUG_ON in:
struct amd_iommu *find_iommu_for_device(int bdf)
{
BUG_ON ( bdf >= ivrs_bdf_entries );
return ivrs_mappings[bdf].iommu;
}
It looks like ivrs_bdf_entries comes from ACPI. Unfortunately the bug
report
2012 Aug 17
2
Bug#684661: Xen BUG at pci_amd_iommu.c:33
Hi Wei,
A Debian user has hit this message and reported it in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684661
I think it is the BUG_ON in:
struct amd_iommu *find_iommu_for_device(int bdf)
{
BUG_ON ( bdf >= ivrs_bdf_entries );
return ivrs_mappings[bdf].iommu;
}
It looks like ivrs_bdf_entries comes from ACPI. Unfortunately the bug
report
2011 Feb 06
6
Xen Restarting on "Scrubbing Free RAM"
Hi, I installed Xen 4.0.1 from source on Debian 5.0.8 and when boot my
computer hardware reboots at like "Scrubbing Free RAM". I tryed to find some
information here but none was helpfull to me. Anyone?
I have 4GB memory and a AMD Turion II X2 M500 (
2013 Aug 28
12
[PATCH V2] x86/AMD-Vi: Add additional check for invalid special->handle
From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
This patch add an additional logic to check for the often case when the
special->handle is not initialized due to firmware bugs.
but the special->usedid is correct. If users overide this using the
command line option ivrs_ioapic, then it should use the value instead.
---
This patch is supposed to follow the patches: