Re: Hot-adding disk on VM

2009-12-25 Thread Daniel Bareiro
Hi, Dustin.

On Saturday, 07 November 2009 21:15:09 -0600,
Dustin Kirkland wrote:

 On Sat, Nov 7, 2009 at 7:01 PM, Daniel Bareiro daniel-lis...@gmx.net wrote:
  According to I see in Launchpad, there is a fix released for Qemu
  and qemu-kvm (Ubuntu).
 
 It's fix committed in QEMU, and Fix Released in Ubuntu's qemu-kvm.
 
 We in Ubuntu have released version of qemu-kvm-0.11.0 that includes an
 extra patch from Anthony, which he posted on the mailing list, and
 committed to QEMU's git tree.  He hasn't officially released an
 upstream QEMU with the fix yet, though.
 
  I'm using KVM-88 compiled from the source code obtained of the KVM
  official site. How I could apply these fix? There is some KVM
  version that includes these corrections in the official site?
 
 Not that I know of, yet.
 
 You can pull the patch [1] we're carrying in Ubuntu, and apply it to
 qemu-kvm-0.11.0 [2] from the kvm website, if you like.

 [1] 
 http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/karmic/qemu-kvm/karmic/annotate/head%3A/debian/patches/11_fix_virtio-blk_hot_add_after_remove.patch
 [2] http://sourceforge.net/projects/kvm/files/

I've tested again with Linux 2.6.32 and qemu-kvm-0.12.0-rc2 and this
time I could verify that no longer happens the problem with Virtio.
That is to say, the virtual disk can be added and be removed every time
without problems.

It drew attention to me that whenever I add the virtio device, this
appears with a different name (vdc, vdd, vde, etc). This it is the
awaited behavior?

Testing the same with if=scsi, I get a tainted again when removing
the virtual disk since the first time that I try to remove it.
Nevertheless, no longer it seems to have problem to add it again.


Thanks for your reply.

Merry Christmas.

Regards,
Daniel
-- 
Fingerprint: BFB3 08D6 B4D1 31B2 72B9  29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Lenny - Linux user #188.598


signature.asc
Description: Digital signature


Re: Hot-adding disk on VM

2009-11-07 Thread Daniel Bareiro
Hi, Dustin.

On Sunday, 11 October 2009 21:25:19 -0500,
Dustin Kirkland wrote:

  According to I see in this document [1], is necessary that is loaded
  two modules in the guest: acpiphp and pci_hotplug.
 
  The pci_hotplug module is loaded. Nevertheless, in spite of existing
  the acpiphp module, cannot be loaded:
 
  chandra:~# lsmod|grep pci_hotplug
  pci_hotplug            23460  0
 
  chandra:~# modprobe acpiphp
  FATAL: Error inserting acpiphp
  (/lib/modules/2.6.26-2-686/kernel/drivers/pci/hotplug/acpiphp.ko): No such 
  device
 
  chandra:~# locate acpiphp | grep 686
  /lib/modules/2.6.26-2-686/kernel/drivers/pci/hotplug/acpiphp.ko
  /lib/modules/2.6.26-2-686/kernel/drivers/pci/hotplug/acpiphp_ibm.ko
 
 
  Which could be being the problem?
 
  I was doing other tests this time with Linux 2.6.31.2 compiled by myself
  from the sources of kernel.org. This time with loading the acpiphp
  module, the pci_hotplug module was loaded automatically without I get
  some type of error message.
 
  central:~# lsmod | grep acpiphp
  central:~#
  central:~# modprobe acpiphp
  central:~#
  central:~# lsmod | grep acpiphp
  acpiphp                22140  0
  pci_hotplug            29024  1 acpiphp
 
 
  Then, I tried to add a disk of the following way in host:
 
  (qemu) pci_add auto storage file=/dev/vm/central-test,if=virtio
  OK domain 0, bus 0, slot 5, function 0
 
  In the guest:
 
  Oct 11 18:09:01 central kernel: [  833.403875] pci :00:02.0: BAR 6: 
  bogus alignment [0x0-0x0] flags 0x2
  Oct 11 18:09:01 central kernel: [  833.406337] decode_hpp: Could not get 
  hotplug parameters. Use defaults
  Oct 11 18:09:01 central kernel: [  833.430492] virtio-pci :00:05.0: 
  enabling device ( - 0001)
  Oct 11 18:09:01 central kernel: [  833.452268] ACPI: PCI Interrupt Link 
  [LNKA] enabled at IRQ 10
  Oct 11 18:09:01 central kernel: [  833.454668] virtio-pci :00:05.0: PCI 
  INT A - Link[LNKA] - GSI 10 (level, high) - IRQ 10
  Oct 11 18:09:01 central kernel: [  833.500051] Clocksource tsc unstable 
  (delta = -148257950 ns)
  Oct 11 18:09:01 central kernel: [  833.566755]  vda: vda1
 
 
  Then I attempt to remove the device assuring previously that it is not
  being used in guest:
 
  (qemu) pci_del 5
 
 
  In the guest:
 
  Oct 11 18:13:32 central kernel: [ 1104.144179] virtio-pci :00:05.0: PCI 
  INT A disabled
 
 
  But if I want to add the device again, I get a segmentation fault of the
  process that handles this virtual machine:
 
  (qemu) pci_add auto storage file=/dev/vm/central-test,if=virtio
  Connection closed by foreign host.
 
 I can actually confirm this behavior.  I've been struggling with this
 for a couple of days now.  CC'ing QEMU, as I've discussed this a bit
 with Anthony Liguori.  There's at least two related bugs we've been
 tracking:

  * https://bugs.edge.launchpad.net/ubuntu/+source/qemu-kvm/+bug/432154
  * https://bugs.edge.launchpad.net/ubuntu/+source/qemu-kvm/+bug/419590

