I'm fully aware that this isn't a high priority bug for anyone primarily due to
the fact that it uses the word 'scsi'.
However, I wanted to document it here.
Also, I'm attaching an IRC log of a conversation with aligouri in #kvm
discussing the issue.
** Attachment added: "#kvm discussion about
Public bug reported:
Binary package hint: seabios
Currently when a grub multiboot image is booted with 'kvm -kernel' and
'biosdisk' module, it will see block devices of type IDE or virtio. It
will not see scsi devices.
To demonstrate this:
$ qemu-img create -f qcow2 disk.img 1G
$ grub-mkrescue
The patch has been included in v0.12.5
** Changed in: qemu
Status: New => Fix Released
--
[ARM]: SIMD add/sub instructions are incorrect
https://bugs.launchpad.net/bugs/591320
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Stat
The patch has been included in v0.12.5
** Changed in: qemu
Status: In Progress => Fix Released
--
[ARM] All variants of ADDSUBX,SUBADDX give incorrect results
https://bugs.launchpad.net/bugs/595906
You received this bug notification because you are a member of qemu-
devel-ml, which is sub
On 07/28/2010 03:00 PM, Edgar E. Iglesias wrote:
>> -NEW_AUX_ENT(AT_BASE, (abi_ulong)(interp_load_addr));
>> +NEW_AUX_ENT(AT_BASE, (abi_ulong)(interp_info->load_addr));
>
>
> Hi Richard,
>
> I think this part breaks loading of statically linked ELFs (no
> interpreter). I beleive Linux se
This header is not present on my system and causes a build
failure, but is also not used in these files, so remove it.
Signed-off-by: Mike McCormack
---
hw/vhost.c |1 -
hw/vhost_net.c |1 -
2 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/hw/vhost.c b/hw/vhost.c
index
On Tue, 2010-07-20 at 09:36 +0800, Amos Kong wrote:
> Mainly test steps:
> 1. get a new mac from pool, and the old mac addr of guest.
> 2. execute the mac_change.sh in guest.
> 3. relogin to guest and query the interfaces info by `ifconfig`
>
> Signed-off-by: Cao, Chen
> Signed-off-by: Amos Kong
On Tue, Jul 27, 2010 at 10:25:33AM -0700, Richard Henderson wrote:
> First, adjust load_symbols to accept a load_bias parameter. At the same
> time, read the entire section header table in one go, use pread instead
> f lseek+read for the symbol and string tables, and properly free
> allocated stru
On Tue, 2010-07-20 at 09:36 +0800, Amos Kong wrote:
> This case just snoop tftp packet through tcpdump, it depends on public dhcp
> server, better to test it through dnsmasq.
It would be a good idea to have an alternate implementation using
dnsmasq, but not urgent.
> Signed-off-by: Jason Wang
>
On Tue, Jul 27, 2010 at 10:25:37AM -0700, Richard Henderson wrote:
> Moving toward a single copy of the elf binary loading code.
> Fill in the details of the loaded image into a struct image_info.
>
> Adjust create_elf_tables to read from such structures instead
> of from a collection of passed ar
On Tue, 2010-07-20 at 09:36 +0800, Amos Kong wrote:
> Use 'ping' to test send/recive multicat packets. Flood ping test is also
> added.
> Limit guest network as 'bridge' mode, because multicast packets could not be
> transmitted to guest when using 'user' network.
> Add join_mcast.py for joining m
On Tue, 2010-07-20 at 09:35 +0800, Amos Kong wrote:
> This test mainly covers TCP sent from host to guest and from guest to host
> with repeatedly turn on/off NIC promiscuous mode.
>
> Signed-off-by: Amos Kong
> ---
> 0 files changed, 0 insertions(+), 0 deletions(-)
>
> diff --git a/client/test
This patch address two issues.
1) When savevm is run using an previously saved snapshot id or name, it will
delete the original and create a new one, using the same id and name and not
prompting the user of what just happened.
This behaviour is not good, IMHO.
We add a '-f' parameter to savevm,
Signed-off-by: Miguel Di Ciurcio Filho
---
savevm.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/savevm.c b/savevm.c
index 6c6adb0..fb38e8a 100644
--- a/savevm.c
+++ b/savevm.c
@@ -1775,7 +1775,7 @@ static int del_existing_snapshots(Monitor *mon, const
char *name)
This series does some cleanups and changes how the monitor command 'savevm'
handles overwriting snapshots with existing names and makes 'savevm' always
create a name for an snapshot being taken.
I'm keeping track of some issues with savevm/loadvm on a wiki page [1].
All feedback is very appreciat
The bdrv_snaphost_find() returns zero in case it finds an snapshot or -ENOENT in
case it doesn't.
Checking returning values as >= zero doesn't make sense.
Signed-off-by: Miguel Di Ciurcio Filho
---
savevm.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/savevm.c
On Tue, 2010-07-20 at 09:35 +0800, Amos Kong wrote:
> Repeatedly load/unload nic driver, try to transfer file between guest and host
> by threads at the same time, and check the md5sum.
>
> Signed-off-by: Amos Kong
> ---
> 0 files changed, 0 insertions(+), 0 deletions(-)
>
> diff --git a/client
On Wed, Jul 28, 2010 at 12:38 PM, Markus Armbruster wrote:
> Miguel Di Ciurcio Filho writes:
>
>> The output generated by 'info snapshots' shows only snapshots that exist on
>> the
>> block device that saves the VM state. This output can cause an user to
>> erroneously try to load an snapshot th
Miguel Di Ciurcio Filho writes:
> The output generated by 'info snapshots' shows only snapshots that exist on
> the
> block device that saves the VM state. This output can cause an user to
> erroneously try to load an snapshot that is not available on all block
> devices.
What happens when you
It is possible that subpage mmio is registered over existing memory
page. When this happens "memory" will have real memory address and not
index into io_mem array so next access to the page will generate
segfault. It is uncommon to have some part of a page to be accessed as
memory and some as mmio,
This abort() condition is easily triggerable by a guest if it configures
pci bar with unaligned address that overlaps main memory.
Signed-off-by: Gleb Natapov
---
kvm-all.c | 16
1 files changed, 4 insertions(+), 12 deletions(-)
diff --git a/kvm-all.c b/kvm-all.c
index fec6d0
Or just a little bit?
Nothing prevents guest from configuring pci mmio bar to overlap system
memory region and the physical memory address will became mmio, but
when guest will change pci bar mapping the physical address location
will not become memory again, but instead it becomes unassigned. Yes
Add APIs to control host header length. First user
will be vhost-net.
Signed-off-by: Michael S. Tsirkin
---
net/tap-aix.c |9 +
net/tap-bsd.c |9 +
net/tap-linux.c | 29 +
net/tap-linux.h |2 ++
net/tap-solaris.c |9 ++
Make host vnet header length a structure field in
preparation for using this support in linux kernel.
Signed-off-by: Michael S. Tsirkin
---
net/tap-linux.h |6 ++
net/tap.c | 28 ++--
2 files changed, 20 insertions(+), 14 deletions(-)
diff --git a/net/tap
use the new tap APIs to set header length
Signed-off-by: Michael S. Tsirkin
---
hw/vhost_net.c | 24 +++-
1 files changed, 23 insertions(+), 1 deletions(-)
diff --git a/hw/vhost_net.c b/hw/vhost_net.c
index 606aa0c..3bd3aa6 100644
--- a/hw/vhost_net.c
+++ b/hw/vhost_net.c
This adds support for mergeable buffers with vhost.
The tun ioctl this relies on is already in 2.6.34,
the vhost support for the feature has been submitted
for 2.6.36.
Michael S. Tsirkin (3):
tap: generalize code for different vnet header len
tap: add APIs for vnet header length
vhost_net: m
Thanks for pushing on this! The fix is in 0.13.0-rc0, and we will merge
this into maverick as soon as it is GA'd. The fix appears to very
cleanly (with a few offsets but no rejects) apply to both the lucid and
maverick source. I propose we merge the patch by itself into lucid, and
wait for the G
On Mon, Jul 26, 2010, Raymes Khoury wrote:
> I am having the problem with qemu, as described in the post
> http://old.nabble.com/-PATCH:-PR-target-42671--Use-Thumb1-GOT-address-loading-sequence-for--%09Thumb2-td27124497.html
> where
> accessing cp15 on ARM causes an error:
See mid 1280086076-2064
I found out Matt Waddel has written a better looking patch, but I
didn't test it; reviews welcome -- attached
--
Loïc Minier
--- Begin Message ---
diff --git a/target-arm/cpu.h b/target-arm/cpu.h
index 7440163..b5d8a6c 100644
--- a/target-arm/cpu.h
+++ b/target-arm/cpu.h
@@ -130,6 +130,7 @@ ty
On 07/28/2010 02:50 PM, Michael Goldish wrote:
> On 07/27/2010 04:01 PM, Lucas Meneghel Rodrigues wrote:
>> On Tue, 2010-07-20 at 09:35 +0800, Amos Kong wrote:
>>> The kvm_net_utils.py is a just a place that wraps common network
>>> related commands which is used to do the network-related tests.
>>
Paolo Bonzini wrote:
> On 07/28/2010 02:51 PM, TeLeMan wrote:
> Even if they are mandatory, subsections still improve the situation
> here, because they provide a clean way to "branch" off an upstream
> vmstate version. At least the failure will be clear, because an
> unsupported subsection is e
jes.soren...@redhat.com writes:
> From: Jes Sorensen
>
> This set of patches adds default CPU types to the PC compat
> definitions, and patch #2 sets the CPU type to kvm64/kvm32 when
> running under KVM.
>
> Long term we might want to qdev'ify the CPUs but I think it is better
> to keep it simple
On 07/28/2010 04:53 AM, Daniel P. Berrange wrote:
On Tue, Jul 27, 2010 at 12:20:55PM -0500, Anthony Liguori wrote:
On 07/27/2010 12:00 PM, Daniel P. Berrange wrote:
Yup. You'll need to decide up front if you want to probe for a feature
when it's introduced and have something added to
On 07/28/2010 02:51 PM, TeLeMan wrote:
On Wed, Jul 28, 2010 at 20:32, Juan Quintela wrote:
TeLeMan wrote:
On Wed, Jul 28, 2010 at 19:51, Juan Quintela wrote:
I hope this hepls to understand how subsections are supposed to work.
Thanks for the comments, Juan.
I see, thanks a lot. But I st
Hi Aaron,
Am 28.07.2010 04:01, schrieb Aaron Mason:
> I tried this once before using command-line parameters and it was
> knocked back. Someone made the mention of using options so I had a
> look and saw that it was really simple to do.
>
> The following is a patch from the latest Git snapshot.
Kevin Wolf writes:
> Am 28.07.2010 13:22, schrieb Markus Armbruster:
>> Anthony Liguori writes:
>>
>>> On 07/27/2010 10:22 AM, Markus Armbruster wrote:
[...]
Raw can't be probed safely, by its very nature. For historical reasons,
we try anyway. I think we should stop doing that, eve
--
SUN OF A BEACH
On Wed, Jul 28, 2010 at 20:32, Juan Quintela wrote:
> TeLeMan wrote:
>> On Wed, Jul 28, 2010 at 19:51, Juan Quintela wrote:
>>> I hope this hepls to understand how subsections are supposed to work.
>>>
>>> Thanks for the comments, Juan.
>>>
>> I see, thanks a lot. But I stil
From: Jes Sorensen
This set of patches adds default CPU types to the PC compat
definitions, and patch #2 sets the CPU type to kvm64/kvm32 when
running under KVM.
Long term we might want to qdev'ify the CPUs but I think it is better
to keep it simple for 0.13.
Jes Sorensen (2):
Set a default C
From: Jes Sorensen
KVM has a minimum CPU requirement in order to run, so there is no
reason to default to the very basic family 6, model 2 (or model 3 for
qemu32) CPU since the additional features are going to be available on
the host CPU.
Signed-off-by: Jes Sorensen
---
hw/pc.c | 13 +++
From: Jes Sorensen
This allows for changing the default CPU type on the current PC
definition without breaking legacy mode.
Signed-off-by: Jes Sorensen
---
hw/boards.h |1 +
hw/pc_piix.c | 15 +++
vl.c |2 ++
3 files changed, 18 insertions(+), 0 deletions(-)
dif
** Project changed: qemu => qemu-kvm
** Also affects: qemu
Importance: Undecided
Status: New
** Also affects: kvm
Importance: Undecided
Status: New
** Changed in: qemu
Status: New => Fix Committed
** Changed in: qemu-kvm
Status: Fix Committed => Confirmed
** C
TeLeMan wrote:
> On Wed, Jul 28, 2010 at 19:51, Juan Quintela wrote:
>> I hope this hepls to understand how subsections are supposed to work.
>>
>> Thanks for the comments, Juan.
>>
> I see, thanks a lot. But I still hope to have the similar subsection
> that can be ignored simply.
Then it is be
Path has been applied to upstream
http://thread.gmane.org/gmane.comp.emulators.qemu/76376
** Changed in: qemu
Status: Confirmed => Fix Committed
--
KVM segmentation fault, using SCSI+writeback and linux 2.4 guest
https://bugs.launchpad.net/bugs/595438
You received this bug notification b
On Wed, Jul 28, 2010 at 19:51, Juan Quintela wrote:
> TeLeMan wrote:
>> On Wed, Jul 28, 2010 at 18:43, Juan Quintela wrote:
>>> TeLeMan wrote:
If the new version adds the new subsection for some vmstate, the old
version will load the new version's vmstate unsuccessfully. So we have
>
Madame, Monsieur Bonjour,
Ne jetez-pas ce mail à la corbeille sans en avoir pris connaîssance.
Que vous soyez chez vous ou au bureau !!!
Connaîssez-vous quelqu'un qui mange tout les jours ?
Tout le monde bien sur !!!
Connaîssez-vous un supermarché qui vous paye pour fair
TeLeMan wrote:
> On Wed, Jul 28, 2010 at 18:43, Juan Quintela wrote:
>> TeLeMan wrote:
>>> If the new version adds the new subsection for some vmstate, the old
>>> version will load the new version's vmstate unsuccessfully. So we have
>>> to ignore the unrecognized subsections.
>>
>> No. That
On 07/27/2010 04:01 PM, Lucas Meneghel Rodrigues wrote:
> On Tue, 2010-07-20 at 09:35 +0800, Amos Kong wrote:
>> The kvm_net_utils.py is a just a place that wraps common network
>> related commands which is used to do the network-related tests.
>> Use -1 as the packet ratio for loss analysis.
>> Us
On Sunday 25 July 2010, Loïc Minier wrote:
> On ARMv7, ignore writes to cp15 with crm == 12; these are to setup perf
> counters which we don't have.
Thanks Loïc, I have tested this and can confirm that I'm able to boot
a CONFIG_PERF_EVENTS kernel now.
Arnd
Am 28.07.2010 13:22, schrieb Markus Armbruster:
> Anthony Liguori writes:
>
>> On 07/27/2010 10:22 AM, Markus Armbruster wrote:
>>> Kevin Wolf writes:
>>>
>>>
Am 27.07.2010 15:00, schrieb Anthony Liguori:
> On 07/27/2010 02:19 AM, Markus Armbruster wrote:
>
>>
On Wed, Jul 28, 2010 at 18:43, Juan Quintela wrote:
> TeLeMan wrote:
>> If the new version adds the new subsection for some vmstate, the old
>> version will load the new version's vmstate unsuccessfully. So we have
>> to ignore the unrecognized subsections.
>
> No. That was the whole point of s
Anthony Liguori writes:
> On 07/27/2010 10:22 AM, Markus Armbruster wrote:
>> Kevin Wolf writes:
>>
>>
>>> Am 27.07.2010 15:00, schrieb Anthony Liguori:
>>>
On 07/27/2010 02:19 AM, Markus Armbruster wrote:
> Anthony Liguori writes:
>
>
>
>>
On 07/28/10 12:51, Avi Kivity wrote:
> On 07/28/2010 01:05 PM, jes.soren...@redhat.com wrote:
>> From: Jes Sorensen
>>
>> KVM has a minimum CPU requirement in order to run, so there is no
>> reason to default to the very basic family 6, model 2 (or model 3 for
>> qemu32) CPU since the additional f
Am 27.07.2010 14:02, schrieb Markus Armbruster:
> bdrv_eject() gets called when a device model opens or closes the tray.
>
> If the block driver implements method bdrv_eject(), that method gets
> called. Drivers host_cdrom implements it, and it opens and closes the
> physical tray, and nothing el
On 07/28/2010 01:05 PM, jes.soren...@redhat.com wrote:
From: Jes Sorensen
KVM has a minimum CPU requirement in order to run, so there is no
reason to default to the very basic family 6, model 2 (or model 3 for
qemu32) CPU since the additional features are going to be available on
the host CPU.
TeLeMan wrote:
> If the new version adds the new subsection for some vmstate, the old
> version will load the new version's vmstate unsuccessfully. So we have
> to ignore the unrecognized subsections.
No. That was the whole point of subsections. If one subsection is
sent, target machine has to
On 07/27/2010 05:08 AM, Lucas Meneghel Rodrigues wrote:
> On Tue, 2010-07-20 at 09:35 +0800, Amos Kong wrote:
>> The function get_interface_name is used to get the interface name of linux
>> guest through the macaddress of specified macaddress.
>
> I wonder if it wouldn't be overkill to have separ
On Tue, Jul 27, 2010 at 12:20:55PM -0500, Anthony Liguori wrote:
> On 07/27/2010 12:00 PM, Daniel P. Berrange wrote:
> >>Yup. You'll need to decide up front if you want to probe for a feature
> >>when it's introduced and have something added to capabilities.
> >>
> >>This is simple though. A few
From: Jes Sorensen
KVM has a minimum CPU requirement in order to run, so there is no
reason to default to the very basic family 6, model 2 (or model 3 for
qemu32) CPU since the additional features are going to be available on
the host CPU.
Signed-off-by: Jes Sorensen
---
hw/pc.c | 13 +++
Assuming that any image on a block device is not properly zero-initialized is
actually wrong: Only raw images have this problem. Any other image format
shouldn't care about it, they initialize everything properly themselves.
Signed-off-by: Kevin Wolf
---
block.c |6 ++
block/ra
On (Tue) Jul 27 2010 [10:55:03], Anthony Liguori wrote:
> +case QEMU_OPTION_libvirt_caps:
> +printf("version: " QEMU_VERSION "\n"
> + "package: " QEMU_PKGVERSION "\n"
> + "caps: name,enable-kvm,no-reboot,uuid,xen-domid,drive"
>
60 matches
Mail list logo
