On Aug 14, 2012, at 10:00 PM, Chuck Thier cth...@gmail.com wrote:
snip
I could get behind this, and was was brought up by others in our group
as a more feasible short term solution. I have a couple of concerns
with this. It may cause just as much confusion if the api can't
reliably
On Mon, 13 Aug 2012, Vishvananda Ishaya wrote:
Hey Everyone,
Resulting Issues
a) The device name only makes sense for linux. FreeBSD will select
different device names, and windows doesn't even use device names. In
addition xen uses /dev/xvda and kvm uses /dev/vda
b)
Hey Vish,
First, thanks for bringing this up for discussion. Coincidentally a
similar discussion had come up with our teams, but I had pushed it
aside at the time due to time constraints. It is a tricky problem to
solve generally for all hypervisors. See my comments inline:
On Mon, Aug 13,
On Aug 13, 2012 11:37 PM, Vishvananda Ishaya vishvana...@gmail.com
wrote:
The second proposal I have is to use a feature of kvm attach and set the
device serial number. We can set it to the same value as the device
parameter. This means that a device attached to /dev/vdb may not always be
at
4 matches
Mail list logo
