similar to: Xen PCI Pass-through: 0xbf701000 is using VM_IO, but it is 0xfffffffffffff000!

I have installed the xen 3.1.0 x86_64 tarball compiled for RHEL5 on a RHEL5 system. The system in question was able to boot with the xen kernel that came with RHEL5. I untarred the tarball, and did cd /boot mkinitrd /boot/initrd-2.6.18-xen.img 2.6.18-xen The command exited properly and made a initrd image. The machine booted with a grub.conf entry like this: title Xen 3.1.0 root

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

On 09/02/09 01:10, Mitchell E Berger wrote: > I apologize for writing to you directly instead of through an officially > supported channel. No problem. > I''ve filed a bug against glibc in Redhat''s Bugzilla > for an issue that only seems to surface on 64-bit Xen paravirt guests > on AMD hosts. Filing this bug with the distro involved seemed to make > sense,

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@yahoo.com> wrote: From: Boris

https://bugs.freedesktop.org/show_bug.cgi?id=28763 Summary: Kernel Oops when displaying a large image Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

I''m currently working on moving storage services into their own domain and I''ve been looking at blktap2. I''ve been trying to get an image mounted with blktap2 and for some odd reason and tapdisk2 keeps hanging instead of quitting at the end. I haven''t removed any of the storage startup code at this point so everything should be as it normally is in xen-unstable.