According to I see in Launchpad, there is a fix released for Qemu and
qemu-kvm (Ubuntu).

I'm using KVM-88 compiled from the source code obtained of the KVM
official site. How I could apply these fix? There is some KVM version
that includes these corrections in the official site?

Thanks for your reply.

Regards,
Daniel
-- 
Fingerprint: BFB3 08D6 B4D1 31B2 72B9  29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Squeeze - Linux user #188.598


signature.asc
Description: Digital signature


Re: Hot-adding disk on VM

2009-11-07 Thread Dustin Kirkland
On Sat, Nov 7, 2009 at 7:01 PM, Daniel Bareiro daniel-lis...@gmx.net wrote:
 According to I see in Launchpad, there is a fix released for Qemu and
 qemu-kvm (Ubuntu).

It's fix committed in QEMU, and Fix Released in Ubuntu's qemu-kvm.

We in Ubuntu have released version of qemu-kvm-0.11.0 that includes an
extra patch from Anthony, which he posted on the mailing list, and
committed to QEMU's git tree.  He hasn't officially released an
upstream QEMU with the fix yet, though.

 I'm using KVM-88 compiled from the source code obtained of the KVM
 official site. How I could apply these fix? There is some KVM version
 that includes these corrections in the official site?

Not that I know of, yet.

You can pull the patch [1] we're carrying in Ubuntu, and apply it to
qemu-kvm-0.11.0 [2] from the kvm website, if you like.

[1] 
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/karmic/qemu-kvm/karmic/annotate/head%3A/debian/patches/11_fix_virtio-blk_hot_add_after_remove.patch

[2] http://sourceforge.net/projects/kvm/files/

:-Dustin
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Hot-adding disk on VM

2009-10-11 Thread Daniel Bareiro
Hi, all!

On Saturday, 22 August 2009 10:59:47 -0300,
Daniel Bareiro wrote:

 According to I see in this document [1], is necessary that is loaded
 two modules in the guest: acpiphp and pci_hotplug.
 
 The pci_hotplug module is loaded. Nevertheless, in spite of existing
 the acpiphp module, cannot be loaded:
 
 chandra:~# lsmod|grep pci_hotplug
 pci_hotplug23460  0
 
 chandra:~# modprobe acpiphp
 FATAL: Error inserting acpiphp
 (/lib/modules/2.6.26-2-686/kernel/drivers/pci/hotplug/acpiphp.ko): No such 
 device
 
 chandra:~# locate acpiphp | grep 686
 /lib/modules/2.6.26-2-686/kernel/drivers/pci/hotplug/acpiphp.ko
 /lib/modules/2.6.26-2-686/kernel/drivers/pci/hotplug/acpiphp_ibm.ko
 
 
 Which could be being the problem?

I was doing other tests this time with Linux 2.6.31.2 compiled by myself
from the sources of kernel.org. This time with loading the acpiphp
module, the pci_hotplug module was loaded automatically without I get
some type of error message.

