I spent about 3 hr before I can find correct command to attach iSCSI /dev/vda
to my instance
euca-attach-volume vol-59A00634 -d /dev/vdb -i i-511908A5
I hope this tip save time for somebody.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscri
@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 aga
@Serge: Yes acpiphp is definitely loaded. I used the UEC images.
@Kiall: Thanks for the hint about vdX. Does that mean you just specify
(for example) vda when attaching the device to the instance and that
will work? I have no cluster installed with which i could test atm.
--
dynamic block device
Yes - 100% sure.
I've since discovered that using /dev/vdX works without a reboot, while
/dev/sdX does not work until after a reboot!
vdX triggers the use of virtio, while sdX uses the "standard" method ..
whatever that is! I stopped digging once i got it working with vdX :)
--
dynamic block de
@Wolfgang and @Kiall: are you sure that the acpiphp module is loaded
in your guest?
--
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 Ubuntu
Server Team, which is subscribed
@Wolfgang I believe this is still an issue in maverick/10.10 aswell. I
can attach a volume with UEC (10.10 metal and 10.10 instance).
If you issue a `shutdown -r now` within the instance, the volume will be
attached after the reboot... just spent about 8 hours getting that far!
--
dynamic block
I believe this bug is still existing in the latest 10.10 server release.
When attaching a volume the nc.log shows that it was properly mounted
via iSCSI and one can access it on the node but it will not appear in
the guest. The guest is the latest UEC release of Lucid. Can anybody
confirm that this
** Changed in: qemu
Status: Fix Committed => Fix Released
--
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 Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu
** Changed in: qemu
Status: Confirmed => Fix Committed
** Changed in: qemu
Milestone: None => 0.12.0
--
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 Ubuntu
Server
** Branch linked: lp:ubuntu/qemu-kvm
--
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 Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs ma
** Changed in: libvirt (Ubuntu Karmic)
Status: Triaged => Invalid
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged => Invalid
--
dynamic block device attach/detach not functional with karmic KVM
https://bugs.launchpad.net/bugs/432154
You received this bug notification beca
This bug was fixed in the package qemu-kvm - 0.11.0-0ubuntu5
---
qemu-kvm (0.11.0-0ubuntu5) karmic; urgency=low
[ Dustin Kirkland ]
* debian/patches/10_fix_scsi_hotplug.patch: cherry-pick patch from
upstream to fix scsi hotplug regression, LP: #432154
* debian/patches/11_fix
I think this is related to Bug #419590.
:-Dustin
--
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 Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-s
** Changed in: qemu-kvm (Ubuntu Karmic)
Status: Triaged => In Progress
--
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 Ubuntu
Server Team, which is subscribed to qemu-
Dan-
I have reproduced your crash on the second invocation of adding a virtio
disk.
I'm looking for a fix now.
:-Dustin
--
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 Ubu
I found this bit of documentation, which I thought I'd link here since it's
pertinent:
*
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.4/html/Virtualization_Guide/chap-Virtualization-KVM_Para_virtualized_Drivers.html
:-Dustin
--
dynamic block device attach/detach not functional
** Changed in: libvirt (Ubuntu Karmic)
Status: Invalid => Triaged
** Changed in: qemu-kvm (Ubuntu Karmic)
Status: In Progress => Triaged
--
dynamic block device attach/detach not functional with karmic KVM
https://bugs.launchpad.net/bugs/432154
You received this bug notification be
My experiments with hot-attaching virtio disks to eucalyptus VMs have
been partially successful. I've been able to attach/detach a virtio
disk to/from a VM once, but the second attach causes a kvm segfault
followed by a libvirtd segfault. Removing eucalyptus from the scenario,
this problem can be
As discussed in Friday's release meeting, using virtio seems to be
better than having no attach/detach at all for 9.10
--
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 Ubuntu
Here's a status update...
I can reproduce this problem as follows, without libvirt or eucalyptus
in the picture...
Create some small auxiliary storage to dynamically add to a running VM.
(host) $ dd if=/dev/zero of=/tmp/foo bs=1M count=64
Boot a vm in Karmic under qemu-kvm-0.11.0 like this:
Soren,
Any chance you can lend a hand with this bug?
:-Dustin
--
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 Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Confirmed => Triaged
--
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 Ubuntu
Server Team, which is subscribed to qemu-
Ah, I just saw Scott's quote of Tim's response.
:-Dustin
--
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 Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
On Tue, Sep 29, 2009 at 1:24 PM, Scott Moser wrote:
> Another option that would work is CONFIG_HOTPLUG_PCI_ACPI=y (as Etienne
> originally suggested)
I think we need to do this. Are there any circumstances where we
would *not* want that?
:-Dustin
--
dynamic block device attach/detach not func
> Another option that would work is CONFIG_HOTPLUG_PCI_ACPI=y (as Etienne
> originally suggested)
Per Tim Gardner in irc:
smoser, I think you're gonna have to go the initramfs route.
i accept your answer, but just curious, why not build in?
smoser, regression potential for existing platforms. i
On Tue, 29 Sep 2009, Etienne Goyer wrote:
> Dustin Kirkland wrote:
> > Note that I had to modprobe acpiphp. Perhaps we should consider loading
> > this module in init or in modules.conf.
>
> I have reported this issue in bug #364916.
Well, specifically in that bug you reported that there was no
Dustin Kirkland wrote:
> Note that I had to modprobe acpiphp. Perhaps we should consider loading
> this module in init or in modules.conf.
I have reported this issue in bug #364916.
--
dynamic block device attach/detach not functional with karmic KVM
https://bugs.launchpad.net/bugs/432154
You r
** Changed in: qemu-kvm (Ubuntu Karmic)
Milestone: ubuntu-9.10-beta => ubuntu-9.10
--
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 Ubuntu
Server Team, which is subscribed
all, here is as much information as I could think of in an attempt to
allow for reproducability (see attached file). Here is what each file
in the attached tarball contains:
setup - quick description of machine set up
orig.libvirt.xml - the XML vm description that is passed to libvirt
kvmcmdline
all, here is as much information as I could think of in an attempt to
allow for reproducability (see attached file). Here is what each file
in the attached tarball contains:
setup - quick description of machine set up
orig.libvirt.xml - the XML vm description that is passed to libvirt
kvmcmdline
** Changed in: eucalyptus (Ubuntu Karmic)
Importance: Undecided => High
--
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 Ubuntu
Server Team, which is subscribed to qemu-kvm
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Invalid => Confirmed
--
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 Ubuntu
Server Team, which is subscribed to qemu-
** Attachment added: "432154_with_counter.sh"
http://launchpadlibrarian.net/32427128/432154_with_counter.sh
--
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 Ubuntu
Server
My crash after several iterations turns out to be not intermittent at
all. I decided to add a counter and see how many times I could
attach/detach before the crash. Interestingly, it is 28 times, every
time. Attached is an updated reproducer with the counter and an added
'sleep 30' after starting t
And I can also confirm Jamie's report. This is intermittent. :-/
:-Dustin
--
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 Ubuntu
Server Team, which is subscribed to qemu-k
Okay, and now I am able to successfully attach a device to a running VM
in both the qemu console, and from virt-manager (which uses libvirt).
In both cases, I'm seeing the device dynamically pop up in the guest.
Note that I had to modprobe acpiphp. Perhaps we should consider loading
this module in
Okay, my core dump is actually Bug #419590, which results from a syntax
error.
>From the qemu console, the proper invocation is:
pci_add auto storage file=image.img,if=virtio
Note "auto" rather than 1 or 0.
So with that, the command succeeds and doesn't crash the VM. However,
I'm not yet seeing
** Changed in: libvirt (Ubuntu Karmic)
Assignee: Dustin Kirkland (kirkland) => (unassigned)
** Changed in: libvirt (Ubuntu Karmic)
Status: In Progress => Invalid
** Project changed: qemu-kvm => qemu
** Changed in: qemu
Status: Invalid => Confirmed
** Changed in: qemu
Impor
Okay, I just took libvirt out of the equation.
Dropping to a qemu console (ctrl-alt-2), and running pci_add, according to:
* http://www.linux-kvm.org/page/Hotadd_pci_devices
crashes qemu-kvm:
kvm: /build/buildd/qemu-kvm-0.11.0~rc2/hw/pci.c:1029: pci_qdev_init:
Assertion `pci_dev' failed.
:-Dus
Let me be clear: my testing is on a 9.10 x86_64 host with qemu-kvm
0.11.0~rc2-0ubuntu4 and a Jaunty 32 bit guest.
--
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 Ubuntu
Serve
I don't think this is a libvirt problem. It also appears intermittent
here. In doing other testing I was looping attach and detach and found
that kvm (presumably) died, with the guest disappearing (and needed to
be started again). Attached is a (very crude) test script that can be
called with:
$ .
This appears possibly related:
* https://bugzilla.redhat.com/show_bug.cgi?id=510425
* http://www.redhat.com/archives/libvir-list/2009-July/msg00115.html
However, we already have that code in our libvirt. Mentioning here for
completeness.
:-Dustin
** Bug watch added: Red Hat Bugzilla #510425
** Changed in: qemu-kvm (Ubuntu Karmic)
Status: Triaged => In Progress
** Changed in: qemu-kvm
Status: New => Invalid
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Karmic)
Status: New => In Progress
** Changed i
** Changed in: qemu-kvm (Ubuntu Karmic)
Status: Confirmed => Triaged
--
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 Ubuntu
Server Team, which is subscribed to qemu-kv
Sorry, no patch. Disregard that.
--
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 Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs maili
Patch attached.
:-Dustin
** Attachment added: "out"
http://launchpadlibrarian.net/32354800/out
** Attachment removed: "out"
http://launchpadlibrarian.net/32354800/out
--
dynamic block device attach/detach not functional with karmic KVM
https://bugs.launchpad.net/bugs/432154
You received
Apparently a regression in kvm-qemu, not something to fix in the
Eucalyptus package... please reopen if I got it wrong.
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => High
** Changed in: qemu-kvm (Ubuntu)
Status: New => Confirmed
** Changed in: qemu-kvm (Ubuntu)
Mileston
Dustin, here is my progress thus far. On a install of Karmic alpha6 CD,
with qemu-kvm 0.11.0~rc2-0ubuntu4
FIRST:
---
boot VM
ubuntu jaunty
kernel 2.6.28-11-generic
load 'acpiphp' module in VM
modprobe acpiphp
try 'virsh attach-device
dd if=/dev/zero o
Okay, any chance you can help narrow down where this functionality
regressed?
:-Dustin
--
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 Ubuntu
Server Team, which is subscribe
I agree with Etienne on this issue; another thing to consider is that
many virtual appliances that are developed for EC2/UEC will be depending
on EBS functionality, due to the persistence observation made above.
--
dynamic block device attach/detach not functional with karmic KVM
https://bugs.lau
Not Dan, but here's my take anyway.
I would say it is fairly critical. The EBS functionality (on which the
block device attach/detach functionality depends) is a pretty important
feature. Without, data persistence is not obvious. For example, you
would run MySQL in the cloud by keeping table da
Dan-
What would you say the priority of this is?
Is Eucalyptus dependent on this functionality?
:-Dustin
--
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 Ubuntu
Server Team
** Also affects: qemu-kvm
Importance: Undecided
Status: New
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
--
dynamic block device attach/detach not functional with karmic KVM
https://bugs.launchpad.net/bugs/432154
You received this bug notification beca
53 matches
Mail list logo
