From: Richard Simpson <rs1002@huskydog.org.uk>
To: Andre Przywara <andre.przywara@amd.com>
Cc: Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: Setting nx bit in virtual CPU
Date: Mon, 12 Apr 2010 22:15:04 +0100 [thread overview]
Message-ID: <4BC38D58.9090802@huskydog.org.uk> (raw)
In-Reply-To: <4BBFBC27.8040007@amd.com>
On 10/04/10 00:45, Andre Przywara wrote:
> Richard Simpson wrote:
>> On 08/04/10 09:52, Andre Przywara wrote:
> OK, AFAIK there are several flags missing. I dimly remember there was a
> bug with masking the CPUID bits in older kernels, so I guess you have to
> celebrate your uptime for the last time and then give it a reboot with a
> more up-to-date host kernel.
> (I also rebooted my desktop after I made the one year and now am gone
> green with turning it off over night ;-)
> Maybe you get around with rebuilding fixed versions of kvm.ko and
> kvm_amd.ko, I can provide a fix for you if you wish (please point me to
> a way to get the actual kernel source you use).
> The userspace was up-to-date? (qemu-kvm 0.12.3)?
Well, its funny how these things turn out. On Saturday, my better half
insisted that I replace a mains socket. It wasn't on the same ring main
as the server so I just switched off the relevant circuit breaker and
got on with it. Unfortunately, whilst I was doing the work the main RCD
tripped, probably because I let the Neutral and Earth touch which can
cause that to happen sometimes. Anyway, by the time I realised there
was a problem the old batteries in my UPS had given up and my uptime was
over with a grand total of 382 days, 12:07:24! If this had happened a
few weeks ago I would probably have thrown myself from the roof! In my
previous house, I installed a special circuit for the server not
protected by an RCD especially to avoid problems of this sort. Adding
one in my current house has now moved a long way up my "To Do" list!
The server has started again, but a few things still aren't happy. As
soon as I have them sorted I will step up to the latest kernel and let
you know what difference it makes.
Thanks,
Richard
prev parent reply other threads:[~2010-04-12 21:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 22:16 Setting nx bit in virtual CPU Richard Simpson
2010-03-30 2:12 ` Chris Wright
2010-03-30 20:42 ` Richard Simpson
2010-04-01 8:43 ` Avi Kivity
2010-04-02 21:07 ` Richard Simpson
2010-04-05 8:27 ` Avi Kivity
2010-04-06 22:31 ` Richard Simpson
2010-04-07 5:39 ` Avi Kivity
2010-04-07 12:10 ` Richard Simpson
2010-04-07 12:23 ` Avi Kivity
2010-04-07 20:38 ` Richard Simpson
2010-04-07 20:48 ` Avi Kivity
2010-04-07 23:13 ` Richard Simpson
2010-04-08 7:23 ` Avi Kivity
2010-04-08 23:55 ` Richard Simpson
2010-04-10 19:34 ` Avi Kivity
2010-04-08 8:52 ` Andre Przywara
2010-04-08 21:23 ` Richard Simpson
2010-04-09 23:45 ` Andre Przywara
2010-04-12 21:15 ` Richard Simpson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BC38D58.9090802@huskydog.org.uk \
--to=rs1002@huskydog.org.uk \
--cc=andre.przywara@amd.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.