central:~# lsmod | grep acpiphp
central:~#
central:~# modprobe acpiphp
central:~#
central:~# lsmod | grep acpiphp
acpiphp22140  0
pci_hotplug29024  1 acpiphp


Then, I tried to add a disk of the following way in host:

(qemu) pci_add auto storage file=/dev/vm/central-test,if=virtio
OK domain 0, bus 0, slot 5, function 0

In the guest:

Oct 11 18:09:01 central kernel: [  833.403875] pci :00:02.0: BAR 6: bogus 
alignment [0x0-0x0] flags 0x2
Oct 11 18:09:01 central kernel: [  833.406337] decode_hpp: Could not get 
hotplug parameters. Use defaults
Oct 11 18:09:01 central kernel: [  833.430492] virtio-pci :00:05.0: 
enabling device ( - 0001)
Oct 11 18:09:01 central kernel: [  833.452268] ACPI: PCI Interrupt Link [LNKA] 
enabled at IRQ 10
Oct 11 18:09:01 central kernel: [  833.454668] virtio-pci :00:05.0: PCI INT 
A - Link[LNKA] - GSI 10 (level, high) - IRQ 10
Oct 11 18:09:01 central kernel: [  833.500051] Clocksource tsc unstable (delta 
= -148257950 ns)
Oct 11 18:09:01 central kernel: [  833.566755]  vda: vda1


Then I attempt to remove the device assuring previously that it is not
being used in guest:

(qemu) pci_del 5


In the guest:

Oct 11 18:13:32 central kernel: [ 1104.144179] virtio-pci :00:05.0: PCI INT 
A disabled


But if I want to add the device again, I get a segmentation fault of the
process that handles this virtual machine:

(qemu) pci_add auto storage file=/dev/vm/central-test,if=virtio
Connection closed by foreign host.


r...@ubuntu:~# tail -f /var/log/messages
[...]
Oct 11 18:21:29 ubuntu kernel: [692002.207026] qemu-system-x86[3481]: segfault 
at 8d0 ip 0041a183 sp 7fff848ef9f0 error 6 in 
qemu-system-x86_64[40+219000]
Oct 11 18:21:29 ubuntu kernel: [692002.291714] br0: port 4(tap2) entering 
disabled state
Oct 11 18:21:29 ubuntu kernel: [692002.330875] br0: port 4(tap2) entering 
disabled state


Also I was testing using if=scsi and when I trying to remove the device,
can be seen a 'tainted' in guest. In host:

(qemu) pci_add auto storage file=/dev/vm/central-test,if=scsi

In guest:

Oct 11 18:35:51 central kernel: [  199.375026] pci :00:02.0: BAR 6: bogus 
alignment [0x0-0x0] flags 0x2
Oct 11 18:35:51 central kernel: [  199.377801] decode_hpp: Could not get 
hotplug parameters. Use defaults
Oct 11 18:35:51 central kernel: [  199.484410] sym53c8xx :00:05.0: enabling 
device ( - 0003)
Oct 11 18:35:51 central kernel: [  199.495739] ACPI: PCI Interrupt Link [LNKA] 
enabled at IRQ 10
Oct 11 18:35:51 central kernel: [  199.498165] sym53c8xx :00:05.0: PCI INT 
A - Link[LNKA] - GSI 10 (level, high) - IRQ 10
Oct 11 18:35:51 central kernel: [  199.503886] sym0: 895a rev 0x0 at pci 
:00:05.0 irq 10
Oct 11 18:35:51 central kernel: [  199.508711] sym0: No NVRAM, ID 7, Fast-40, 
LVD, parity checking
Oct 11 18:35:51 central kernel: [  199.512023] sym0: SCSI BUS has been reset.
Oct 11 18:35:51 central kernel: [  199.530575] scsi2 : sym-2.2.3
Oct 11 18:35:54 central kernel: [  202.512229] scsi 2:0:0:0: Direct-Access 
QEMU QEMU HARDDISK0.10 PQ: 0 ANSI: 3
Oct 11 18:35:54 central kernel: [  202.515687]  target2:0:0: tagged command 
queuing enabled, command queue depth 16.
Oct 11 18:35:54 central kernel: [  202.519013]  target2:0:0: Beginning Domain 
Validation
Oct 11 18:35:54 central kernel: [  202.521737]  target2:0:0: Domain Validation 
skipping write tests
Oct 11 18:35:54 central kernel: [  202.524167]  target2:0:0: Ending Domain 
Validation
Oct 11 18:35:54 central kernel: [  202.530816] sd 2:0:0:0: Attached scsi 
generic sg3 type 0
Oct 11 18:35:54 central kernel: [  202.533321] sd 2:0:0:0: [sdc] 10485760 
512-byte logical blocks: (5.36 GB/5.00 GiB)
Oct 11 18:35:54 central kernel: [  202.536661] sd 2:0:0:0: [sdc] Write Protect 
is off
Oct 11 18:35:54 central kernel: [  202.538825] sd 2:0:0:0: [sdc] Write cache: 
enabled, read cache: enabled, doesn't support DPO or FUA
Oct 11 18:35:54 central kernel: [  202.543108]  sdc: sdc1
Oct 11 18:35:54 central 

