Hi,
We are now checking about what we should do on vm fail-over.
Concerning this, does anybody know about any danger about data
consistency when we are using shared disk?
What I'm concerning is if crashed VM-side host is still holding
buffered data, starting a new VM instance on another node m
Gleb Natapov kirjoitti:
On Mon, Jul 19, 2010 at 10:17:02AM +0300, Harri Olin wrote:
Gleb Natapov kirjoitti:
On Thu, Jul 15, 2010 at 03:19:44PM +0200, Christoph Adomeit wrote:
But one Windows 2008 64 Bit Server Standard is freezing regularly.
This happens sometimes 3 times a day, sometimes it t
On 07/21/2010 03:55 AM, Marcelo Tosatti wrote:
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -4709,6 +4709,19 @@ static int vcpu_enter_guest(struct kvm_vcpu *vcpu)
if (unlikely(r))
goto out;
+ inject_pending_event(vcpu);
+
+ /* enable NMI/IRQ window o
When supported by the host kernel, we can use read/write on the
PCI sysfs resource file for I/O port regions. This allows us to
avoid raw in/out commands and works with deprivileged guests via
libvirt. For uid 0 callers, we use in/out directly to avoid any
compatibility issues.
Signed-off-by: Al
On Tue, Jul 20, 2010 at 02:42:19PM -0600, Cam Macdonell wrote:
> I think I've found a bug when running a guest with vhost with less
> than 4GB of RAM.
>
> If a guest has less than 4GB of RAM, then above_4g_mem_size is 0 for
> this call to cpu_register_physical_memory() in pc_memory_init() from
> h
On Tue, Jul 20, 2010 at 04:17:07PM +0300, Avi Kivity wrote:
> Change the interrupt injection code to work from preemptible, interrupts
> enabled context. This works by adding a ->cancel_injection() operation
> that undoes an injection in case we were not able to actually enter the guest
> (this co
Xiao Guangrong wrote:
> In the speculative path, we should check guest pte's reserved bits just as
> the real processor does
>
Ping..?
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.
* Alex Williamson (alex.william...@redhat.com) wrote:
> When supported by the host kernel, we can use read/write on the
> PCI sysfs resource file for I/O port regions. This allows us to
> avoid raw in/out commands and works with deprivileged guests via
> libvirt. For uid 0 callers, we use in/out
When supported by the host kernel, we can use read/write on the
PCI sysfs resource file for I/O port regions. This allows us to
avoid raw in/out commands and works with deprivileged guests via
libvirt. For uid 0 callers, we use in/out directly to avoid any
compatibility issues.
Signed-off-by: Al
On 07/19/2010 10:53 PM, Avi Kivity wrote:
On 07/19/2010 11:06 PM, Zachary Amsden wrote:
+static void tsc_khz_changed(void *data)
{
-/* nothing */
+struct cpufreq_freqs *freq = data;
+unsigned long khz = 0;
+
+if (data)
+khz = freq->new;
+else if (!boot_cpu_has(X86_F
I think I've found a bug when running a guest with vhost with less
than 4GB of RAM.
If a guest has less than 4GB of RAM, then above_4g_mem_size is 0 for
this call to cpu_register_physical_memory() in pc_memory_init() from
hw/pc.c:922
#if TARGET_PHYS_ADDR_BITS > 32
cpu_register_physical_memory
On Sat, Jul 17, 2010 at 10:45:23AM +0200, Piotr Jaroszy??ski wrote:
> On 16 July 2010 23:58, Tom Lyon wrote:
> > The VFIO "driver" is used to allow privileged AND non-privileged processes
> > to
> > implement user-level device drivers for any well-behaved PCI, PCI-X, and
> > PCIe
> > devices.
>
> Yes, we are using Virtio drivers for networking and storage in both VMs
> with cache=none. Both VMs are running Linux 2.6.32-bpo.5-amd64 from
> Lenny Backports repositories. For VMHost, we are using a stable version
> of KVM with Linux 2.6.32.12 compiled from source code of kernel.org and
> qemu
On 07/20/2010 11:29 AM, Aurelien Jarno wrote:
It's a pitty I can't easily attend to this conference call, as it seems
a lot of decisions are taken there. Anyway let me comment the part
concerning 0.12 stable:
Is it a matter of time zone or conflict? The call has historically been
centered
On 07/20/10 08:45, Chris Wright wrote:
> 0.13
> - rc RSN (hopefully this week, top priority for anthony)
Can Cam's inter-vm shared memory device get committed for 0.13? It's
been stagnant on the list for a while now waiting for inclusion (or NAK
comments).
David
--
To unsubscribe from this list
It's a pitty I can't easily attend to this conference call, as it seems
a lot of decisions are taken there. Anyway let me comment the part
concerning 0.12 stable:
On Tue, Jul 20, 2010 at 07:45:51AM -0700, Chris Wright wrote:
> 0.12.stable
> - start w/ git tree + pull requests
> - release process i
On 07/20/2010 04:44 PM, Amos Kong wrote:
> On Tue, Jul 20, 2010 at 01:19:39PM +0300, Michael Goldish wrote:
>>
>
> Michael,
>
> Thanks for your comments. Let's simplify this method together.
>
>> On 07/20/2010 04:34 AM, Amos Kong wrote:
>>> Old method uses the mac address in the configuration fi
On Sunday, 11 July 2010 19:08:58 -0300,
Daniel Bareiro wrote:
> > > I have an installation with Debian GNU/Linux 5.0.4 amd64 with
> > > qemu-kvm 0.12.3 compiled with the source code obtained from the
> > > official site of KVM and Linux 2.6.32.12 compiled from source code
> > > of kernel.org. All
0.12.stable
- start w/ git tree + pull requests
- release process is separate from commit access
- justin will put up a tree for pull requests
- there's current backlog, what about that?
- anthony's concern with -stable is the testing (upstream tree gets more
testing than -stable)
- 0.12.5?
- p
On 07/20/2010 05:04 PM, 吴忠远 wrote:
in guest os , a module with sidt instruction was execution to get
start address of IDT.does this return the correct address of IDT in
guest OS? thanks.
Yes.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list
in guest os , a module with sidt instruction was execution to get
start address of IDT.does this return the correct address of IDT in
guest OS? thanks.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at ht
On Tue, Jul 20, 2010 at 01:19:39PM +0300, Michael Goldish wrote:
>
Michael,
Thanks for your comments. Let's simplify this method together.
> On 07/20/2010 04:34 AM, Amos Kong wrote:
> > Old method uses the mac address in the configuration files which could
> > lead serious problem when multiple
Change the interrupt injection code to work from preemptible, interrupts
enabled context. This works by adding a ->cancel_injection() operation
that undoes an injection in case we were not able to actually enter the guest
(this condition could never happen with atomic injection).
Signed-off-by: A
vmx_complete_interrupts() does too much, split it up:
- vmx_vcpu_run() gets the "cache important vmcs fields" part
- a new vmx_complete_atomic_exit() gets the parts that must be done atomically
- a new vmx_recover_nmi_blocking() does what its name says
- vmx_complete_interrupts() retains the ev
Currently vmx_complete_interrupts() can decode event information from vmx
exit fields into the generic kvm event queues. Make it able to decode
the information from the entry fields as well by parametrizing it.
Signed-off-by: Avi Kivity
---
arch/x86/kvm/vmx.c | 19 ++-
1 files
This patchset changes interrupt injection to be done from normal process
context instead of interrupts disabled context. This is useful for real
mode interrupt injection on Intel without the current hacks (injecting as
a software interrupt of a vm86 task), reducing latencies, and later, for
allowi
On Tue, 20 Jul 2010 09:07:11 +0300
Avi Kivity wrote:
> On 07/20/2010 12:46 AM, Chris Wright wrote:
> > Please send in any agenda items you are interested in covering.
> >
> >
> Last week's agenda, minus the item that we started to discuss.
(includes 0.13)
--
To unsubscribe from this list:
On Tue, Jul 20, 2010 at 08:01:15AM -0500, Neil Aggarwal wrote:
> Hello:
>
> One of my customers asked for access to stop and start
> their guest VM.
>
> Right now, I can do that using virsh, but I do not want
> to give this customer the ability to stop and start
> all VMs running on the host.
>
Hello:
One of my customers asked for access to stop and start
their guest VM.
Right now, I can do that using virsh, but I do not want
to give this customer the ability to stop and start
all VMs running on the host.
Is there a way to give stop and start control of one
VM to someone?
I am using
Currently vmx_complete_interrupts() can decode event information from vmx
exit fields into the generic kvm event queues. Make it able to decode
the information from the entry fields as well by parametrizing it.
Signed-off-by: Avi Kivity
---
arch/x86/kvm/vmx.c | 19 ++-
1 files
vmx_complete_interrupts() does too much, split it up:
- vmx_vcpu_run() gets the "cache important vmcs fields" part
- a new vmx_complete_atomic_exit() gets the parts that must be done atomically
- a new vmx_recover_nmi_blocking() does what its name says
- vmx_complete_interrupts() retains the ev
Change the interrupt injection code to work from preemptible, interrupts
enabled context. This works by adding a ->cancel_injection() operation
that undoes an injection in case we were not able to actually enter the guest
(this condition could never happen with atomic injection).
Signed-off-by: A
This patchset changes interrupt injection to be done from normal process
context instead of interrupts disabled context. This is useful for real
mode interrupt injection on Intel without the current hacks (injecting as
a software interrupt of a vm86 task), reducing latencies, and later, for
allowi
On Tue, 2010-07-20 at 09:34 +0800, Amos Kong wrote:
> The following series contain 11 network related subtests, welcome to give me
> some suggestions about correctness, design, enhancement.
Awesome work, will start to review them today. Thanks!
> Thank you so much!
>
> ---
>
> Amos Kong (14):
>
On 07/20/2010 04:34 AM, Amos Kong wrote:
> Old method uses the mac address in the configuration files which could
> lead serious problem when multiple tests running in different hosts.
>
> This patch adds a new macaddress pool algorithm, it generates the mac prefix
> based on mac address of the ho
On 07/19/2010 11:06 PM, Zachary Amsden wrote:
+static void tsc_khz_changed(void *data)
{
-/* nothing */
+struct cpufreq_freqs *freq = data;
+unsigned long khz = 0;
+
+if (data)
+khz = freq->new;
+else if (!boot_cpu_has(X86_FEATURE_CONSTANT_TSC))
+khz = cpufre
On 20.07.2010, at 09:27, Milton Miller wrote:
> On Mon, 19 Jul 2010 about 14:00:56 +0200, Alexander Graf wrote:
>> Milton Miller wrote:
>>> I wrote:
>>>
>>> Oh yea, and for book-3s, the code copies from 0x100 to __end_interrupts
>>> in arch/powerpc/kernel/exceptions-64s.h down to the real 0, but
37 matches
Mail list logo
