Hi All,
I am testing NPIV feature on upstream Qemu, I have configured the zone
and able to see the created vport on the storage array.
Since, I am learning on how to setup the NPIV, I haven't created the different
zone for
the vport and the array, I just added in the existing zone.
Now, how do
Hi,
Please find the status of the upstream testing:
Kernel : 3.10.0-rc5+
Qemu : 1.5.50
Libvirt : 1.0.6
Bugs filed in this week : 5
Qemu Bugs in Launchpad :
---
Bug# 1199416 - Hot-add qcow2 [virtio-scsi] devices doesn't work in
SlLES-11-SP2guest
https://bugs
On 07/05/2013 01:52 PM, Stefan Hajnoczi wrote:
> The destination VM's log says:
>
>qemu: warning: error while loading state section id 1
>
> This indicates that either there was an error on the destination while
> loading state or the migration stream got out of sync.
>
> Please check that QEMU
Hi,
Below are bugs filed in this week for Upstream qemu and libvirt:
Qemu in Launchpad:
https://bugs.launchpad.net/opensuse/+bug/1199416
Hot-add qcow2 [virtio-scsi] devices doesn't work in SlLES-11-SP2guest
Libvirt Bugs:
Bug 982224 - Attaching of the Virtio-scsi [qcow2] drives fails with
"er
Thanks Stefanha.
If we use the commad virsh attach-disk rhel64-64 /home/images/virtio-
scsi11.img --persistent sdr --cache writethrough the qcow2 images will
also gets added as raw which is by default. Hence we should use
"virsh attach-disk rhel64-64 /home/images/virtio-scsi11.img --persistent
sd
Thanks, I ll work on this and update 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/1192499
Title:
virsh migration copy-storage-all fails with "Unable to read from
monitor: Connection reset b
On 06/13/2013 02:14 PM, Stefan Hajnoczi wrote:
On Thu, Jun 13, 2013 at 10:31:04AM +0530, chandrashekar shastri wrote:
We are testing the upstream KVM with :
Kernel, Qemu, Libvirt, Virt-Manager is built from the source (git).
kernel version : 3.9.0+
qemu version : QEMU emulator version 1.5.0
** Attachment added: "Destination guest logs"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725329/+files/dest.tar.bz2
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1
** Attachment added: "Destination Libvirtd logs"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725331/+files/destination_libvirtd.logs
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.laun
** Attachment added: "Source Libvirtd logs"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725330/+files/source_libvirtd.logs
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/
** Attachment added: "source guest logs"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499/+attachment/3725328/+files/source.log.tar.bz2
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/
Guest output:
---
[root@redhat ~]# ls -lrt /dev/sd
sda sda1 sda2 sdb
[root@redhat ~]# ls -lrt /dev/sd
sda sda1 sda2 sdb
[root@redhat ~]# ls -lrt /dev/sdb
brw-rw. 1 root disk 8, 16 Jul 4 21:58 /dev/sdb
[root@redhat ~]# blockdev --getsize64 /dev/sdb
197120
[root@r
** Attachment added: "Screen shot"
https://bugs.launchpad.net/fedora/+bug/1197663/+attachment/3724283/+files/Screenshot2.png
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1197663
Title:
qcow2 [
I tried booting with the qemu and observed the same thing.
qemu-system-x86_64 /home/images/rhel64-64.qcow2 -drive
if=none,id=hd,file=/home/images/virtio-scsi11.img -device virtio-scsi-
pci,id=scsi --enable-kvm -device scsi-hd,drive=hd -m 2000
After creating the filesystem tried running the iozone
** Also affects: fedora
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1197663
Title:
qcow2 [virtio-scsi] devices when mapped to the guest shows as 0MB
Moving to qemu component as qemu is crashing based on the inputs from
Michal Privoznik
Bugzilla : Bug 979411 - virsh migration copy-storage-all fails with
"Unable to read from monitor: Connection reset by peer"
** Project changed: libvirt => qemu
** Bug watch added: Red Hat Bugzilla #979411
Public bug reported:
qcow2 [virtio-scsi] devices when mapped to the guest shows as 0MB
irrespective of the volume size.
Kernel Version: 3.10.0-rc5+
Libvirt Version: 1.0.6
Qemu Version: 1.5.50
Steps to reproduce the issue:
1. Create a qcow2 voulme using the command qemu-img create -f qcow2
vi
Adding Libvirt list.
Thanks,
Shastri
Original Message
Subject:Biweekly upstream qemu-kvm test report - July 1st, 2013
Date: Mon, 01 Jul 2013 19:45:32 +0530
From: chandrashekar shastri
To: qemu-devel@nongnu.org, ltc-...@lists.linux.ibm.com,
virt-test-de
Hi,
Please find the status of the upstream testing:
Kernel : 3.10.0-rc5+
Qemu : 1.5.50
Libvirt : 1.0.6
Total number of bugs filed : 6
Bugs filed in this week : 5
Qemu Bugs in Launchpad :
1) 1192499 - virsh migration copy-storage-all fails with "Unable to
read from monitor: Connection r
Ok. Thanks.
On 06/27/2013 02:39 PM, Paolo Bonzini wrote:
> Il 27/06/2013 11:03, chandrashekar shastri ha scritto:
>> Hi Bonzini,
>>
>> Thanks, cpu hot-plug is working.
>> Could you please help me with cpu hot-unplug It is working.
> It is not implemented yet.
>
Hi Bonzini,
Thanks, cpu hot-plug is working.
Could you please help me with cpu hot-unplug It is working.
Thanks,
chandrashekar
On 06/27/2013 01:19 PM, Paolo Bonzini wrote:
> You need to specify "-smp maxcpus=N" on the command-line, for example
> "-smp cpus=2,maxcpus=4" will start the VM with 2 C
Public bug reported:
cpu hot-add doesn't work with upstream qemu 1.5.50. When we add the cpu
[through QMP] it throws error as " {"error": {"class": "GenericError",
"desc": "Unable to add CPU: 2, max allowed: 1"}} ", when we have booted
the guest with two cpus.
Host Kernel Version: 3.10.0-rc5+
Li
Hi All,
The Libvirt compliation fails to bootstarp for local gnulib. We do not
have outbound access for the test machines.
So, we ll pull the gnulib from and copy to the test machines.
When we run ./bootstrap --no-git --gnulib-srcdir=/path/to/local, below
is the error:
./bootstrap: Bootstr
Hi All,
I have filed the following bug for watchdog:
NMI watchdog fails to increment the NMI counter in /proc/interrupts
Kernel Version: 3.10.0-rc5+
Libvirt Version: 1.0.6
Qemu Version: 1.5.50
Steps to reproduce the issue:
1. Booted the VM with :
qemu-system-x86_64 VM1.qcow2 -enable-kvm -watc
On 06/14/2013 03:15 AM, Paolo Bonzini wrote:
Il 13/06/2013 13:26, chandrashekar shastri ha scritto:
On 06/13/2013 02:14 PM, Stefan Hajnoczi wrote:
On Thu, Jun 13, 2013 at 10:31:04AM +0530, chandrashekar shastri wrote:
We are testing the upstream KVM with :
Kernel, Qemu, Libvirt, Virt-Manager
Hi,
Please find the result of upstream testing, we ran the test cases
against following git versions:
Host kernel 3.9.0+ (Upstream)
v3.9-10518-gd7ab73 Branch master SHA1
d7ab7302f970a254997687a1cdede421a5635c68
Qemu 1.5.0
Libvirt 1.0.5 v1.0.5-57-ga605b Branch master SHA1
a605b7e041a6702
On 06/14/2013 03:15 AM, Paolo Bonzini wrote:
Il 13/06/2013 13:26, chandrashekar shastri ha scritto:
On 06/13/2013 02:14 PM, Stefan Hajnoczi wrote:
On Thu, Jun 13, 2013 at 10:31:04AM +0530, chandrashekar shastri wrote:
We are testing the upstream KVM with :
Kernel, Qemu, Libvirt, Virt-Manager
On 06/13/2013 02:14 PM, Stefan Hajnoczi wrote:
On Thu, Jun 13, 2013 at 10:31:04AM +0530, chandrashekar shastri wrote:
We are testing the upstream KVM with :
Kernel, Qemu, Libvirt, Virt-Manager is built from the source (git).
kernel version : 3.9.0+
qemu version : QEMU emulator version 1.5.0
On 06/13/2013 06:20 PM, Laszlo Ersek wrote:
On 06/13/13 12:19, chandrashekar shastri wrote:
Hi,
I have filed a bug "fdisk still shows the "/dev/sdb" partitions even
after the removal of scsi disk" for the upstream kernel.
Bug link:
https://bugs.launchpad.net/qemu/+bug
Hi,
I have filed a bug "fdisk still shows the "/dev/sdb" partitions even
after the removal of scsi disk" for the upstream kernel.
Bug link:
https://bugs.launchpad.net/qemu/+bug/1190525
RHEL guest shows the partittions even after the removal of scsi disk:
fdisk still shows the "/dev/sdb" parti
Public bug reported:
RHEL guest shows the partittions even after the removal of scsi disk:
fdisk still shows the "/dev/sdb" partitions even after the removal of scsi disk.
Guest details:
---
Kernel : 2.6.32-358
Host Details :
Upstream Kernel, Qemu, Libvirt and virt-manager
Hi All,
We are testing the upstream KVM with :
Kernel, Qemu, Libvirt, Virt-Manager is built from the source (git).
kernel version : 3.9.0+
qemu version : QEMU emulator version 1.5.0
libvirt version : 1.0.5
virt-install : 0.600.3
I have followed the below steps to test the "Live migration w/o s
Hi All,
We are testing the upstream KVM with :
Kernel, Qemu, Libvirt, Virt-Manager is built from the source (git).
kernel version : 3.9.0+
qemu version : QEMU emulator version 1.5.0
libvirt version : 1.0.5
virt-install : 0.600.3
I have followed the below steps to test the NMI watchdog feature
Hi All,
Upstream : virt-install and virt-manager fails to install the guest with the error
"qemu: could not load PC BIOS 'bios.bin'"
Kernel, Qemu, Libvirt, Virt-Manager is built from the source (git).
kernel version : 3.9.0+
qemu version : QEMU emulator version 1.5.0
libvirt version : 1.0.5
v
Hi,
Please find the result of upstream testing, we ran the test cases
against following git versions:
Host kernel 3.9.0+ (Upstream), Base Kernel is RHEL 7 Alpha 3 x86_64
v3.9-10518-gd7ab73 Branch master SHA1
d7ab7302f970a254997687a1cdede421a5635c68
uname -a
Linux localhost.localdomain 3.9
35 matches
Mail list logo
