On Wed, Dec 29, 2010 at 10:29 PM, Irek Szczesniak
<577...@bugs.launchpad.net> wrote:
> In my previous tests I didn't continue, because I assumed something went
> wrong, but now I tried again, and things just work: the installer can
> resolve names and reach the Internet.
>
> In conclusion, I raised
Thanks for your instructions, Stefan.
Wireshark showed me that in DHCPOFFER and DHCPACK there are given the
DNS server and the router addresses. Then I saw that the CentOS
installer uses the assigned IP address to query the 10.0.2.3 DNS server.
So the CentOS insaller got the DNS address and uses
Most of emulated CPU have instructions aligned on 16 or 32 bits, while
on others GCC tries to align the target jump location. This means that
1/2 or 3/4 of tb_phys_hash entries are never used.
Update the hash function tb_phys_hash_func() to ignore the two lowest
bits of the address. This brings a
On big endian hosts, the curses interface is unusable: the emulated
graphic card only displays garbage, while the monitor interface displays
nothing (or rather only spaces).
The curses interface is waiting for data in native endianness, so
console_write_ch() should not do any conversion. The conve
On Mon, Dec 20, 2010 at 11:45:08PM +0100, Alexander Graf wrote:
>
> Since this just came up again - are you still working on this? It's be a
> shame to see this target bitrot to extinction. Also, do you think it's a
> valuable target to have in upstream qemu? If so, please create a proper patch
From: Jan Kiszka
Report KVM_EXIT_UNKNOWN, KVM_EXIT_FAIL_ENTRY, and KVM_EXIT_EXCEPTION
with more details to stderr. The latter two are so far x86-only, so move
them into the arch-specific handler. Integrate the Intel real mode
warning on KVM_EXIT_FAIL_ENTRY that qemu-kvm carries, but actually
rest
From: Jan Kiszka
The ordering doesn't matter in this case, but better keep it consistent.
Signed-off-by: Jan Kiszka
---
target-i386/kvm.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index fda07d2..b4c6cd4 100644
--- a/targ
From: Jan Kiszka
Ensure that we stop the guest whenever we face a fatal or unknown exit
reason. If we stop, we also have to enforce a cpu loop exit.
Signed-off-by: Jan Kiszka
---
kvm-all.c | 15 +++
target-i386/kvm.c |4
target-ppc/kvm.c |4
3 files cha
From: Jan Kiszka
No functional changes.
Signed-off-by: Jan Kiszka
---
kvm-all.c | 137 ++--
1 files changed, 78 insertions(+), 59 deletions(-)
diff --git a/kvm-all.c b/kvm-all.c
index 35fc73c..3bb5722 100644
--- a/kvm-all.c
+++ b/kvm-al
From: Jan Kiszka
This code path will not yet be taken as we still lack in-kernel irqchip
support. But qemu-kvm can already make use of it and drop its own
mp_state access services.
Signed-off-by: Jan Kiszka
---
target-i386/kvm.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
dif
From: Jan Kiszka
It is not used, it is not needed, so let's remove it.
Signed-off-by: Jan Kiszka
---
kvm-all.c |6 ++
kvm-stub.c |4 ++--
kvm.h |2 +-
3 files changed, 5 insertions(+), 7 deletions(-)
diff --git a/kvm-all.c b/kvm-all.c
index 3bb5722..858c252 100644
--- a/
Nothing critical, see patches for details.
Jan Kiszka (6):
kvm: Fix coding style violations
kvm: Drop return value of kvm_cpu_exec
kvm: x86: Align kvm_arch_put_registers code with comment
kvm: Stop on all fatal exit reasons
kvm: Improve reporting of fatal errors
kvm: x86: Prepare kvm_g
I believe this issue to be affecting my systems too. I am willing to
provide more information as necessary.
Running two equivalent systems hardware wise - RAM type (not amount),
CPU, BIOS, Ubuntu version except qemu-kvm binary.
Both systems are running Ubuntu version 10.04.1 x86_64.
Running Ubun
956a3e6bb7386de48b642d4fee11f7f86a2fcf9a introduced a bug concerning
reset bit for port 92.
Since the keyboard output port and port 92 are not compatible anyway,
let's separate them.
Reported-by: Peter Lieven
Signed-off-by: Blue Swirl
--
v2: added reset handler and VMState
---
hw/pc.c| 8
On Wed, Dec 29, 2010 at 5:28 AM, Stefan Hajnoczi wrote:
> On Tue, Dec 28, 2010 at 9:45 PM, Peter Lieven wrote:
>> What happens if I set the A20 Gate via the keyboard controller and then read
>> its status via ioport 0x92? This doesn't work, or does it?
>> What was wrong reading the A20 via
>>
>>
does qemu support firewire in current distribution?
If so, does it have better success with external devices than USB with
XP under qemu running on Linux?
Thanks
On 12/29/2010 05:05 PM, Jan Kiszka wrote:
Am 28.12.2010 11:36, Avi Kivity wrote:
> The following changes since commit
> 4cdc1cd137e0b98766916a7cdf2d5a9b3c6632fa:
>
>target-mips: fix host CPU consumption when guest is idle (2010-12-27
> 00:58:06 +0100)
>
> are available in the git reposito
On Wed, Dec 29, 2010 at 10:38 AM, Irek Szczesniak
<577...@bugs.launchpad.net> wrote:
> I got the very same result as you did:
>
> VLAN 0 devices:
> user.0: net=10.0.2.0, restricted=n
> e1000.0: model=e1000,macaddr=52:54:00:12:34:56
> Devices not on any VLAN:
In that case QEMU's user networking s
Am 28.12.2010 11:36, Avi Kivity wrote:
> The following changes since commit
> 4cdc1cd137e0b98766916a7cdf2d5a9b3c6632fa:
>
> target-mips: fix host CPU consumption when guest is idle (2010-12-27
> 00:58:06 +0100)
>
> are available in the git repository at:
> git://git.kernel.org/pub/scm/virt/kv
On Wed, Dec 29, 2010 at 11:26:32AM +0100, Sebastian Herbszt wrote:
> Michael S. Tsirkin wrote:
> >On Tue, Dec 28, 2010 at 07:48:23PM +0100, Sebastian Herbszt wrote:
> >>Michael S. Tsirkin wrote:
> >>>On Tue, Dec 28, 2010 at 05:24:06PM +0100, Sebastian Herbszt wrote:
> Michael S. Tsirkin wrote:
This is on top of the ioeventfd patches, and
fixes two potential issues when ioeventfd is mixed with vhost-net:
- ioeventfd could start running then get stopped for vhost-net.
For example, vm state change handlers run in no particular order.
This would be hard to debug. Prevent this by always r
On Wed, Dec 29, 2010 at 11:26:32AM +0100, Sebastian Herbszt wrote:
> Michael S. Tsirkin wrote:
> >On Tue, Dec 28, 2010 at 07:48:23PM +0100, Sebastian Herbszt wrote:
> >>Michael S. Tsirkin wrote:
> >>>On Tue, Dec 28, 2010 at 05:24:06PM +0100, Sebastian Herbszt wrote:
> Michael S. Tsirkin wrote:
I got the very same result as you did:
VLAN 0 devices:
user.0: net=10.0.2.0, restricted=n
e1000.0: model=e1000,macaddr=52:54:00:12:34:56
Devices not on any VLAN:
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launch
Michael S. Tsirkin wrote:
On Tue, Dec 28, 2010 at 07:48:23PM +0100, Sebastian Herbszt wrote:
Michael S. Tsirkin wrote:
>On Tue, Dec 28, 2010 at 05:24:06PM +0100, Sebastian Herbszt wrote:
>>Michael S. Tsirkin wrote:
>>>On Mon, Dec 20, 2010 at 10:18:01PM +0100, Sebastian Herbszt wrote:
Use pci
On Sat, Dec 25, 2010 at 11:44 PM, Ronnie Sahlberg
wrote:
> This patch adds a new block driver : block.iscsi.c
> This driver interfaces with the multiplatform posix library
> for iscsi initiator/client access to iscsi devices hosted at
> git://github.com/sahlberg/libiscsi.git
>
> The patch adds the
25 matches
Mail list logo
