Hi, Bernd.
Sunday, November 13, 2005 5:14 AM Bernd Waldboth wrote:
i noticed that when I updated the OpenVPN Tap Driver
for Windows with the one coming in OpenVPN version
2.04 or 2.05, the same qemu.exe isn't able to connect
to the tap-device anymore. The old driver works without
problem. I tri
V L P V A X CI e r A m a IA v o L b n AG i z I i a LR t a U e x IA ra c M n S 3,32 1,22 3,75http://www.kitendaise.com
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
is there a way to save the disk snapshot file together with a saved vm
state? So that the complete guest state could be restored and would be
consistent?
Regards,
Oliver
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fabrice Bellard schrieb:
> Lonnie Mendez wrote:
>
>> On Saturday 05 November 2005 11:10 am, Fabrice Bellard wrote:
>>
>>> 1) The host OS must not use the USB device. It means in particular
>>> that no host OS driver must be present for that device. Th
On Saturday 12 November 2005 15:14, Bernd Waldboth wrote:
> Hello,
>
> i noticed that when I updated the OpenVPN Tap Driver
> for Windows with the one coming in OpenVPN version
> 2.04 or 2.05, the same qemu.exe isn't able to connect
> to the tap-device anymore. The old driver works without
> probl
Hello,
i noticed that when I updated the OpenVPN Tap Driver
for Windows with the one coming in OpenVPN version
2.04 or 2.05, the same qemu.exe isn't able to connect
to the tap-device anymore. The old driver works without
problem. I tried it on different machines.
Did anyone else notice the same b
The dumping of cpu state before each TB is currently enabled by "-d exec". It
should be controlled by "-d cpu". The patch below fixes this.
Paul
Index: cpu-exec.c
===
RCS file: /cvsroot/qemu/qemu/cpu-exec.c,v
retrieving revision 1
On Sat, 12 Nov 2005 17:16:02 +0100, Lars Roland wrote:
> I did not even knew that this information was always in the README,
> that is a sensible policy but given the frequency that questions like
> this pop up then perhaps the F.A.Q (http://free.oszoo.org/faq.html) or
> download page (http://free.
On 11/12/05, Stefano Marinelli <[EMAIL PROTECTED]> wrote:
> That's wrong: each contributor uses different passwords and, as a normal
> procedure, all the passwords are included in the README file of each
> image.
I did not even knew that this information was always in the README,
that is a sensibl
On Sat, 12 Nov 2005 14:26:32 +0100, Lars Roland wrote:
> can however tell you that the root password is "piripicchio". I think
Correct :)
> that perhaps http://free.oszoo.org/ should include this information on
> the main download site as the passwords are no secret they are just
> hard to find (
On 11/12/05, gianluca mazza <[EMAIL PROTECTED]> wrote:
> Hi, I downloaded debian sarge x86 imaging for my emulator QemuX.
> It works fine but I need root password for access can you send me it?
> Thanks and sorry for my english but I don't speak it very well
Well this is strictly not the place to
Hi, I downloaded debian sarge x86 imaging for my emulator QemuX.It works fine but I need root password for access can you send me it?Thanks and sorry for my english but I don't speak it very well___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lis
12 matches
Mail list logo
