From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL13N Subject: Re: hvm-pv installation failed... IO errors? Date: Sat, 06 Apr 2013 23:17:15 +0200 Message-ID: <5492514.RtHuLfqnDm@localhost> References: <33326649.VbvSaMPCm1@localhost> <7615317.gp3puESTU4@localhost> <1633816.Vc1B8t3eXY@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1633816.Vc1B8t3eXY@localhost> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Op zaterdag 6 april 2013 20:43:40 schreef AL13N: > Op donderdag 4 april 2013 22:47:31 schreef AL13N: > [...] > > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > ... > Unknown PV product 3 loaded in guest > PV driver build 1 > > > the io thing could refer to the disk... maybe > > the unknown pv stuff, are those number supposed to match? what do they refer > to? > > is this something like the xen-blkfront driver? it appears this is really libvirt's fault? when i create an lvm entry with virt-manager, it seems to create an lvm which is an active snapshot destination for a source (that doesn't exist), which has a 4MB COW space... this runs out fairly quick and thus fucks up shit. I have no idea why the hell libvirt would do something like this... why in godsname would this be needed???