Hi all
I've found two repeatable (possibly related) ways to crash kqemu with 0.9.0
and several earlier versions also I think. It's under linux 2.6.9 fully
updated CentOS 4.4 (clone of RH enterprise linux 4.4)
First, I cannot use kqemu 1.3.0pre11 (either prebuilt or compiled from
source, they're b
> Could you try to find out which change in qemu triggers this behaviour?
> I don't have a windows to test, and given there weren't (yet :-) loud
> complaints I figure the problem might be connected to you local setup.
Ah, found it. I guess cvs after September requires updated .bin files.
Sorry.
I just compiled CVS and have experienced a regression with some windows
qcow images (2000 pro and server). The images work with cvs I compiled back
in July, but current cvs produces blue screen with INACCESSIBLE_BOOT_DEVICE.
I'm running under linux, with only option -hda disk.
Thanks
_
> > - I noticed that images refer to their base image using an absolute path. Is
> > there a way to change an image's base image reference? (for example when the
> > base image is renamed / moved to a different directory)
> qemu-img convert [-c] -O qcow
> should do what you want.
I believe that
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
I've heard that VMware has the ability to do delta (incremental) images but
I've never found it. With Qemu it's easy to make a large (read-only) system
image (burned to CD or DVD, for example) and have all disk writes go to
a different smaller media (like the USB flash drive you booted from, which
I'm using CVS i386, running patched win2000 on a 4G qcow install,
FAT formatted. Command line has only -hda and -snapshot.
Qemu crashes consistently when I pull up the Disk Administrator in
Administrative Tool's Computer Management, and click on the FAT partition.
I get output like this:
EAX=000
First some suggestions for what they're worth...
$ qemu-img info someimage
image: someimage
file format: qcow
virtual size: 75G (80026361856 bytes)
disk size: 304K
For files with a backing file, has anyone thought about having it print out
the name of the backing file? Particularly this would b
With the new command-line syntax for 0.8.0 I've modified the program that
opens up tap devices (tundev.c) accordingly. The diffs are below for both
tundev.c and another version that opens up two nics, tundev2.c.
I am not providing the whole program because its license is not stated.
If Fabrice can
Hi, it looks like I stirred up some change by asking about tun and tap.
(and definately it's important to know that "tun" is a tap device!)
In case anyone's interested, here is a tapdev2.c that I put together
to make use of two virtual nics as tap devices. Maybe also the script
setup will interest
I'm very pleased with qemu's price/performance ratio.
I've used that one "pricey" product at work, but it always seemed a bit
expensive for home users. But I only knew about some of the other emulators,
the ones that are so slow you wonder why didn't they warn you not to
bother downloading the thi
11 matches
Mail list logo
