Re: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-3 rpm available from koji / F12 problem with pygrub
by Boris Derzhavets
>However, If I do 'rpmbuild --bb xen.spec' for xen-3.4.1-3.fc12.src.rpm and > install the rebuilt rpms, pygrub works just fine!
Sorry, you have noticed it already
B.
--- On Sun, 9/13/09, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-3 rpm available from koji / F12 problem with pygrub
To: "Gerd Hoffmann" <kraxel(a)redhat.com>, "Pasi Kärkkäinen" <pasik(a)iki.fi>
Cc: fedora-xen(a)redhat.com
Date: Sunday, September 13, 2009, 1:01 PM
>Anyway, it seems the F12/rawhide xen-3.4.1-3 rpms contain pygrub that
>doesn't support ext4.
Please, view :-
http://www.fsdaily.com/HighEnd/Setup_Xen_3_4_1_Libvirt_on_top_F12_Alpha_r...
It's on 64-bit.
Boris.
--- On Sun, 9/13/09, Pasi Kärkkäinen <pasik(a)iki.fi> wrote:
From: Pasi Kärkkäinen <pasik(a)iki.fi>
Subject: Re: [Fedora-xen] [Xen-devel] [ANNOUNCE] Xen 3.3.2 and 3.4.1 released / 3.4.1-3 rpm available from koji / F12 problem with pygrub
To: "Gerd Hoffmann" <kraxel(a)redhat.com>
Cc: fedora-xen(a)redhat.com
Date: Sunday, September 13, 2009, 12:16 PM
On Wed, Sep 02, 2009 at 04:08:32PM +0300, Pasi Kärkkäinen wrote:
> On Wed, Sep 02,
2009 at 03:59:31PM +0300, Pasi Kärkkäinen wrote:
> > On Wed, Sep 02, 2009 at 03:41:09PM +0300, Pasi Kärkkäinen wrote:
> > > On Wed, Sep 02, 2009 at 02:25:59PM +0200, Gerd Hoffmann wrote:
> > > > Hi,
> > > >
> > > > >>Still no stubdom/pvgrub bzip2/lzma support though. I'll look more into
> > > > >>it tonight.
> > > > >
> > > > >.. but don't wait for the final patch, since I don't know yet how long
> > > > >it takes to get the stubdom/pvgrub stuff sorted out.
> > > >
> > > > Bits committed, koji builds done.
> > > >
> > >
> > > Great, thanks!
> > >
> > > Does 3.4.1-3 end up in F12 automatically?
> > >
> >
> > btw the url is this:
> > http://kojipkgs.fedoraproject.org/packages/xen/3.4.1/3.fc12/
> >
> > Changelog:
> >
> > * Wed Sep 02 2009 Gerd Hoffmann <kraxel(a)redhat.com> - 3.4.1-3
> > - swap bzip2+xz linux kernel compression support patches.
> > - backport one more bugfix (videoram option).
> >
> > * Tue Sep 01 2009 Gerd Hoffmann <kraxel(a)redhat.com> - 3.4.1-2
> > - backport bzip2+xz linux kernel compression support.
> > - backport a few bugfixes.
> >
>
> btw 3.4.1-2 and 3.4.1-3 do contain the fix for pygrub timeout=0
> handling, so F11 PV domUs/guests will work out-of-the-box.
>
Hello,
I just noticed something weird.. I upgraded my host to F12/rawhide, so
now I'm running everything straight from rawhide, except my custom
pv_ops dom0 kernel.
Anyway, it seems the F12/rawhide xen-3.4.1-3 rpms contain pygrub that
doesn't support ext4.
# /usr/bin/pygrub --output=/tmp/debug /dev/vg_dom0test/test3vm
Traceback (most recent call last):
File "/usr/bin/pygrub", line 680, in <module>
chosencfg = run_grub(file, entry, fs, incfg["args"])
File "/usr/bin/pygrub", line 515, in run_grub
g = Grub(file, fs)
File "/usr/bin/pygrub", line 202, in __init__
self.read_config(file, fs)
File "/usr/bin/pygrub", line 397, in read_config
raise RuntimeError, "couldn't find bootloader config file in the image provided."
RuntimeError: couldn't find bootloader config file in the image
provided.
However, If I do 'rpmbuild --bb xen.spec' for xen-3.4.1-3.fc12.src.rpm and install
the rebuilt rpms, pygrub works just fine!
So is there some lib missing from the build requirements or?
Any ideas?
-- Pasi
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
14 years, 7 months
Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
by Boris Derzhavets
I was able to get login prompt ( commit 7c62209cde5b13b81685e79b2f9e3757e293aef1 ) first time via serial console:-
title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)
root (hd1,0)
kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1
module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=hvc0 earlyprintk=xen
module /initrd-2.6.31-rc8.img
Then disconnected NUL modem cable and loaded Dom0 via :
title Xen 3.4.1 Fedora 12 Serial (2.6.31-rc8 ) (/dev/sdb1)
root (hd1,0)
kernel /xen-3.4.1.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1
module /vmlinuz-2.6.31-rc8 ro root=/dev/mapper/vg_fdr12-lv_root console=tty0 earlyprintk=xen
module /initrd-2.6.31-rc8.img
Usual Grub entry drops console to stack trace.
Dmesg output is attached.
Boris.
--- On Tue, 9/8/09, Mark Schloesser <mark.schloesser(a)rwth-aachen.de> wrote:
From: Mark Schloesser <mark.schloesser(a)rwth-aachen.de>
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
To: "Boris Derzhavets" <bderzhavets(a)yahoo.com>
Cc: fedora-xen(a)redhat.com
Date: Tuesday, September 8, 2009, 8:13 AM
Top commit in my checkout is:
commit 3b316bf67dcbe550e648703475e811fc0cedc705
Merge: 226206a 27a3a52
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge(a)citrix.com>
Date: Thu Sep 3 16:25:12 2009 -0700
Mark
Boris Derzhavets wrote:
> Yep ;)
>
> Please, run
> # git log|more
> in linux-2.6-xen ( obtained via git clone).
> I am wondering what was the top commit for good build 2.6.31-rc8
> I am trying to bisect.
>
> Boris.
>
>
> --- On Sun, 9/6/09, Mark Schloesser <mark.schloesser(a)rwth-aachen.de> wrote:
>
> From: Mark Schloesser <mark.schloesser(a)rwth-aachen.de>
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
> To: "Boris Derzhavets" <bderzhavets(a)yahoo.com>
> Cc: xen-devel(a)lists.xensource.com, fedora-xen(a)redhat.com
> Date: Sunday, September 6, 2009, 12:17 PM
>
> I am on standard F11, using a fresh install and then updated all
> packages before doing anything xen related. Xen build was done with
> current xen-unstable checkout using only "xen" and "tools" build
> targets. I have no libvirt or libvirt-preview currently. My Xorg still
> does not want to come up btw :)
>
> Do you need anything else?
>
> Mark
>
>
>
>
>
>
>
14 years, 8 months
Re: [Xen-devel] Dmesg log for 2.6.31-rc8 kernel been built on F12 (rawhide) vs log for same kernel been built on F11 and installed on F12
by Boris Derzhavets
>I am not sure if I understand you correctly. Are you saying that 2.6.31-rc8
>boots without the stack-trace failure? Can you attach the dmesg please
>and also 'lspci -vvv' output?
If i built rc8 on F11 ( dual booting) with F12 and install kernel and modules via
# mount /dev/mapper/serverfedora11-lv_root /mnt
#cd /mnt/usr/src/linux-2.6-xen
# make modules_install install
in F12 env, then i get a stable kernel rc8 on F12.
If i compile and and install on F12 kernel has stack trace and is pretty unstable at
runtime.
Now i am sending two dmesg reports :-
1. Kernel 2.6.31-rc8 been built on F11 and installed on F12
dmesg.log.gz (clean)
2. Kernel 2.6.31-rc8 been built on F12 and installed on F12
dmesg.1.gz ( stack trace here)
"lspci -vvv" report has been also sent to you per your request, but i will repeat. This one is for C2D E8400 box.
Boris.
--- On Wed, 9/9/09, Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com> wrote:
From: Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com>
Subject: Re: [Xen-devel] Dmesg log for 2.6.31-rc8 kernel been built on F12 (rawhide) vs log for same kernel been built on F11 and installed on F12
To: "Boris Derzhavets" <bderzhavets(a)yahoo.com>
Cc: "Jeremy Fitzhardinge" <jeremy(a)goop.org>, xen-devel(a)lists.xensource.com, fedora-xen(a)redhat.com
Date: Wednesday, September 9, 2009, 10:10 AM
On Wed, Sep 09, 2009 at 12:19:20AM -0700, Boris Derzhavets wrote:
> Previous 2.6.31-rc8 kernel was built on F11 and installed with modules on F12.
> Current kernel has been built on F12 (2.6.31-0.204.rc9.fc12.x86_64) and installed
> on F12 before loading under Xen 3.4.1.
> Dmesg log looks similar to Michael Yuong's 'rc7.git4' kernel for F12.
I am not sure if I understand you correctly. Are you saying that 2.6.31-rc8
boots without the stack-trace failure? Can you attach the dmesg please
and also 'lspci -vvv' output?
>
> Boris.
>
> --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote:
>
> From: Boris Derzhavets <bderzhavets(a)yahoo.com>
> Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem
> To: "Pasi Kärkkäinen" <pasik(a)iki.fi>, "Konrad Rzeszutek Wilk" <konrad..wilk(a)oracle.com>
> Cc: "Jeremy Fitzhardinge" <jeremy(a)goop.org>, xen-devel(a)lists.xensource.com, fedora-xen(a)redhat.com
> Date: Tuesday, September 8, 2009, 3:45 PM
>
> Dmesg log for rc8 under Xen 3.4.1 on F12 rawhide attached.
I took a look at the dmesg and it looks fine. I did not see a stack trace in it?
Maybe I was looking at the wrong one. This is the identifying timestamp at the beginning:
Linux version 2.6.31-rc8 (root@ServerXen35) (gcc version 4.4.1 20090725 (Red Hat 4.4.1-2) (GCC) ) #3 SMP Tue Sep 8 04:24:43 EDT 2009
is that the right dmesg?
***************************************************
Yes , this one is fine.
Kernel had been built on F11 and installed on F12
***************************************************
_______________________________________________
Xen-devel mailing list
Xen-devel(a)lists.xensource.com
http://lists.xensource.com/xen-devel
14 years, 8 months
Dmesg log for 2.6.31-rc8 kernel been built on F12 (rawhide) vs log for same kernel been built on F11 and installed on F12
by Boris Derzhavets
Previous 2.6.31-rc8 kernel was built on F11 and installed with modules on F12.
Current kernel has been built on F12 (2.6.31-0.204.rc9.fc12.x86_64) and installed
on F12 before loading under Xen 3.4.1.
Dmesg log looks similar to Michael Yuong's 'rc7.git4' kernel for F12.
Boris.
--- On Tue, 9/8/09, Boris Derzhavets <bderzhavets(a)yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets(a)yahoo.com>
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem
To: "Pasi Kärkkäinen" <pasik(a)iki.fi>, "Konrad Rzeszutek Wilk" <konrad.wilk(a)oracle.com>
Cc: "Jeremy Fitzhardinge" <jeremy(a)goop.org>, xen-devel(a)lists.xensource.com, fedora-xen(a)redhat.com
Date: Tuesday, September 8, 2009, 3:45 PM
Dmesg log for rc8 under Xen 3.4.1 on F12 rawhide attached.
Boris.
--- On Tue, 9/8/09, Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com> wrote:
From: Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com>
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem
To: "Pasi Kärkkäinen" <pasik(a)iki.fi>
Cc: "Boris Derzhavets" <bderzhavets(a)yahoo.com>, xen-devel(a)lists.xensource.com, "Jeremy Fitzhardinge" <jeremy(a)goop.org>, fedora-xen(a)redhat.com
Date: Tuesday, September 8, 2009, 3:34 PM
On Tue, Sep 08, 2009 at 10:22:46PM +0300, Pasi Kärkkäinen wrote:
> On Tue, Sep 08, 2009 at 12:14:54PM -0700, Boris
Derzhavets wrote:
> > Console drops into the same stack trace in both cases.
> >
>
> Jeremy: Any ideas could some recent change in pv_ops dom0 kernel cause
> usb stuff to stop working with >4096M of dom0 memory?
The last set of changes in Jeremy's kernel are a set of patches I sent,
so the problem is most likely caused by my work.
A dmesg from both Xen and Linux kernel would be most helpfull. Also
a lspci -vvv would be nice.
And as Pasi suggested, booting the same kernel without Xen would
be most helpful.
>
> dom0_mem=4096M works
> dom0_mem=4097M fails with stacktrace
>
> Boris: What was the last kernel that worked without backtraces?
> Also, does that same kernel work as baremetal (without Xen) ?
_______________________________________________
Xen-devel mailing list
Xen-devel(a)lists.xensource.com
http://lists.xensource.com/xen-devel
-----Inline Attachment Follows-----
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
14 years, 8 months
Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem
by Boris Derzhavets
> lspci -vvv would be nice.
Attached
Boris.
--- On Tue, 9/8/09, Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com> wrote:
From: Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com>
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem
To: "Pasi Kärkkäinen" <pasik(a)iki.fi>
Cc: "Boris Derzhavets" <bderzhavets(a)yahoo.com>, "Jeremy Fitzhardinge" <jeremy(a)goop.org>, xen-devel(a)lists.xensource.com, fedora-xen(a)redhat.com
Date: Tuesday, September 8, 2009, 3:34 PM
On Tue, Sep 08, 2009 at 10:22:46PM +0300, Pasi Kärkkäinen wrote:
> On Tue, Sep 08, 2009 at 12:14:54PM -0700, Boris Derzhavets wrote:
> > Console drops into the same stack trace in both cases.
> >
>
> Jeremy: Any ideas could some recent change in pv_ops dom0 kernel cause
> usb stuff to stop working with >4096M of dom0 memory?
The last set of changes in Jeremy's kernel are a set of patches I sent,
so the problem is most likely caused by my work.
A dmesg from both Xen and Linux kernel would be most helpfull. Also
a lspci -vvv would be nice.
And as Pasi suggested, booting the same kernel without Xen would
be most helpful.
>
> dom0_mem=4096M works
> dom0_mem=4097M fails with stacktrace
>
> Boris: What was the last kernel that worked without backtraces?
> Also, does that same kernel work as baremetal (without Xen) ?
14 years, 8 months
Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem
by Boris Derzhavets
Dmesg log for rc8 under Xen 3.4.1 on F12 rawhide attached.
Boris.
--- On Tue, 9/8/09, Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com> wrote:
From: Konrad Rzeszutek Wilk <konrad.wilk(a)oracle.com>
Subject: Re: [Xen-devel] Re: [Fedora-xen] Xorg on JF 2.6.31-rc8 with xen 3.5 unstable, stacktrace with >4096M of dom0_mem
To: "Pasi Kärkkäinen" <pasik(a)iki.fi>
Cc: "Boris Derzhavets" <bderzhavets(a)yahoo.com>, xen-devel(a)lists.xensource.com, "Jeremy Fitzhardinge" <jeremy(a)goop.org>, fedora-xen(a)redhat.com
Date: Tuesday, September 8, 2009, 3:34 PM
On Tue, Sep 08, 2009 at 10:22:46PM +0300, Pasi Kärkkäinen wrote:
> On Tue, Sep 08, 2009 at 12:14:54PM -0700, Boris Derzhavets wrote:
> > Console drops into the same stack trace in both cases.
> >
>
> Jeremy: Any ideas could some recent change in pv_ops dom0 kernel cause
> usb stuff to stop working with >4096M of dom0 memory?
The last set of changes in Jeremy's kernel are a set of patches I sent,
so the problem is most likely caused by my work.
A dmesg from both Xen and Linux kernel would be most helpfull. Also
a lspci -vvv would be nice.
And as Pasi suggested, booting the same kernel without Xen would
be most helpful.
>
> dom0_mem=4096M works
> dom0_mem=4097M fails with stacktrace
>
> Boris: What was the last kernel that worked without backtraces?
> Also, does that same kernel work as baremetal (without Xen) ?
_______________________________________________
Xen-devel mailing list
Xen-devel(a)lists.xensource.com
http://lists.xensource.com/xen-devel
14 years, 8 months
Xorg on JF 2.6.31-rc8 with xen 3.5 unstable
by Mark Schloesser
Hey guys,
I sadly had no luck fixing my X problem. The system seems to run fine
and as the subject says I moved from 3.4.1-3 to xen-unstable. As I am
already doing fairly bleeding-edge stuff here I thought this would
probably make most sense.
As I only have an nvs290 gfx card available right now I can't check if
this is the problem. But I'll try to get my hands on some other cards
for next week.
Today I read through a lot of mailing list archives and PDFs trying to
dig deeper into the IOMMU/PCI passthrough stuff and I want to give the
graphics passthrough situation a shot myself. Sadly it is very confusing
to read about the different setups and hardware environments with both
positive and negative results. Also the patchsets and versions everybody
is talking about do not make it any easier :)
My current questions would be:
- is the combination of JF git kernel with xen-unstable the right way to
go for this setup? Or should I perhaps use older xen version and apply
some patchset? I think some of those patches were applied in
xen-unstable already but I am not quite sure...
- does anyone have hints or clarification regarding the Xorg problem on
dom0? As I said there are no eye-catching log entries or errors except
the Xorg backtrace at the end of the log file (posted to list before).
This happens regardless of which driver I enable (vesa/nv/nouveau). The
nvidia binary driver compiles without problems and seems to come up but
only gives me a black screen and also locks the vtys.
Thanks to the great help, reports and instructions Boris and others!
Mark
14 years, 8 months
Re: [Xen-devel] Re: Errors when build 2.6.31-rc8
by Boris Derzhavets
Attempt to load 2.6-31-rc8 under Xen 3.4.1 , installed via xen-3.4.1-3.src.rpm along with
libvirt(rawhide) , on top F12 rawhide. yum update gcc,glibc,kernel had been run.
Call trace:
usb_hc_died + .....
usb_add_hcd +.....
usb_hcd_pci_probe + ....
do_work_for_cpu + .....
local_pci_probe + ...
do_work_for_cpu +....
kthread +.....
child_rip+....
restore_args + .....
child_rip + .....
Code : . . . .
.. . . .
RIP [<ffff...c7>] usb_kick_khubd + 0x10/0x25
RSP < ffff ... e0>
CR2: 00000...098
---[ end trace 8219......]----
uhci_hcd 0000:00:1a:0 host controller process error, something bad happened !
uhci_hcd 0000:00:1a:0 host controller halted , very bad
uhci_hcd 0000:00:1a:0 HC died, cleaning up
2.6.31-rc6 loads fine in same environment under Xen 3.4.1 on top of F12 rawhide
Boris,
--- On Sat, 9/5/09, Jeremy Fitzhardinge <jeremy(a)goop.org> wrote:
From: Jeremy Fitzhardinge <jeremy(a)goop.org>
Subject: [Xen-devel] Re: Errors when build 2.6.31-rc8
To: "Boris Derzhavets" <bderzhavets(a)yahoo.com>
Cc: "Xen-devel" <xen-devel(a)lists.xensource.com>
Date: Saturday, September 5, 2009, 11:48 AM
On 09/05/09 04:18, Boris Derzhavets wrote:
> After fresh git clone, git checkout tune "make menuconfig" the same
> way as for RC6
>
> When build :-
>
> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:5,
> from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
> include/linux/swiotlb.h:48: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:48: warning: its scope is only this definition
> or declaration, which is probably not what you want
> include/linux/swiotlb.h:51: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:63: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:68: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:72: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:76: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:80: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:84: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:89: warning: ‘enum dma_data_direction’
> declared inside parameter list
> include/linux/swiotlb.h:94: warning: ‘enum dma_data_direction’
> declared inside parameter list
> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
> from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
> ‘get_dma_ops’:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:29: error:
> dereferencing pointer to incomplete type
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:32: error:
> dereferencing pointer to incomplete type
> In file included from
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:37,
> from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
> from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:12: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:11: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_map_single_attrs’:
> include/asm-generic/dma-mapping-common.h:18: error: implicit
> declaration of function ‘valid_dma_direction’
> In file included from
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:37,
> from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
> from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
> include/asm-generic/dma-mapping-common.h:19: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:31: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:30: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_unmap_single_attrs’:
> include/asm-generic/dma-mapping-common.h:36: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:37: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:43: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:42: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function ‘dma_map_sg_attrs’:
> include/asm-generic/dma-mapping-common.h:52: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:60: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:59: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_unmap_sg_attrs’:
> include/asm-generic/dma-mapping-common.h:66: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:67: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:72: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:72: error: parameter 5
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function ‘dma_map_page’:
> include/asm-generic/dma-mapping-common.h:79: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:86: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:86: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function ‘dma_unmap_page’:
> include/asm-generic/dma-mapping-common.h:91: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:92: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:98: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:98: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_sync_single_for_cpu’:
> include/asm-generic/dma-mapping-common.h:103: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:104: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:111: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:111: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_sync_single_for_device’:
> include/asm-generic/dma-mapping-common.h:116: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:117: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:126: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:126: error: parameter 5
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_sync_single_range_for_cpu’:
> include/asm-generic/dma-mapping-common.h:131: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:132: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:137: error: type of formal
> parameter 4 is incomplete
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:144: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:144: error: parameter 5
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_sync_single_range_for_device’:
> include/asm-generic/dma-mapping-common.h:149: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:150: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:155: error: type of formal
> parameter 4 is incomplete
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:160: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:160: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_sync_sg_for_cpu’:
> include/asm-generic/dma-mapping-common.h:165: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:166: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h: At top level:
> include/asm-generic/dma-mapping-common.h:173: warning: ‘enum
> dma_data_direction’ declared inside parameter list
> include/asm-generic/dma-mapping-common.h:173: error: parameter 4
> (‘dir’) has incomplete type
> include/asm-generic/dma-mapping-common.h: In function
> ‘dma_sync_sg_for_device’:
> include/asm-generic/dma-mapping-common.h:178: error: dereferencing
> pointer to incomplete type
> include/asm-generic/dma-mapping-common.h:179: error: dereferencing
> pointer to incomplete type
> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
> from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
> ‘dma_mapping_error’:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:42: error:
> dereferencing pointer to incomplete type
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:43: error:
> dereferencing pointer to incomplete type
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: At top level:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:60: warning:
> ‘enum dma_data_direction’ declared inside parameter list
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:60: error:
> parameter 4 (‘dir’) has incomplete type
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
> ‘dma_alloc_coherent_mask’:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:77: error:
> dereferencing pointer to incomplete type
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:79: error:
> implicit declaration of function ‘DMA_BIT_MASK’
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
> ‘dma_alloc_coherent’:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:114: error:
> implicit declaration of function ‘is_device_dma_capable’
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:117: error:
> dereferencing pointer to incomplete type
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:120: error:
> dereferencing pointer to incomplete type
> In file included from /usr/src/linux-2.6-xen/arch/x86/include/asm/agp.h:9,
> from drivers/gpu/drm/ttm/ttm_agp_backend.c:40:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h: In function
> ‘dma_free_coherent’:
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:138: error:
> dereferencing pointer to incomplete type
> /usr/src/linux-2.6-xen/arch/x86/include/asm/dma-mapping.h:139: error:
> dereferencing pointer to incomplete type
> make[4]: *** [drivers/gpu/drm/ttm/ttm_agp_backend.o] Error 1
> make[3]: *** [drivers/gpu/drm/ttm] Error 2
> make[2]: *** [drivers/gpu/drm] Error 2
> make[1]: *** [drivers/gpu] Error 2
> make: *** [drivers] Error 2
>
Does this help?
diff --git a/include/linux/swiotlb.h b/include/linux/swiotlb.h
index cb1a663..f4ebffb 100644
--- a/include/linux/swiotlb.h
+++ b/include/linux/swiotlb.h
@@ -2,6 +2,7 @@
#define __LINUX_SWIOTLB_H
#include <linux/types.h>
+#include <linux/dma-mapping.h>
struct device;
struct dma_attrs;
J
_______________________________________________
Xen-devel mailing list
Xen-devel(a)lists.xensource.com
http://lists.xensource.com/xen-devel
14 years, 8 months
xen 3.4.1 + myoung x86_64 kernel
by Mark Schloesser
Hi,
I was just trying to get this combination setup up and running. I am on
Fedora 11 and mostly followed Boris Derzhavets' blog to get it done.
Sadly the box complains that it can not connect to the hypervisor when
starting libvirtd and also xend startup fails.
libvirtd screen message:
ERROR Internal error: Could not obtain handle on privileged command
interface (13 = Permission denied)
FATAL: Failed to open connection to hypervisor: Permission denied
In the kernel log I saw this:
======================================================
[ INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ]
2.6.31-0.1.2.60.rc7.git4.xendom0.fc12.x86_64 #1
------------------------------------------------------
See dmesg at http://p.carnivore.it/MrGxdQ for more info.
Thanks for any hints or clarification!
Cheers,
Mark
14 years, 8 months
Cross-posting to fedora-virt
by Mark McLoughlin
Hey,
I think the fedora-xen mailing list is serving well as a place for all
you brave souls working on getting Xen pv_ops Dom0 into shape.
However, I don't think there's much point in having the separate list if
people cross-post everything to fedora-virt.
So, thoughts on whether we should either:
a) close down the fedora-xen list or
b) stop cross-posting everything to fedora-virt
?
Cheers,
Mark.
14 years, 8 months
