Quoting Alex Bligh (a...@alex.org.uk):
>
> On 29 Sep 2014, at 11:08, Michael S. Tsirkin wrote:
>
> > On Sun, Sep 28, 2014 at 09:33:08PM +0100, Alex Bligh wrote:
> >> Hang on a second! v2 of this patch DID use a new virtual machine,
> >> called exactly that. I thought you were objecting to that a
Quoting Serge E. Hallyn (se...@hallyn.com):
> Quoting Alexander Graf (ag...@suse.de):
> >
> >
> > On 27.08.14 23:35, Peter Maydell wrote:
> > > On 27 August 2014 22:30, Alexander Graf wrote:
> > >>
> > >>
> > >>
Quoting Alexander Graf (ag...@suse.de):
>
>
> On 27.08.14 23:35, Peter Maydell wrote:
> > On 27 August 2014 22:30, Alexander Graf wrote:
> >>
> >>
> >> On 27.08.14 21:01, Peter Maydell wrote:
> >>> [adding qemu-ppc]
> >>>
>
Quoting Peter Maydell (peter.mayd...@linaro.org):
> On 27 August 2014 18:55, Serge E. Hallyn wrote:
> > This is a part of a patch proposed by jaejunh at
> > https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1358268
> > which enables running ppc64le binaries through qemu-us
This is a part of a patch proposed by jaejunh at
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1358268
which enables running ppc64le binaries through qemu-user.
Not sure if it's the right way to do it, but it does allow
me to chroot into a ppc64el rootfs on amd64 host.
Signed-off-by: Serge
Quoting Michael S. Tsirkin (m...@redhat.com):
> commit 868270f23d8db2cce83e4f082fe75e8625a5fbf9
> acpi-build: tweak acpi migration limits
> broke kernel loading with -kernel/-initrd: it doubled
> the size of ACPI tables but did not reserve
> enough memory.
>
> As a result, issues on boot and h
Quoting Alex Bligh (a...@alex.org.uk):
>
> On 7 Aug 2014, at 20:26, Serge E. Hallyn wrote:
>
> > A-ha, acpi wasn't a problem. I actually had a general migration
> > problem even when coming from other utopic hosts. With that fixed,
> > I've got succ
Quoting Alex Bligh (a...@alex.org.uk):
> Serge,
>
> On 7 Aug 2014, at 03:50, Serge Hallyn wrote:
>
> > This worked for me when migrating by hand. I'm trying to make it work
> > through libvirt, using the following patch. (So whether to have
> > pc-1.0 be treated as qemu's or qemu-kvm's pc-1.0
Quoting Alex Bligh (a...@alex.org.uk):
> Serge,
>
> On 7 Aug 2014, at 03:50, Serge Hallyn wrote:
>
> > This worked for me when migrating by hand. I'm trying to make it work
> > through libvirt, using the following patch. (So whether to have
> > pc-1.0 be treated as qemu's or qemu-kvm's pc-1.0
Quoting Alex Bligh (a...@alex.org.uk):
> Serge,
>
> > I don't think that is in any way a problem. Is migrating to older
> > versions ever actually expected to work? In either case I don't
> > think for this particular case it's a problem.
>
> Good; no; and good - respectively.
>
> > (The "how
Quoting Paolo Bonzini (pbonz...@redhat.com):
> Il 11/04/2014 22:10, Serge Hallyn ha scritto:
> >Quoting Paolo Bonzini (pbonz...@redhat.com):
> >>Il 11/04/2014 04:31, Michael Tokarev ha scritto:
> >>>ENOENT means the kernel has an empty dirty bitmap for this
> >>>slot. Don't abort in that case. Th
D'oh, sorry. I generated that patch against my qemu tree at the bad_commit^.
That won't apply to the tree... this should.
>From 0d818e334f6db88b2770e9a1076ae1e68c41e460 Mon Sep 17 00:00:00 2001
From: Serge Hallyn
Date: Tue, 8 Apr 2014 22:14:20 -0500
Subject: [PATCH 1/1] kvm_physical_sync_dirty_
Quoting Cole Robinson (crobi...@redhat.com):
> On 03/21/2014 01:00 PM, Serge E. Hallyn wrote:
> > Quoting Cole Robinson (crobi...@redhat.com):
> >> On 03/19/2014 12:16 PM, Serge E. Hallyn wrote:
> >>> Quoting Serge E. Hallyn (se...@hallyn.com):
> >>>&g
Quoting Cole Robinson (crobi...@redhat.com):
> On 03/19/2014 12:16 PM, Serge E. Hallyn wrote:
> > Quoting Serge E. Hallyn (se...@hallyn.com):
> >> Quoting Paolo Bonzini (pbonz...@redhat.com):
> >>> Il 19/03/2014 16:42, Serge E. Hallyn ha scritto:
>
Quoting Dr. David Alan Gilbert (dgilb...@redhat.com):
> * Serge E. Hallyn (se...@hallyn.com) wrote:
>
> > Although, some people are using newer qemu with '-M pc-1.0'. So we'd be
> > stopping thing from migrating to support the people coming from qemu-kvm.
> &
Quoting Serge E. Hallyn (se...@hallyn.com):
> Quoting Paolo Bonzini (pbonz...@redhat.com):
> > Il 19/03/2014 16:42, Serge E. Hallyn ha scritto:
> > >Hi,
> > >
> > >at https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321
> > >it was found t
Hi,
at https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321
it was found that migrating running vms from a machine with
qemu-kvm to one with qemu, migration fails due to some mismatches.
The first one we usually hit is
Length mismatch: vga.vram: 100 in != 80
while the second on
Quoting Paolo Bonzini (pbonz...@redhat.com):
> Il 19/03/2014 16:42, Serge E. Hallyn ha scritto:
> >Hi,
> >
> >at https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321
> >it was found that migrating running vms from a machine with
> >qemu-kvm to one with
Quoting Aneesh Kumar K.V (aneesh.ku...@linux.vnet.ibm.com):
> Paolo Bonzini writes:
>
> > Il 03/03/2014 20:08, Aneesh Kumar K.V ha scritto:
> >> From: "Aneesh Kumar K.V"
> >>
> >> After commit ba1183da9a10b94611cad88c44a5c6df005f9b55 we are including
> >> hw/Makefile.objs directly from Makefile.
Quoting Michael Tokarev (m...@tls.msk.ru):
> 06.06.2013 12:48, David Gibson wrote:
> >pci-hotplug.c and the CONFIG_PCI_HOTPLUG variable which controls its
> >compilation are misnamed. They're not about PCI hotplug in general, but
> >rather about the pci_add/pci_del interface which are now deprecat
Hi,
I'm not sure anyone is using this version, but since our precise LTS
qemu-kvm version is based on 1.0, I've gone ahead and created a
qemu-kvm-1.0-stable branch at http://github.com/hallyn/qemu where I'll
keep all the (non-ubuntu-specific) patches we are using. If anyone
else does maintain any
Quoting mdroth (mdr...@linux.vnet.ibm.com):
> On Fri, Feb 22, 2013 at 05:10:29PM +0000, Serge E. Hallyn wrote:
> > Hi,
> >
> > up to and including 1.3.0, monitor.c:do_info(), if it got no arg or an
> > unknown arg, would do help_cmd(mon, "info"); That behavio
Hi,
up to and including 1.3.0, monitor.c:do_info(), if it got no arg or an
unknown arg, would do help_cmd(mon, "info"); That behavior is gone in
1.4.0, so that 'info', 'info help', and 'info whatever' just say unknown
argument. Was that intended, or would re-introducing the old behavior
be accep
The snprintf format isn't taking into account the new 'left' and
'right' variables (for ipv6 []) when placing the ':', which should
go immediately before the port.
Signed-off-by: Serge Hallyn
---
qemu-char.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/qemu-char.c b/qemu-c
Hi,
a regression test of CVE-2011-1751 (fixed by
505597e4476a6bc219d0ec1362b760d71cb4fdca) found that when writing 2 to
0xae08, qemu-system-i386 crashes with
ERROR:qom/object.c:386:object_finalize: assertion failed: (obj->ref == 0)
A simple way to reproduce this (in qemu 1.1 or 1.2) is:
serge@u
Quoting Jan Kiszka (jan.kis...@siemens.com):
> On 2012-04-10 16:06, Serge E. Hallyn wrote:
> > Quoting Jan Kiszka (jan.kis...@siemens.com):
> >> On 2012-04-09 17:36, Serge E. Hallyn wrote:
> >>> Hi,
> >>>
> >>> at https://bugs.laun
Quoting Jan Kiszka (jan.kis...@siemens.com):
> On 2012-04-09 17:36, Serge E. Hallyn wrote:
> > Hi,
> >
> > at https://bugs.launchpad.net/debian/+source/qemu-kvm/+bug/975240 there is
> > reported a problem in 1.0.0 with running unaccelerated qemu with hpet.
> > Th
Hi,
at https://bugs.launchpad.net/debian/+source/qemu-kvm/+bug/975240 there is
reported a problem in 1.0.0 with running unaccelerated qemu with hpet.
This is fixed upstream as of commit ce967e2f33861b0e17753f97fa4527b5943c94b6.
However, that one seems very depending on many of the preceding ~thous
Quoting Anthony Liguori (anth...@codemonkey.ws):
> On 03/26/2012 10:13 AM, Serge E. Hallyn wrote:
> >Currently, if the user doesn't pass a uuid, the system uuid is set to
> >all zeros. This patch generates a random one instead.
> >
> >Is there a reason to prefer
Quoting Brian Jackson (i...@theiggy.com):
> On Mon, 26 Mar 2012 10:13:40 -0500, Serge E. Hallyn
> wrote:
>
> >Currently, if the user doesn't pass a uuid, the system uuid is set to
> >all zeros. This patch generates a random one instead.
> >
> >Is there a re
Quoting Andreas Färber (afaer...@suse.de):
> Am 26.03.2012 17:13, schrieb Serge E. Hallyn:
> > Currently, if the user doesn't pass a uuid, the system uuid is set to
> > all zeros. This patch generates a random one instead.
> >
> > Is there a reason to prefer
Currently, if the user doesn't pass a uuid, the system uuid is set to
all zeros. This patch generates a random one instead.
Is there a reason to prefer all zeros? If not, can a patch like this
one be applied?
Signed-off-by: Serge Hallyn
---
vl.c | 11 +++
1 files changed, 11 inserti
Quoting Scott Moser (smo...@ubuntu.com):
> Re-sending to qemu-devel. I'd originally sent this to kvm mailing list.
>
>
> -- Forwarded message --
> Date: Sat, 17 Mar 2012 00:08:06
> From: Scott Moser
> To: k...@vger.kernel.org
> Subject: [PATCH] fix multiboot loading if load_end_
Thanks. As there's been no substantial feedback, I'll resend with
those changes.
-serge
Quoting Ryan Harper (ry...@us.ibm.com):
> * Serge Hallyn [2012-03-02 15:13]:
> > Hi,
> >
> > I don't know where the best place to catch this would be, but
> > with vnc and vmware_vga it's possible to get se
Quoting Paul Moore (pmo...@redhat.com):
> On Wednesday, December 07, 2011 12:48:16 PM Anthony Liguori wrote:
> > On 12/07/2011 12:25 PM, Corey Bryant wrote:
> > > A group of us are starting to work on sandboxing QEMU device emulation
> > > code. We're just getting started investigating various appr
Quoting Kevin Wolf (kw...@redhat.com):
> > The footer->size appears to be double the 'real' size. So I'm actually
> > doing
> > the blow. Does this seem sensible?
>
> Double size sounds really weird. 'qemu-img create' uses the size in
> bytes for it. Is that wrong?
>
> > Doing it this way, try
Quoting Kevin Wolf (kw...@redhat.com):
> Am 26.07.2011 18:08, schrieb Serge E. Hallyn:
> > Quoting Kevin Wolf (kw...@redhat.com):
> >> Am 25.07.2011 20:34, schrieb Serge E. Hallyn:
> >>> VHD files technically can be up to 2Tb, but virtual pc is limited
> >>&g
Quoting Kevin Wolf (kw...@redhat.com):
> Am 25.07.2011 20:34, schrieb Serge E. Hallyn:
> > VHD files technically can be up to 2Tb, but virtual pc is limited
> > to 127G. Currently qemu-img refused to create vpc files > 127G,
> > but it is failing to return error when c
VHD files technically can be up to 2Tb, but virtual pc is limited
to 127G. Currently qemu-img refused to create vpc files > 127G,
but it is failing to return error when converting from a non-vpc
VHD file which is >127G. It returns success, but creates a truncated
converted image. Also, qemu-img
Quoting Stefan Berger (stef...@linux.vnet.ibm.com):
> On 05/17/2011 04:58 PM, Serge E. Hallyn wrote:
> >Quoting Stefan Berger (stef...@linux.vnet.ibm.com):
> >>This patch adds support for TPM command line options.
> >>The command line supported here (considering the lib
Quoting Stefan Berger (stef...@linux.vnet.ibm.com):
> This patch adds support for TPM command line options.
> The command line supported here (considering the libtpms based
> backend) are
>
> ./qemu-... -tpm type=,path=,
Hm, I did
kvm -tpm type=builtin,path=tpm.img -m 1G disk.img -vnc :1
with d
Quoting Stefan Berger (stef...@linux.vnet.ibm.com):
> >What is your plan regarding libtpms? Will you be making actual
> >releases at sf.net at some point?
> I was going to wait for a review of all the patches here on the ml
> and see the code checked in -- until that hasn't happened anything
> cou
Quoting Stefan Berger (stef...@linux.vnet.ibm.com):
> On 05/10/2011 12:07 AM, Serge E. Hallyn wrote:
> >To get this to compile on top of qemu-kvm, I needed the following
> >patch to force CONFIG_THREAD on so as to define things like
> >qemu_mutex_lock:
> >
>
To get this to compile on top of qemu-kvm, I needed the following
patch to force CONFIG_THREAD on so as to define things like
qemu_mutex_lock:
Index: qemu-kvm-tpm/configure
===
--- qemu-kvm-tpm.orig/configure 2011-05-09 21:19:10.92000
Quoting Stefan Berger (stef...@linux.vnet.ibm.com):
> The following series of patches adds a TPM (Trusted Platform Module)
> TIS (TPM Interface Spec) interface to Qemu and with that provides
> means to access a backend implementing the actual TPM functionality.
> This frontend enables for example L
Quoting Stefan Berger (stef...@linux.vnet.ibm.com):
> This patch adds the main code of the TPM frontend driver, the TPM TIS
> interface, to Qemu. The code is largely based on my previous implementation
> for Xen but has been significantly extended to meet the standard's
> requirements, such as the
Quoting Stefan Berger (stef...@linux.vnet.ibm.com):
> On 05/06/2011 04:23 PM, Serge E. Hallyn wrote:
> >Quoting Stefan Berger (stef...@linux.vnet.ibm.com):
> >>This patch adds support for TPM command line options.
> >>The command line supported here (considering the lib
Quoting Stefan Berger (stef...@linux.vnet.ibm.com):
> This patch adds support for TPM command line options.
> The command line supported here (considering the libtpms based
> backend) are
>
> ./qemu-... -tpm type=,path=,
>
> and
>
> ./qemu-... -tpm ?
>
> where the latter works similar to -soundh
Hi Stefan,
I was hoping to take a look at the TPM patchset. Rumor has it you
have some updates. Would you mind re-sending the set?
thanks,
-serge
Hi,
When I grabbed the latest qemu (up to commit
bfddb47a343b4718e5768aa80bce8adead0f7fca) from git://git.qemu.org/qemu.git
and did:
./qemu-system-x86_64 -net user -net nic -vga std -usb -usbdevice tablet -m 512
-hda /home/serge/disk.img -boot c -monitor stdio -vnc :1 -L
/opt/qemu/share/qemu/
Thanks, Stefan. That patch actually doesn't compile for me, because
it leaves references in hw/pckbd.c to both ioport92_write and
ioport92_read, which it deletes from there. Should ioport92_read
just be renamed to outport_read instead of delted, and the remaining
references changed to {input,outp
Hi,
I don't see this patch in the git tree, nor a revert of the buggy
commit. Was any decision made on this?
thanks,
-serge
Quoting Stevens, Weston (wstev...@eecs.wsu.edu):
> I run Ubuntu 10.04 LTS and have qemu 0.12.3. For a class project, we are
> building our own pseudo-linux operating system, so we have our own kernel AND
> user processes that we built, and we run this OS from a virtual floppy disk.
> So we don't
Thanks, Anthony. Do I understand correctly that that's the
"case '/'" in monitor_parse_command() for '/10x' gdb-like format?
thanks,
-serge
Quoting Anthony Liguori (anth...@codemonkey.ws):
> The '/' character is used to create special expressions if double quotes
> aren't used.
>
> ** Changed i
54 matches
Mail list logo
