Re: [Xen-devel] VMX status report. Xen: #17630 & Xen0: #540 -- blocked

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Li, Haicheng writes ("[Xen-devel] VMX status report. Xen: #17630 & Xen0: #540 
-- blocked"):
> Today's nightly testing is still blocked for both PAE and 32E, c/s 17606
> introduced this issue.
...
> New issue:
> [Bug 1250] HVM guest can not boot with Qcow image
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1250

I'm afraid you are using the wrong syntax.
file:... is for raw images.

Prior to changeset 17606, the emulated IDE controller would, if the
specified file looked like a qcow image, interpret it that way - but
the PV presentation of the same device (via blktap) to the same guest
would treat it as a raw image.  This (and other related scenarios)
allows a malicious guest to read any file on the host (including for
example the host's underlying disk devices), because the qcow image
format contains the (host) pathname of the backing file.

In changeset 17606 the behaviour was changed so that file:... always
treats the specified file as a raw disk image.  To use a file
containing a qcow image, you have to say tap:qcow:...

This was discussed here on the list quite recently; feel free to
comment further if you think the fix is the wrong one.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel