On Mon, 12 Oct 2009, Boris Derzhavets wrote:
> Attempt to load under Xen 3.4.1 on F12 rawhide ( yum updated)
> via Fedora's 12 kernel :-
> - - - - - - - - - - - dmesg - - - - - - - - - - - - - - - - - -
> [drm] radeon: Initializing kernel modesetting.
> [drm] register mmio base: 0xFE8E0000
> [drm] register mmio size: 65536
> ATOM BIOS: 11X
> [drm] Clocks initialized !
> mtrr: type mismatch for d0000000,10000000 old: write-back new:
> [drm] Detected VRAM RAM=256M, BAR=256M
> [drm] RAM width 128bits DDR
> [TTM] Zone kernel: Available graphics memory: 4076336 kiB.
> [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
> [drm] radeon: 256M of VRAM memory ready
> [drm] radeon: 512M of GTT memory ready.
> [drm] Loading RV730 CP Microcode
> platform radeon_cp.0: firmware: requesting radeon/RV730_pfp.bin
> r600_cp: Failed to load firmware "radeon/RV730_pfp.bin"
> [drm:rv770_init] *ERROR* Failed to load firmware!
> [drm:radeon_driver_load_kms] *ERROR* Fatal error while trying to initialize
> radeon 0000:01:00.0: PCI INT A disabled
> radeon: probe of 0000:01:00.0 failed with error -2
The file radeon/RV730_pfp.bin is there in the corresponding
kernel-firmware package at /lib/firmware/radeon/RV730_pfp.bin . Perhaps it
is missing from the initrd file that was generated when ypu installed it
(I have been using the traditional method of generating this file rather
than using dracut for various reasons).
I was just playing with Fedora on x86_64 box, and I upgraded it from F11
to F12 rawhide.
I installed xen rpms and myoung xendom0 kernel, added /etc/fstab
/proc/xen entry and rebooted into xen.
Now it seems xend doesn't start for some reason. Has anyone noticed this?
[root@f12test ~]# /etc/init.d/xend start
Starting xend daemon: [FAILED]
[root@f12test ~]# tail -29 /var/log/xen/xend.log
[2009-10-11 18:49:12 1976] INFO (SrvDaemon:339) Xend Daemon started
[2009-10-11 18:49:12 1976] INFO (SrvDaemon:343) Xend changeset: unavailable.
[2009-10-11 18:49:14 1976] ERROR (SrvDaemon:356) Exception starting xend ((111, 'Connection refused'))
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py", line 348, in run
servers = SrvServer.create()
File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvServer.py", line 251, in create
File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvRoot.py", line 40, in __init__
File "/usr/lib64/python2.6/site-packages/xen/web/SrvDir.py", line 84, in get
val = val.getobj()
File "/usr/lib64/python2.6/site-packages/xen/web/SrvDir.py", line 52, in getobj
self.obj = klassobj()
File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDomainDir.py", line 41, in __init__
self.xd = XendDomain.instance()
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 1736, in instance
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 113, in init
File "/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xstransact.py", line 355, in Mkdir
complete(path, lambda t: t.mkdir(*args))
File "/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xstransact.py", line 361, in complete
t = xstransact(path)
File "/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xstransact.py", line 29, in __init__
self.transaction = xshandle().transaction_start()
File "/usr/lib64/python2.6/site-packages/xen/xend/xenstore/xsutil.py", line 18, in xshandle
xs_handle = xen.lowlevel.xs.xs()
Error: (111, 'Connection refused')
Ok, to be sure, I though I could check kernel compiled option somewhere
... but can find where ....
No I haven't tried yet for the guests, I would have prefered to be sure
By the way, I supose that a clean solution would be to upgrade my 32 bit
system (domain-0) to a 64 bit one !
but apparently it is not an easy thing to do :-(
is there a simpler solution ?
> I think yes, all new kernels seems to be PAE by default
> about your guests, there are only one way to know.
> have you tried ?
> On Fri, Oct 9, 2009 at 10:37 AM, jehan procaccia
> <jehan.procaccia(a)it-sudparis.eu> wrote:
>> I noticed that with my 32 bit architecture kernel-xen, I can see my 16 Gb of
>> ram !
>> does that mean that kernel-xen is PAE enabled by default ? how can I check
>> that ?
>> then, if it does manages my 16 GB, will my para-virtualized 32 bits xen
>> guests could have more than 4 GB each ?
>> Regards .
I noticed that with my 32 bit architecture kernel-xen, I can see my 16
Gb of ram !
does that mean that kernel-xen is PAE enabled by default ? how can I
check that ?
then, if it does manages my 16 GB, will my para-virtualized 32 bits xen
guests could have more than 4 GB each ?
When I try to install a PV instance of F11, I'm getting an 'invalid
kernel' message. The Dom0 is Sun xVM - equivalent to Xen 3.1.4
I have tried both the i386 and x86_64 versions.
This was supposed to be a straightforward config. Is there something