Am 17.12.2009 um 05:26 schrieb G 3 programmingk...@gmail.com:
Everytime I try to send a patch using 'git send-email', I receive
this error:
qemu-devel@nongnu.org: host mx10.gnu.org[199.232.76.166] said:
550-Verification failed for localhost
550-Unrouteable address 550 Sender verify
On 12/17/09 00:47, Alexander Graf wrote:
Am 16.12.2009 um 18:46 schrieb Gerd Hoffmann kra...@redhat.com:
Hi,
quick draft of a file xfer api for fw_cfg, qemu side only, not tested
yet, to be used for option roms.
comments?
2/3 is missing here.
Hmm, I got it via qemu-devel. Maybe it is
On 12/17/09 02:24, Kevin O'Connor wrote:
On Wed, Dec 16, 2009 at 05:22:41PM +0100, Gerd Hoffmann wrote:
The current CBFS mechanism looks for named files of the following
form:
- pci,.rom - a rom associated with a PCI device with the given
vendor and device id.
Might be useful for
On Thu, Dec 17, 2009 at 10:45:45AM +0100, Gerd Hoffmann wrote:
On 12/17/09 02:24, Kevin O'Connor wrote:
On Wed, Dec 16, 2009 at 05:22:41PM +0100, Gerd Hoffmann wrote:
The current CBFS mechanism looks for named files of the following
form:
- pci,.rom - a rom associated with a PCI
Gerd Hoffmann wrote:
On 12/17/09 00:47, Alexander Graf wrote:
Am 16.12.2009 um 18:46 schrieb Gerd Hoffmann kra...@redhat.com:
Hi,
quick draft of a file xfer api for fw_cfg, qemu side only, not tested
yet, to be used for option roms.
comments?
2/3 is missing here.
Hmm, I got it via
Hi guys,
I've gotten vmware going again on master using some patches from
Anthony (rebased onto master)
and a fix for the cursor pixmap which was causing a segfault.
The patches are in
git://people.freedesktop.org/~airlied/qemu.git vmware-queue
struct fw_files {
u32 filecount;
struct fw_file {
u32 type;/* vga, option, other? */
u32 size;/* file size */
u32 select; /* write this to 0x510 to read it */
u32 reserved;/* you never know ;) */
char name[16];/* maybe:
On Tue, Dec 15, 2009 at 06:45:01PM +, Jamie Lokier wrote:
access=rw
access=ro
access=auto (default)
Yes, that sounds like the least clumsy one. I still think the current
implementation is a very bad default, though.
FYI I don't think this is all too useful. Just about no one actually
uses file locking APIs on block devices. If you want to provide
protection against mounting the image on the host or scribbling over it
using mkfs you need to open the block device node with O_EXCL on Linux
as that's the
On Thu, Dec 17, 2009 at 11:53:45AM +0100, Christoph Hellwig wrote:
If you're primarily interested in protection against other qemu
instances you can add you code on top, but that seems like a rather
marginal use case.
It's a pretty serious case for people accessing live virtual machines
with
On Mon, Dec 14, 2009 at 03:35:07PM +0200, Naphtali Sprei wrote:
block.c | 29 +
block.h |7 +--
hw/xen_disk.c |3 ++-
monitor.c |2 +-
qemu-config.c |4 ++--
qemu-img.c| 14 --
qemu-nbd.c|2 +-
We used to always create one single virtio console device. This breaks when
either zero of multiple virtio console devices are requested, so let's use
the same code as on x86.
Signed-off-by: Alexander Graf ag...@suse.de
---
hw/s390-virtio.c |6 +-
1 files changed, 5 insertions(+), 1
While trying out 0.12-rc2 on my S390x, I stumbled over several issues.
This set fixes them, making KVM on S390x work great again.
Alexander Graf (3):
S390: Loop through virtio console devices
add default virtcon initialization
S390: Don't tell guest we're updating config space
When going through the default devices, we don't initialize the virtio
console, unless we're doing -nographic.
I suppose that's just a leftover from the recent code restructuring, so
let's put it in.
Signed-off-by: Alexander Graf ag...@suse.de
---
vl.c |2 ++
1 files changed, 2
Currently we always set the config space changed bit to 1 when triggering
any virtio interrupt. While that worked in 2.6.27, newer kernels interpret
that value as only the config space changed and nothing else happened.
Since we usually trigger interrupts to tell the guest that something did
Hi,
All in one patch series for pci rom bar support and option rom loading
via fw_cfg for the non-pci roms. This time the fw_cfg interface is
actually tested with a little linux userspace app (attached below).
cheers,
Gerd
- [ cut here ] -
#include stdio.h
#include stdlib.h
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/fw_cfg.c | 26 --
hw/fw_cfg.h | 16 +---
2 files changed, 21 insertions(+), 21 deletions(-)
diff --git a/hw/fw_cfg.c b/hw/fw_cfg.c
index b25afff..2e3662d 100644
--- a/hw/fw_cfg.c
+++ b/hw/fw_cfg.c
@@
From: Anthony Liguori aligu...@us.ibm.com
Currently, we preload option roms into the option rom space in memory. This
prevents DDIM from functioning correctly which severely limits the number
of roms we can support.
This patch introduces a pci_add_option_rom() which registers the
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/loader.c | 25 ++---
hw/loader.h |5 +++--
hw/pc.c |2 ++
3 files changed, 27 insertions(+), 5 deletions(-)
diff --git a/hw/loader.c b/hw/loader.c
index 2d7a2c4..451ee54 100644
--- a/hw/loader.c
+++
We were being a bit too nice and didn't give the guest an invalid instruction
interrupt.
While that works, it's not exactly the fastest thing to do, since now the
guest doesn't know that we're not really implementing that instruction, so it
continues doing it.
We run into this with the
Signed-off-by: David Kozub z...@linux.fjfi.cvut.cz
---
qemu-binfmt-conf.sh |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/qemu-binfmt-conf.sh b/qemu-binfmt-conf.sh
index ba916ac..9c65c9a 100644
--- a/qemu-binfmt-conf.sh
+++ b/qemu-binfmt-conf.sh
@@ -1,5 +1,5 @@
Christoph Hellwig wrote:
On Tue, Dec 15, 2009 at 06:45:01PM +, Jamie Lokier wrote:
access=rw
access=ro
access=auto (default)
Yes, that sounds like the least clumsy one. I still think the current
implementation is a very bad default, though.
Without agreeing or disagreeing over
Kevin Wolf wrote:
You might think the user could do that by setting the permissions to
read-only, but root ignores file permissions. (That's why we need a
ro option too).
We do have readonly=on|off.
Sure, but if you have to do that for safe behaviour when running qemu
as root, and you
Am 17.12.2009 14:16, schrieb Jamie Lokier:
Christoph Hellwig wrote:
On Tue, Dec 15, 2009 at 06:45:01PM +, Jamie Lokier wrote:
access=rw
access=ro
access=auto (default)
Yes, that sounds like the least clumsy one. I still think the current
implementation is a very bad default, though.
Jamie Lokier ja...@shareable.org writes:
Christoph Hellwig wrote:
On Tue, Dec 15, 2009 at 06:45:01PM +, Jamie Lokier wrote:
access=rw
access=ro
access=auto (default)
Yes, that sounds like the least clumsy one. I still think the current
implementation is a very bad default,
This patch series adds the functionality to change the backing file of existing
images. This includes simple renaming of a backing file without converting the
COW image as well as safe rebasing onto a different backing file that has some
changes compared to the current backing file.
v2:
- Added
This adds a rebase subcommand to qemu-img which allows to change the backing
file of an image.
In default mode, both the current and the new backing file need to exist, and
after the rebase, the COW image is guaranteed to have the same guest visible
content as before. To achieve this, old and new
If an image references a backing file that doesn't exist, qemu-img info fails
to open this image. Exactly in this case the info would be valuable, though:
the user might want to find out which file is missing.
This patch introduces a BDRV_O_NO_BACKING flag to ignore the backing file when
opening
Introduce the functions needed to change the backing file of an image. The
function is implemented for qcow2.
Signed-off-by: Kevin Wolf kw...@redhat.com
---
block.c | 20 +
block.h |2 +
block/qcow2.c | 88 +
On 12/17/09 13:32, Gerd Hoffmann wrote:
Hi,
All in one patch series for pci rom bar support and option rom loading
via fw_cfg for the non-pci roms. This time the fw_cfg interface is
actually tested with a little linux userspace app (attached below).
Now some seabios bits.
I got the
Kevin Wolf wrote:
Am 17.12.2009 14:16, schrieb Jamie Lokier:
You can decide to protect your images with the qemu readonly option and
get the protection that qemu defines, or you take the permissions of the
OS and get from the OS whatever the definition of that protection is
(including write
On Wed, 16 Dec 2009, Richard Henderson wrote:
This patch series adds support for setcond (aka setcc) and
movcond (aka cmov) opcodes to TCG.
These new opcodes are considered required by the backend,
because expanding them at the tcg level breaks the basic block.
There might be some way to
Gerd Hoffmann wrote:
Hi,
All in one patch series for pci rom bar support and option rom loading
via fw_cfg for the non-pci roms. This time the fw_cfg interface is
actually tested with a little linux userspace app (attached below).
Does this mean that -kernel works with this series?
On Thu, Dec 17, 2009 at 4:32 PM, malc av1...@comtv.ru wrote:
[...]
Some:
a. It breaks tcg on PPC[1]:
...qemu/tcg/tcg.c:1378: tcg fatal error
What a surprise :-)
I can provide a similar patch for ARM (I already have one
for my own implementation of setcond), but I'll wait for this
patch
Christoph Hellwig wrote:
If you want to provide
protection against mounting the image on the host or scribbling over it
using mkfs you need to open the block device node with O_EXCL on Linux
as that's the mechanisms most tools and the filesystem code us for
exclusion.
Due to that I do
Signed-off-by: Markus Armbruster arm...@redhat.com
---
I took the liberty to create docs/. Existing documentation should move
there, but I left that for another day, because I want to get this file
out.
docs/qdev-device-use.txt | 353 ++
1 files
Reposting for inclusion into qemu for the next release (hopefully)
I've rebased against master and rediffed. Since we've missed 0.12 I've reordered
the patches so that virtio-rng depends on the socket reconnect patches,
and has the matching functionality thats needed to handle reconnect events.
This patch rationalises the declaration of inet_listen_opts such that
it matches the other inet_{listen,connect}_opts functions.
This change is needed for a patch adding socket reconection support.
Signed-off-by: Ian Molton ian.mol...@collabora.co.uk
---
qemu-sockets.c |9 +++--
This patch adds support for virtio-rng. Data is read from a chardev and
can be either raw entropy or received via the EGD protocol.
Signed-off-by: Ian Molton ian.mol...@collabora.co.uk
---
Makefile.target |2 +-
hw/pci.h|1 +
hw/virtio-pci.c | 27 +++
This patch adds a 'SIZE' type property to those available to qdevs.
It is the analogue of the OPT_SIZE property for options.
Signed-off-by: Ian Molton ian.mol...@collabora.co.uk
---
hw/qdev-properties.c | 34 ++
hw/qdev.h|4
Dave Airlie wrote:
Hi guys,
I've gotten vmware going again on master using some patches from
Anthony (rebased onto master)
and a fix for the cursor pixmap which was causing a segfault.
Excellent, I just ran into a bug report indicating that as the cause of
the seg fault.
The patches
Add a reconnect option that allows sockets to reconnect (after a
specified delay) to the specified server. This makes the virtio-rng driver
useful in production environments where the EGD server may need to be restarted.
Signed-off-by: Ian Molton ian.mol...@collabora.co.uk
---
On 12/17/2009 07:32 AM, malc wrote:
These new opcodes are considered required by the backend,
because expanding them at the tcg level breaks the basic block.
There might be some way to emulate within tcg internals, but
that doesn't seem worthwhile, as essentially all hosts have
some form of
On Mon, 14 Dec 2009, Richard Henderson wrote:
On 12/14/2009 04:31 PM, Richard Henderson wrote:
Hmph. One more patch for correctness. With this 183.equake runs correctly.
I just finished running all of spec2k Alpha through Qemu.
With these patches installed (the 4 fpu ones, and the 5 from
On Thu, Dec 17, 2009 at 03:41:47PM -0200, Luiz Capitulino wrote:
Hi there,
Currently, when a regular command doesn't have any data to output,
QMP will emit:
{ return: OK }
I thought this was a good idea because it has a clear meaning. Silly me,
this is optimized for humans, but
On 12/17/2009 09:07 AM, Richard Henderson wrote:
+ case TCG_COND_NE:
+ if (const_arg2) {
+ if ((uint16_t) arg2 == arg2) {
+ tcg_out32 (s, XORI | RS (arg1) | RA (0) | arg2);
+ }
+ else {
+ tcg_out_movi (s, TCG_TYPE_I32, 0, arg2);
+ tcg_out32 (s, XOR | SAB (arg1, 0, 0));
+ }
+ }
+ else {
+
On 12/17/2009 09:47 AM, malc wrote:
Urgh.. I really hate implementing those 2 ops.
See for example this lovely thread:
http://www.archivum.info/qemu-devel@nongnu.org/2008-06/00306/%5BQemu-devel%5D_%5B4705%5D_Fix_div%5Bu%5D2.
Heh, that one's pretty nasty.
But fwiw, you can just call into
Luiz Capitulino lcapitul...@redhat.com writes:
Hi there,
Currently, when a regular command doesn't have any data to output,
QMP will emit:
{ return: OK }
I thought this was a good idea because it has a clear meaning. Silly me,
this is optimized for humans, but for machines it
Luiz Capitulino wrote:
Hi there,
Currently, when a regular command doesn't have any data to output,
QMP will emit:
{ return: OK }
I thought this was a good idea because it has a clear meaning. Silly me,
this is optimized for humans, but for machines it introduces the problem
that
G 3 programmingk...@gmail.com wrote:
This patch allows for the file vl.c to compile without any warnings.
Signed-off-by: John Arbuckle programmingk...@gmail.com
---
vl.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/vl.c b/vl.c
index c0d98f5..b466fe0
There are places, like brcond2, where we know that the destination
of a forward branch will be within 127 bytes. Add the R_386_PC8
relocation type to support this, and add a flag to tcg_out_jxx to
generate it. Set the flag in the small forward branches in brcond2.
Signed-off-by: Richard
Implement conditional moves in the i386 backend.
Signed-off-by: Richard Henderson r...@twiddle.net
---
tcg/i386/tcg-target.c | 173 +
1 files changed, 173 insertions(+), 0 deletions(-)
diff --git a/tcg/i386/tcg-target.c b/tcg/i386/tcg-target.c
It is very handy to have a reliable mapping of a condition to its inverse.
This will be used in several patches to follow.
Signed-off-by: Richard Henderson r...@twiddle.net
---
tcg/tcg.h |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/tcg/tcg.h b/tcg/tcg.h
index
Defines setcond and movcond for implementing conditional moves at
the tcg opcode level. 64-bit-on-32-bit is expanded via a setcond2
primitive plus other operations.
Signed-off-by: Richard Henderson r...@twiddle.net
---
tcg/README| 26 +++-
tcg/tcg-op.h | 91
funny how you seem to follow the same paths I did months ago :-)
Heh. They are the obvious points for improvement in the emulation.
Hopefully we can get them finished this time, so that some third
person doesn't go through the same thing next year. =)
- cosmetics: don't use tabs and be sure
Split out tcg_out_cond from tcg_out_brcond. Add small arguments
to all branch functions for completeness. Unify all the calls to
generate branches within brcond2 and pass on the small flag.
Signed-off-by: Richard Henderson r...@twiddle.net
---
tcg/i386/tcg-target.c | 87
On 12/17/2009 05:11 AM, David Kozub wrote:
;;
+ sh4)
+ cpu=sh4
+ ;;
You don't need this entry. That table is supposed to be for changing
the name. You'd use it if uname returned sh4eb though...
r~
Gerd Hoffmann wrote:
This patch adds a romfile property to the pci bus. It allows to specify
a romfile to load into the rom bar of the pci device. The default value
comes from a new field in PCIDeviceInfo. The property allows to change
the file and also to disable the rom loading using an
Gerd Hoffmann wrote:
On 12/17/09 13:32, Gerd Hoffmann wrote:
Hi,
All in one patch series for pci rom bar support and option rom loading
via fw_cfg for the non-pci roms. This time the fw_cfg interface is
actually tested with a little linux userspace app (attached below).
Now some seabios
Rob Landley wrote:
For background of CELF project proposals, see:
http://elinux.org/CELF_Open_Project_Proposal_2010
Summary:
Integrate a flattened device tree parser into the emulator QEMU, so QEMU can
create board emulations on the fly (at runtime) from the same data files the
Linux
Gerd Hoffmann wrote:
On 12/15/09 23:51, Sebastian Herbszt wrote:
Qemu will map rom1.bin to PC_ROM_MIN_OPTION (0xc8000) and map rom2.bin
to 0xd.
No.
rom1.bin will be loaded to max(0xc8000, 0xc + cirrus-bios-size)
aligned to 2k, which (with cirrus) is 0xc9.
My bad - for some
On Thu, 17 Dec 2009, Richard Henderson wrote:
Defines setcond and movcond for implementing conditional moves at
the tcg opcode level. 64-bit-on-32-bit is expanded via a setcond2
primitive plus other operations.
Signed-off-by: Richard Henderson r...@twiddle.net
---
tcg/README| 26
Anthony Liguori wrote:
Sebastian Herbszt wrote:
What about isapc? Or (pci)pc with isa card?
I'm not sure how the bios enumerates isa option roms on bare metal.
Let's give this a shot:
A typical isa expansion card seems to have a jumper to select a I/O port, IRQ
and
boot rom location,
On Thu, 17 Dec 2009, Richard Henderson wrote:
;;
+ sh4)
+ cpu=sh4
+ ;;
You don't need this entry. That table is supposed to be for changing the
name. You'd use it if uname returned sh4eb though...
Indeed, I got swayed. Then also m68k and i386 are superfluous there.
As for sh4eb, AFAIK
The default iobase and irq for the ne2k_isa card are 0x300 and 9.
It should be possible to override both using the -net syntax like
-net nic,model=ne2k_isa,irq=5,iobase=0x280.
- Sebastian
I haven't built/tested at all, but this is the set of patches I've
collected for the 0.12.0 release. Will be testing tonight and tomorrow
and tagging probably around 5pm CST. Will then upload the release and
announce once things are propagated.
If you have a pending patch that you think
First patch adds a second PCI BAR as per the VMware SVGA specification for
the fifo instead of using the top of the VRAM BAR.
Patches 2-5 are from Anthony and I just rebased them on top of master.
Patch6: fixes a crasher in vmware when X starts inside the guest.
I've booted these with an F12
From: Anthony Liguori aligu...@us.ibm.com
Apparently, VBE maps the VGA vram to a fixed physical location. KVM requires
that all mappings of the VGA vram have dirty tracking enabled on them. Any
access to the VGA vram through the VBE mapping currently fails to result in
dirty page tracking
From: Dave Airlie airl...@linux.ie
---
hw/vmware_vga.c | 35 ++-
1 files changed, 30 insertions(+), 5 deletions(-)
diff --git a/hw/vmware_vga.c b/hw/vmware_vga.c
index f3e3749..28bbc3f 100644
--- a/hw/vmware_vga.c
+++ b/hw/vmware_vga.c
@@ -67,6 +67,11 @@ struct
From: Anthony Liguori aligu...@us.ibm.com
This is needed for VMware VGA to work properly under KVM.
Signed-off-by: Anthony Liguori aligu...@us.ibm.com
---
hw/vmware_vga.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/hw/vmware_vga.c b/hw/vmware_vga.c
index
From: Anthony Liguori aligu...@us.ibm.com
VMware VGA requires that the depth presented to the guest is the same as the
DisplaySurface that it renders to. This is because it performs a very simple
memcpy() to blit from one surface to another.
We currently hardcode a 24-bit depth. The surface
From: Dave Airlie airl...@linux.ie
The cursor pixmap size we calculate later ends up being 4096 dwords
long by the looks of it. This boots an F12 LiveCD now.
Signed-off-by: Dave Airlie airl...@linux.ie
---
hw/vmware_vga.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
From: Anthony Liguori aligu...@us.ibm.com
This patch enables dirty log tracking whenever it's needed and disables it
when it is not.
We unconditionally enable dirty log tracking on reset, restart dirty log
tracking when PCI IO regions are remapped, and disable/enable it based on
commands from
Hi Roland,
Roland Dreier wrote:
Hi Anthony -- just sent this patch to qemu-devel (although I don't see
it in archives yet). Anyway I realize it is really really late given
your release timeframe but I think the risk of this pretty minimal, and
the patch fixes a crash in a pretty reasonable
On 12/17/2009 01:15 PM, David Kozub wrote:
On a side note, why is the mask for e_type 0xfffe, allowing both ET_EXEC
and ET_DYN? I.e. when would we need it for shared libraries?
-fpie generates an ET_DYN executable.
r~
Roland Dreier wrote:
His last patch has the same fix without the printf(). The printf is
probably something to avoid since a malicious guest could create a
storm of them. Since libvirt logs stderr by default, the result could
be pretty nasty.
By the way, are the
Roland Dreier wrote:
Thanks for the patch. I'm planning on giving Dave Airlie's series a
try for 0.12.0. I'm pretty comfortable with those patches (since a
few of them are mine :-)). I also don't think vmware-vga is going to
be reliable without them so I don't think pulling in the one
-Original Message-
From: virtualization-boun...@lists.linux-foundation.org
[mailto:virtualization-boun...@lists.linux-foundation.org] On Behalf
Of
Arnd Bergmann
Sent: Tuesday, December 08, 2009 8:08 AM
To: virtualizat...@lists.linux-foundation.org
Cc: qemu-devel@nongnu.org
Hi,
I need your help:
I am working for an industrial company. Here, we build a machine composed of
- a board with a PowerPC as CPU
- classic devices such as ethernet
- other private devices.
LynxOS runs on the board with private applications and private
additional drivers.
We would like to use
Hi,
Sorry if I can already find this answer somwhere on the Qemu site, but I really
would like to find out if QEMU support Solaris 2.6 as a Guest operating system
but can't find the answer.
What I am looking for is something like Quick Transit and hoping that QEMU does
this?
Regards
Mia
Signed-off-by: David Kozub z...@linux.fjfi.cvut.cz
---
qemu-binfmt-conf.sh |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/qemu-binfmt-conf.sh b/qemu-binfmt-conf.sh
index ba916ac..9c65c9a 100644
--- a/qemu-binfmt-conf.sh
+++ b/qemu-binfmt-conf.sh
@@ -1,5 +1,5 @@
-Original Message-
From: Arnd Bergmann [mailto:a...@arndb.de]
Sent: Wednesday, December 16, 2009 6:16 AM
To: virtualizat...@lists.linux-foundation.org
Cc: Leonid Grossman; qemu-devel@nongnu.org
Subject: Re: Guest bridge setup variations
On Wednesday 16 December 2009, Leonid
QEMU crashes with vmware_vga when running a Linux guest with the latest
X.org vmware video driver if QEMU is using SDL for video output. In
this case, vmware_vga advertises cursor acceleration to the guest, and
the crash comes when the guest does a DEFINE_CURSOR command with a 64x64
32bpp cursor.
Hi Anthony -- just sent this patch to qemu-devel (although I don't see
it in archives yet). Anyway I realize it is really really late given
your release timeframe but I think the risk of this pretty minimal, and
the patch fixes a crash in a pretty reasonable config (running a modern
Linux distro
Thanks for the patch. I'm planning on giving Dave Airlie's series a
try for 0.12.0. I'm pretty comfortable with those patches (since a
few of them are mine :-)). I also don't think vmware-vga is going to
be reliable without them so I don't think pulling in the one fix is
good enough.
His last patch has the same fix without the printf(). The printf is
probably something to avoid since a malicious guest could create a
storm of them. Since libvirt logs stderr by default, the result could
be pretty nasty.
By the way, are the
fprintf(stderr, %s: update width
Rob Landley wrote:
For background of CELF project proposals, see:
http://elinux.org/CELF_Open_Project_Proposal_2010
Summary:
Integrate a flattened device tree parser into the emulator QEMU, so QEMU can
create board emulations on the fly (at runtime) from the same data files the
Hi,
I am running latest Qemu 0.12-rc. My guest VM runs Linux kernel 2.6.31.
Because Qemu now supports SVM, I expect to see the SVM flag in
/proc/cpuinfo, but that is not the case.
So it seems SVM support is not enabled by default configuration??
Thanks,
Jun
On Fri, Dec 18, 2009 at 11:37 AM, Jun Koi junkoi2...@gmail.com wrote:
Hi,
I am running latest Qemu 0.12-rc. My guest VM runs Linux kernel 2.6.31.
Because Qemu now supports SVM, I expect to see the SVM flag in
/proc/cpuinfo, but that is not the case.
So it seems SVM support is not enabled
Sebastian Herbszt herb...@gmx.de writes:
The default iobase and irq for the ne2k_isa card are 0x300 and 9.
It should be possible to override both using the -net syntax like
-net nic,model=ne2k_isa,irq=5,iobase=0x280.
-device ne2k_isa,irq=5,iobase=0x280
Commit 731b9ff6 is correct, but commit 24598d23 is more general, and it
comes first. Drop it the former?
Nice to have commit log corrections:
* 92375e10 qdev: Improve uni-north device names (was: [Qemu-devel] [FOR 0.12
PATCH] qdev: Replace device names containing whitespace)
The (was: ...)
Florent Defay schrieb:
Hi,
I need your help:
I am working for an industrial company. Here, we build a machine
composed of
- a board with a PowerPC as CPU
- classic devices such as ethernet
- other private devices.
LynxOS runs on the board with private applications and private
Anthony Liguori wrote:
I haven't built/tested at all, but this is the set of patches I've
collected for the 0.12.0 release. Will be testing tonight and tomorrow
and tagging probably around 5pm CST. Will then upload the release and
announce once things are propagated.
If you have a pending
93 matches
Mail list logo
