qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 432154] Re: dynamic block device attach/detach not fun


From: Kiall
Subject: [Qemu-devel] [Bug 432154] Re: dynamic block device attach/detach not functional with karmic KVM
Date: Wed, 10 Nov 2010 17:13:06 -0000

@Wolfgang: Yes - Specifying, for example, /dev/vda triggers the use of
virtio over the "standard" - and works exactly as you would expect EBS
volumes to :)

There *is* still a bug preventing /dev/sdX from working .. but I've sank
too much time into finding it at the moment, I'll probably dig in again
later.

-- 
dynamic block device attach/detach not functional with karmic KVM
https://bugs.launchpad.net/bugs/432154
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: Fix Released
Status in “eucalyptus” package in Ubuntu: Invalid
Status in “libvirt” package in Ubuntu: Invalid
Status in “qemu-kvm” package in Ubuntu: Fix Released
Status in “eucalyptus” source package in Karmic: Invalid
Status in “libvirt” source package in Karmic: Invalid
Status in “qemu-kvm” source package in Karmic: Fix Released

Bug description:
The version of KVM currently in karmic does not appear to have a fully 
functional dynamic block device attach/detach:


outside VM:
---------------------------------------------------------------
address@hidden:/root# virsh list
Connecting to uri: qemu:///system
 Id Name                 State
----------------------------------
  1 i-512A0927           running

address@hidden:/root# ls -l /tmp/foobar
-rw-r--r-- 1 root root 33554432 2009-09-17 15:09 /tmp/foobar
address@hidden:/root# cat /tmp/meh
<disk type='block'><driver name='phy'/><source dev='/tmp/foobar'/><target 
dev='sdb'/></disk>
address@hidden:/root# virsh attach-device 1 /tmp/meh
Connecting to uri: qemu:///system
Device attached successfully

address@hidden:/root# 

inside VM (with acpiphp loaded)
--------------------------------------------------------------
address@hidden:/lib/modules# dmesg
[ 1482.978287] pci 0000:00:06.0: reg 10 io port: [0x00-0xff]
[ 1482.978327] pci 0000:00:06.0: reg 14 32bit mmio: [0x000000-0x0003ff]
[ 1482.978365] pci 0000:00:06.0: reg 18 32bit mmio: [0x000000-0x001fff]
[ 1482.978673] pci 0000:00:02.0: BAR 6: bogus alignment [0x0-0x0] flags 0x2
[ 1482.978750] decode_hpp: Could not get hotplug parameters. Use defaults
[ 1482.982167] sym53c8xx 0000:00:06.0: enabling device (0000 -> 0003)
[ 1482.982274] sym53c8xx 0000:00:06.0: PCI INT A -> Link[LNKB] -> GSI 10 
(level, high) -> IRQ 10
[ 1482.984011] sym1: <895a> rev 0x0 at pci 0000:00:06.0 irq 10
[ 1482.989722] sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking
[ 1482.992017] sym1: SCSI BUS has been reset.
[ 1483.001733] scsi6 : sym-2.2.3
address@hidden:/lib/modules# 
----------------------------------------------------------------

libvirt/kvm appear to believe that the block device has been attached, but the 
device is not showing up in the guest (this process with the same VM/kernel 
works on Jaunty).  Apparmor is disabled.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]