Comment 11 for bug 205450

Todd Deshane said:
> It is actually fixed for me, but with the workarounds listed above:
>
> sda --> hda
>
> file:/ --> tap:aio/

You're right, with the following config I have a working domU - as far
as the block devices are concerned anyway. (I did not have the hda/sda
problem: strange.)

kernel = '/boot/vmlinuz-2.6.24-15-xen'
ramdisk = '/boot/initrd.img-2.6.24-15-xen'
memory = '256'
root = '/dev/xvda2 ro'
disk = [
                  'tap:aio:/xen/domains/domU/swap.img,xvda1,w',
                  'tap:aio:/xen/domains/domU/disk.img,xvda2,w',
              ]
name = 'domU'
dhcp = 'dhcp'
vif = [ 'mac=00:16:3E:6C:07:90' ]
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
extra = '2 console=xvc0'

Now I have to look at what you and other people have done to get a
functional console (got boot output but no getty) and networking.

> The bugs above could be fixed by fixing xen-tools and/or are different
> separate bugs.

And indeed xen-tools (3.8-4ubuntu4) has slipped in quietly to fix the
xvda problem and to add support for hardy guests. It hasn't fixed the
tap:aio: instead of file: yet.

> So, the bug as filed has basically been fixed and has workarounds for
> things that are broken otherwise

Agreed, I suppose.

Andrew.

--
Andrew Shugg <email address hidden> http://www.neep.com.au/

"Just remember, Mr Fawlty, there's always someone worse off than yourself."
"Is there? Well I'd like to meet him. I could do with a good laugh."