after echo 1 /sys/modules/kvm/parameters/ignore_msrs in host, the
guest (with my own kernel config) boot up fine.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/994378
Title:
Nested-virt)L1 (kvm
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git next Commit:9576c4cd6b6fa5716400e63618757b76cff6a813
qemu-kvm uq/master Commit:0779caeb1a17f4d3ed14e2925b36ba09b084fb7b
Host Kernel
Re-tested this bug with:
kvm.git(next tree):e47a5f5fb715b90b40747e9e235de557c6abd56c
qemu-kvm.git(uq/master tree): 199472259a41677417fb7de168bd8c589383c6de
This bug has been fixed.
** Changed in: qemu
Status: New = Fix Committed
** Changed in: qemu
Status: Fix Committed = Fix
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit: 660696d1d16a71e15549ce1bf74953be1592bcd3
qemu.git Commit: 64afc2b4d48fb21e085517c38a59a3f61a11283c
Host Kernel Version:3.9.0-rc3
** Attachment added: lspci-in-host
https://bugs.launchpad.net/qemu/+bug/1182716/+attachment/3683492/+files/lspci.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1182716
Title:
guest cannot
** Attachment added: dmesg-in-host
https://bugs.launchpad.net/qemu/+bug/1182716/+attachment/3683493/+files/host-dmesg.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1182716
Title:
guest
the output of 'dmesg' and 'lspci' command in host is attached as above.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1182716
Title:
guest cannot boot up when Intel 82572 NIC assigned
Status in
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):linux
kvm.git next branch Commit:660696d1d16a71e15549ce1bf74953be1592bcd3
qemu-kvm.git uq/master branch Commit:9953f8822cc316eec9962f0a2858c3439a80adec
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:e11ae1a102b46f76441e328a2743ae5d6e201423
qemu-kvm Commit:4d9367b76f71c6d938cf8201392abe4bfb1136cb
Host Kernel Version:3.7.0
I used a small script in the guest to touch files in NFS.
#!/bin/bash
mount vt-nfs:/temp /mnt
cd /mnt
# create files endlessly
for ((i=0; ; i++))
do
mkdir $i
cd $i
# 1 files at most in a directory
for ((j=0; j1; j++))
do
touch $j
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:1a577b72475d161b6677c05abe57301362023bb2
qemu-kvm Commit:98f1f30a89901c416e51cc70c1a08d9dc15a2ad4
Host Kernel Version:3.5.0-rc1
This was fixed a long time ago. I just verified it with latest qemu-kvm.git and
kvm.git.
A RHEL6.3 guest can boot up with 10 VFs, and each VF has good network.
So, mark this bug as fixed and verified.
** Changed in: qemu
Status: New = Fix Released
--
You received this bug notification
qemu64 cpu model has PAE/NX/SSE2 Support by default.
Also, after I used -cpu qemu64,+3dnow, 32bit Win8 also can't be installed and
had a BSOD with Error code: 0x005D.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Verified this bug against latest qemu-kvm upstream.
kvm + qemu-kvm: ae7a2a3f + a212f79f..
The following commit fixed it.
commit a212f79fc4596570124fb864425b980c157cd001
Author: Jason Wang jasow...@redhat.com
Date: Thu May 17 13:25:43 2012 +0800
rtl8139: validate rx ring before receiving
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux(RHEL6u1)
kvm.git Commit:ae7a2a3fb6f8b784c2752863f4f1f20c656f76fb
qemu-kvm Commit:a212f79fc4596570124fb864425b980c157cd001
Host Kernel
** Attachment added: guest dmesg log
https://bugs.launchpad.net/qemu/+bug/1013467/+attachment/3190179/+files/dmesg-guest.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1013467
Title:
** Attachment added: lspci -vvv in guest
https://bugs.launchpad.net/qemu/+bug/1013467/+attachment/3190180/+files/lspci-guest.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1013467
Title:
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:25e531a988ea5a64bd97a72dc9d3c65ad5850120
qemu-kvm Commit:0a948cbb1835e5f36990e173966d30bc4c8cc038
Host Kernel Version:3.5.0-rc1
Re-tested against latest qemu-kvm master branch with commit 0a948cbb. And
found this issue has gone.
Jan Kiszka's following patch fixed this bug.
commit 0cdd3d14447da1a04e778c219c77db8b96f9cf33
Author: Jan Kiszka
Date: Wed Jun 6 16:28:42 2012 +0200
kvm: i8254: Fix conversion of in-kernel
reply to Jan Kiszka:
I looked at the patch in uq/master branch in qemu-kvm.git as you mentioned.
There's another issue in uq/master branch, so I can't conclude whether your
patch will make a difference.
The issue is Windows(e.g. win7) will get a BSOD with a message STOP:
ox005D.
RAW
reply to Michael Tokarev:
Windows qcow2 image will be more easier for reproducing the issue I
reported. And there's a great chance to reproduce it when you do the first try
after rebooting the system.
--
You received this bug notification because you are a member of qemu-
devel-ml, which
after reverting bef0fd59 in qemu-kvm, this issue doesn't exist.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1002121
Title:
disk error when guest boot up via qcow2 image
Status in QEMU:
New
64bit Win8 client can work fine as a kvm guest, however, 32bit can't
work.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1007269
Title:
Can’t install or boot up 32bit win8 guest.
Status in QEMU:
For 32bit Win8, I used different cpu mode and got different results as
following.
n270: can boot up
athlon: fail (Error code: 0x005D)
pentium3: can boot up
pentium2: fail(Error code: 0x005D)
Pentium: fail(error code: 0xc260)
486: fail(error code: 0xc260)
Coreduo: can
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux(rhel6u1)
kvm.git Commit:51bfd2998113e1f8ce8dcf853407b76a04b5f2a0
qemu-kvm Commit:3fd9fedb9fae4517d93d76e93a2924559cacf2f6
Host Kernel
Public bug reported:
Host OS (ia32/ia32e/IA64): ia32e
Guest OS (ia32/ia32e/IA64): ia32e
Guest OS Type (Linux/Windows): Linux(rhel6u1)
kvm.git Commit: 51bfd2998113e1f8ce8dcf853407b76a04b5f2a0
qemu-kvm Commit: e54f008ef8f968cfc2f3ecab78491d180fa31efc
Host Kernel Version:3.4.0-rc7
Hardware: WSM-EP,
Latest commit 3fd9fedb in qemu-kvm master tree still has this issue.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1002121
Title:
disk error when guest boot up via qcow2 image
Status in QEMU:
It was fixed in latest qemu-kvm tree.
verified it against kvm + qemu-kvm: 331b646d..+ e54f008e..
** Changed in: qemu
Status: New = Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:19853301ef3289bda2d5264c1093e74efddaeab9
qemu-kvm Commit:69abebf20280152da8fa7c418a819ae51e862231
Host Kernel Version:3.4.0-rc3
verified.
this bug should have been fixed by the following commit.
commit 80019541e9c13fab476bee35edcef3e11646222c
Author: Jan Kiszka jan.kis...@siemens.com
Date: Mon Apr 23 10:47:14 2012 +0200
qemu-kvm: Switch to upstream in-kernel KVM PIT
The upstream version provides the same
From my test, this bug is fixed in the latest kvm.git. I tried 82572 NIC for
device assignment in WinXP, Win7 and Win2k8. The VT-d NIC works fine in
Windows guest.
kvm.git+qemu-kvm.git = result
f4d1f417 +df44afac = bad
eb9ede96 +df44afac = good
But I don't
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows): Linux(RHEL6u1)
kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b
qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad
Host Kernel
** Attachment added: guest dmesg log
https://bugs.launchpad.net/qemu/+bug/953754/+attachment/2861052/+files/dmesg-guest.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/953754
Title:
one of
** Attachment added: lspci -vvv 82576 NIC in guest
https://bugs.launchpad.net/qemu/+bug/953754/+attachment/2861057/+files/lspci-guest-82576.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
** Description changed:
Environment:
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows): Linux(RHEL6u1)
kvm.git Commit:186195928e8149b27cdd603a660dace454969f2b
qemu-kvm Commit: 81bdec908fb2be0ccaff1d4ee67956c509e440ad
Host
** Attachment added: lspci -vvv 82576 NIC in host
https://bugs.launchpad.net/qemu/+bug/953754/+attachment/2861055/+files/lspci-host-82576.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/953754
** Attachment added: lspci -vvv I350 NIC in host
https://bugs.launchpad.net/qemu/+bug/953754/+attachment/2861054/+files/lspci-host-I350.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/953754
** Attachment added: host dmesg log
https://bugs.launchpad.net/qemu/+bug/953754/+attachment/2861051/+files/dmesg-host.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/953754
Title:
one of the
And if you try with smp=4, you may see some error info from qemu.
assigned_dev_update_msix_mmio: No such device or address
fail to set MSI-X entry number for MSIX! Invalid argument
The message is generated from the funtion assigned_dev_update_msix_mmio in
hw/device-assignment.c
1035 r =
** Attachment added: lspci -vvv I350 NIC in guest
https://bugs.launchpad.net/qemu/+bug/953754/+attachment/2861056/+files/lspci-guest-I350.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/953754
** Changed in: qemu
Status: New = Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/912612
Title:
rhel5u5 guest panic when booting up
Status in QEMU:
Fix Released
Bug
fixed by the following commit.
commit 024a6fbdb9d8cbc4d7f833b23db51c9d1004bc47
Author: Anthony Liguori aligu...@us.ibm.com
Date: Fri Jan 13 07:45:55 2012 -0600
qdev: fix device_del by refactoring reference counting
Commit 8eb0283 broken device_del by having too overzealous reference
Already fixed.
pls. track the following bug.
https://bugzilla.kernel.org/show_bug.cgi?id=42563
** Bug watch added: Linux Kernel Bug Tracker #42563
http://bugzilla.kernel.org/show_bug.cgi?id=42563
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
** Attachment added: lspci -vvv in guest
https://bugs.launchpad.net/qemu/+bug/913774/+attachment/2664205/+files/lspci-guest.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/913774
Title:
** Attachment added: guest dmesg log
https://bugs.launchpad.net/qemu/+bug/913774/+attachment/2664198/+files/dmesg-guest.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/913774
Title:
device
** Attachment added: host dmesg log
https://bugs.launchpad.net/qemu/+bug/913774/+attachment/2664196/+files/dmesg-host.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/913774
Title:
device
** Attachment added: lspci -vvv in host
https://bugs.launchpad.net/qemu/+bug/913774/+attachment/2664197/+files/lspci-host.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/913774
Title:
device
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64): ia32e
Guest OS (ia32/ia32e/IA64): ia32e
Guest OS Type (Linux/Windows): Linux(RHEL6u1)
kvm.git Commit: ff92e9b5571b34f53cbfde0899cf6e6a579cb3fa
qemu-kvm Commit: aad3b517a1b83561f2755dc4451596a421399c19
Host Kernel Version:
This should be a kvm kernel bug. As 'bugzilla.kernel.org' is down, I
reported it here just for tracking.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/912612
Title:
rhel5u5 guest panic when
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64): ia32e
Guest OS (ia32/ia32e/IA64): ia32e
Guest OS Type (Linux/Windows): Linux(rhel5u5)
kvm.git Commit:781f306789361d671187d9ddb518eea3ffda786a
qemu-kvm Commit:2850e9e3d3119f98ff775a75503b2153836c7475
Host Kernel
** Attachment added: guest panic serial log
https://bugs.launchpad.net/bugs/912612/+attachment/2659505/+files/guest-rhel5u5-panic.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/912612
Title:
This is the dmesg in host in vtd assignment. Please look at the log from
its tail. The device with BDF 08:00.0 is the assigned 82572EI NIC to a
Win7 guest.
** Attachment added: dmesg in host in vtd assignment
You can try to follow the reproduce steps described in bug description to
reproduce this bug with the given commit of kvm.git
I think it's easy to reproduce. For Intel NIC drivers in windows, you can
download the appropriate driver you need via searching Network Adapter Drivers
for Windows
This bug is got fixed in qemu-kvm upstream. I verified it. The following
is the commit info for the fix in qemu-kvm.
commit c4cd183600aa6319b4a4a0b48cb41d63198e08c3
Author: Alex Williamson alex.william...@redhat.com
Date: Wed Nov 16 13:45:32 2011 -0700
pci-assign: Fix device removal
This is because kvm is not enabled when starting guest by default even if I add
KVM support when configuring qemu.
Now it got fixed by the following commit.
author Marcelo Tosatti mtosa...@redhat.com
Thu, 27 Oct 2011 20:34:42 +0800 (10:34 -0200)
committer Marcelo Tosatti mtosa...@redhat.com
Thu,
same reason as this bug: https://bugs.launchpad.net/qemu/+bug/882358
This is because kvm is not enabled when starting guest by default even if I add
KVM support when configuring qemu.
Now it got fixed by the following commit.
author Marcelo Tosatti mtosa...@redhat.com
Thu, 27 Oct 2011 20:34:42
It's the same reason as the following bug.
https://bugs.launchpad.net/qemu/+bug/882358
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/855633
Title:
guest boots up too slowly
Status in QEMU:
I also tried this issue with Intel 82576EI NIC, and this normal VT-D NIC
doesn't have this detachment issue.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/875723
Title:
guest aborts when detaching
This is because kvm is not enabled by default even if I add KVM support when
configuring qemu.
Now it got fixed by the following commit.
author Marcelo Tosatti mtosa...@redhat.com
Thu, 27 Oct 2011 20:34:42 +0800 (10:34 -0200)
committer Marcelo Tosatti mtosa...@redhat.com
Thu, 27
It works now.
** Changed in: qemu
Status: New = Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/882358
Title:
device assignment doesn't work: error: requires KVM support
Status
I found this bug in memory/queue branch of qemu.git on September 21st.
As some codes in memory branch were merged into master branch, the
master tree of qemu.git also has this issue now.
** Description changed:
- qemu.git commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b
+ qemu.git (memory/queue
I found this bug in memory/queue branch of qemu.git on September 21st.
As some codes in memory branch were merged into master branch, the
master tree of qemu.git also has this issue now.
** Description changed:
- qemu.git commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b
+ qemu.git (memory/queue
** Description changed:
qemu-kvm commit: b73357ecd2b14c057134cb71d29447b5b988c516
( Author: Marcelo Tosatti mtosa...@redhat.comDate: Wed Mar 16
17:04:16 2011 -0300)
kvm commit: a72e315c509376bbd1e121219c3ad9f23973923f
After restoring from saved img, some I/O errors appear in
** Attachment added: qemu configuration log
https://bugs.launchpad.net/bugs/882358/+attachment/2574718/+files/configure.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/882358
Title:
device
** Attachment added: qemu compiling log
https://bugs.launchpad.net/qemu/+bug/882358/+attachment/2574719/+files/make.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/882358
Title:
device
Public bug reported:
qemu.git commit:8843cf40c0f482949e6ae9d0119e45d6b96fe890
I met the following error when do device assignment with qemu in kvm host.
./x86_64-softmmu/qemu-system-x86_64 -smp 2 -m 1024 -device
pci-assign,host=0e:00.0 -hda /root/jay/rhel6u1.img
qemu-system-x86_64: -device
using the following command line to restore guest, it works for me now.
qemu-system-x86_64 -m 256 -net nic,macaddr=00:16:3e:06:8a:08,model=rtl8139 -net
tap,script=/etc/kvm/qemu-ifup -hda /root/test0320.img
-incoming=/roo/test-save.img
** Changed in: qemu
Status: New = Fix Released
--
Public bug reported:
[This should be a kvm kernel bug. I met this issue with quemu and kvm for
virtualization. For https://bugzilla.kernel.org is not available yet, I just
file this bug here just for tracking. ]
Environment:
Host OS (ia32/ia32e/IA64):All
Guest OS
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):All
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:211978fb6c666f824ae8221baea7ee28efc1
qemu.git Commit:edbb7c0de56692868e6126c7ff7e8bf917f8d0e7
Host Kernel Version:3.1.0-rc9+
Yes, this bug is got fixed.
** Changed in: qemu
Status: New = Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/799036
Title:
NIC assignment order in command line make some NIC
this bug doesn't exist in the latest qemu tree.
** Changed in: qemu
Status: New = Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/830558
Title:
VF doesn't work in guest when not
I used the default 'memory/queue' branch when I filed this bug.
The master tree doesn't have these two bugs, and I'll mark the bugs as invalid.
Mark as invalid.
** Changed in: qemu
Status: New = Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml,
I used the default 'memory/queue' branch when I filed this bug.
The master tree doesn't have this bug.
Mark as invalid.
** Changed in: qemu
Status: New = Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Eh? I can reproduce very easily and it always has this issue in the qemu.git
upstream in the past two weeks. I used rhel5u5, rhel6, rhel6u1 or any other
images as guest, and met the same issue. And this is not a platform specific
issue. It can be reproduced in Westmere-EP and Sandybrige-EP
Public bug reported:
qemu.git commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b
kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34
It will costs about 180 seconds to booting up a rhel6 guest. But when I
use qemu-kvm.git with commit a040d28b, the rhel6 guest can boot up in
about 50 seconds.
Public bug reported:
qemu.git commit: 6cc7686696f73ae87cadef4450776a488b0e0c8b
kvm.git commit: 7f914d61cd2156e34a7852462bb4932621f33a34
64-bit Windows guest cannot boot up, but 32-bit windows guest can boot
up successfully. For Win7, it will show blue scream of death when
booting up. For Windows
sorry, the right command to reproduce is 'qemu-system-x86_64 -m 1024
-smp 2 -hda /root/rhel6.img'. I missed the '-hda' in the bug
description.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/855633
** Project changed: qemu-kvm = qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/830558
Title:
VF doesn't work in guest when not pinned with addr=
Status in QEMU:
New
Bug description:
** Project changed: qemu-kvm = qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739088
Title:
I/O errors after Save/Restore
Status in QEMU:
New
Bug description:
qemu-kvm commit:
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):All
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux (rhel6 and rhel5u5)
kvm.git Commit:ef7c782ea4a99fafb3d60dc8b8c057e0ef14f9f7
qemu-kvm Commit:44755ea36fee3f0b1093ef27404def8857602274
Host Kernel
this issue occurred again. So reopen this bug.
I use upstream kvm.git ef7c782ea and qemu-kvm.git 44755ea36.
The host is rhel6.1 with lastest kvm and qemu-kvm installed, and its file
system type is ext4.
here's the dmesg info in rhel5u5 guest after being restored.
this issue got fixed. It doesn't exist in qemu-kvm.git
fda19064e889d4419dd3dc69ca8e6e7a1535fdf5
** Changed in: qemu
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
I found this issue is also exist in latest qemu-kvm.git
commit d58931037dbb4fbc2fbb33858629d3fabfd1b0d4
Merge: bcd4f22... f8121c4...
Author: Avi Kivity a...@redhat.com
Date: Tue Jun 28 15:11:13 2011 +0300
Git log shows it has merged commit 2fb0c09f4f*, but the bug is not
fixed.
--
You
dmesg and lspci logs are attached as a tar package. There are many logs
in it, please read README.txt first, which will tell you which log is in
which case.
** Attachment added: vtd-NIC-assignment-order-issue.tar
Without fixing address of the device, the first device will get 00:03.0 in my
guest, and the second get 00:04.0.
And when NIC 82576 is in the first order, it will get 00:03.0 in my guest, and
it will not working.
If I fix 82576 NIC using addr=0x3 and other using addr=0x4, 82576 NIC in
guest
It was fixed in kvm.git.
This bug is fixed in the kvm upstream. It was fixed in kvm.git f8fcfd7 by
alex.william...@redhat.com.
commit f8fcfd775523347afe460dc3a0f45d0479e784a2
Author: Alex Williamson alex.william...@redhat.com
Date: Tue May 10 10:02:39 2011 -0600
KVM: Use
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):All
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux
kvm.git Commit:681fb677ace0754589792c92b8dbee9884d07158
qemu-kvm Commit:05f1737582ab6c075476bde931c5eafbc62a9349
Host Kernel Version:3.0.0-rc2+
I can reproduce it stably. I use igb driver for my NIC. And Alex
Williamson is on the way to fix it.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/754591
Title:
NIC doesn't work when it had been
hot-plug NIC doesn't have this issue.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/754591
Title:
NIC doesn't work when it had been used before
Status in QEMU:
New
Bug description:
** Changed in: qemu
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/730441
Title:
NIC doesn't work with pci=nomsi in grub.conf
Status in QEMU:
Fix
this bug is fixed in latest commit.
kvm.git Commit:b35049715d619c9badaea07dec766787b433facf
qemu-kvm Commit:27f368604a3d27ca4ddac0f62a6928bb93cdacd5
** Changed in: qemu
Status: New = Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64): All
Guest OS (ia32/ia32e/IA64): All
Guest OS Type (Linux/Windows):All
kvm.git Commit:3b840cc27e5b831a26e3303096b88e112d1cf59f
qemu-kvm Commit:df85c051d780bca0ee2462cfeb8ef6d9552a19b0
Host Kernel Version:2.6.38+
** Attachment added: dmesg_guest_NIC
https://bugs.launchpad.net/bugs/754591/+attachment/125/+files/dmesg.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/754591
Title:
NIC doesn't work
qemu-kvm.git
bad:df85c051d780bca0ee2462cfeb8ef6d9552a19b0 and
9488459ff2ab113293586c1c36b1679bb15deee
good:2c9bb5d4e5ae3b12ad71bd6a0c1b32003661f53a
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
a related issues was reported and fiexed before, but the two is not the same
problem.
http://sourceforge.net/tracker/?func=detailaid=2847560group_id=180599atid=893831
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Public bug reported:
Environment:
Host OS (ia32/ia32e/IA64):All
Guest OS (ia32/ia32e/IA64): All
Guest OS Type (Linux/Windows): Linux
kvm.git Commit:a3e2cba1e702cfe15e2ebb20a75b88f02c834d3f
qemu-kvm Commit:2c9bb5d4e5ae3b12ad71bd6a0c1b32003661f53a
Host Kernel Version:2.6.38+
this bug is fixed in the latest qemu-kvm.git:
2c9bb5d4e5ae3b12ad71bd6a0c1b32003661f53a
** Changed in: qemu
Status: New = Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739088
this bug is fixed in the latest qemu-kvm.git:
2c9bb5d4e5ae3b12ad71bd6a0c1b32003661f53a
** Changed in: qemu
Status: New = Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739092
** Attachment added: dmesg after restoring
https://bugs.launchpad.net/qemu/+bug/739088/+attachment/1925364/+files/restore1.jpg
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739088
Title:
I/O
** Attachment added: running commands after restoring
https://bugs.launchpad.net/qemu/+bug/739088/+attachment/1925365/+files/restore2.jpg
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739088
1 - 100 of 108 matches
Mail list logo
