On Thu, Jun 03, 2010 at 02:23:15PM +1000, Virgil wrote: > On Thu, 3 Jun 2010 05:34:34 am M A Young wrote: > > On Wed, 2 Jun 2010, Virgil wrote: > > > Just doing an rpmbuild on: > > > > > > xen-4.0.0-0.7.fc12.x86_64 > > > > > > and I get this error towards the end: > > > > > > Processing files: xen-debuginfo-4.0.0-0.7.fc12.x86_64 > > > Checking for unpackaged file(s): /usr/lib/rpm/check-files > > > /root/rpmbuild/BUILDROOT/xen-4.0.0-0.7.fc12.x86_64 > > > > > > error: Installed (but unpackaged) file(s) found: > > > /etc/hotplug/xen-backend.agent > > > > If you actually got some RPMs built then you should be able to use them. > > It looks like you might have the hotplug package installed (current Fedora > > doesn't have this package) and xen is trying to set things up accordingly. > > > > If you didn't get any RPMs I did a test build of xen-4.0.0-0.7.fc12 at > > http://koji.fedoraproject.org/koji/taskinfo?taskID=2225738 for rawhide > > that you might be able to use. > > > > Michael Young > > OK have rebuilt the machine from the ground up. DVD install then `yum update` > > What works: > > xendom0-97/xen-4.0.0 runs most domU images (not WinXP - runs for a while then > locks up). Even the old FC6 domUs run well. > Anything in "xm log" when the WinXP locks up? or "xm dmesg" ? or in /var/log/xen/* > What doesn't: > > xendom0-105/xen-4.0.0 crashes and burns badly with a pv32fc12 domU (so badly > the keyboard lights blink in pain. Reset button required. Lots and lots of > hypervisorish stuff all over the screen. Very likely the cause is noted in > there somewhere). > Please set up a serial console so you can capture the full boot and error/crash messages: http://wiki.xensource.com/xenwiki/XenSerialConsole A couple of questions: - Do you have "nomodeset" parameter for the dom0 kernel? - Did you limit dom0 memory to, say, 1024 MB ? http://wiki.xensource.com/xenwiki/XenBestPractices > Not tested: > xen-3.4.3 with either kernel. Is this version of Xen more likely to react in a > more stable manner? Or is this a kernel thing? > You can try. I'd guess it's the dom0 kernel, and not Xen itself. -- Pasi > ????????? Xen-fc12 > ????????? xen-3.4.3 > ??? ????????? xen-3.4.3-2.fc12.x86_64.rpm > ??? ????????? xen-devel-3.4.3-2.fc12.x86_64.rpm > ??? ????????? xen-doc-3.4.3-2.fc12.x86_64.rpm > ??? ????????? xen-hypervisor-3.4.3-2.fc12.x86_64.rpm > ??? ????????? xen-libs-3.4.3-2.fc12.x86_64.rpm > ??? ????????? xen-runtime-3.4.3-2.fc12.x86_64.rpm > ????????? xen-4.0.0 > ??? ????????? xen-4.0.0-0.7.fc12.src.rpm > ??? ????????? xen-4.0.0-0.7.fc12.x86_64.rpm > ??? ????????? xen-debuginfo-4.0.0-0.7.fc12.x86_64.rpm > ??? ????????? xen-devel-4.0.0-0.7.fc12.x86_64.rpm > ??? ????????? xen-doc-4.0.0-0.7.fc12.x86_64.rpm > ??? ????????? xen-hypervisor-4.0.0-0.7.fc12.x86_64.rpm > ??? ????????? xen-libs-4.0.0-0.7.fc12.x86_64.rpm > ??? ????????? xen-runtime-4.0.0-0.7.fc12.x86_64.rpm > ????????? xendom0-105 > ??? ????????? kernel-2.6.32.14-1.2.105.xendom0.fc12.x86_64.rpm > ??? ????????? kernel-devel-2.6.32.14-1.2.105.xendom0.fc12.x86_64.rpm > ??? ????????? kernel-firmware-2.6.32.14-1.2.105.xendom0.fc12.noarch.rpm > ??? ????????? kernel-headers-2.6.32.14-1.2.105.xendom0.fc12.x86_64.rpm > ????????? xendom0-97 > ????????? kernel-2.6.32.11-1.2.97.xendom0.fc12.x86_64.rpm > ????????? kernel-devel-2.6.32.11-1.2.97.xendom0.fc12.x86_64.rpm > ????????? kernel-firmware-2.6.32.11-1.2.97.xendom0.fc12.noarch.rpm > ????????? kernel-headers-2.6.32.11-1.2.97.xendom0.fc12.x86_64.rpm > > Cheers > V > -- > xen mailing list > xen@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/xen
