Re: [Qemu-devel] QCOW image corruption under QEMU 0.9.0

2007-02-24 Thread J M Cerqueira Esteves
J M Cerqueira Esteves wrote: > This time, after installing some packages in a similar Debian guest, > the [guest] system froze while shutting down (using 100% CPU on host). > I then noticed that its supposed QCOW2 image file (a 20 GB virtual disk, > in a by then more than 4GB file) was no longer co

Re: [Qemu-devel] QCOW image corruption under QEMU 0.9.0

2007-02-24 Thread J M Cerqueira Esteves
J M Cerqueira Esteves wrote: > Curiously this damaged image file has 4543348736 bytes. > I wonder if there some new bug triggered by the image file size, > for some size around 45 bytes... I have a copy of the disk image file as it was just before starting the qemu run which damaged it, an

Re: [Qemu-devel] QCOW image corruption under QEMU 0.9.0

2007-02-24 Thread J M Cerqueira Esteves
J M Cerqueira Esteves wrote: > After shutting down the guest, I inspected its image files with > qemu-info, which reported for hda > > image: nisaba.hda.qcow > file format: raw > virtual size: 4.3G (4596273152 bytes) > disk size: 4.3G > > but hda was supposed to have a virtual size of approximately

Re: [Qemu-devel] FreeBSD Support

2007-02-24 Thread Leonardo Reiter
MAP_PRIVATE|MAP_ANON also works on Solaris. In fact, Linux is the only platform where it doesn't work due to a bug in the Linux kernel as Fabrice mentions: http://www.qemu.org/kqemu-tech.html#SEC7 Technically on Solaris, /tmp is probably the same thing as MAP_PRIVATE|MAP_ANON since the filesyst

[Qemu-devel] Hotplugging

2007-02-24 Thread Luke-Jr
Does anyone have plans to add more hotplugging support to qemu? For example, PCI hotplug (for video and network) and/or memory hotplug? Perhaps even disk hotplugging for more than just CD-ROMs? ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://

Re: [Qemu-devel] FreeBSD Support

2007-02-24 Thread Juergen Lock
In article <[EMAIL PROTECTED]> you write: >-=-=-=-=-=- > >Ok FreeBSD Support round one.. > >Be gentle this is my first attempt at working with the rest of this >community.. > >Files it modifies and the reasons are as follows > >configure - Adds HOST_FREEBSD type to alter included libraries FreeBSD

[Qemu-devel] [PATCH][UPDATE] Make removing IOHandlers safe from within an IOHandler

2007-02-24 Thread Anthony Liguori
Daniel P. Berrange wrote: On Sat, Feb 24, 2007 at 11:54:17AM -0600, Anthony Liguori wrote: I was getting random SEGVs when disconnecting from the VNC server. I tracked it down to the fact that if you remove a IOHandler from another IOHandler, all sorts of badness may result as you're removi

Re: [Qemu-devel] PATCH: Secure TLS encrypted authentication for VNC

2007-02-24 Thread Daniel P. Berrange
On Sat, Feb 24, 2007 at 06:57:16PM +, Luke-Jr wrote: > On Saturday 24 February 2007 04:54:44 pm Daniel P. Berrange wrote: > > Having repeatedly said that we should be doing TLS encryption for VNC, I > > figured I ought to get down & implement it. So, in the spirit of 'release > > early, release

Re: [Qemu-devel] [PATCH] Make removing IOHandlers safe from within an IOHandler

2007-02-24 Thread Daniel P. Berrange
On Sat, Feb 24, 2007 at 11:54:17AM -0600, Anthony Liguori wrote: > I was getting random SEGVs when disconnecting from the VNC server. I > tracked it down to the fact that if you remove a IOHandler from another > IOHandler, all sorts of badness may result as you're removing entries > from a link

[Qemu-devel] [PATCH] Make removing IOHandlers safe from within an IOHandler

2007-02-24 Thread Anthony Liguori
I was getting random SEGVs when disconnecting from the VNC server. I tracked it down to the fact that if you remove a IOHandler from another IOHandler, all sorts of badness may result as you're removing entries from a linked list while transversing it. My solution is to simply add a deleted f

[Qemu-devel] PATCH: Secure TLS encrypted authentication for VNC

2007-02-24 Thread Daniel P. Berrange
Having repeatedly said that we should be doing TLS encryption for VNC, I figured I ought to get down & implement it. So, in the spirit of 'release early, release often', here is the very first cut of my patch for QEMU. This isn't suitable for inclusion in CVS yet - I just want to put it out for pe

Re: [Qemu-devel] Page protection and i386 cmpxchg8b

2007-02-24 Thread Pierre d'Herbemont
On 23 févr. 07, at 23:56, Ilya Shar wrote: Sure. At first I was hitting unsupported mach syscalls, so I modified darwin-user/syscall.h according to /Developer/SDKs/MacOSX10.3.9.sdk/usr/include/mach/syscall_sw.h : $ diff syscall.c syscall.c.orig 458,465d457 < case -33: < DPRINTF("s