>> Actually we're in the middle of developing pci pass through support
>> for enabling physical device pass through for guests. It's work in
>> progress but eventually we'll post the code to the list.
>
>Cool. Are you relying on an isolation-capable IOMMU or using the
>Neocleus approach?
Actually
>> Hello Dor,
>>
>> Thank you so much for the quick reply.
>>
>> My project is to run a qnx4.4 legacy application (which talks
>> to custom made hardware) on virtualized environment. I am
>> using KVM for that and am able to read and write to the actual
>> hardware. I used serial driver in qemu as
On Wed, Aug 08, 2007 at 12:03:03AM -0700, Dor Laor wrote:
> Actually we'll do both.
Doubly cool. Looking forward to more information.
Cheers,
Muli
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log
I've never encountered that problem.
I haven't used "exec" migration protocol too many times though.
I have not used libvirt too many times either.
I'll look into it too.
Thanks,
Uri.
Jim Paris wrote:
> I wrote:
>
>> It's almost as if migrate_write() is being called after
>> migrate_finish()
Bugs item #1769884, was opened at 2007-08-08 17:43
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1769884&group_id=180599
Please note that this message will contain a full copy
Avi:
We (Yunfeng) encountered some warning from KVM in certain
situation like:
"kvm: 9612: cpu0 unhandled wrmsr: 0xc1"
Further check find that we are doing MSR write virtualization
per a predefined whitelist and give gp fault for others. On the other
hand, Xen just silently return (
A new issue has been found:
Fails to boot linux guests with 2.6.22 kernel
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1769884&group_id=180599
>-Original Message-
>From: Zhao, Yunfeng
>Sent: 2007年8月6日 15:45
>To: 'kvm-devel@lists.sourceforge.net'
>Cc: Zhao, Yunfeng
>Subject
The patch below removes individual control register definitions from
struct kvm_vcpu and replaces them with an array similar to general
purpose registers.
When splitting kvm_vcpu in architecture dependent and architecture
independent parts, this will allow to keep the control registers in the
archi
Dong, Eddie wrote:
> Avi:
> We (Yunfeng) encountered some warning from KVM in certain
> situation like:
> "kvm: 9612: cpu0 unhandled wrmsr: 0xc1"
> Further check find that we are doing MSR write virtualization
> per a predefined whitelist and give gp fault for others. On the other
> han
Carsten Otte wrote:
> The patch below removes individual control register definitions from
> struct kvm_vcpu and replaces them with an array similar to general
> purpose registers.
> When splitting kvm_vcpu in architecture dependent and architecture
> independent parts, this will allow to keep the
Avi Kivity wrote:
> I don't think we should aim for keeping control registers in an arch
> independent manner, since there is nothing common among the different
> architectures in that area. For x86, keeping them in an array is not
> helpful since the individual control registers have nothing t
Avi Kivity wrote:
> Anthony Liguori wrote:
>
>> I don't think adding annotations as snapshots is the right approach. I
>> think proper support should be added in the header. I wouldn't be too
>> concerned with breaking compatibility in qcow2. That's why it's qcow2
>> and not just an update
On 8/8/07, Anthony Liguori <[EMAIL PROTECTED]> wrote:
> Avi Kivity wrote:
> > Anthony Liguori wrote:
> >
> >> I don't think adding annotations as snapshots is the right approach. I
> >> think proper support should be added in the header. I wouldn't be too
> >> concerned with breaking compatibilit
This patch adds an extra 'annot' field to qcow2 snapshots, and updates
serialization functions.
Signed-off-by: Jorge Lucángeli Obes <[EMAIL PROTECTED]>
---
diff --git a/qemu/block-qcow2.c b/qemu/block-qcow2.c
index 0f7a069..361d300 100644
--- a/qemu/block-qcow2.c
+++ b/qemu/block-qcow2.c
@@ -106,6
This patch adds block driver functions to use qcow2 image annotations.
Signed-off-by: Laurent Vivier <[EMAIL PROTECTED]>
Signed-off-by: Jorge Lucángeli Obes <[EMAIL PROTECTED]>
---
diff --git a/qemu/block.c b/qemu/block.c
index 39ec37a..4d794f6 100644
--- a/qemu/block.c
+++ b/qemu/block.c
@@ -56,6
This patch adds a new qemu-img option to store
command line arguments in qcow2 snapshots.
Signed-off-by: Laurent Vivier <[EMAIL PROTECTED]>
Signed-off-by: Jorge Lucángeli Obes <[EMAIL PROTECTED]>
---
diff --git a/qemu/qemu-img.c b/qemu/qemu-img.c
index a259546..afa1fcc 100644
--- a/qemu/qemu-img.c
This patch makes QEMU check for command line options stored in qcow2 images.
Signed-off-by: Laurent Vivier <[EMAIL PROTECTED]>
Signed-off-by: Jorge Lucángeli Obes <[EMAIL PROTECTED]>
---
diff --git a/qemu/vl.c b/qemu/vl.c
index 4ad39f1..1d28794 100644
--- a/qemu/vl.c
+++ b/qemu/vl.c
@@ -184,6 +184
This should go through qemu-devel BTW. Please submit there and I'll
provide comments.
Regards,
Anthony Liguori
Jorge Lucángeli Obes wrote:
> This patch adds an extra 'annot' field to qcow2 snapshots, and updates
> serialization functions.
>
> Signed-off-by: Jorge Lucángeli Obes <[EMAIL PROTECT
If *has_error==0, s is freed before s->detach is used. Save a copy of
s->detach earlier.
Signed-off-by: Jim Paris <[EMAIL PROTECTED]>
---
This shouldn't change much since the memory is most likely still
valid even after it's been freed, but it's still a bug.
qemu/migration.c |3 ++-
1 file
If readline_handle_byte() is sent both a CR and LF, and
readline_start() is not called after the first CR, then the LF will
cause the same command to be executed a second time. Fix this by
explicitly resetting the buffer pointer when it is processed.
Signed-off-by: Jim Paris <[EMAIL PROTECTED]>
-
I think I've (finally!) tracked it down. See the attached patches.
The main problem is this: when using "-monitor pty", all incoming
commands are terminated with CRLF even though they were sent with just
LF, probably because of the pty layer somewhere. When qemu's readline
gets CR and LF without
Signed-off-by: Jim Paris <[EMAIL PROTECTED]>
---
Having two migrations run simultaneously was causing my crashes.
The command was sent twice because of a bug in the readline routines,
but adding a check here as well seems like a good idea.
qemu/migration.c |6 ++
1 files changed, 6 inse
ia64 allmodconfig says
drivers/kvm/Kconfig:14:warning: 'select' used by config symbol 'KVM' refers to
undefined symbol 'PREEMPT_NOTIFIERS'
Because of
commit 8928fb48c7a7f9053a55f1d0023cbc533f2b3663
Author: Avi Kivity <[EMAIL PROTECTED]>
Date: Wed Jul 11 18:17:21 2007 +0300
KVM: Use the
* Andrew Morton <[EMAIL PROTECTED]> wrote:
> ia64 allmodconfig says
>
> drivers/kvm/Kconfig:14:warning: 'select' used by config symbol 'KVM'
> refers to undefined symbol 'PREEMPT_NOTIFIERS'
hm, why doesnt ia64 pick up kernel/Kconfig.preempt, like all the other
arches? Due to that ia64 also mi
Ingo Molnar wrote:
> * Andrew Morton <[EMAIL PROTECTED]> wrote:
>
>
>> ia64 allmodconfig says
>>
>> drivers/kvm/Kconfig:14:warning: 'select' used by config symbol 'KVM'
>> refers to undefined symbol 'PREEMPT_NOTIFIERS'
>>
>
> hm, why doesnt ia64 pick up kernel/Kconfig.preempt, like all the
On Thu, 09 Aug 2007 01:48:07 +0300
Avi Kivity <[EMAIL PROTECTED]> wrote:
> Ingo Molnar wrote:
> > * Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> >
> >> ia64 allmodconfig says
> >>
> >> drivers/kvm/Kconfig:14:warning: 'select' used by config symbol 'KVM'
> >> refers to undefined symbol 'PREEM
Andrew Morton wrote:
> On Thu, 09 Aug 2007 01:48:07 +0300
> Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>
>> Ingo Molnar wrote:
>>
>>> * Andrew Morton <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>>
ia64 allmodconfig says
drivers/kvm/Kconfig:14:warning: 'select' used by config s
27 matches
Mail list logo
