Hey All, Long time no email. Please cc me on replies, as I can't keep up with this list and no longer subscribe.
SO I got some new hardware... to wit: Motherboard: Gigabyte GA-G33M-DS2R Drives: 4 250 GB SATA Anyway, Etch worked, right up until boot time came. Every single time I tried, I got dumped into a grubsh on boot and just got nowhere. So I moved to testing...lo and behold it worked. SO I am building my very minimal system up (I even unchecked "standard system" on install to keep my dom0 lean) Some packages I have installed: ii libc6-xen 2.6.1-1+b1 ii xen-hypervisor 3.1.1-1 ii xen-tools 3.8-4 ii xen-utils-3.1- 3.1.1-1 ii xen-utils-comm 3.1.0-1 ii linux-image-2. 2.6.22-4 ~# xm list WARING! Can't find hypervisor information in sysfs! Error: Unable to connect to xend: No such file or directory. Is xend running? # xend WARING! Can't find hypervisor information in sysfs! ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): (snipped traceback) I found many copies all over the web of a post that describes this issue and a solution: http://www.debianhelp.org/node/11088 Except.... # dmesg |grep para Booting paravirtualized kernel on bare hardware ... and the changelog for the kernel says: * Update xen patch to changeset 48670 from fedora 2.6.20 branch. * Support xen versions 3.0.4-1 and 3.0.3-1. So.... am I reading this right that the linux-image currently in testing does NOT support the version of xen in testing? Is there an easy solution here? I don't really care hat version of xen I run so much as that I want it to run and I do NOT want to be in the custome kernel game. -Steve -- "Mankind, The Public enemy's not the man who speaks his mind The Public enemy's the man who goes and acts blind" -- Anthrax "Keep it in the Fammily" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