Re: Hot-adding disk on VM

2009-10-11 Thread Dustin Kirkland
On Sun, Oct 11, 2009 at 4:51 PM, Daniel Bareiro daniel-lis...@gmx.net wrote:
 Hi, all!

 On Saturday, 22 August 2009 10:59:47 -0300,
 Daniel Bareiro wrote:

 According to I see in this document [1], is necessary that is loaded
 two modules in the guest: acpiphp and pci_hotplug.

 The pci_hotplug module is loaded. Nevertheless, in spite of existing
 the acpiphp module, cannot be loaded:

 chandra:~# lsmod|grep pci_hotplug
 pci_hotplug            23460  0

 chandra:~# modprobe acpiphp
 FATAL: Error inserting acpiphp
 (/lib/modules/2.6.26-2-686/kernel/drivers/pci/hotplug/acpiphp.ko): No such 
 device

 chandra:~# locate acpiphp | grep 686
 /lib/modules/2.6.26-2-686/kernel/drivers/pci/hotplug/acpiphp.ko
 /lib/modules/2.6.26-2-686/kernel/drivers/pci/hotplug/acpiphp_ibm.ko


 Which could be being the problem?

 I was doing other tests this time with Linux 2.6.31.2 compiled by myself
 from the sources of kernel.org. This time with loading the acpiphp
 module, the pci_hotplug module was loaded automatically without I get
 some type of error message.

 central:~# lsmod | grep acpiphp
 central:~#
 central:~# modprobe acpiphp
 central:~#
 central:~# lsmod | grep acpiphp
 acpiphp                22140  0
 pci_hotplug            29024  1 acpiphp


 Then, I tried to add a disk of the following way in host:

 (qemu) pci_add auto storage file=/dev/vm/central-test,if=virtio
 OK domain 0, bus 0, slot 5, function 0

 In the guest:

 Oct 11 18:09:01 central kernel: [  833.403875] pci :00:02.0: BAR 6: bogus 
 alignment [0x0-0x0] flags 0x2
 Oct 11 18:09:01 central kernel: [  833.406337] decode_hpp: Could not get 
 hotplug parameters. Use defaults
 Oct 11 18:09:01 central kernel: [  833.430492] virtio-pci :00:05.0: 
 enabling device ( - 0001)
 Oct 11 18:09:01 central kernel: [  833.452268] ACPI: PCI Interrupt Link 
 [LNKA] enabled at IRQ 10
 Oct 11 18:09:01 central kernel: [  833.454668] virtio-pci :00:05.0: PCI 
 INT A - Link[LNKA] - GSI 10 (level, high) - IRQ 10
 Oct 11 18:09:01 central kernel: [  833.500051] Clocksource tsc unstable 
 (delta = -148257950 ns)
 Oct 11 18:09:01 central kernel: [  833.566755]  vda: vda1


 Then I attempt to remove the device assuring previously that it is not
 being used in guest:

 (qemu) pci_del 5


 In the guest:

 Oct 11 18:13:32 central kernel: [ 1104.144179] virtio-pci :00:05.0: PCI 
 INT A disabled


 But if I want to add the device again, I get a segmentation fault of the
 process that handles this virtual machine:

 (qemu) pci_add auto storage file=/dev/vm/central-test,if=virtio
 Connection closed by foreign host.

I can actually confirm this behavior.  I've been struggling with this
for a couple of days now.  CC'ing QEMU, as I've discussed this a bit
with Anthony Liguori.  There's at least two related bugs we've been
tracking:
 * https://bugs.edge.launchpad.net/ubuntu/+source/qemu-kvm/+bug/432154
 * https://bugs.edge.launchpad.net/ubuntu/+source/qemu-kvm/+bug/419590

:-Dustin
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html