Dor Laor wrote:
> On Thu, 2008-05-08 at 12:03 +0200, Nicolas Daneau wrote:
>> Hi,
>>
>> I saw there was an active discussion about pci passthrough support in
>> KVM. I'm not a Dev, only a sys admin that need this support. As i saw
>> on the KVM home page that this feature is plan for 2H2008 in the
Marcelo Tosatti wrote:
> Slots 9 and 25 were using the identifier of the previous slot.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
-
This SF.net email is sponsored by the 2008 Ja
Slots 9 and 25 were using the identifier of the previous slot.
Signed-off-by: Marcelo Tosatti <[EMAIL PROTECTED]>
diff --git a/bios/acpi-dsdt.dsl b/bios/acpi-dsdt.dsl
index d2e33f4..c145c4b 100755
--- a/bios/acpi-dsdt.dsl
+++ b/bios/acpi-dsdt.dsl
@@ -269,10 +269,10 @@ DefinitionBlock (
Avi Kivity wrote:
> David Abrahams wrote:
>> Jon gmail.com> writes:
>>
>>
>>> I use:
>>>
>>> export QEMU_AUDIO_DRV=alsa
>>> export QEMU_AUDIO_DAC_FIXED_FREQ=48000
>>> export QEMU_AUDIO_ADC_FIXED_FREQ=48000
>>> export QEMU_ALSA_DAC_BUFFER_SIZE=16384
>>>
>>> Buffer size is very important, else it
David Abrahams wrote:
> Jon gmail.com> writes:
>
>
>> I use:
>>
>> export QEMU_AUDIO_DRV=alsa
>> export QEMU_AUDIO_DAC_FIXED_FREQ=48000
>> export QEMU_AUDIO_ADC_FIXED_FREQ=48000
>> export QEMU_ALSA_DAC_BUFFER_SIZE=16384
>>
>> Buffer size is very important, else it crackles and pops for me.
>>
Jon gmail.com> writes:
>
> I use:
>
> export QEMU_AUDIO_DRV=alsa
> export QEMU_AUDIO_DAC_FIXED_FREQ=48000
> export QEMU_AUDIO_ADC_FIXED_FREQ=48000
> export QEMU_ALSA_DAC_BUFFER_SIZE=16384
>
> Buffer size is very important, else it crackles and pops for me.
Unfortunately with my upgrade to Ubu
On Apr 25, 2008, at 10:39 PM, Marcelo Tosatti wrote:
> On Fri, Apr 25, 2008 at 11:38:21AM +0200, Alexander Graf wrote:
>>
>> On Apr 25, 2008, at 3:01 AM, Marcelo Tosatti wrote:
>>
>>>
>>> Add three PCI bridges to support 128 slots. Vendor and device_id
>>> have
>>> been stolen from my test box.
On Fri, Apr 25, 2008 at 11:38:21AM +0200, Alexander Graf wrote:
>
> On Apr 25, 2008, at 3:01 AM, Marcelo Tosatti wrote:
>
> >
> >Add three PCI bridges to support 128 slots. Vendor and device_id have
> >been stolen from my test box.
> >
> >I/O port addresses behind each bridge are statically alloc
Marcelo Tosatti wrote:
> Now that threads are spinned up before machine->init(), clearing
> of HF_HALTED_MASK for irqchip in kernel case needs to be moved
> to actual vcpu startup.
>
Applied, thanks.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
Now that threads are spinned up before machine->init(), clearing
of HF_HALTED_MASK for irqchip in kernel case needs to be moved
to actual vcpu startup.
Signed-off-by: Marcelo Tosatti <[EMAIL PROTECTED]>
diff --git a/qemu/qemu-kvm.c b/qemu/qemu-kvm.c
index f7a217a..50589a7 100644
--- a/qemu/qemu-
Marcelo Tosatti wrote:
> Make sure that all threads are paused in userspace before saving machine
> state.
>
>
Applied, thanks.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-
This SF.net email
Make sure that all threads are paused in userspace before saving machine
state.
Signed-off-by: Marcelo Tosatti <[EMAIL PROTECTED]>
--- kvm-userspace.io/qemu/qemu-kvm.c
+++ kvm-userspace.io/qemu/qemu-kvm.c
@@ -244,7 +244,7 @@ static int all_threads_paused(void)
int i;
for (i = 0; i <
Marcelo Tosatti wrote:
> kvm_arch_load_regs() might load APIC base and APIC TPR from the
> uninitialized userspace APIC emulation.
>
> This happened when running X11 on SMP guest in my case, disabling the
> APIC for vcpu3:
>
> vcpu not ready for apic_round_robin
> vcpu not ready for apic_round_robi
* Marcelo Tosatti <[EMAIL PROTECTED]> [2008-04-03 18:22]:
>
> kvm_arch_load_regs() might load APIC base and APIC TPR from the
> uninitialized userspace APIC emulation.
>
> This happened when running X11 on SMP guest in my case, disabling the
> APIC for vcpu3:
>
> vcpu not ready for apic_round_ro
kvm_arch_load_regs() might load APIC base and APIC TPR from the
uninitialized userspace APIC emulation.
This happened when running X11 on SMP guest in my case, disabling the
APIC for vcpu3:
vcpu not ready for apic_round_robin
vcpu not ready for apic_round_robin
vcpu not ready for apic_round_robi
Marcelo Tosatti wrote:
> Use asynchronous IO in the virtio block QEMU driver.
>
> virtio_blk_handle_output should not block for long periods, since it
> holds the mutex lock prohibiting other vcpu's from doing IO to QEMU
> devices. Without AIO write intensive benchmarks make guests hang for
> sever
Marcelo Tosatti wrote:
> Use asynchronous IO in the virtio block QEMU driver.
>
> virtio_blk_handle_output should not block for long periods, since it
> holds the mutex lock prohibiting other vcpu's from doing IO to QEMU
> devices. Without AIO write intensive benchmarks make guests hang for
> sever
Use asynchronous IO in the virtio block QEMU driver.
virtio_blk_handle_output should not block for long periods, since it
holds the mutex lock prohibiting other vcpu's from doing IO to QEMU
devices. Without AIO write intensive benchmarks make guests hang for
several seconds. Write performance als
2008/3/24, Avi Kivity <[EMAIL PROTECTED]>:
> Avi Kivity wrote:
> >>
> >>
> >> Tested - and actually seeing no difference in my case of memory leak.
> >> Still it looks like over 30M per execution of qemu is lost.
> >> (tested with fresh 2.6.25-rc6 with your patch)
> >>
> >>
> >
> > Can you
Avi Kivity wrote:
Tested - and actually seeing no difference in my case of memory leak.
Still it looks like over 30M per execution of qemu is lost.
(tested with fresh 2.6.25-rc6 with your patch)
Can you double check? 2.6.25-rc6 definitely leaks without, and here it
doesn't with the patch
Zdenek Kabelac wrote:
> 2008/3/23, Avi Kivity <[EMAIL PROTECTED]>:
>
>> Avi Kivity wrote:
>> >
>> > I see the same issue too now, and am investigating.
>> >
>>
>>
>> The attached patch should fix the issue. It is present in 2.6.25-rc6
>> only, and not in kvm.git, which is why few people not
2008/3/23, Avi Kivity <[EMAIL PROTECTED]>:
> Avi Kivity wrote:
> >
> > I see the same issue too now, and am investigating.
> >
>
>
> The attached patch should fix the issue. It is present in 2.6.25-rc6
> only, and not in kvm.git, which is why few people noticed it.
>
Hi
Tested - and actually
Avi Kivity wrote:
I see the same issue too now, and am investigating.
The attached patch should fix the issue. It is present in 2.6.25-rc6
only, and not in kvm.git, which is why few people noticed it.
--
error compiling committee.c: too many arguments to function
diff --git a/arch/x86/kv
Zdenek Kabelac wrote:
> 2008/3/19, Avi Kivity <[EMAIL PROTECTED]>:
>
>> Zdenek Kabelac wrote:
>> > 2008/3/19, Avi Kivity <[EMAIL PROTECTED]>:
>> >
>> >> Zdenek Kabelac wrote:
>> >> > 2008/3/16, Avi Kivity <[EMAIL PROTECTED]>:
>>
>> The -vnc switch, so there's no local X server. A remote X
Zdenek Kabelac wrote:
> 2008/3/19, Avi Kivity <[EMAIL PROTECTED]>:
>
>> Zdenek Kabelac wrote:
>> > 2008/3/16, Avi Kivity <[EMAIL PROTECTED]>:
>> >
>> >> Zdenek Kabelac wrote:
>> >> > Hello
>> >> >
>> >> > Recently I'm using qemu-kvm on fedora-rawhide box with my own kernels
>> >> > (w
2008/3/19, Avi Kivity <[EMAIL PROTECTED]>:
> Zdenek Kabelac wrote:
> > 2008/3/16, Avi Kivity <[EMAIL PROTECTED]>:
> >
> >> Zdenek Kabelac wrote:
> >> > Hello
> >> >
> >> > Recently I'm using qemu-kvm on fedora-rawhide box with my own kernels
> >> > (with many debug options) I've noticed
Zdenek Kabelac wrote:
> 2008/3/16, Avi Kivity <[EMAIL PROTECTED]>:
>
>> Zdenek Kabelac wrote:
>> > Hello
>> >
>> > Recently I'm using qemu-kvm on fedora-rawhide box with my own kernels
>> > (with many debug options) I've noticed that over the time my memory
>> > seems to disappear somewhere
2008/3/16, Avi Kivity <[EMAIL PROTECTED]>:
> Zdenek Kabelac wrote:
> > Hello
> >
> > Recently I'm using qemu-kvm on fedora-rawhide box with my own kernels
> > (with many debug options) I've noticed that over the time my memory
> > seems to disappear somewhere.
> >
> > Here is my memory trace
Zdenek Kabelac wrote:
> Hello
>
> Recently I'm using qemu-kvm on fedora-rawhide box with my own kernels
> (with many debug options) I've noticed that over the time my memory
> seems to disappear somewhere.
>
> Here is my memory trace after boot and some time of work - thus memory
> should be popula
Hello
Recently I'm using qemu-kvm on fedora-rawhide box with my own kernels
(with many debug options) I've noticed that over the time my memory
seems to disappear somewhere.
Here is my memory trace after boot and some time of work - thus memory
should be populated.
MemTotal: 2007460 kB
MemF
And the corresponding QEMU support to report parafeatures on cpuid.
Signed-off-by: Marcelo Tosatti <[EMAIL PROTECTED]>
Index: kvm-userspace/libkvm/libkvm.c
===
--- kvm-userspace.orig/libkvm/libkvm.c
+++ kvm-userspace/libkvm/libkvm.c
On Dec 6, 2007 5:13 AM, Uri Lublin <[EMAIL PROTECTED]> wrote:
> Lukasz Lempart wrote:
> > Hi,
> >
> > I am having a problem with starting qemu/kvm from a previously saved
> > statefile. qemu/kvm starts and the console output is the same as when
> > I initially stopped the vm and saved state. Howev
Lukasz Lempart wrote:
> Hi,
>
> I am having a problem with starting qemu/kvm from a previously saved
> statefile. qemu/kvm starts and the console output is the same as when
> I initially stopped the vm and saved state. However, after a 'cont'
> the guest reboots (i.e. takes me back to the grub m
Hi,
I am having a problem with starting qemu/kvm from a previously saved
statefile. qemu/kvm starts and the console output is the same as when I
initially stopped the vm and saved state. However, after a 'cont' the guest
reboots (i.e. takes me back to the grub menu).
The specs for my setup are as
David Abrahams wrote:
>>> "For ALSA 1.0.9rc2 and higher you don't need to setup dmix. Dmix is
>>> enabled as default for soundcards which don't support hw mixing."
>>>
>>> I've found this to be the case on my laptop, where I use:
>>>
>>> export QEMU_AUDIO_DRV=alsa
>>> export QEMU_AUDIO_DAC_FIXED_F
on Wed May 23 2007, Avi Kivity wrote:
> Jon wrote:
>> On Mon, May 21, 2007 at 08:37:48AM -0700, Shahar Frank wrote:
>>
>>
>>> You have to make QEMU use ALSA as your sound system and specify a
>>> mixer device for input and output. This can be done using some
>>> environment variables that s
Jon wrote:
> On Mon, May 21, 2007 at 08:37:48AM -0700, Shahar Frank wrote:
>
>
>> You have to make QEMU use ALSA as your sound system and specify a
>> mixer device for input and output. This can be done using some
>> environment variables that should be set before the qemu binary is
>> run.
>
David Abrahams wrote:
> on Mon May 21 2007, Avi Kivity
> wrote:
>
>
>> David Abrahams wrote:
>>
>>> When I have windows XP running under kvm, I get
>>>
>>> [EMAIL PROTECTED]:/tmp$ aplay /usr/share/sounds/gaim/receive.wav
>>> ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open
On Tuesday 22 May 2007 23:37:56 David Abrahams wrote:
> on Mon May 21 2007, Avi Kivity
wrote:
> > David Abrahams wrote:
> >> When I have windows XP running under kvm, I get
> >>
> >> [EMAIL PROTECTED]:/tmp$ aplay /usr/share/sounds/gaim/receive.wav
> >> ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_op
on Mon May 21 2007, Avi Kivity
wrote:
> David Abrahams wrote:
>> When I have windows XP running under kvm, I get
>>
>> [EMAIL PROTECTED]:/tmp$ aplay /usr/share/sounds/gaim/receive.wav
>> ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
>> aplay: main:550: audio open erro
On Mon, May 21, 2007 at 08:37:48AM -0700, Shahar Frank wrote:
> You have to make QEMU use ALSA as your sound system and specify a
> mixer device for input and output. This can be done using some
> environment variables that should be set before the qemu binary is
> run.
>From the ALSA wiki:
"
You have to make QEMU use ALSA as your sound system and specify a mixer
device for input and output. This can be done using some environment
variables that should be set before the qemu binary is run.
The following may work:
export QEMU_AUDIO_DRV=alsa # the default is OSS if I recall
corr
David Abrahams wrote:
> When I have windows XP running under kvm, I get
>
> [EMAIL PROTECTED]:/tmp$ aplay /usr/share/sounds/gaim/receive.wav
> ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
> aplay: main:550: audio open error: Device or resource busy
>
> As soon as I shut
When I have windows XP running under kvm, I get
[EMAIL PROTECTED]:/tmp$ aplay /usr/share/sounds/gaim/receive.wav
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
aplay: main:550: audio open error: Device or resource busy
As soon as I shut down my VM, though, it works perf
On Tue, Feb 27, 2007 at 05:20:27PM +0200, Avi Kivity wrote:
> Daniel P. Berrange wrote:
> >The virt-manager in Fedora Core 6 hasn't been updated to the newest
> >0.3.1 release yet - only the underling libvirt has been pushed to FC6
> >thus far.
>
> Will we see it in FC6-updates? I'd like to try
Daniel P. Berrange wrote:
> The virt-manager in Fedora Core 6 hasn't been updated to the newest
> 0.3.1 release yet - only the underling libvirt has been pushed to FC6
> thus far.
Will we see it in FC6-updates? I'd like to try it, but I'm not keen on
rawhide.
--
error compiling committee.c:
Daniel P. Berrange wrote:
> On Sun, Feb 25, 2007 at 07:32:58AM +0200, Avi Kivity wrote:
>
>> Daniel P. Berrange wrote:
>>
>>> FYI, as of libvirt 0.2.0 and virt-manager 0.3.1 there is now
>>> (experimental!)
>>> support for managing virtual machines running under QEMU or KVM
>>> virtualiz
On Sun, Feb 25, 2007 at 10:34:15AM +0200, Avi Kivity wrote:
> Avi Kivity wrote:
> >Daniel P. Berrange wrote:
> >
> >>FYI, as of libvirt 0.2.0 and virt-manager 0.3.1 there is now
> >>(experimental!)
> >>support for managing virtual machines running under QEMU or KVM
> >>virtualization
> >>platf
On Sun, Feb 25, 2007 at 07:32:58AM +0200, Avi Kivity wrote:
> Daniel P. Berrange wrote:
> >FYI, as of libvirt 0.2.0 and virt-manager 0.3.1 there is now
> >(experimental!)
> >support for managing virtual machines running under QEMU or KVM
> >virtualization
> >platforms, as well as the existing Xe
Avi Kivity wrote:
> Daniel P. Berrange wrote:
>
>> FYI, as of libvirt 0.2.0 and virt-manager 0.3.1 there is now (experimental!)
>> support for managing virtual machines running under QEMU or KVM
>> virtualization
>> platforms, as well as the existing Xen support.
>>
>>
>>
>
> Great; as
Daniel P. Berrange wrote:
> FYI, as of libvirt 0.2.0 and virt-manager 0.3.1 there is now (experimental!)
> support for managing virtual machines running under QEMU or KVM virtualization
> platforms, as well as the existing Xen support.
>
>
Great; as I see it hit FC6-updates I'll give it a shot
FYI, as of libvirt 0.2.0 and virt-manager 0.3.1 there is now (experimental!)
support for managing virtual machines running under QEMU or KVM virtualization
platforms, as well as the existing Xen support.
Project sites:
http://libvirt.org/
http://virt-manager.org/
Release announcements here:
* Simon Kagstrom <[EMAIL PROTECTED]> [061114 11:30]:
> At Tue, 14 Nov 2006 10:50:23 +0200,
> Avi Kivity wrote:
> >
> > Baruch Even wrote:
> > > Can the Qemu built with KVM support run without KVM? Froma quick perusal
> > > of the kvm.patch it seems that there are places where USE_KVM implies a
> >
At Tue, 14 Nov 2006 10:50:23 +0200,
Avi Kivity wrote:
>
> Baruch Even wrote:
> > Can the Qemu built with KVM support run without KVM? Froma quick perusal
> > of the kvm.patch it seems that there are places where USE_KVM implies a
> > qemu-panic without any runtime conditionals.
>
> qemu-kvm.patch
Baruch Even wrote:
> Can the Qemu built with KVM support run without KVM? Froma quick perusal
> of the kvm.patch it seems that there are places where USE_KVM implies a
> qemu-panic without any runtime conditionals.
>
qemu-kvm.patch is an older release. With the new release, it should be
possi
Simon Kagstrom wrote:
> At Tue, 14 Nov 2006 10:50:23 +0200,
> Avi Kivity wrote:
>
>> Baruch Even wrote:
>>
>>> Can the Qemu built with KVM support run without KVM? Froma quick perusal
>>> of the kvm.patch it seems that there are places where USE_KVM implies a
>>> qemu-panic without any runt
At Tue, 14 Nov 2006 09:26:01 +0200,
Baruch Even wrote:
>
> Can the Qemu built with KVM support run without KVM? Froma quick perusal
> of the kvm.patch it seems that there are places where USE_KVM implies a
> qemu-panic without any runtime conditionals.
There is the -no-kvm option which you can pa
Can the Qemu built with KVM support run without KVM? Froma quick perusal
of the kvm.patch it seems that there are places where USE_KVM implies a
qemu-panic without any runtime conditionals.
I'd like to push the KVM patches to Debian Qemu and need to know if they
need to create new executables or j
58 matches
Mail list logo
