I thought using blktap might help it, but i've been unable to get it to work...
booting the kernel i just get eventually:
XENBUS: Waiting for devices to initialise: 295s.. then it just fails to boot.
In my config:
disk = ['tap2:tapdisk:aio:/root/testvm/disks/test.img,xvda1,w']
looks like it was working?
On Fri, Feb 18, 2011 at 10:55 PM, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
> On Fri, Feb 18, 2011 at 5:58 PM, moncojhr <moncojhr@xxxxxxxxx> wrote:
>> Having a problem here where, if I write quickly in a domU, dom0
>> freezes up and I cant do anything but reboot, you can still type, just
>> nothing will ever do anything.
>> I noticed that I am able to get much faster speeds writing in the domU
>> then in dom0:
>> dom0: 1073741824 bytes (1.1 GB) copied, 27.3189 s, 39.3 MB/s
>> domU: 1073741824 bytes (1.1 GB) copied, 6.80832 s, 158 MB/s
> That's because dom0 is buffering the writes.
>> I do not get the freeze/lockup when writing in dom0, only when writing
>> quickly a lot of data in domU.
>> I am using file: for my vm's , using the 126.96.36.199 dom0 from git.
> Don't use file:.
> - tap2:tapdisk:aio: (if you're using Xen >= 4.0.1)
> - tap:tapdisk:aio: (if you're using Xen = 4.0.0)
> - tap:aio (anything older than 4.0.0)
Xen-users mailing list