On Mon, Jul 28, 2014 at 08:23:52PM +0400, Denis V. Lunev wrote:
> Parallels image format has several additional fields inside:
> - nb_sectors is actually 64 bit wide. Upper 32bits are not used for
> images with signature "WithoutFreeSpace" and must be explicitly
> zeroed according to Parallels.
On Mon, Jul 28, 2014 at 08:23:54PM +0400, Denis V. Lunev wrote:
> and rework error path a bit. There is no difference at the moment, but
> the code will be definitely shorter when additional processing will
> be required for WithouFreSpacExt
>
> Signed-off-by: Denis V. Lunev
> CC: Jeff Cody
> CC
Am 25.07.2014 um 14:10 hat Cornelia Huck geschrieben:
> Currently, qemu will take a hard exit if it fails to set up guest or
> host notifiers, giving no real clue as to what went wrong (e.g., when
> out of file descriptors).
>
> This patchset tries to make this more manageable: Both by improving t
On Mon, Jul 28, 2014 at 08:23:55PM +0400, Denis V. Lunev wrote:
> Parallels has released in the recent updates of Parallels Server 5/6
> new addition to his image format. Images with signature WithouFreSpacExt
> have offsets in the catalog coded not as offsets in sectors (multiple
> of 512 bytes) b
Am 23.07.2014 um 23:22 hat Jeff Cody geschrieben:
> Changes from v2 -> v3:
> * Patch 2: Removed extra #ifdef __linux__ from top of file (Max)
> * Patch 4: Removed extra #ifdef __linux__ from top of file (Max)
> * Patch 5: Removed output from debug cruft (Max)
> * Added Max's R-b to
On 7 August 2014 15:13, Christopher Covington wrote:
> On 08/07/2014 09:53 AM, Peter Maydell wrote:
>> I think the biggest difficulty is not the code to actually
>> do the switch but figuring out what the command line
>> UI to request "start in AArch32" ought to be and how that
>> then gets plumbe
On 07/08/14 18:39, Jeff Cody wrote:
On Mon, Jul 28, 2014 at 08:23:55PM +0400, Denis V. Lunev wrote:
Parallels has released in the recent updates of Parallels Server 5/6
new addition to his image format. Images with signature WithouFreSpacExt
have offsets in the catalog coded not as offsets in se
On Thu, Aug 07, 2014 at 02:53:33PM +0100, Peter Maydell wrote:
> On 7 August 2014 14:43, Christopher Covington wrote:
> > On 08/07/2014 08:03 AM, Peter Maydell wrote:
> >> No, because at the moment our AArch64 TCG implementation
> >> (and the way we configure KVM) assumes that the highest
> >> exc
On Thu, Aug 07, 2014 at 07:03:12PM +0400, Denis V. Lunev wrote:
> On 07/08/14 18:39, Jeff Cody wrote:
> >On Mon, Jul 28, 2014 at 08:23:55PM +0400, Denis V. Lunev wrote:
> >>Parallels has released in the recent updates of Parallels Server 5/6
> >>new addition to his image format. Images with signatu
On 07/08/14 19:14, Jeff Cody wrote:
On Thu, Aug 07, 2014 at 07:03:12PM +0400, Denis V. Lunev wrote:
On 07/08/14 18:39, Jeff Cody wrote:
On Mon, Jul 28, 2014 at 08:23:55PM +0400, Denis V. Lunev wrote:
Parallels has released in the recent updates of Parallels Server 5/6
new addition to his image
On Thu, 7 Aug 2014 16:39:01 +0200
Kevin Wolf wrote:
> Am 25.07.2014 um 14:10 hat Cornelia Huck geschrieben:
> > Currently, qemu will take a hard exit if it fails to set up guest or
> > host notifiers, giving no real clue as to what went wrong (e.g., when
> > out of file descriptors).
> >
> > Thi
On 07/08/14 19:22, Denis V. Lunev wrote:
Another question - do you have any sample images? If they compress
well (bzip2 does a good job with most blank images) it would be nice
to have a couple of parallels images (e.g. one "WithouFreSpacExt" and
one "WithoutFreeSpace") in the tests sample_imag
On 7 August 2014 16:06, Richard W.M. Jones wrote:
> On Thu, Aug 07, 2014 at 02:53:33PM +0100, Peter Maydell wrote:
>> I think the biggest difficulty is not the code to actually
>> do the switch but figuring out what the command line
>> UI to request "start in AArch32" ought to be and how that
>> t
On 08/07/2014 03:19 AM, Michael Roth wrote:
>>
>> Libvirt could support active commit against qemu 2.0.1 if you backport
>> these patches:
>>
>> Jeff Cody
>> 7676e2c597 block: make 'top' argument to block-commit optional
>>
>> Fam Zheng
>> 9e48b02540 mirror: Go through ready -> complete process
Sorry, I'm having trouble following your findings. Could you please give a new
table, like
this:
==
GuestOS | Guestkernel | HostOS | Hostkernel | qemu version|
libvir
Quoting Eric Blake (2014-08-07 10:50:41)
> On 08/07/2014 03:19 AM, Michael Roth wrote:
> >>
> >> Libvirt could support active commit against qemu 2.0.1 if you backport
> >> these patches:
> >>
> >> Jeff Cody
> >> 7676e2c597 block: make 'top' argument to block-commit optional
> >>
> >> Fam Zheng
>
The current code supplies the PSCI v0.1 funciton IDs in the DT even when
KVM uses PSCI v0.2.
This will break guest kernels that only support PSCI v0.1 as they will
use the IDs provided in the DT. Guest kernels with PSCI v0.2 support
are not affected by this patch, because they ignore the function
On 08/06/2014 10:01 PM, zhanghailiang wrote:
> if (!lock_user_struct(VERIFY_READ, target_mb, msgp, 0))
> return -TARGET_EFAULT;
> host_mb = malloc(msgsz+sizeof(long));
> +if (!host_mb) {
> +return -TARGET_ENOMEM;
> +}
lock_user allocates memory; returning from th
On 7 August 2014 17:30, Christoffer Dall wrote:
> The current code supplies the PSCI v0.1 funciton IDs in the DT even when
"function"
> KVM uses PSCI v0.2.
>
> This will break guest kernels that only support PSCI v0.1 as they will
> use the IDs provided in the DT. Guest kernels with PSCI v0.2 s
On 24.06.2014 17:36, Kevin Wolf wrote:
A not too small part of the recent CVEs were DoS scenarios by letting
qemu abort with too large memory allocations. We generally "fixed" these
cases by setting some limits on values read from image files that
influence the size of allocations.
Because we st
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
On Thu, Aug 7, 2014 at 9:30 AM, Christoffer Dall
wrote:
>
> The current code supplies the PSCI v0.1 funciton IDs in the DT even when
> KVM uses PSCI v0.2.
>
> This will break guest kernels that only support PSCI v0.1 as they will
> use the IDs provided in the DT. Guest kernels with PSCI v0.2 supp
On 08/06/2014 02:38 PM, Michael Roth wrote:
> Hi everyone,
>
> The following new patches are queued for QEMU stable v2.0.1:
>
> https://github.com/mdroth/qemu/commits/stable-2.0-staging
>
> The release is planned for 2014-08-15:
>
> http://wiki.qemu.org/Planning/2.0
>
> Please respond here
On 08/07/2014 02:21 PM, Eric Blake wrote:
> On 08/06/2014 02:38 PM, Michael Roth wrote:
>> Hi everyone,
>>
>> The following new patches are queued for QEMU stable v2.0.1:
>>
>> https://github.com/mdroth/qemu/commits/stable-2.0-staging
>>
>> Testing/feedback is greatly appreciated.
>>
>
> I trie
On Thu, Aug 07, 2014 at 07:06:12PM +0100, Peter Maydell wrote:
> On 7 August 2014 17:30, Christoffer Dall wrote:
> > The current code supplies the PSCI v0.1 funciton IDs in the DT even when
>
> "function"
>
> > KVM uses PSCI v0.2.
> >
> > This will break guest kernels that only support PSCI v0.1
qemu-img check calls bdrv_check() twice if the first run repaired some
inconsistencies. If the first run however again triggered corruption
prevention (on qcow2) due to very bad inconsistencies, bs->drv may be
NULL afterwards. Thus, bdrv_check() should check whether bs->drv is set.
Signed-off-by:
The first two patches in this series address
https://bugs.launchpad.net/qemu/+bug/1349972.
For the third patch I found it hard to write an appropriate test case
(it would have to make qemu-img check repair some leaks but induce the
corruption prevention at the same time). One can use the test imag
qcow2_alloc_cluster_offset() uses host_offset == 0 as "no preferred
offset" for the (data) cluster range to be allocated. However, this
offset is actually valid and may be allocated on images with a corrupted
refcount table or first refcount block.
In this case, the corruption prevention should no
Add a test for an image with an unallocated image header; instead of an
assertion, this should result in the image being marked corrupt.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/060 | 9 +
tests/qemu-iotests/060.out | 8
2 files changed, 17 insertions(+)
diff --git a
On 08/07/2014 02:23 PM, Eric Blake wrote:
>>
>> I tried to compile on Fedora 20, but had to backport this to get it to work:
>>
>> Luiz Capitulino
>> a49db98d fpu: softfloat: drop INLINE macro
>
> Oops, spoke too soon. I hit another build failure - anyone recognize
> this, or which commit to bac
On 08/07/2014 02:47 PM, Max Reitz wrote:
> The first two patches in this series address
> https://bugs.launchpad.net/qemu/+bug/1349972.
>
> For the third patch I found it hard to write an appropriate test case
> (it would have to make qemu-img check repair some leaks but induce the
> corruption pr
On 7 August 2014 21:55, Eric Blake wrote:
> Turns out to be caused by leftovers, from trying an incremental build in
> the same tree where I had 2.1 object files. Maybe the makefiles can be
> improved to deal gracefully with this case, but as a clean build didn't
> suffer from the problem, it's n
On 08/07/2014 03:10 PM, Peter Maydell wrote:
> On 7 August 2014 21:55, Eric Blake wrote:
>> Turns out to be caused by leftovers, from trying an incremental build in
>> the same tree where I had 2.1 object files. Maybe the makefiles can be
>> improved to deal gracefully with this case, but as a cl
On 08/06/2014 02:38 PM, Michael Roth wrote:
> Hi everyone,
>
> The following new patches are queued for QEMU stable v2.0.1:
>
> https://github.com/mdroth/qemu/commits/stable-2.0-staging
>
> The release is planned for 2014-08-15:
>
> http://wiki.qemu.org/Planning/2.0
>
> Please respond here
Quoting Tomoki Sekiyama (2014-06-30 16:51:21)
> Hi,
>
> As patch 3/3 was missing in the last post, I'm resending this patchset.
>
> ===
> This is v5 patch for qemu-ga to add functions to freeze specific file systems
> mounted in a guest.
>
> Changes since v4:
> - PATCH 2: fix coding styles (spa
On Thu, 2014-08-07 at 00:22 +0200, Benedikt Morbach wrote:
> I think one of those gtk patches broke mouse/keyboard grab for my
> Windows 8 vfio/vga-passthrough setup in 2.1.0 and I was instructed on
> IRC to report that here.
>
> With 2.0.0 I got a black qemu window with "This VM has no graphic
>
On 08/07/2014 09:50 AM, Eric Blake wrote:
> On 08/07/2014 03:19 AM, Michael Roth wrote:
>>>
>>> Libvirt could support active commit against qemu 2.0.1 if you backport
>>> these patches:
>>>
>>> Jeff Cody
>>> 7676e2c597 block: make 'top' argument to block-commit optional
>>>
>>> Fam Zheng
>>> 9e
On 06/30/2014 03:51 PM, Tomoki Sekiyama wrote:
> If an array of mount point paths is specified as 'mountpoints' argument
> of guest-fsfreeze-freeze-list, qemu-ga will only freeze the file systems
> mounted on specified paths in Linux guests. Otherwise, it works as the
> same way as guest-fsfreeze-f
On 06/30/2014 03:51 PM, Tomoki Sekiyama wrote:
> Add command to get mounted filesystems information in the guest.
> The returned value contains a list of mountpoint paths and
> corresponding disks info such as disk bus type, drive address,
> and the disk controllers' PCI addresses, so that manageme
Hello,
Please pull the following changes, which add a new guest-fsfreeze-freeze-list
command to qemu-ga that supports specifying specific mounts to freeze, and
improves the introspection information from guest-info by explicitly
blacklisting/reporting commands that aren't supported on a particular
From: Tomoki Sekiyama
Currently management softwares cannot know whether a qemu-ga command is
supported or not on the running platform until they actually execute it.
This patch disables unsupported commands at launch time of qemu-ga, so that
management softwares can check whether they are suppor
From: Tomoki Sekiyama
If an array of mount point paths is specified as 'mountpoints' argument
of guest-fsfreeze-freeze-list, qemu-ga will only freeze the file systems
mounted on specified paths in Linux guests. Otherwise, it works as the
same way as guest-fsfreeze-freeze.
This would be useful whe
From: Tomoki Sekiyama
Add command to get mounted filesystems information in the guest.
The returned value contains a list of mountpoint paths and
corresponding disks info such as disk bus type, drive address,
and the disk controllers' PCI addresses, so that management layer
such as libvirt can re
Quoting Eric Blake (2014-08-07 17:03:57)
> On 06/30/2014 03:51 PM, Tomoki Sekiyama wrote:
> > If an array of mount point paths is specified as 'mountpoints' argument
> > of guest-fsfreeze-freeze-list, qemu-ga will only freeze the file systems
> > mounted on specified paths in Linux guests. Otherwis
On 08/07/2014 04:10 PM, Michael Roth wrote:
> Hello,
>
> Please pull the following changes, which add a new guest-fsfreeze-freeze-list
> command to qemu-ga that supports specifying specific mounts to freeze, and
> improves the introspection information from guest-info by explicitly
> blacklisting/
Public bug reported:
I'm unable to restart a VM. virt-manager is giving me:
Error starting domain: internal error: process exited while connecting
to monitor: qemu-system-x86_64: -drive
file=/var/lib/libvirt/images/poppy.qcow2,if=none,id=drive-virtio-
disk0,format=qcow2: could not open disk ima
Quoting Eric Blake (2014-08-07 16:23:14)
> On 08/06/2014 02:38 PM, Michael Roth wrote:
> > Hi everyone,
> >
> > The following new patches are queued for QEMU stable v2.0.1:
> >
> > https://github.com/mdroth/qemu/commits/stable-2.0-staging
> >
> > The release is planned for 2014-08-15:
> >
> >
From: Mike Frysinger
The current code always returns the length of the path when it should
be returning the number of bytes it wrote to the output string.
Further, readlink is not supposed to append a NUL byte, but the current
snprintf logic will always do just that.
Even further, if you pass i
On 2014/8/8 1:19, Richard Henderson wrote:
On 08/06/2014 10:01 PM, zhanghailiang wrote:
if (!lock_user_struct(VERIFY_READ, target_mb, msgp, 0))
return -TARGET_EFAULT;
host_mb = malloc(msgsz+sizeof(long));
+if (!host_mb) {
+return -TARGET_ENOMEM;
+}
lock_us
On 08/07/2014 04:34 AM, Bastian Koppelmann wrote:
> +/* PSW flag cache for faster execution
> + if flag != 0 then flag is set. Else flag is not set.
> +*/
> +target_ulong PSW_USB_C;
> +target_ulong PSW_USB_V;
> +target_ulong PSW_USB_SV;
> +target_ulong PSW_USB_AV; /*
> +static inline void gen_add_d(TCGv ret, TCGv r1, TCGv r2)
> +{
> +TCGv t0 = tcg_temp_new_i32();
> +/* Addition and set V/SV bits */
> +tcg_gen_add_tl(ret, r1, r2);
> +/* calc V bit */
> +tcg_gen_xor_tl(cpu_PSW_V, ret, r1);
> +tcg_gen_xor_tl(t0, r1, r2);
> +tcg_gen_andc
Currently syscall instruction is buggy on user mode X86_64,
the EIP is updated after do_syscall(), that is too late for
clone(). Because clone() will create a thread at the env->EIP
(the address of syscall insn), and then child thread enters
do_syscall() again, that is not expected. Sometimes it is
On Thu, Aug 07, 2014 at 04:28:39PM +0900, Hitoshi Mitake wrote:
> The update is required for supporting iSCSI multipath. It doesn't
> affect behavior of QEMU driver but adding a new field to vdi request
> struct is required.
>
> Cc: Kevin Wolf
> Cc: Stefan Hajnoczi
> Cc: Liu Yuan
> Cc: MORITA K
this patch fixed the bug:
commit 338b522ca43cfd32d11a370f4203bcd089c6c877
Author: Kan Liang
Date: Mon Jul 14 12:25:56 2014 -0700
perf/x86/intel: Protect LBR and extra_regs against KVM lying
With -cpu host, KVM reports LBR and extra_regs support, if the host has
support.
When t
On Thu, Aug 07, 2014 at 04:28:40PM +0900, Hitoshi Mitake wrote:
> Recently, sheepdog revived its VDI locking functionality. This patch
> updates sheepdog driver of QEMU for this feature:
>
> 1. Improve error message when QEMU fails to acquire lock of
> VDI. Current sheepdog driver prints an error
when L1 guest kernel: 3.16.0(kvm.git+ qemu.git: c77dcacb..-69f87f71)
create L1 guest:
qemu-system-x86_64 -enable-kvm -m 6G -smp 4 -net nic,macaddr=00:12:31:45:56:13
-net tap,script=/etc/kvm/qemu-ifup ia32e_nested-kvm.img -cpu host
the L1 guest boot up fine
--
You received this bug notification b
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/994378
Title:
Nested-virt)L1 (kvm on kvm)guest panic with parameter “-cpu host” in
qemu comman
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:9f6226a762c7ae02f6a23a3d4fc552dafa57ea23
qemu.git Commit:5a7348045091a2bc15d85bb177e5956aa6114e5a
Host Kernel Version:3.16.0-rc1
Hardwa
the first bad commit is:
commit 22a893e4f55344f96e1aafc66f5fedc491a5ca97
Author: Paolo Bonzini
Date: Wed Jun 11 10:58:06 2014 +0200
memory: MemoryRegion: replace owner field with QOM parent
The two are now the same.
Reviewed-by: Peter Crosthwaite
Signed-off-by: Paolo
Hi Anshul,
On 08/07/2014 09:31 PM, Anshul Makkar wrote:
> Thanks Gu.. cpu-hotunplug is working fine in my tests.
Thanks for your quick test.
>
> For cpu-hotplug, I get inconsistent result if I delete arbitrary cpu
> and not just the last one.
>
> for eg
> list of cpus: 1, 2 ,3
> device_add cp
On Thu, Aug 07, 2014 at 09:24:35PM +1000, Peter Crosthwaite wrote:
> On Thu, Aug 7, 2014 at 7:10 PM, Hu Tao wrote:
> > Add parameter errp to qemu_ram_alloc and qemu_ram_alloc_from_ptr so that
> > we can handle errors.
> >
> > Signed-off-by: Hu Tao
>
> Reviewed-by: Peter Crosthwaite
>
> Optiona
At Fri, 8 Aug 2014 13:20:39 +0800,
Liu Yuan wrote:
>
> On Thu, Aug 07, 2014 at 04:28:39PM +0900, Hitoshi Mitake wrote:
> > The update is required for supporting iSCSI multipath. It doesn't
> > affect behavior of QEMU driver but adding a new field to vdi request
> > struct is required.
> >
> > Cc:
At Fri, 8 Aug 2014 13:31:39 +0800,
Liu Yuan wrote:
>
> On Thu, Aug 07, 2014 at 04:28:40PM +0900, Hitoshi Mitake wrote:
> > Recently, sheepdog revived its VDI locking functionality. This patch
> > updates sheepdog driver of QEMU for this feature:
> >
> > 1. Improve error message when QEMU fails to
On Wed, Aug 06, 2014 at 05:12:46PM +0400, Maria Kustova wrote:
> 'Overall fuzzer requirements' chapter contains the current product vision and
> features done and to be done. This chapter is still in progress.
>
> Signed-off-by: Maria Kustova
> ---
> tests/image-fuzzer/docs/image-fuzzer.txt | 23
Reported-by: Valerio Pachera
Signed-off-by: Liu Yuan
---
sheep/group.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sheep/group.c b/sheep/group.c
index 06a80bd..08e3884 100644
--- a/sheep/group.c
+++ b/sheep/group.c
@@ -979,7 +979,7 @@ static int send_join_request(void)
{
i discovered with iproute2 i have to manually bring the "lo" interface
link up which to me is pretty new.. after which the spice port can
immediately work with 127.0.0.1:.
what I originally meant when installing iproute2 on debian was that it
uninstalls ifupdown as well as iproute.
I don't kno
On Fri, Aug 08, 2014 at 03:17:59PM +0900, Hitoshi Mitake wrote:
> At Fri, 8 Aug 2014 13:31:39 +0800,
> Liu Yuan wrote:
> >
> > On Thu, Aug 07, 2014 at 04:28:40PM +0900, Hitoshi Mitake wrote:
> > > Recently, sheepdog revived its VDI locking functionality. This patch
> > > updates sheepdog driver of
Sebastian Tanase writes:
> Make icount parameter use QemuOpts style options in order
> to easily add other suboptions.
>
> Signed-off-by: Sebastian Tanase
> Tested-by: Camille Bégué
> Signed-off-by: Paolo Bonzini
[...]
> diff --git a/qemu-options.hx b/qemu-options.hx
> index 9e54686..143def4 1
On Wed, Aug 06, 2014 at 05:12:47PM +0400, Maria Kustova wrote:
> The purpose of the test runner is to prepare the test environment (e.g. create
> a work directory, a test image, etc), execute a program under test with
> parameters, indicate a test failure if the program was killed during the test
>
On Wed, Aug 06, 2014 at 05:12:45PM +0400, Maria Kustova wrote:
>
> This patch series introduces the image fuzzer, a tool for stability and
> reliability testing.
> Its approach is to run large amount of tests in background. During every test
> a
> program (e.g. qemu-img) is called to read or modi
101 - 170 of 170 matches
Mail list logo
