Hi Riel,
I tried qcow backend in Beta 2 and for blktap:qemu syntax I receive hotplug failure.
For tap:qemu syntax I don't receive any failure but device is not created anyway.
Any ideas ?
Are there any known issues with blktap ?
What is the righ procedure for creation qcow backend?
I use SWM mode.
Nice day
Rudolf
------------ Původní zpráva ------------
Od: Rik van Riel <[EMAIL PROTECTED]>
Předmět: Re: [rhelv5-beta-list] Xen filesystems for DomU
Datum: 22.11.2006 23:39:40
----------------------------------------
Jeffrey D Lane wrote:
> A certain other Linux that uses Xen uses sparse files mounted over
> loopback, my RHEL5 test box, however, is not using anything (that I can
> see) mounted over loopback. So is it some sort of magic occurring in the
> Hypervisor that accesses the DomU filesystem directly on disk??
Loopback has the problem that the dom0 kernel may not write your
data back to disk when the guest OS expects it to, leading to
data corruption after a power failure. I lost a test database
to this bug a few times already :)
Because of this, we fixed qemu-dm to do synchronous IO for fully
virtualized guests and made blktap-aio work right for paravirtualized
domains.
Now when a guest OS thinks disk IO has been done, the data really
is on disk.
--
All Rights Reversed
_______________________________________________
rhelv5-beta-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-beta-list
_______________________________________________
rhelv5-beta-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-beta-list
