Mailinglist Archive: opensuse-bugs (7309 mails)

< Previous Next >
[Bug 489425] New: unable to use tap:vmdk
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 26 Mar 2009 11:19:25 -0600 (MDT)
  • Message-id: <bug-489425-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=489425


Summary: unable to use tap:vmdk
Classification: openSUSE
Product: openSUSE 11.1
Version: Final
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Xen
AssignedTo: cgriffin@xxxxxxxxxx
ReportedBy: snorp@xxxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---


Created an attachment (id=282349)
--> (https://bugzilla.novell.com/attachment.cgi?id=282349)
/var/log/messages from 'xm create'

It seems that tap:vmdk is broken. I created a disk with 'qemu-img convert
disk.raw disk.vmdk', so I would think that should work. Instead, 'xm create'
gives the following (after a long pause):

xm create -c Xen_Test.i686-0.0.1.xenconfig
Using config file "./Xen_Test.i686-0.0.1.xenconfig".
Error: Device /dev/xvdp (tap) could not be disconnected.

Things are pretty hosed in general afterwards. Running 'xm block-list' shows
the device:

xm block-list 0
Vdev BE handle state evt-ch ring-ref BE-path
51952 0 0 3 28 8 /local/domain/0/backend/tap/0/51952

But removing it is not possible:

xm block-detach 0 51952
Error: Device 51952 not connected

There is a lot of bad looking stuff in /var/log/messages from blktapctrl. I've
attached the log. The xen config I used is below:

memory=512
disk=[ "tap:vmdk:/tmp/disk.vmdk,xvda,w" ]
vif=[ "bridge=xenbr0" ]

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >