On Fri, Jul 20, 2012 at 11:27:40AM -0400, Jason Baron wrote:
> On Thu, Jul 05, 2012 at 05:07:43PM +0200, Alexander Graf wrote:
> > On 07/05/2012 04:06 PM, Jason Baron wrote:
> > >On Wed, Jul 04, 2012 at 10:33:18AM +0200, Alexander Graf wrote:
> > >>On 04.07.2012, at 03:29, Jason Baron wrote:
> > >>
I ran strace while running the test and I see few times:
open("/srv/kvm/iso/ubuntu-12.04-server-amd64.iso", O_RDONLY|O_NONBLOCK) = 12
fstat(12, {st_mode=S_IFREG|0666, st_size=717533184, ...}) = 0
close(12)
But the final open looks like this:
open("/srv/kvm/iso/ubuntu-12.04-server-amd64.iso",
O_R
Public bug reported:
When issuing a "change" command via the monitor, qemu is unable to open
the iso file if it is mounted on a read-only nfs share. If I mount read-
write (and make sure the file is writable by the qemu process), then the
change command succeeds. Note that this doesn't affect medi
On Sun, Jul 22, 2012 at 12:30 PM, Sheldon wrote:
> I find there are four kinds of uri for qmp_migrate
> "tcp:", "exec:", "unix:", and "fd:"
>
>
> now I want to migrate the vm to a local file with "exec:" uri by
> hmp-command.
>
> How should I do the migration?
>
(qemu) migrate -d exec:cat>/tmp/vm
I find there are four kinds of uri for qmp_migrate
"tcp:", "exec:", "unix:", and "fd:"
now I want to migrate the vm to a local file with "exec:" uri by
hmp-command.
How should I do the migration?
Hi all,
I've been looking at the git.qemu.org OpenBIOS git-svn mirror, and it
seems that the mirror is out of date. The git.qemu.org mirror indicates
that the last commit is r1057, whereas the current commit in OpenBIOS
SVN trunk is r1061.
ATB,
Mark.
On Fri, Jul 20, 2012 at 10:59:22AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> Quick review, giving me the opportunity for a quick v2 before
> disappearing into my summer vacation, fixing the nits pointed
> out by Kevin.
>
> The series also got a third commit which moves the usb mass
> storage define
On 2012-07-21 14:57, Peter Maydell wrote:
> On 21 July 2012 13:35, Jan Kiszka wrote:
>> On 2012-07-21 14:17, Peter Maydell wrote:
>>> You still haven't really explained why we can't just ignore irqfd
>>> for now. I don't see how it would particularly affect the design
>>> of the kernel implementat
On Sat, Jul 21, 2012 at 05:52:59PM +0530, Vijay Bellur wrote:
> On 07/21/2012 01:59 PM, Bharata B Rao wrote:
> >We now
> >specify the gluster backed image like this:
> >
> >-drive file=gluster:server@port:volname:image
> >
> >- Here 'gluster' is the protocol.
> >- 'server@port' specifies the server
On 07/21/2012 01:59 PM, Bharata B Rao wrote:
We now
specify the gluster backed image like this:
-drive file=gluster:server@port:volname:image
- Here 'gluster' is the protocol.
- 'server@port' specifies the server where the volume file specification for
the given volume resides. 'port' is the
On 21 July 2012 13:35, Jan Kiszka wrote:
> On 2012-07-21 14:17, Peter Maydell wrote:
>> You still haven't really explained why we can't just ignore irqfd
>> for now. I don't see how it would particularly affect the design
>> of the kernel implementation very much, and the userspace interface
>> se
From: Stefan Weil
Since commit 541dc0d47f10973c241e9955afc2aefc96adec51,
some new packed structures were added without using QEMU_PACKED.
QEMU_PACKED is needed for compilations with MinGW.
For other platforms nothing changes.
The code was fixed using this command:
git grep -la '__attribute
From: Stefan Weil
Commit 0d936928ef87ca1bb7b41b5b89c400c699a7691c removed code,
but left the related comment at a location where it no longer
belongs to.
The patch moves the comment to the correct callback and improves the text.
Signed-off-by: Stefan Weil
Signed-off-by: Stefan Hajnoczi
---
h
From: Alexey Kardashevskiy
By default mingw-gcc is trying to pack structures the way to
preserve binary compatibility with MS Visual C what leads to
incorrect and unexpected padding in the PCI bus ranges property of
the sPAPR PHB.
The patch replaces __attribute__((packed)) with more strict QEMU_
On 07/21/2012 09:12 AM, Wen Congyang wrote:
> +#define KVM_PV_PORT (0x505UL)
> +
> #ifdef __KERNEL__
> #include
>
> @@ -221,6 +223,11 @@ static inline void kvm_disable_steal_time(void)
> }
> #endif
>
> +static inline unsigned int kvm_arch_pv_features(void)
> +{
> + return inl(KVM_PV_P
From: Stefan Weil
Hopefully they will be eliminated one day.
Signed-off-by: Stefan Weil
Signed-off-by: Stefan Hajnoczi
---
docs/usb-storage.txt |2 +-
qemu-options.hx |4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/usb-storage.txt b/docs/usb-storage.t
On 2012-07-21 14:17, Peter Maydell wrote:
> On 21 July 2012 12:08, Jan Kiszka wrote:
>> On 2012-07-21 12:53, Peter Maydell wrote:
>>> This is still sounding like "there is an extra feature which you should
>>> probably implement at some point and should certainly design with the
>>> intention of s
From: Peter Maydell
Commit 946fb27c1 moved all the uses of all_cpu_threads_idle()
into cpus.c. This means we can mark the function 'static'
(again), if we shuffle it a bit earlier in the source file.
Signed-off-by: Peter Maydell
Signed-off-by: Stefan Hajnoczi
---
cpus.c| 52
From: "Mao, Junjie"
This patch makes Qemu recognize the PCID feature specified from configuration
or command line options.
Signed-off-by: Junjie Mao
Signed-off-by: Stefan Hajnoczi
---
target-i386/cpu.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target-i386/cpu.c b
The following changes since commit 61dc008f3529fa74a63aad1907438dad857e255a:
Revert "audio: Make PC speaker audio card available by default" (2012-07-19
18:25:52 -0500)
are available in the git repository at:
git://github.com/stefanha/qemu.git trivial-patches
for you to fetch changes up to
On 21 July 2012 12:08, Jan Kiszka wrote:
> On 2012-07-21 12:53, Peter Maydell wrote:
>> This is still sounding like "there is an extra feature which you should
>> probably implement at some point and should certainly design with the
>> intention of supporting", not "you cannot have an irqchip with
On Mon, Jul 16, 2012 at 2:37 PM, X O wrote:
> Hello,
>
> I suspect upgrading my system to glibc-2.15 was a mistake. It seems to
> be qemu-1.0.1, and latter versions including qemu-1.1.1, can't be
> compiled anymore. Yes, I did search around and that led me to glibc,
> resp. http://sourceware.org/m
On 2012-07-21 12:53, Peter Maydell wrote:
> On 21 July 2012 11:22, Jan Kiszka wrote:
>> On 2012-07-21 11:56, Peter Maydell wrote:
>>> Or are you trying to talk about defining interrupt routes when the
>>> source and destination are both kernel code but the route needs to
>>> be set by userspace (i
On 21 July 2012 11:22, Jan Kiszka wrote:
> On 2012-07-21 11:56, Peter Maydell wrote:
>> Or are you trying to talk about defining interrupt routes when the
>> source and destination are both kernel code but the route needs to
>> be set by userspace (ie is machine specific not cpu specific)?
>
> It
On 2012-07-21 11:56, Peter Maydell wrote:
> On 21 July 2012 10:44, Jan Kiszka wrote:
>> On 2012-07-21 11:30, Peter Maydell wrote:
>>> On 21 July 2012 10:14, Jan Kiszka wrote:
On 2012-07-21 10:54, Peter Maydell wrote:
> On 21 July 2012 07:57, Jan Kiszka wrote:
Naming is x86 specific
On 21 July 2012 10:44, Jan Kiszka wrote:
> On 2012-07-21 11:30, Peter Maydell wrote:
>> On 21 July 2012 10:14, Jan Kiszka wrote:
>>> On 2012-07-21 10:54, Peter Maydell wrote:
On 21 July 2012 07:57, Jan Kiszka wrote:
>>> Naming is x86 specific, semantic not. It means that KVM doesn't prevent
On Mon, Jul 16, 2012 at 12:10 PM, Stefan Hajnoczi wrote:
> On Sun, Jul 15, 2012 at 09:38:25PM +0200, Laszlo Ersek wrote:
>> ... after commit 417c9d72 ("configure: add -Werror to QEMU_CFLAGS early")
>>
>> Signed-off-by: Laszlo Ersek
>> ---
>> configure |2 +-
>> 1 files changed, 1 insertions(
On Fri, Jul 20, 2012 at 11:26:02PM +0200, Stefan Weil wrote:
> Hopefully they will be eliminated one day.
>
> Signed-off-by: Stefan Weil
> ---
> docs/usb-storage.txt |2 +-
> qemu-options.hx |4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
Thanks, applied to the trivial
On Fri, Jul 20, 2012 at 11:04:49PM +0200, Stefan Weil wrote:
> Commit 0d936928ef87ca1bb7b41b5b89c400c699a7691c removed code,
> but left the related comment at a location where it no longer
> belongs to.
>
> The patch moves the comment to the correct callback and improves the text.
>
> Signed-off-
On Thu, Jul 19, 2012 at 04:52:27PM +0100, Peter Maydell wrote:
> Commit 946fb27c1 moved all the uses of all_cpu_threads_idle()
> into cpus.c. This means we can mark the function 'static'
> (again), if we shuffle it a bit earlier in the source file.
>
> Signed-off-by: Peter Maydell
> ---
> cpus.c
On Wed, Jul 18, 2012 at 06:12:37PM +0200, Stefan Weil wrote:
> Since commit 541dc0d47f10973c241e9955afc2aefc96adec51,
> some new packed structures were added without using QEMU_PACKED.
>
> QEMU_PACKED is needed for compilations with MinGW.
> For other platforms nothing changes.
>
> The code was f
On 2012-07-21 11:30, Peter Maydell wrote:
> On 21 July 2012 10:14, Jan Kiszka wrote:
>> On 2012-07-21 10:54, Peter Maydell wrote:
>>> On 21 July 2012 07:57, Jan Kiszka wrote:
On 2012-07-20 21:14, Peter Maydell wrote:
> I'm sure this isn't the only x86ism in the KVM generic source
> f
On Fri, Jul 20, 2012 at 07:08:21AM +, Mao, Junjie wrote:
> This patch makes Qemu recognize the PCID feature specified from configuration
> or command line options.
>
> Signed-off-by: Junjie Mao
> ---
> target-i386/cpu.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Thanks,
On Wed, Jul 18, 2012 at 05:41:36PM +0200, Alexander Graf wrote:
> On 07/18/2012 05:40 PM, Stefan Weil wrote:
> >Am 18.07.2012 10:22, schrieb Alexey Kardashevskiy:
> >>By default mingw-gcc is trying to pack structures the way to
> >>preserve binary compatibility with MS Visual C what leads to
> >>in
On Tue, Jul 17, 2012 at 08:28:40PM +0100, Peter Maydell wrote:
> On 17 July 2012 20:24, Stefan Weil wrote:
> > The arguments why -Werror is a bad idea for some configure tests
> > are reasonable.
> >
> > Nevertheless the QEMU community was able to produce thousands of
> > lines of code which compi
On 21 July 2012 10:14, Jan Kiszka wrote:
> On 2012-07-21 10:54, Peter Maydell wrote:
>> On 21 July 2012 07:57, Jan Kiszka wrote:
>>> On 2012-07-20 21:14, Peter Maydell wrote:
I'm sure this isn't the only x86ism in the KVM generic source
files. However the thing I'm specifically trying t
On 2012-07-21 10:54, Peter Maydell wrote:
> On 21 July 2012 07:57, Jan Kiszka wrote:
>> On 2012-07-20 21:14, Peter Maydell wrote:
>>> I'm sure this isn't the only x86ism in the KVM generic source
>>> files. However the thing I'm specifically trying to do is
>>> nuke all the uses of kvm_irqchip_in_
Ping?
patchwork url: http://patchwork.ozlabs.org/patch/169860/
-- PMM
On 9 July 2012 15:28, Peter Maydell wrote:
> The qemu_chr_new() function doesn't set errno on failure, so
> don't print strerror(errno) on the error handling path when
> dealing with the -serial, -parallel and -virtioconsole
On 21 July 2012 00:23, Catalin Patulea wrote:
> On Mon, Jul 16, 2012 at 5:19 PM, Peter Maydell
> wrote:
>> On 16 July 2012 21:11, Catalin Patulea wrote:
>>> To build/run the tests:
>>> $ cd $BUILD_PATH/tests/tcg
>>> $ SRC_PATH=path/to/qemu make
>>>
>>> Signed-off-by: Catalin Patulea
>>> ---
>
On 20 July 2012 23:48, Catalin Patulea wrote:
> On Tue, Jul 17, 2012 at 10:49 AM, Catalin Patulea wrote:
>> > the Windows build would not put the fields 'mantissa' and
>> > 'one' in the same 64 bit word, it would insert a padding bit.
>> Since floatx80 is not part of a Windows API (in fact, it's
On 20 July 2012 22:14, Anthony Liguori wrote:
> Handle is uninitialized which causes the configure check to fail.
Do keep up at the back :-). I posted a whole series earlier this
week which among other things fixes a whole pile of these
-Werror related configure issues.
http://lists.gnu.org/archi
On 21 July 2012 07:57, Jan Kiszka wrote:
> On 2012-07-20 21:14, Peter Maydell wrote:
>> I'm sure this isn't the only x86ism in the KVM generic source
>> files. However the thing I'm specifically trying to do is
>> nuke all the uses of kvm_irqchip_in_kernel() in common code,
>
> No, "irqchip in ker
We can know the guest is panicked when the guest runs on xen.
But we do not have such feature on kvm.
Another purpose of this feature is: management app(for example:
libvirt) can do auto dump when the guest is panicked. If management
app does not do auto dump, the guest's user can do dump by hand
At 07/21/2012 03:19 PM, Jan Kiszka Wrote:
> On 2012-07-21 09:12, Wen Congyang wrote:
>> We can know the guest is panicked when the guest runs on xen.
>> But we do not have such feature on kvm.
>>
>> Another purpose of this feature is: management app(for example:
>> libvirt) can do auto dump when th
block: gluster as block backend
From: Bharata B Rao
This patch adds gluster as the new block backend in QEMU. This gives QEMU
the ability to boot VM images from gluster volumes.
Signed-off-by: Bharata B Rao
---
block/Makefile.objs |1
block/gluster.c | 483 +
qemu: Add a config option for GlusterFS as block backend
From: Bharata B Rao
Signed-off-by: Bharata B Rao
---
configure | 34 ++
1 files changed, 34 insertions(+), 0 deletions(-)
diff --git a/configure b/configure
index 500fe24..03547b9 100755
--- a/configu
Hi,
Here is the v2 patchset for supporting GlusterFS protocol from QEMU.
This set of patches enables QEMU to boot VM images from gluster volumes.
This is achieved by adding gluster as a new block backend driver in QEMU.
Its already possible to boot from VM images on gluster volumes, but this
patc
Luiz Capitulino writes:
> Allow for specifying an alias for each option name, see next commits
> for examples.
>
> Signed-off-by: Luiz Capitulino
> ---
> qemu-option.c | 5 +++--
> qemu-option.h | 1 +
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/qemu-option.c b/qemu-opti
Luiz Capitulino writes:
> Call qemu_opt_set() instead of duplicating opt_set().
>
> Signed-off-by: Luiz Capitulino
> ---
> qemu-option.c | 28 +---
> 1 file changed, 1 insertion(+), 27 deletions(-)
>
> diff --git a/qemu-option.c b/qemu-option.c
> index bb3886c..2cb2835 1
On 2012-07-21 09:12, Wen Congyang wrote:
> We can know the guest is panicked when the guest runs on xen.
> But we do not have such feature on kvm.
>
> Another purpose of this feature is: management app(for example:
> libvirt) can do auto dump when the guest is panicked. If management
> app does no
The qom device uses a fixed PIO port that might conflict
with (non-Linux) guest expectations and/or future device models.
So allow the user to disable it.
Signed-off-by: Wen Congyang
---
hw/pc_piix.c|6 +-
qemu-config.c |4
qemu-options.hx |3 ++-
3 files changed, 11 i
If the target is x86/x86_64, the guest's kernel will write 0x01 to the
port KVM_PV_PORT when it is panciked. This patch introduces a new qom
device kvm_pv_ioport to listen this I/O port, and deal with panicked
event according to panicked_action's value. The possible actions are:
1. emit QEVENT_GUES
This event will be emited when the guest is panicked.
Signed-off-by: Wen Congyang
---
monitor.c |1 +
monitor.h |1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/monitor.c b/monitor.c
index 09aa3cd..a388e61 100644
--- a/monitor.c
+++ b/monitor.c
@@ -458,6 +458,7 @@ sta
The guest will be in this state when it is panicked.
Signed-off-by: Wen Congyang
---
qapi-schema.json |6 +-
qmp.c|3 ++-
vl.c |7 ++-
3 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index a92adb1..58
Corresponding kvm.git hash: 37e41afa and apply my patch for kvm
Signed-off-by: Wen Congyang
---
linux-headers/asm-x86/kvm_para.h |2 ++
linux-headers/linux/kvm_para.h |6 ++
2 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/linux-headers/asm-x86/kvm_para.h b/linux-head
The guest should run after reseting it, but it does not run if its
old state is RUN_STATE_INTERNAL_ERROR or RUN_STATE_PAUSED.
We don't set runstate to RUN_STATE_PAUSED when reseting the guest,
so the runstate will be changed from RUN_STATE_INTERNAL_ERROR or
RUN_STATE_PAUSED to RUN_STATE_RUNNING(no
We can know the guest is panicked when the guest runs on xen.
But we do not have such feature on kvm.
Another purpose of this feature is: management app(for example:
libvirt) can do auto dump when the guest is panicked. If management
app does not do auto dump, the guest's user can do dump by hand
57 matches
Mail list logo
