On 08/27/2013 11:06 AM, Richard W.M. Jones wrote:
On Thu, Aug 22, 2013 at 03:09:06PM -0500, Anthony Liguori wrote:
Paolo Bonzini pbonz...@redhat.com writes:
Also, a virtio watchdog device makes little sense, IMHO. PV makes sense
if emulation has insufficient performance, excessive CPU usage,
How about adding a flag that tells QEMU whether to pause or reboot the guest
after the panic?
We cannot assume that we always have a management layer that takes care
of this.
One example is Microsoft's WHQL that deliberately generates a BSOD, and then
examines the dump files.
Ronen.
On
On 07/18/2013 05:28 PM, Anthony Liguori wrote:
Marcel Apfelbaum marce...@redhat.com writes:
Categorize devices that appear as output to -device ? command
by logical functionality. Sort the devices by logical categories
before showing them to user.
Signed-off-by: Marcel Apfelbaum
On 12/19/2012 11:32 AM, Gleb Natapov wrote:
On Wed, Dec 19, 2012 at 03:24:45PM +0800, Amos Kong wrote:
Current seabios will try to boot from selected devices first,
if they are all failed, seabios will also try to boot from
un-selected devices.
For example:
@ qemu-kvm -boot order=n,menu=on ...
On 01/01/2012 12:16 PM, Dor Laor wrote:
On 12/29/2011 06:16 PM, Anthony Liguori wrote:
On 12/29/2011 10:07 AM, Dor Laor wrote:
On 12/26/2011 11:05 AM, Avi Kivity wrote:
On 12/26/2011 05:14 AM, Nikunj A Dadhania wrote:
btw you can get an additional speedup by enabling x2apic, for
On 12/21/2011 11:42 PM, Alex Williamson wrote:
Including rationale for design, example usage and API description.
Signed-off-by: Alex Williamsonalex.william...@redhat.com
---
Documentation/vfio.txt | 352
1 files changed, 352 insertions(+),
On 12/20/2011 03:39 PM, Anthony Liguori wrote:
On 12/20/2011 01:06 AM, Ronen Hod wrote:
Well the issue is not new, anyhow, following a conversation with Orit
...
Since we want the migration to finish, I believe that the migration
speed
parameter alone cannot do the job.
I suggest using two
Well the issue is not new, anyhow, following a conversation with Orit ...
Since we want the migration to finish, I believe that the migration
speed parameter alone cannot do the job.
I suggest using two distinct parameters:
1. Migration speed - will be used to limit the network resources
to 0/1 (correctly).
Acked-by: Ronen Hod r...@redhat.com
Signed-off-by: Gleb Natapovg...@redhat.com
diff --git a/vl.c b/vl.c
index 624da0f..641629b 100644
--- a/vl.c
+++ b/vl.c
@@ -460,8 +460,11 @@ int qemu_timedate_diff(struct tm *tm)
if (rtc_date_offset == -1)
if (rtc_utc
On 09/09/2011 06:28 PM, al pat wrote:
We are doing an experiment with kvm-clock to validate its
effectiveness, particularly when running NTP on the host to make sure
the host’s clock stays properly sync.
Our observations leads us to a few unanswered questions, including the
possibility of a
Well, we want to support Microsoft's VSS, and that requires a guest
agent that communicates with all the writers (applications), waiting
for them to flush their app data in order to generate a consistent
app-level snapshot. The VSS platform does most of the work.
Still, at the bottom line, the
On 06/22/2011 09:55 PM, Michael Roth wrote:
Goal:
Provide a mechanism, similar to vmware and virtualbox guest tools
ISOs, that allows us to easily distribute guest tools (and potentially
drivers) for linux and windows guests.
Advantages (rough list to start the discussion, feel free to
12 matches
Mail list logo
