Brain,
Thank you for information. With your confirmation, I think our engineer
must have done something wrong during the software upgrade process. I will
keep an eye on this when we re-do the test.
-Original Message-
From: Brian Jackson [mailto:i...@theiggy.com]
Sent:
Hi Brian,
Do you have any finding for VirtIO Net driver problem?
The latest Ubuntu release(v 12.04) still comes with Qemu 0.14.1.
Did you find any debug report for VirtIO Net driver on qemu 0.14.1?
If we need to upgrade qemu, is there any installation package available over
the web?
Last time,
We hit a kernel panic when a VM was configured with bridge mode. After the
IpTable was disabled using the following command lines, the kernel panic was
gone. We would like to know if there is any fix in latest kernel for this issue?
Note that we ran qemu 1.0 on Ubuntu 11.10
--
Hi Brian,
Here are the information from our system.
We launched the VM using the following XML file.
The kernel version is 3.0.0.12
The Qemu version is 1.0.0(we upgraded it. Default one is 0.14.1)
We recently ran an Ubuntu 11.10 VM which was installed with VirtIO NIC driver.
The VirtIO net driver came from the Ubuntu's default package. The VM we
installed was configured as a bridge mode. When we ran the Iperf test against
the VM, the network interface of the VM was fairly unstable.
The kernel version is 3.0.0.12
The Qemu version is 1.0.0(we upgraded it)
What version of kernel do we need to upgrade?
-Original Message-
From: mathslinux [mailto:riegama...@gmail.com]
Sent: Monday, June 04, 2012 2:03 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: qemu-devel@nongnu.org
Subject: Re:
I am just curious about this issue. Is there any document mentioning the lowest
version of the kernel to be supported by VirtIO?
-Original Message-
From: Dunrong Huang [mailto:riegama...@gmail.com]
Sent: Monday, June 04, 2012 2:17 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: qemu-devel@nongnu.org
Yes, I saw that page too. But our current kernel version meets the kernel
requirement.
Why do we need to upgrade it?
-Original Message-
From: Dunrong Huang [mailto:riegama...@gmail.com]
Sent: Monday, June 04, 2012 2:26 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: qemu-devel@nongnu.org
Subject: Re:
We recently ran an Ubuntu 11.10 VM which was installed with VirtIO NIC driver.
The VirtIO net driver came from the Ubuntu's default package. The VM we
installed was configured as a bridge mode. When we ran the Iperf test against
the VM, the network interface of the VM was fairly unstable.
Stefan,
Hans replied me back and he suggested me to use strace.
Hopefully, this issue can be resolved.
Additionally, we encountered a tough issue right now.
When we ran a 64-bit Windows 7 VM overnight, the kvm process was killed for
some reasons.
Here is the qemu version I copied from the
Stefan,
I made two test cases here.
1) case one:
A 32-bit Windows 7 VM with 8G virtual disk size.
In this test, the virtual disk is almost full.
Like what you said, the instance VM size only increased 2%
initially and only a little
Stefan,
Can you explain why a 64KB could be allocated for each sector write?
Right now, I am testing a VM with 8G virtual disk space.
The disk only has 12.6 MB free space left when I run the test.
I am going to see what will happen in this test case.
Hi Stefan,
I had a problem to launch the VM using the script that contains the Qemu
options. My script used to work before updating the latest Qemu code suggested
by Hans. I also tried to latest code from Freedesktop, it still failed to work
either.
Obviously, Qemu was broken somewhere in the
Stefan,
Here are what we tested and found for this issue.
1. We checked the integrity of the qcow2 image by running
“qemu-img check” and it looked good.
2. We monitored the I/O activities of VM using
“Process monitor”, “Process explorer” and could not
Stefan,
Thank you for information. What we worried is an endless growth of the image
size.
If virtual disk size is the ceiling of the max. image size to be grew, we
should not have to worry about this issue.
-Original Message-
From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
Sent:
Thanks. Good alternative view.
-Original Message-
From: Michael Tokarev [mailto:m...@tls.msk.ru]
Sent: Wednesday, May 23, 2012 9:11 PM
To: Stefan Hajnoczi
Cc: Charles.Tsai-蔡清海-研究發展部; Jonah.Wu-吳君勉-研究發展部; qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] The image size of instance VM keeps
We created a qcow2 based-image for a VM whose size is big when it is created.
When a VM is launched, it is a instance VM image which refers to the
based-image. Initially, the image size of instance VM is smaller than that of
the based-mage. But we found the image size of the instance VM kept
Stefan,
We can run a tool to see if there is any active I/O or not. Does the image size
shrink back if an I/O activity stops?
What we found here is that the image size kept growing. If this problem
persists, it could eat up the entire disk space.
-Original Message-
From: Stefan
Stefan,
Thank you for information. We will try to isolate the issue here and give you
an update.
-Original Message-
From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
Sent: Monday, May 21, 2012 9:24 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: qemu-devel@nongnu.org; Jonah.Wu-吳君勉-研究發展部
Subject:
Christophe,
Great!, we finally are at the same page.
-Original Message-
From: Christophe Fergeau [mailto:cferg...@redhat.com]
Sent: Monday, March 19, 2012 6:13 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Vadim Rozenfeld; qemu-devel; Michael Roth; Paul Lu-盧偉智-研究發展部;
Vadim,
My colleague will give you more information we found here.
Qemu somehow in this particular case returns a wrong bar0 value.
In working case, the bar0 is 0xc140. But in failure case, the bar0 is changed
to 0xC141.
-Original Message-
From: Vadim Rozenfeld
Hi Vadim,
We recently encountered with many issues with new Windows Virio driver
running on Qemu 1.0 and Qemu 1.0.50.
My initial investigation was found that the new Viro driver could not
be installed before Qemu 1.0.50.
But my colleague right now can install the new
Vadim,
What do you mean qemu configuration string? Is it the build configuration or
command line option?
Please let me know it. Thanks.
-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Monday, March 19, 2012 5:17 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael
Vadim,
Thanks. I tested Windows guest OS driver the over qemu-kvm-devel 1.0.50 from
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git and it worked.
The latest Windows guest driver from (https://github.com/YanVugenfirer/) seems
to have to work with Qemu 1.0.50. My previous test ran over Qemu
Vadim,
I did the same test again today and no luck to made it work.
Let us what you find since we might have missed some points when we did the
test.
-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Sunday, February 05, 2012 2:14 AM
To:
Vadim,
We tested the free build driver on 32-bit Windows 7 and the symptom was the
same. In other words, the latest driver source from
https://github.com/YanVugenfirer/ is buggy and it was not workable at all.
-Original Message-
From: Charles.Tsai-蔡清海-研究發展部
Sent: Friday, February
Vadim,
I downloaded the latest Windows guest driver code from
(https://github.com/YanVugenfirer/) and built the test binary driver code.
When I tested the release build Vioserial driver on 64-bit Windows 7, the
driver seemed to wait for something to happen and the update driver Windows
dialog
Vadim,
Thanks. We will download the code from Yan's repository.
-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Friday, January 20, 2012 8:48 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex
Vadim,
It is SMP system.
-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 3:58 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex
Huang-黃必賢-研究發展部; Alon Levy; qemu-devel
Subject:
Vadim,
We built it from the driver source. Up to this moment, we always use the same
binary to test Qemu.
-Original Message-
From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
Sent: Thursday, January 19, 2012 5:39 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Michael Roth; Stefan Hajnoczi;
Alon,
Thank you for your information and we will use it if we need to find the bug
next time.
-Original Message-
From: Alon Levy [mailto:al...@redhat.com]
Sent: Thursday, January 19, 2012 7:26 PM
To: Stefan Hajnoczi
Cc: Charles.Tsai-蔡清海-研究發展部; qemu-devel; Michael Roth; Vadim Rozenfeld;
Vadim,
We downloaded the driver source from the following website.
===
wget --no-check-certificate
https://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/src/virtio-win-prewhql-0.1-15-sources.zip
-Original Message-
From:
Vadim,
I tested on Qemu 1.0.50. and found the VioSerial driver had problem to install
on 64-bit Win7 guest.
During the driver installation, the system hung after the driver being
installed. After I rebooted the
guest OS, the Vioserial driver work. The hang system seemed to be found only
during
Vadim,
I just ran the Qemu monitor to get the PCI information. The information is
listed belowe.
From the listed information, I did not see anything wrong with the BAR0.
---
INFO:
Bus 0, device 0, function 0:
Host bridge: PCI device 8086:1237
id
Bus 0, device 1,
Stefan,
We need the spice support in Qemu. Does qemu-kvm 1.0 support for spice?
-Original Message-
From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
Sent: Monday, January 16, 2012 4:37 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Vadim Rozenfeld; Alon Levy; spice-de...@lists.freedesktop.org; Alex
Dominique,
Thank you for your information and we will try it here.
From: Dominique Rodrigues [mailto:dominique.rodrig...@nanocloud.com]
Sent: Monday, January 16, 2012 5:51 PM
To: Charles.Tsai-蔡清海-研究發展部
Cc: Stefan Hajnoczi; spice-de...@lists.freedesktop.org; Alex Huang-黃必賢-研究發展部;
Vadim
Vadim,
I am sorry that it was my mistake because I did not see there was a PIC device
which was created with no device driver installed.
Instead of updating the driver, I ran the hardware installation wizard to
install the Vioserial driver.
As such, the system could not install the device
Vadim,
Thank you for your prompt reply. Here are the information for our test case.
1) we use the following command line to launch the guest OS
/usr/bin/kvm -S -M pc-0.14 -enable-kvm -m 1024 -smp
1,sockets=1,cores=1,threads=1 -name win_xp -uuid
d9388815-ddd3-c38e-33c2-a9d5fcc7a775
38 matches
Mail list logo
