On 10/16/2009 07:45 PM, Antoine Martin wrote:
Hi,
Is there an easy way that I have missed to share a virtual disk
read-only between many guests whilst still having the ability to update
it occasionally from the host?
That's very fragile, since the guest won't expect the disk to change
un
Avi Kivity пишет:
On 10/16/2009 07:45 PM, Antoine Martin wrote:
Hi,
Is there an easy way that I have missed to share a virtual disk
read-only between many guests whilst still having the ability to update
it occasionally from the host?
That's very fragile, since the guest won't expect the disk
On Thu, Oct 15, 2009 at 05:48:19PM +0200, Michael S. Tsirkin wrote:
> On Thu, Oct 15, 2009 at 10:18:18AM -0500, Anthony Liguori wrote:
> > Michael S. Tsirkin wrote:
> >> On Thu, Oct 15, 2009 at 08:32:03AM -0500, Anthony Liguori wrote:
> >>
> >>> Michael S. Tsirkin wrote:
> >>>
> On Wed
Commit 705c5323 opened the doors of hell by unconditionally injecting
single-step flags as long as guest_debug signaled this. This doesn't
work when the guest branches into some interrupt or exception handler
and triggers a vmexit with flag reloading.
Fix it by saving cs:rip when user space reques
Push the NMI-related singlestep variable into vcpu_svm. It's dealing
with an AMD-specific deficit, nothing generic for x86.
Signed-off-by: Jan Kiszka
---
arch/x86/include/asm/kvm_host.h |1 -
arch/x86/kvm/svm.c | 12 +++-
2 files changed, 7 insertions(+), 6 deletions(
Hi,
I've had this problem before and worked around it using scripts, but
this seems to happen a lot more now that a host has been upgraded to
2.6.31.4 (could just be me noticing more too)
After the guest kernel shuts off, the qemu process ends up spinning,
consuming 200% cpu (both cores!) and str
On Sun, Oct 18, 2009 at 01:24:54PM +0200, Jan Kiszka wrote:
> Push the NMI-related singlestep variable into vcpu_svm. It's dealing
> with an AMD-specific deficit, nothing generic for x86.
>
> Signed-off-by: Jan Kiszka
Acked-by: Gleb Natapov
> ---
>
> arch/x86/include/asm/kvm_host.h |1 -
>
Michael Tokarev wrote:
> Avi Kivity пишет:
>> On 10/16/2009 07:45 PM, Antoine Martin wrote:
>>> Hi,
>>>
>>> Is there an easy way that I have missed to share a virtual disk
>>> read-only between many guests whilst still having the ability to update
>>> it occasionally from the host?
>>
>> That's ver
Hello:
I am looking at the RHEL 5.4 virtualization guide.
According to Chapter 17, if I want to use KVM on my
machine, I need to check if it has the constant Time Stamp
Counter by running this:
cat /proc/cpuinfo | grep constant_tsc
When I do that on the server (Currently running CentOS 5.3),
I
I forgot to mention that I have an AMD Opteron 2210
processor.
When I get cat /proc/cpuinfo, I get this output for the
first core (The second core is the same):
vendor_id : AuthenticAMD
cpu family : 15
model : 65
model name : Dual-Core AMD Opteron(tm) Processor 2210
step
> > so, setup with
> > opcontrol --deinit; modprobe oprofile timer=1; opcontrol --start
> >
> Use 'opreport -l'. Make sure your qemu isn't stripped.
ok ... will do
>
> > Try to start without timer=1 hung up my physical machine after daemon is
> > started:
>
> Is there an oops in dmesg, o
> > > so, setup with
> > > opcontrol --deinit; modprobe oprofile timer=1; opcontrol --start
> > >
>
> > Use 'opreport -l'. Make sure your qemu isn't stripped.
Build kvm-86 with "./configure ... --disable-strip"
and paused vm, now I got:
opreport -l
CPU: CPU with timer interrupt, speed 0 MHz
On 10/19/2009 03:47 AM, Daniel Schwager wrote:
Build kvm-86 with "./configure ... --disable-strip"
and paused vm, now I got:
opreport -l
CPU: CPU with timer interrupt, speed 0 MHz (estimated)
Profiling through timer interrupt
samples %image name app name
symbol name
11218
Bugs item #2880336, was opened at 2009-10-16 00:46
Message generated for change (Settings changed) made by jiajun
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2880336&group_id=180599
Please note that this message will contain a full copy of the comment
On Sunday, October 18, 2009 8:30 AM Marcelo Tosatti wrote:
> On Fri, Oct 16, 2009 at 04:06:49PM +0800, Xu, Jiajun wrote:
>> Hi All,
>>
>> This Weekly KVM Testing Report against lastest kvm.git
>> 604b0ca1fc3c0d45e404db97482f9febe001c685 and qemu-kvm.git
>> 47e465f031fc43c53ea8f08fa55cc3482c6435c8
On 10/18/2009 09:25 PM, Antoine Martin wrote:
The idea is to move the original _unmodified_ image out of the way but keep
it. All guests who have it open now will keep it open and will not see the
changes. But you now require at least 2x space - for old image and for the
new one. Or more, if yo
Bugs item #2880337, was opened at 2009-10-16 00:47
Message generated for change (Comment added) made by jiajun
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2880337&group_id=180599
Please note that this message will contain a full copy of the comment th
Bugs item #2723366, was opened at 2009-03-31 07:00
Message generated for change (Comment added) made by jiajun
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2723366&group_id=180599
Please note that this message will contain a full copy of the comment th
On 10/15/2009 09:17 PM, Christoph Hellwig wrote:
So can we please get the detailed setup where this happens, that is:
Here's a setup where it doesn't happen (pwrite() + fdatasync() get to
the disk):
filesystem used in the guest
ext4
any volume manager / software raid used in t
19 matches
Mail list logo
