I was mistaken, I'm only seeing this problem on maverick. FWIW running
lucid or natty on domU moves the first hd to /dev/xvda and iscsi works
just fine.
Also if I boot my maverick domU via HVM-boot-policy="BIOS order" instead
of pygrub, the first hd still goes to /dev/sda - but iscsi initiator
wi
I tried udev stuff initially, before the fix in Natty, but I couldn't
get around this issue. Maybe my udev foo is not strong enough. It
seemed to me that if udev actually had a say, then the order would be
/dev/sda /dev/sdb. I think the issue was the kernel implementation of
the hypervisor disk
I've run into the same issue with a lucid guest running on XCP.
Everything I can find says that the first block device *should* be xvda,
but mine is sda, and that causes the open-iscsi to sysfs error.
Is there a way to force xen or this udev to move the block device out of
the way?
# udevadm info
** Changed in: open-iscsi (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672759
Title:
open-iscsi duplicates exsiting block device on initiator login
--
This problem is resolved for me in Natty 11.04. Xen pv_ops kernels use
xvda, so there is no longer a conflict for sda during initiator login.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672759
Titl
Similar dmesg with the virtual kernel shown here. A hard power off (xm
destroy) is the only way to restart the system.
[ 704.493694] scsi 0:0:0:0: Direct-Access IET VIRTUAL-DISK 0
PQ: 0 ANSI: 4
[ 704.493901] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 704.505016] sd 0:0:0:0
Same issue with linux-image-2.6.35-23-virtual and linux-
image-2.6.35-23-server. Looks like xenpv + iscsi is likely a problem
for all Ubuntu flavors.
--
open-iscsi duplicates exsiting block device on initiator login
https://bugs.launchpad.net/bugs/672759
You received this bug notification becau
** Attachment added: "dmesg after executing initiator login"
https://bugs.launchpad.net/bugs/672759/+attachment/1727257/+files/dmesg.txt
--
open-iscsi duplicates exsiting block device on initiator login
https://bugs.launchpad.net/bugs/672759
You received this bug notification because you are
