On Wednesday 16 April 2014 10:44:36 Rick Vernam wrote:
On Wednesday 16 April 2014 07:12:16 Richard Vernam wrote:
On Apr 16, 2014 3:07 AM, Dr. David Alan Gilbert dgilb...@redhat.com
wrote:
* Rick Vernam (rtver...@hobi.com) wrote:
On Tuesday 15 April 2014 19:25:22 Rick Vernam wrote
On Wednesday 16 April 2014 07:12:16 Richard Vernam wrote:
On Apr 16, 2014 3:07 AM, Dr. David Alan Gilbert dgilb...@redhat.com
wrote:
* Rick Vernam (rtver...@hobi.com) wrote:
On Tuesday 15 April 2014 19:25:22 Rick Vernam wrote:
Looks like it's in Spice:
snip old backtrace without
I have been trying out the 2.0 RCs, and I've noticed that when I use spice
qemu aborts when I reboot the VM. This occurs on Win XP guest, Win 7 (64-bit)
guest and Win 8 (64-bit) guest.
Is this something that anybody else experiences?
I don't care to divert anybody's energy if this a spice thing
Gilbert wrote:
* Rick Vernam (rtver...@hobi.com) wrote:
I have been trying out the 2.0 RCs, and I've noticed that when I use spice
qemu aborts when I reboot the VM. This occurs on Win XP guest, Win 7
(64-bit) guest and Win 8 (64-bit) guest.
Is this something that anybody else experiences
On Tuesday 15 April 2014 19:25:22 Rick Vernam wrote:
Looks like it's in Spice:
[New Thread 0x7ffe5dffb700 (LWP 28129)]
main_channel_handle_parsed: agent start
main_channel_handle_parsed: agent start
[Thread 0x7fff5a7fc700 (LWP 28072) exited]
Program received signal SIGSEGV, Segmentation
Yes, I would say it is the same bug. I will test the driver that Vadim
linked in Comment 33
(https://bugzilla.redhat.com/show_bug.cgi?id=771390#c33) and report
back.
Thanks, Mike, for posting here.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
well, the link in the redhat bug, comment 33, is no good apparently. I
will follow that bug, and test when I see Vadim has posted a new driver
to test.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
I experience this on uni-processor.
On Tuesday 24 January 2012 16:48:04 Vitalis wrote:
And more: i have too more virtual PC with WindowsXP SP3 and with one
CPU, but them doesnt have any problems. Maybe this bug depends on 2 and
more CPU??
--
You received this bug notification because you are
In reply to comment #32, I encounter this problem with 1VCPU - see the original
description of the bug.
Also note that after qemu quits with the error, the subsequent execution of the
same qemu invocation will run stable.
--
You received this bug notification because you are a member of qemu-
From the Qemu Monitor, try looking at info mice
I'm not exactly sure ho to access the Qemu Monitor from VNC. You might have
to start qemu with additional parameters: -monitor
telnet:localhost:12341,server,nowait
then use telnet localhost 12341 to access the monitor...
On Monday 19 December
On Monday 07 November 2011 15:58:24 Anthony Liguori wrote:
Hi,
On behalf of the QEMU Team, I'd like to announce the availability of QEMU
1.0, release candidate 1. This is the first release candidate for the 1.0
release. This is not intended for production use but rather for testing.
To
On Tuesday 08 November 2011 12:50:47 Stefan Weil wrote:
Am 08.11.2011 18:42, schrieb Rick Vernam:
Are there supporting windows binaries (ie, various virtio drivers and
vdagent)?
Also, I've seen instructions to build the various windows binaries from
source in a number of different
On Tuesday 01 November 2011 19:43:53 Anthony Liguori wrote:
Hi,
I've just pushed the VERSION update so we are officially in hard freeze.
I've cleared out my patch and pull request queues and processed everything
I intend on processing for 1.0.
If you're a contributor and have a question
On Tuesday 11 October 2011 10:45:14 Paolo Bonzini wrote:
Hi all, please go here to cast your vote on when QEMU 1.0 test day will
be help.
http://www.doodle.com/35ae4zk7e4ndb5qq
Having an official date will make it easier to put people in contact
and have someone reproducing other
So I've built qemu with -enable-debug and tried running with an attached GDB,
but got nothing.
I've never tried to debug Qemu before, but I know it's not quite a simple as
debugging other apps.
I am honestly clueless about how to further debug this problem.
Should I give up on using
Vadim,
Did you see comment #27? Is that helpful, would you like any additional
info? Are there other things you would like for me to try?
Thanks,
-Rick
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On Friday 23 September 2011 14:07:17 Alon Levy wrote:
On Thu, Sep 22, 2011 at 02:10:04PM -0500, Rick Vernam wrote:
On Friday 16 September 2011 12:42:02 Rick Vernam wrote:
On Friday 16 September 2011 03:52:34 hkran wrote:
[snip]
I have tried many times with many restarts
On Friday 16 September 2011 12:42:02 Rick Vernam wrote:
On Friday 16 September 2011 03:52:34 hkran wrote:
[snip]
I have tried many times with many restarts or shutdown-and-boot xp guest
but failed to meet the crashing.
(I am using the virtio drivers referenced in the earlier mail list
On Friday 16 September 2011 03:52:34 hkran wrote:
[snip]
I have tried many times with many restarts or shutdown-and-boot xp guest
but failed to meet the crashing.
(I am using the virtio drivers referenced in the earlier mail list.)
my command:
/home/huikai/qemu15/bin/qemu --enable-kvm
On Friday 16 September 2011 12:42:02 Rick Vernam wrote:
On Friday 16 September 2011 03:52:34 hkran wrote:
[snip]
I have tried many times with many restarts or shutdown-and-boot xp guest
but failed to meet the crashing.
(I am using the virtio drivers referenced in the earlier mail list
On Wednesday 14 September 2011 16:30:11 Rick Vernam wrote:
On Wednesday 14 September 2011 14:42:09 vrozenfe wrote:
Thank you, Rick.
Could you help me to narrow this problem down?
Absolutely.
As I see, you have three virtio drivers installed on your system - block,
net, and virtio
On Thursday 15 September 2011 11:23:53 Rick Vernam wrote:
On Wednesday 14 September 2011 16:30:11 Rick Vernam wrote:
On Wednesday 14 September 2011 14:42:09 vrozenfe wrote:
Thank you, Rick.
Could you help me to narrow this problem down?
Absolutely.
As I see, you have three
so if I use -vga std instead of -vga qxl (and of course take out the -spice
stuff), I don't crash.
perhaps this is spice/qxl related?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818673
Title:
sorry, scratch that last about -vga std ... it still crashed just the
same using -vga std.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818673
Title:
virtio: trying to map MMIO memory
Status in
On Wednesday 14 September 2011 14:42:09 vrozenfe wrote:
Thank you, Rick.
Could you help me to narrow this problem down?
Absolutely.
As I see, you have three virtio drivers installed on your system - block,
net, and virtio serial. Technically, anyone of them can create trying to
map MMIO
Still crashes just the same.
I updated the drivers for virt net, scsi serial from the XP and WXp folders
in the zip file that you referenced.
Then I shutdown the VM.
Because it only seems to happen every other time that Qemu is started, I
started it back up and shut it down again.
Then the VM
ping...
I understand that Vadim must be very busy that he can't look at this - I can
relate.
But is there really only one person in all of Qemu and/or Spice who can be
addressed to look into this?
So that I can plan around the viability of Qemu for my users, I need to
know if the technologies
Using qemu-kvm-0.15.0 for a few weeks now, I'd like to report that maybe
1/10 times it works as expected: ie, there is no virtio-serial-bus
error, vdagent in the windows guest starts, etc.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
So that would point to virtio. This appears to be the place for virtio bugs,
correct?
Should I be doing anything to help usher this along?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818673
Continues with Qemu 0.15.0 and Qemu-KVM 0.15.0
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818673
Title:
virtio: trying to map MMIO memory
Status in QEMU:
New
Bug description:
Qemu host is
This continues to occur with qemu-kvm 0.15 on only one of my WXP VMs.
The fact that one of them works fine led me to believe it was a windows
issue (or spice), but the fact that both work fine with straight qemu
indicates that there is something with qemu-kvm involved in the problem.
--
You
On Tuesday 09 August 2011 21:34:10 Natalia Portillo wrote:
Hi,
El 08/08/2011, a las 20:16, Anthony Liguori escribió:
Hi,
On behalf of the entire QEMU team, I'm please to announce the release of
QEMU 0.15.0. This is the first release of the 0.15 branch and is
intended for production
Vadim,
Have you been able to reproduce this?
Do you require any additional information?
Thanks,
-Rick
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/818673
Title:
virtio: trying to map MMIO
it seems that qxl is not working correctly with any of the 0.15 releases thus
far. this includes qemu and qemu-kvm.
when I start qemu like so:
qemu-system-x86_64 -cpu host -enable-kvm -m 768 -usb -vga qxl -monitor stdio
I get a black screen.
when I start with -vga std:
qemu-system-x86_64 -cpu
./configure --disable-vnc
make
...
monitor.o: In function `add_graphics_client':
/home/rick/qemu/src/qemu-0.15.0-rc1/monitor.c:1205: undefined reference to
`vnc_display_add_client'
On Thursday 04 August 2011 11:09:30 Daniel P. Berrange wrote:
On Thu, Aug 04, 2011 at 11:03:10AM -0500, Rick Vernam wrote:
it seems that qxl is not working correctly with any of the 0.15 releases
thus far. this includes qemu and qemu-kvm.
when I start qemu like so:
qemu-system-x86_64
On Thursday 04 August 2011 13:15:35 Gerd Hoffmann wrote:
Hi,
I recently had black screen problems with QXL in 0.14.x that turned out
to actually be a Seabios bug due to the default 64MB vram QXL has.
It is a seabios issue indeed.
I suspect
this would hit 0.15.x builds too. If
sorry, the output from qemu-kvm which seems to indicate an error is
qemu-system-x86_64: virtio-serial-bus: Unexpected port id 3125770964 for device
virtio-serial0.0
or sometimes
qemu-system-x86_64: virtio-serial-bus: Unexpected port id 47936 for device
virtio-serial0.0
--
You received this bug
Public bug reported:
With qemu-kvm-0.15.0-rc1 virtio-serial-bus reports an error, and windows
vdagent can not start. qemu-0.15.0-rc1 behaves as expected, ie vdagent runs in
the guest, mouse passes seamlessly between spicec and host and copy/paste works
between guest and host.
qemu-kvm has
Continues to occur with recently updated qxl, vdagent virtio serial windows
binaries from spice-space.org.
Also continues with qemu-kvm-0.15.0-rc1, qemu-0.15.0-rc1 qemu-0.15.0-rc2
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Seems to only crash the first time qemu is started after booting the host
machine.
After the first crash, qemu will run solid for days if the host machine is not
rebooted.
If I have an opportunity, I'll test if it also crashes after first start when
kvm and/or kvm_intel modules are unloaded and
On Monday 01 August 2011 09:34:32 Gerd Hoffmann wrote:
On 07/29/11 04:48, Rick Vernam wrote:
I'd like to do some very high-level testing of qemu-stable-0.15
(qemu-system- x86_64, specifically) running Linux host, Windows XP SP3
guest.
I'm afraid that I don't have a ready environment
Public bug reported:
Qemu host is Core i7, running Linux. Guest is Windows XP sp3.
Often, qemu will crash shortly after starting (1-5 minutes) with a statement
qemu-system-x86_64: virtio: trying to map MMIO memory
This has occured with qemu-kvm 0.14, qemu-kvm 0.14.1, qemu-0.15.0-rc0 and qemu
I'd like to do some very high-level testing of qemu-stable-0.15 (qemu-system-
x86_64, specifically) running Linux host, Windows XP SP3 guest.
I'm afraid that I don't have a ready environment for building the windows
guest bits, and the added time requirement simply puts it over the top for me.
Serge,
I run qemu-kvm from source. My distro is Gentoo, so I can't check your debs.
I applied the patch from comment #4 last night and found that I have not
encountered this bug since.
Let me know if I can provide any additional info...
--
You received this bug notification because you are a
On Tuesday 01 March 2011 12:29:14 Serge Hallyn wrote:
@Rick,
would you expect a fedora guest to reproduce this? Would it have the
qxl driver? Or must it be Windows?
I don't have a fedora guest to test on, and I don't know the implementation
details well enough to postulate.
-Rick
On Sunday 27 February 2011 13:03:14 Alon Levy wrote:
On Sat, Feb 26, 2011 at 01:29:01PM +0100, Jan Kiszka wrote:
On 2011-02-26 12:43, xming wrote:
When trying to start X (and it loads qxl driver) the kvm process just
crashes.
This is fixed by Gerd's attached patch (taken from rhel
I also intended to mention that using qemu-0.14.0 works just fine; the
crash only occurs with qemu-kvm-0.14.0.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/723871
Title:
qemu-kvm-0.14.0 Aborts
Public bug reported:
Host CPU is Core i7 Q820. KVM is from 2.6.35-gentoo-r5 kernel (x86_64).
Host has spice-0.7.2 and spice-protocol-0.7.0.
Guest is Windows XP SP3 with qxl driver 0.6.1, virtio-serial 1.1.6 and vdagent
0.6.3.
qemu-kvm is started like so:
qemu-system-x86_64 -cpu host
sorry, on the guest it is virtio-serial-1.1.16, not 1.1.6.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/723871
Title:
qemu-kvm-0.14.0 Aborts with -vga qxl
Status in QEMU:
New
Bug description:
On Thursday 17 February 2011 16:06:24 Anthony Liguori wrote:
The QEMU team is pleased to announce the availability of the 0.14.0
release.
Download instructions are available at http://wiki.qemu.org/Download
A detailed change log is available at http://wiki.qemu.org/Changelog/0.14
On
Using 0.14.0-rc2 it looks like a SPICE pid file is left over in /dev/shm, ie
spice.10005, after qemu closes.
Please reply to this message with a subject starting with [PING 0.14]
and a link to patchwork, gmane, or whatnot; or [PULL 0.14] for tree
pulls. Also, I believe all patches meant for stable should also start
having [PATCH 0.14], too.
I am not the author of this patch, but it fixed a
Please reply to this message with a subject starting with [PING 0.14]
and a link to patchwork, gmane, or whatnot; or [PULL 0.14] for tree
pulls. Also, I believe all patches meant for stable should also start
having [PATCH 0.14], too.
I'm not sure how to tell which version of seabios is
I encountered two issues with 0.13.0-rc1, not sure how to tell if the patches
have been applied?
one is this patch: http://patchwork.ozlabs.org/patch/62420/
discussed here:
http://lists.nongnu.org/archive/html/qemu-devel/2010-09/msg01114.html
the other was
On Wednesday 15 September 2010 05:46:55 Yoshiaki Tamura wrote:
Hi Rick,
2010/9/15 Corentin Chary corentin.ch...@gmail.com:
On Tue, Sep 14, 2010 at 10:00 PM, Rick Vernam ri...@hobi.com wrote:
I don't have nearly enough info to file a proper bug report.
I am running qemu-kvm-0.13.0 rc1
On Wednesday 15 September 2010 05:46:55 you wrote:
Hi Rick,
2010/9/15 Corentin Chary corentin.ch...@gmail.com:
On Tue, Sep 14, 2010 at 10:00 PM, Rick Vernam ri...@hobi.com wrote:
I don't have nearly enough info to file a proper bug report.
I am running qemu-kvm-0.13.0 rc1
starting
I don't have nearly enough info to file a proper bug report.
I am running qemu-kvm-0.13.0 rc1
starting qemu like so:
/root/qemu/bin/qemu-system-x86_64 -cpu host -enable-kvm -drive
file=/root/qemu/w2k3_server.raw,if=virtio,aio=native -net
nic,model=virtio,macaddr=52:54:00:12:34:56 -net
On Wednesday 15 September 2010 10:24:29 Gleb Natapov wrote:
On Wed, Sep 15, 2010 at 10:16:29AM -0500, Rick Vernam wrote:
I don't have nearly enough info to file a proper bug report.
I am running qemu-kvm-0.13.0 rc1
starting qemu like so:
/root/qemu/bin/qemu-system-x86_64 -cpu host
On Wednesday 15 September 2010 10:32:51 Gleb Natapov wrote:
On Wed, Sep 15, 2010 at 10:30:38AM -0500, Rick Vernam wrote:
On Wednesday 15 September 2010 10:24:29 Gleb Natapov wrote:
On Wed, Sep 15, 2010 at 10:16:29AM -0500, Rick Vernam wrote:
I don't have nearly enough info to file
On Wednesday 15 September 2010 10:16:29 Rick Vernam wrote:
I noticed this failure with qemu-0.13.0-rc0, qemu-0.13.0-rc1 qemu-
kvm-0.13.0-rc1
I should have also mentioned that I did not try with any previous version of
Qemu or Qemu-KVM.
If you think it would be a worth while test, I will run
On Wednesday 15 September 2010 10:57:10 Gleb Natapov wrote:
On Wed, Sep 15, 2010 at 10:50:15AM -0500, Rick Vernam wrote:
On Wednesday 15 September 2010 10:32:51 Gleb Natapov wrote:
On Wed, Sep 15, 2010 at 10:30:38AM -0500, Rick Vernam wrote:
On Wednesday 15 September 2010 10:24:29 Gleb
On Wednesday 15 September 2010 10:16:29 Rick Vernam wrote:
I don't have nearly enough info to file a proper bug report.
I am running qemu-kvm-0.13.0 rc1
starting qemu like so:
/root/qemu/bin/qemu-system-x86_64 -cpu host -enable-kvm -drive
file=/root/qemu/w2k3_server.raw,if=virtio,aio=native
I don't have nearly enough info to file a proper bug report.
I am running qemu-kvm-0.13.0 rc1
starting qemu like so:
/root/qemu/bin/qemu-system-x86_64 -cpu host -enable-kvm -drive
file=/root/qemu/w2k3_server.raw,if=virtio,aio=native -net
nic,model=virtio,macaddr=52:54:00:12:34:56 -net
On Wednesday 07 July 2010 13:57:48 Corentin Chary wrote:
This set contains all my patchs related to tight and threaded vnc server.
Since v1:
* Add a fix for jpeg and png with non-24bpp displays
* Better default values for vnc options in ./configure
* Fixed Tight PNG to use its own encoding
On Tuesday 20 April 2010 09:15:36 Chris Wright wrote:
call agenda
- send out a bit earlier
- cancel call if no agenda
0.12.4
- expect when Anthony is back online
For planning purposes, is there a ballpark time line?
I do not know the nature of Anthony's absence; my deepest apology if my
On Monday 01 February 2010 08:26:54 Anthony Liguori wrote:
Hi,
The new qemu.org wiki is now live. I've transferred all of the content
from the old website and have now switched www.qemu.org to redirect to
wiki.qemu.org.
My hope is with the new wiki format, qemu.org can be a centralized
On Tuesday 17 November 2009 12:11:58 am Luiz Felipe wrote:
Hi, i tried to use kqemu in ubuntu to start Windows XP SP3. I used the
command line: qemu -kernel-kqemu and the system started to run windows on
qemu. Although, i observed the following message on my shell:
QEMU acceleration layer
WTF? Rick suggested removing that configure message that you need to
explicitely override its quite sane default to refuse work with gcc4,
because at least one platform (the most common one) has problems with it.
I did? where? when? You might have mis-read something.
I was against
On Friday 14 March 2008 06:07:37 am Andreas Färber wrote:
So I absolutely _fail_ to understand what you thought, implying that
I was
restricting platform variability.
So in fact you do agree with Rick on that part and replied to the
'wrong' message, creating minor confusion: In your
On Friday 14 March 2008 07:59:28 am Rick Vernam wrote:
And it is necessary to have configure require a special step to build with
gcc4 anyway.
necessary, as in a very good idea.
necessary to inform those who might not otherwise know...
Pulling todays CVS (including Aurelien Jaron's recent commits), I've not been
able to build.
./configure --prefix=/usr --enable-ac97 --enable-alsa --disable-vnc-tls
--disable-linux-user --disable-gcc-check --target-list=i386-softmmu
make
[...]
gcc -Wall -O2 -g -fno-strict-aliasing
On Thursday 13 March 2008 04:27:29 pm Ben Taylor wrote:
On Thu, Mar 13, 2008 at 4:47 PM, Paul Brook [EMAIL PROTECTED] wrote:
gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.2)
Which part of gcc 4.x is not supported didn't you understand?
Paul
Apparently, we should make configure fail horribly
On Wednesday 20 February 2008 01:01:33 pm Anthony Liguori wrote:
Daniel P. Berrange wrote:
On Wed, Feb 20, 2008 at 04:31:56PM +, Jamie Lokier wrote:
Ian Jackson wrote:
Paul Brook writes (Re: [Qemu-devel] [PATCH] bdrv_flush error
handling):
Disk full is a fundamentally unfriendly
On Tuesday 04 December 2007 06:35:53 pm Carlo Marcelo Arenas Belon wrote:
On Mon, Dec 03, 2007 at 08:20:28PM -0600, Rick Vernam wrote:
any comments on the current status of moving beyond dependency on GCC
3.3.6?
you meant dependency on GCC 4 right?
yeah..thanks.
I use gcc 3.4.6
any comments on the current status of moving beyond dependency on GCC 3.3.6?
no need to go into details of 'why' on my behalf, so spare yourself the time
on that... :-)
thanks
On Thursday 08 November 2007 10:51:01 pm Kyle Kilpatrick wrote:
Hello. First, let me say that I realize this is not exactly the place for
this. Non-developer problems with Qemu should go on the Qemu forum... But
they're down right now, so please bear with me here. I apologize for
taking up
Regarding this patch, adding VMware's VGA SVGA II emulation:
http://lists.gnu.org/archive/html/qemu-devel/2007-03/msg00116.html
I just decided to try it today, but did not get very good results.
I tried with User+Kernel kqemu, just user kqemu no kqemu
with -soundhw es1370 -vmwarevga it
sorry - accidentally sent before I finished the mail...
On Tuesday 25 September 2007 12:06:28 pm Rick Vernam wrote:
Regarding this patch, adding VMware's VGA SVGA II emulation:
http://lists.gnu.org/archive/html/qemu-devel/2007-03/msg00116.html
I just decided to try it today, but did not get
On Tuesday 27 March 2007 08:53:42 pm Rick Vernam wrote:
On Tuesday 27 March 2007 06:34:04 pm Kyle Hubert wrote:
I've been looking online, but I can't say that I have found the answer
to this yet.
When using QEMU, I've noticed that if I switch away to a different
virtual desktop
On Tuesday 27 March 2007 06:34:04 pm Kyle Hubert wrote:
I've been looking online, but I can't say that I have found the answer
to this yet.
When using QEMU, I've noticed that if I switch away to a different
virtual desktop on the host OS's WM, then QEMU stops what it is doing.
It's really
I recently built cvs, and found that I can no longer have multiple instances
of qemu using tun/tap.
the invocation of qemu includes, for each instance:
-net nic -net tap,script=/etc/qemu-ifup
/etc/qemu-ifup:
#!/bin/sh
sudo /sbin/ifconfig $1 192.168.2.196
sudo brctl addif br0 $1
strace of
a while to figure
out where the bad call to tap_open is coming from...
On Tuesday 09 January 2007 10:57, Rick Vernam wrote:
I recently built cvs, and found that I can no longer have multiple
instances of qemu using tun/tap.
the invocation of qemu includes, for each instance:
-net nic -net tap
I'm not too familiar with diff, so if the attached patch is no good, please do
let me know how to correct it.
On Tuesday 09 January 2007 11:57, Rick Vernam wrote:
in vl.c, it looks like tap_open is called with an uninitialized ifname -
instead of ifname[0] == '\0', or a valid ifname
I've spent quite a lot of time trying to figure out why this keeps happening:
$ export QEMU_AUDIO_DRV=alsa
$ qemu-system-x86_64 -kernel-kqemu -hda /home/rick/docs/.qemu/wxp1.qemu -m
192 -net nic -net tap,script=/etc/qemu-ifup -localtime -snapshot -usbdevice
tablet -soundhw es1370
alsa: Could
On Wednesday 05 July 2006 15:57, Daniel Carrera wrote:
Try to take this approach: You are writing to a technically competent
user (perhaps a sysadmin) who wants to run Windows under Linux with qemu
(perhaps to migrate some of the company computers). He has a Windows
install CD, he has qemu
qemu -cdrom /dev/cdrom -hda /path/to/your/image -boot d
On Wednesday 05 July 2006 16:19, Daniel Carrera wrote:
On Wed, 2006-05-07 at 17:12 -0400, Nathaniel McCallum wrote:
A person who is in your position (frustrated for lack of documentation)
is actually the most qualified person to write
On Saturday 17 June 2006 11:32, Alex wrote:
This patch has been around for a while but never committed to the
mainstream.
Are there any known issues with the patch?
not here.
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
QEMU leaves me with very few 'itches to be scratched' ...
The basic tasks that a QUI should confine itself to, IMO, are already pretty
darn easy - define/manage a VM (via a shell script for me), start it, stop
it, pause it...etc..
Even so, I've been thinking about this for some time - months
On Thursday 15 June 2006 23:31, Joe Lee wrote:
I glad to see many people sharing comments and making suggestions since
this thread topic started. I seems there enough interest to have a
GUI-Frontend for QEMU. I am hopeful this can lead to getting something
started.
I'd like to see a poll
90 matches
Mail list logo
