On Sat, Jan 13, 2007 at 12:28:26PM +0100, Johannes Schindelin wrote:
>Hi,
>
>On Sat, 13 Jan 2007, Bernhard Fischer wrote:
>
>> On Fri, Jan 12, 2007 at 11:36:06AM -0800, alex wrote:
>>
>> >
>> >--- /d/qemu/vl.c Fri Jan 12 10:43:12 2007
>> >+++ vl.c Fri Jan 12 10:49:37 2007
>> >@@ -2692,8 +2692,13 @
Hi,
On Sat, 13 Jan 2007, Bernhard Fischer wrote:
> On Fri, Jan 12, 2007 at 11:36:06AM -0800, alex wrote:
>
> >
> >--- /d/qemu/vl.c Fri Jan 12 10:43:12 2007
> >+++ vl.c Fri Jan 12 10:49:37 2007
> >@@ -2692,8 +2692,13 @@
> > if (ret < 0) {
> > err = socket_error();
> >
On Fri, Jan 12, 2007 at 11:36:06AM -0800, alex wrote:
>This is a second attempt to post, first one did not get through.
>
>This patch fixes -parallel and -serial options work with TCP targets on
>Windows host.
>
>Alex.
>
>--- /d/qemu/vl.c Fri Jan 12 10:43:12 2007
>+++ vl.c Fri Jan 12 10:49:37 2007
Doing some more tests and trying to get more info about the problem
shows some common behaviours:
- the problems are with the x86_64 emulation regardless if it is
running on a 32bit or 64bit host (in my case always Linux host)
- The problems happen in all qemu modes: no kqemu, user kqemu, kerne
Hello,
I hope you can enlight me a little bit :).
I'm trying to use qemu-img to create two disk images: a base image and a
snapshot image (diff image or copy on write, name it the way you want).
I think either qemu-img has a bug if the snapshot image has type vmdk or
this format is not supported/s
