using the SDL cursor is all that useful? As soon as gtk
widgets get involved, the cursor becomes ARGB so in practice, I'm not
sure that it's all that helpful.
BTW, I've got the ALPHA_CURSOR working with VNC.. it's very sweet :-)
Regards,
Anthony Liguori
Regards,
Andrzej
directory `/home/Denis/qemu/i386-softmmu'
make: *** [subdir-i386-softmmu] Error 2
You probably need to rerun configure. I do not see this problem using a
mingw cross compiler.
Regards,
Anthony Liguori
Selon Christian MICHON [EMAIL PROTECTED]:
use mingw to compile qemu for windows hosts
with people more
familiar with gcc asm foo would be appreciated!
Regards,
Anthony Liguori
there were a lot of discussions about compiling qemu with gcc4 or higher. The
summary of the discussions were, as I understood, that compiling qemu with
gcc4 requires changing the code generation engine
that no other hosts are harmed.
Regards,
Anthony Liguori
Cheers,
loader run without having to
deal with paravirtualizing it. It would be nice to use emulation to
avoid paravirtualizing the non-performance critical bits.
Regards,
Anthony Liguori
Cheers,
Mark
Wouldn't this be a *significant*
performance enhancement for this setup which I'm sure is a common
up in CVS?
Why have the abstraction if it's not going to be used? I'm not really
sure I see the value in having GGD...
Regards,
Anthony Liguori
thanks,
--- ../qemu_trunk.orig/vl.h 2006-12-27 14:17:48.0
Christopher Olsen wrote:
Anyone here know if there is a way to append to the VNC display header?
I'm not sure I understand what you're asking. What is the VNC display
header?
Regards,
Anthony Liguori
-Christopher
in everyones benefit to ensure that the
largest number of clients Just Work out of the box.
Regards,
Anthony Liguori
--
Ramesh
=${myhdb}
EOF
Regards,
Anthony Liguori
I would prefer that you write another cross platform shell, than
another config file. At least that way I could use the same config
tool for more than one application.
Everytime this comes up, do I have to disagree again, so that my voice
is not lost
these too. I'll spend a little time in the next week enumerating these
extensions and assigning proper values to them.
Do you have any documentation on your currently client messages? Those
aren't documented as part of the FFMPEG project.
Regards,
Anthony Liguori
server-client pseudorectangle
already does. In fact, it's an exceedingly common
technique.
Regards,
Anthony Liguori
rather than testing each store to see if it modifies the framebuffer,
it keeps the framebuffer write-protected (via mprotect(), or the
equivalent on non-POSIX systems) and uses a SIGSEGV handler to catch
would
implement a create_pidfile() function. I think this general approach
would help clean up a lot of the win32 code.
Thoughts?
Regards,
Anthony Liguori
Patch attached for both. Built on linux and tested on Windows Server
2003.
Comments? Please include me in the CC.
Cheers,
Carlos.
Axel Zeuner wrote:
On Saturday 24 March 2007 21:15, Anthony Liguori wrote:
The tricky thing I still can't figure out is how to get ASM_SOFTMMU
working. The problem is GLUE(st, SUFFIX) function. First GCC cannot
deal with the register pressure. The problem I can't seem to fix though
Axel Zeuner wrote:
On Saturday 24 March 2007 21:15, Anthony Liguori wrote:
Axel Zeuner wrote:
Hi,
Hi Axel,
By adding some GCC4 fixes on top of your patch, I was able to get qemu
for i386 (on i386) to compile and run. So far, I've only tested a win2k
guest.
Hi Anthony
andrzej zaborowski wrote:
Hi, sorry for late reply.
On 21/03/07, Anthony Liguori [EMAIL PROTECTED] wrote:
Do you think using the SDL cursor is all that useful? As soon as gtk
widgets get involved, the cursor becomes ARGB so in practice, I'm not
sure that it's all that helpful.
It's pretty
Kyle Hubert wrote:
Hi, I'm working with QEMU on an XFree86 machine. I was desirous of
having 1600x1200 working in the virtual machine, so I looked at using
the -std-vga option with the vesa X driver.
You probably have to increase your hsync and vrefresh ranges.
Regards,
Anthony Liguori
Axel Zeuner wrote:
Hi Anthony,
On Monday 26 March 2007 01:44, you wrote:
Axel Zeuner wrote:
On Saturday 24 March 2007 21:15, Anthony Liguori wrote:
The tricky thing I still can't figure out is how to get ASM_SOFTMMU
working. The problem is GLUE(st, SUFFIX) function. First
Axel Zeuner wrote:
Hi Anthony,
On Thursday 29 March 2007 04:07, you wrote:
Axel Zeuner wrote:
Hi Anthony,
On Monday 26 March 2007 01:44, you wrote:
Axel Zeuner wrote:
On Saturday 24 March 2007 21:15, Anthony Liguori wrote:
The tricky thing I still can't
as
AFAIK I'm the only person with a reserved client message type. Of
course, I think using a pseudo-encoding is a perfectly suitable way to
address this problem.
Regards,
Anthony Liguori
--
Ramesh
on this subject.
Same here! Thanks for the response.
Regards,
Anthony Liguori
--
Ramesh
the SetServerEncodings message)?
I think it's easier to just add something to the psuedo-encoding to
allow client messages that make sense to disable to be disabled on a
case-by-case basis.
Regards,
Anthony Liguori
--
Ramesh
for
old, broken systems).
I thought I'd add that this isn't just portability. stdint.h is what
C99 mandates although as Paul mentions, some older systems used inttypes.h.
Regards,
Anthony Liguori
Why is it that qemu knows what the definition of these prototypes
are on all systems without
.
Are you familiar with USBIP? If so, does this sound reasonable?
Regards,
Anthony Liguori
It would allow quick USB device development in high level languages
without recompiling QEMU. We could have an instance of QEMU running
all the time while we create our device and hot plug/unplug it
whenever we
tree (actually I doubt it).
What makes you think this won't work? Have you tried it?
This has worked for me in the past.
Regards,
Anthony Liguori
Paul
deamons, but they refuse
because these see their pidfiles already from pre-powerout..
-pidfile behaves properly in CVS. You may be able to find the patch on
the ML that fixed it.
Regards,
Anthony Liguori
I have seen other daemons somehow locking their pidfiles while
running, and when killed
model. If that assumption is wrong,
we'd be happy to change it. In any case, there are other more portable
ways to generate fds, so if it's needed we can do that.
There's no fd at all? How do you get notifications about an
asynchronous event completion?
Regards,
Anthony Liguori
. If that assumption is wrong,
we'd be happy to change it. In any case, there are other more portable
ways to generate fds, so if it's needed we can do that.
There's no fd at all? How do you get notifications about an asynchronous
event completion?
Regards,
Anthony Liguori
(resending
(password never expires).
Signed-off-by: Gerd Hoffmannkra...@redhat.com
This has been posted before and I've never understood it. Why can't a
management tool just expire passwords on it's own?
How does password expiration help with security at all?
Regards,
Anthony Liguori
/plugging during migration is not a good idea
universally so it's something that needs to happen as a policy at the
management level.
Regards,
Anthony Liguori
then (no plug yet since the device is marked as auto_attach=0) client reconnects
(actually this happens before but to a paused machine
with vmstate2 eventually.
Regards,
Anthony Liguori
Regards,
Anthony Liguori
run concurrently.
Concurrently to what? How do you prevent them from running concurrently
with qemu?
If you saw lock ups, I bet that's what it was from.
Regards,
Anthony Liguori
Do you
see any specific concurrency issue? We can add some mutex protection
around at the aio callback, so
itself.
Regards,
Anthony Liguori
The first callback, called by librados whenever aio completes, runs in
the context of a single librados thread:
+static void rbd_finish_aiocb(rados_completion_t c, RADOSCB *rcb)
+{
+RBDAIOCB *acb = rcb-acb;
rcb is per a single aio. Was created before
On 10/07/2010 05:45 PM, Sage Weil wrote:
On Thu, 7 Oct 2010, Anthony Liguori wrote:
On 10/07/2010 04:49 PM, Yehuda Sadeh Weinraub wrote:
On Thu, Oct 7, 2010 at 2:04 PM, Anthony Liguorianth...@codemonkey.ws
wrote:
On 10/07/2010 03:47 PM, Yehuda Sadeh Weinraub wrote
. If you schedule a BH in a thread then you open yourself up to
the race.
Regards,
Anthony Liguori
...@linux.vnet.ibm.com
Acked-by: Anthony Liguori aligu...@us.ibm.com
Regards,
Anthony Liguori
---
block/qcow2.c | 22 --
cutils.c | 18 ++
qemu-common.h |1 +
3 files changed, 19 insertions(+), 22 deletions(-)
diff --git a/block/qcow2.c b/block/qcow2.c
How is this different than usb_del? Is it that it detaches it but does
not delete the device?
Regards,
Anthony Liguori
On 10/05/2010 09:40 AM, Alon Levy wrote:
Signed-off-by: Alon Levyal...@redhat.com
---
qemu-monitor.hx | 17 +
sysemu.h|1 +
vl.c
. With this patch, you get:
qemu: -net tap,fd=42: invalid fd= for tap network device. If you're copying
from libvirt, use `virsh dom2xml-to-native' instead
qemu: -net tap,fd=42: Device 'tap' could not be initialized
Signed-off-by: Anthony Liguori aligu...@us.ibm.com
diff --git a/hw/usb-uhci.c b/hw
On 10/08/2010 06:28 PM, Alexander Graf wrote:
On 09.10.2010, at 00:04, Anthony Liguori wrote:
A lot of people copy libvirt's command line from ps -ef and then wonder why the
VM isn't working correctly. Let's be kind and tell them what they should do
instead.
Without this patch, if you
. With this patch, you get:
qemu: -net tap,fd=42: invalid fd= for tap network device. If you're copying
from libvirt, use `virsh dom2xml-to-native' instead
qemu: -net tap,fd=42: Device 'tap' could not be initialized
Signed-off-by: Anthony Liguori aligu...@us.ibm.com
---
v1 - v2
- Remove garbage
as long as 3 hasn't returned? (at which point
it becomes a non-allocating write)?
Correct. The table lock in 0 is held until the request completes fully
(including the write out of all of the fill data--step 3) which means 5
will not begin until 3 has completed
Regards,
Anthony Liguori
on older QEMUs.
Regards,
Anthony Liguori
. If the freelist is completed
used, the freelist bit can be cleared and the image is then usable by
older QEMUs.
Regards,
Anthony Liguori
until you actually allocate the block.
This implies a cost because you'll need to do metadata syncs to make
this work. However, that eliminates leakage.
Regards,
Anthony Liguori
On 10/11/2010 10:24 AM, Avi Kivity wrote:
On 10/11/2010 05:02 PM, Anthony Liguori wrote:
On 10/11/2010 08:44 AM, Avi Kivity wrote:
On 10/11/2010 03:42 PM, Stefan Hajnoczi wrote:
A leak is acceptable (it won't grow; it's just an unused, incorrect
freelist), but data corruption
be non-compat.
I think we just need a feature bit then that indicates that the backing
file is non-probeable which certainly simplifies the implementation.
QED_F_BACKING_FORMAT_NOPROBE maybe?
Regards,
Anthony Liguori
Stefan
On 10/11/2010 11:02 AM, Avi Kivity wrote:
On 10/11/2010 05:49 PM, Anthony Liguori wrote:
On 10/11/2010 09:58 AM, Avi Kivity wrote:
A leak is unacceptable. It means an image can grow to an unbounded
size. If you are a server provider offering multitenancy, then a
malicious guest can
On 10/11/2010 11:18 AM, Anthony Liguori wrote:
On 10/11/2010 10:46 AM, Stefan Hajnoczi wrote:
On Mon, Oct 11, 2010 at 05:39:01PM +0200, Avi Kivity wrote:
On 10/11/2010 05:30 PM, Stefan Hajnoczi wrote:
It was discussed before, but I don't think we came to a
conclusion. Are
there any
booting from each available
NIC in sequence.
It still registers a BEV entry though, no?
Does it at least try to boot from the PCI bus/addr/fn of the selected
BEV entry?
Regards,
Anthony Liguori
Stefan
? The one used for -kernel for example?
-option-rom rom.bin,bootindex=3?
We can pass boot index along with option rom via fw_cfg interface.
If the option rom is just hijacking int19, then there is no meaningful
order you can give it.
Regards,
Anthony Liguori
for example?
-kernel hijacks int19 so it cannot participate in any kind of boot
order. It's either present (and therefore the bootable disk) or not
present.
Regards,
Anthony Liguori
cheers,
Gerd
with it's
own set of devices and select a preferred order that it can then give
back to SeaBIOS. SeaBIOS can then present that list to the user for
additional refinement.
Regards,
Anthony Liguori
--
Gleb.
On 10/11/2010 03:36 PM, Gleb Natapov wrote:
On Mon, Oct 11, 2010 at 03:30:21PM -0500, Anthony Liguori wrote:
On 10/11/2010 02:59 PM, Gleb Natapov wrote:
No boot rom should do that. extboot wreaks havoc when it is used.
And since virtio is now supported by bios there is no reason
that depends on it.
The following changes since commit 358664cc6d1b5f7c36004be0179b36011b81c49d:
console: Avoid dereferencing NULL active_console (2010-10-03 06:43:10 +)
Pulled. Thanks.
Regards,
Anthony Liguori
are available in the git repository at:
git://git.kernel.org/pub/scm/linux
of time.
So please get any requests to me before 6PM US Central time October 12th.
Post 0.13.0, as part of the 0.14 planning, we can discuss how to avoid
future delay with releases.
Thanks!
Regards,
Anthony Liguori
an int, then do a query-replace on the source tree to make all
invocations of it simply check the return value and exit if it's non-zero.
Regards,
Anthony Liguori
the format of the backing file name.
I agree with Kevin. There's no need to have the ill-defined backing
format AFAICT.
Yeah, I've now convinced myself we don't need backing format name too.
Regards,
Anthony Liguori
Stefan
.
I think there's a fair bit of value in looking like autoconf but a 39
patch series is a bit to digest at once.
I'll try to do a thorough review but I'd suggest keeping patch series
down to about 20 patches whenever possible and do multiple rounds as
necessary.
Regards,
Anthony Liguori
to nofail().
Regards,
Anthony Liguori
because the L2 entry is written, in which case the old version
of the data is present.
Are you referring to a scenario where the cluster is partially written
because the data is present in the write cache and the write cache isn't
flushed on power failure?
Regards,
Anthony Liguori
Kevin
come from the world of spice - in spice we use monitor commands for this.
And none of that is upstream.
Regards,
Anthony Liguori
I could
change this to have qemu connect to vscclient, but I don't see the logic in
general -
sometimes you do want to have a chardev that is listening (the fact
On 10/12/2010 10:59 AM, Stefan Hajnoczi wrote:
On Tue, Oct 12, 2010 at 05:39:48PM +0200, Kevin Wolf wrote:
Am 12.10.2010 17:22, schrieb Anthony Liguori:
On 10/12/2010 10:08 AM, Kevin Wolf wrote:
Otherwise we might destroy data that isn't
even touched by the guest request
,
Anthony Liguori
,
Anthony Liguori
I don't understand the use-case behind this. Is this so that a local
physical smart card can be passed through to a guest from a Spice
client
and when migration happens, the QEMU instance connects back to the
Spice
client? So the device is never actually migrated?
The *smart
below an additional fix? If so, please submit
against master.
Regards,
Anthony Liguori
==
And the zaurus patch, problem was the 2nd scoop's base address
(0x08800040) gets rounded down to start of page which causes its
io read/write callbacks to be passed addresses 0x40 higher than
CODING_STYLE.
Regards,
Anthony Liguori
diff --git a/configure b/configure
index af50607..5d8f620 100755
--- a/configure
+++ b/configure
@@ -325,6 +325,7 @@ cpu_emulation=yes
check_utests=no
user_pie=no
zero_malloc=
+rbd=
# OS specific
if check_define __linux__ ; then
@@ -724,6 +725,10
(which
means during an fsync()).
That means we can maintain the physical size without introducing
additional fsync()s in the allocation path. Since we're already writing
out the header anyway, the write operation is basically free too.
Regards,
Anthony Liguori
Kevin
a check in
the normal case where you have a clean shutdown.
Regards,
Anthony Liguori
On 10/13/2010 08:50 AM, Avi Kivity wrote:
On 10/13/2010 03:24 PM, Anthony Liguori wrote:
On 10/13/2010 08:07 AM, Kevin Wolf wrote:
Am 13.10.2010 14:13, schrieb Stefan Hajnoczi:
We can avoid it when a backing image is not used. Your idea to check
for zeroes in the backing image is neat too
.
Regards,
Anthony Liguori
Stefan
On 10/13/2010 09:16 AM, Avi Kivity wrote:
On 10/13/2010 04:11 PM, Anthony Liguori wrote:
Why would you ever update the header, apart from relocating L1 for
some reason?
To update the L1/L2 tables clean bit. That's what prevents a check
in the normal case where you have a clean shutdown
On 10/13/2010 10:08 AM, Avi Kivity wrote:
On 10/13/2010 04:53 PM, Anthony Liguori wrote:
On 10/13/2010 09:16 AM, Avi Kivity wrote:
On 10/13/2010 04:11 PM, Anthony Liguori wrote:
Why would you ever update the header, apart from relocating L1 for
some reason?
To update the L1/L2 tables
is to make the virtio-net devices multifunction and to fill out
all 8 functions for each slot.
Regards,
Anthony Liguori
Thanks
Anjali
** Changed in: qemu
Importance: Undecided = Wishlist
** Changed in: qemu
Status: New = Confirmed
--
qemu-img convert -O qcow2 -o backing_file makes huge images
https://bugs.launchpad.net/bugs/660366
You received this bug notification because you are a member of qemu-
devel-ml, which
On 10/14/2010 07:07 AM, Avi Kivity wrote:
On 10/14/2010 12:54 AM, Anthony Liguori wrote:
On 10/13/2010 05:32 PM, Anjali Kulkarni wrote:
Hi,
Using the legacy way of starting up NICs, I am hitting a limitation
after 29
NICs ie no more than 29 are detected (that's because of the 32 PCI slot
On 10/14/2010 07:10 AM, Daniel P. Berrange wrote:
On Thu, Oct 14, 2010 at 02:07:17PM +0200, Avi Kivity wrote:
On 10/14/2010 12:54 AM, Anthony Liguori wrote:
On 10/13/2010 05:32 PM, Anjali Kulkarni wrote:
Hi,
Using the legacy way of starting up NICs, I am hitting
On 10/14/2010 07:36 AM, Markus Armbruster wrote:
Avi Kivitya...@redhat.com writes:
On 10/14/2010 12:54 AM, Anthony Liguori wrote:
On 10/13/2010 05:32 PM, Anjali Kulkarni wrote:
Hi,
Using the legacy way of starting up NICs, I am hitting a limitation
after 29
NICs ie
the status myself next time
or do we have rules on who handles bugs?
I'm pretty sure anyone can do it. If not, I'm certainly willing to give
people extra rights on the project if they want to help with bug triage.
Regards,
Anthony Liguori
Stefan
On 10/14/2010 08:23 AM, Avi Kivity wrote:
On 10/14/2010 02:54 PM, Anthony Liguori wrote:
The key is to make the virtio-net devices multifunction and to fill
out all 8 functions for each slot.
This is unlikely to work right wrt pci hotplug.
Yes. Our hotplug design is based on devices
On 10/14/2010 01:37 PM, Robert Relyea wrote:
Anthony Liguori wrote:
And how does the smart card state get migrated during migration? How
do you keep it synced with QEMU?
I don't understand the use-case behind this. Is this so that a local
physical smart card can be passed through
don't know that the answer is obvious to me.
Regards,
Anthony Liguori
Jes
On 10/14/2010 02:58 PM, Alex Williamson wrote:
On Thu, 2010-10-14 at 14:48 -0500, Anthony Liguori wrote:
On 10/14/2010 02:44 PM, Jes Sorensen wrote:
On 10/14/10 20:33, Alex Williamson wrote:
We can't let the compiler define the alignment for qemu_cfg data.
Signed-off
,snapshot=on,id=disk${slot}_${fn}
args=$args -device
virtio-blk-pci,addr=${slot}.${fn},drive=disk${slot}_${fn},multifunction=on
done
done
x86_64-softmmu/qemu-system-x86_64 -hda ~/images/linux.img ${args}
-enable-kvm -serial stdio
Regards,
Anthony Liguori
Rich.
address that includes
a function number. Then you can pack 8 virtio PCI devices into a single
slot.
Regards,
Anthony Liguori
Anjali
On 10/14/10 2:57 PM, Anthony Liguorianth...@codemonkey.ws wrote:
On 10/14/2010 04:42 PM, Richard W.M. Jones wrote:
On Thu, Oct 14, 2010 at 01:10:47PM
model.
Regards,
Anthony Liguori
bob
Regards,
Anthony Liguori
It now appears to me that qemu punts on this case, except for the
keyboard and mouse -- well maybe not punts, but simply doesn't support
any device that isn't on the host machine. If you look at the way qemu
handles the sound
On 10/14/2010 05:12 PM, Anjali Kulkarni wrote:
Thanks. Does this work for e1000 as well?
Haven't tried. I don't know how various e1000 drivers would react.
Also, does it support pci hotplug?
No, but that's fixable down the road.
Regards,
Anthony Liguori
Anjali
On 10/14/10 3
On 10/15/2010 01:49 PM, Anjali Kulkarni wrote:
Hi,
- If I want to pass in additional arguments to the guest OS while booting(in
particular which slot I want to map a nic to) - is there any way to do it?
Some kind of configuration file that I can pass in would also be ok for me.
- Is there a
romfile.
Maybe it's better to use fw_cfg to explicitly tell SeaBIOS to ignore the
PCI device id in the rom header for a certain device?
Regards,
Anthony Liguori
The i825xx ethernet controller family is a typical example
which is implemented in hw/eepro100.c. It uses at least
3 different device
(which will be coming very soon).
Regards,
Anthony Liguori
Thanks,
Sergei.
-introduces
debian#578846.
Thanks!
Can you send a patch to the mailing list with a Signed-off-by and an
explanation of the change?
Regards,
Anthony Liguori
/mjt
in an
incompatible way but there are likely to be missing features.
Regards,
Anthony Liguori
On 10/18/2010 03:22 AM, Roedel, Joerg wrote:
(Sorry for the late reply)
On Thu, Oct 07, 2010 at 08:48:06AM -0400, Anthony Liguori wrote:
On 10/07/2010 03:42 AM, Roedel, Joerg wrote:
On Wed, Oct 06, 2010 at 03:24:59PM -0400, Anthony Liguori wrote:
+qemu_compat_version
On 10/18/2010 05:09 AM, Gerd Hoffmann wrote:
On 10/15/10 23:05, Anthony Liguori wrote:
On 10/15/2010 03:51 PM, Stefan Weil wrote:
PCI device with different device ids sometimes share
the same rom code. Only the device id and the checksum
differ in a boot rom for such devices.
BTW, SeaBIOS
, uint8_t *ptr, int size)
let's return an error code on malformed roms so management can detect errors?
A bad/missing PnP header does not mean it's an invalid ROM.
Regards,
Anthony Liguori
that the ROM
doesn't somehow depend on the contents of its header? Maybe it has an
internal CRC built into it or something like that.
Regards,
Anthony Liguori
---
hw/pci.c | 58 ++
1 files changed, 58 insertions(+), 0 deletions(-)
diff --git
On 10/18/2010 01:44 PM, Anthony Liguori wrote:
On 10/18/2010 12:55 PM, Stefan Weil wrote:
PCI devices with different vendor or device ids sometimes share
the same rom code. Only the ids and the checksum
differs in a boot rom for such devices.
The i825xx ethernet controller family is a typical
have to use -k.
Regards,
Anthony Liguori
Thanks!
/mjt
Regards!
--Oleg
On 10/18/2010 02:03 PM, Michael S. Tsirkin wrote:
On Mon, Oct 18, 2010 at 01:42:06PM -0500, Anthony Liguori wrote:
+/* Patch the PCI vendor and device ids in a PCI rom image if necessary.
+ This is needed for an option rom which is used for more than one device. */
+static void
and ROMs, when the virtual BIOS attempts to measure itself if
we've patched the ROM underneath of it, then the measurements will fail.
In the very least, if we go this route, it has to be an optional feature.
Regards,
Anthony Liguori
Regards,
Stefan
provided that you simply prevent
the FW update commands? I'm certainly not.
Ping?
Who are you pinging?
Regards,
Anthony Liguori
Alex
is at
http://repo.or.cz/w/qemu/mdroth.git
Regards,
Anthony Liguori
What about FS that span over LVM with multiple drives? IDE/SCSI?
Good points.
801 - 900 of 9887 matches
Mail list logo