[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Xen-users] No hvm support? AMD Athlon 64, AM2
|
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
Andreas Fromm
Sent: 05 November 2006 14:13
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] No hvm support? AMD Athlon 64, AM2
first of all hi to everybody. I have been reading this list a
while and
searched the archive, but couldn't get a answer to my problem, so here
it is.
I' have bought myself a new Computer which I wanted to be able to run
hvm domains under xen. So I took a AMD Athlon 64 3800+ (Orleans) CPU
with AM2 socket and a Asus M2NPV-MX mainboard (nvidia nforce c51
chipset). I installed debian amd64 unstable with the stock xen kernel
and related packages. The CPU reports the svm capability, but xm dmesg
doesn't show anything about svm.
Does that mean that my mainboard doesn't support hvm-domains
under xen,
or is there a chance to get it to run?
That's very strange - can you see SVM in the Dom0 with "cat
/proc/cpuinfo | grep svm"?
And what does "xm dmesg | grep -i svm" say?
Oh, I didn't say -i to grep, I thougt case ignoring
where default, so I didn't saw anything. SVM isenabled for cpu0, but
this doesn't solve my problem.
As far as I'm aware, there is no way that you could turn off SVM in the
processor (with currently available processors on the market today -
this may change in the future).
Which changeset is it ("xm info|grep changeset")?
~# xm info|grep
changeset
xen_changeset
: Tue Oct 17 22:09:52 2006 +0100
Well,
if it was built using the HG changeset, it would show which changeset in the
mercurial revision control it was, but since it's obviously built outside the HG
archive for the code, it's not got that information, just a date-stamp of the
build, so there's no way to figure out which code-base it used (other than the
fact that it's no later than the time-stamp),
what is the
changeset? The day of the cvs checkout the binary was build with or something
like that?
As the problem doesn't seem to be a hardware-model-problem,
here is the output of the logs I get when I try to create a hvm domain. Maybe
someone can give me a hint of what is going wrong.
[2006-11-06 23:48:49 xend.XendDomainInfo 14855] ERROR (__init__:1072)
Domain construction failed
Traceback (most recent call last):
File
"/usr/lib/xen-3.0.3-1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 195,
in create
vm.initDomain()
File
"/usr/lib/xen-3.0.3-1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 1363,
in initDomain
raise VmError(str(exn))
VmError: (12,
'Cannot allocate memory')
That's
my guess on what's going wrong. Try setting "dom0_mem=256M" on the
"kernel=.../xen.gz ..." line in your /boot/grub/grub.conf (or menu.lst)...
CPU frequency scaling (cpufreq) doesn't work under Xen at the moment -
mainly because the white-list that allows MSR writes doesn't include the
MSR_K7_FID_VID_CTL register to be written - but even if you can write
it, it wouldn't work "right" for the system. I presume this is what you
mean by throttling, and not the trick that was used on some processors
to prevent them from overheating: pulling stpclk for a few microseconds
every so often, until they were running "slow enough" to not get too
hot... Which is the technique that I would use the term throttling for -
frequency scaling is where software and hardware co-operates to save
power and/or reduce heat generated by adjusting the speed of the
processor. Throttling is more of a "stick a log in the spokes for a bit"
type solution.
Well, yes I meant frequency scaling. I know that it doesn't work under
xen, and I understand that it would be hard to implement it, but it doesn't
work under a non xen kernel either. Thats what I'm worried about.
Hmm -
it should do, unless the BIOS is "broken". I wouldn't think it's related to your
above problems tho'. Is there any powernow or cpufreq messages in
dmesg?
--
Mats
Greetings
Andreas
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
