Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: HVM disc corruption (was Re: Xen won't start its device backend?)


On Tue, Jun 02, 2015 at 08:55:38PM +0200, Manuel Bouyer wrote:
> On Tue, Jun 02, 2015 at 08:50:17PM +0200, Reinoud Zandijk wrote:
> > The error only starts to show between block 250.000.000 (27.89 bits) and block
> > 300.000.000 (28.16 bits). And indeed, block 268.435.456 (2^28) maps to sector
> > 0 but block 268.435.455 is wrong already.
> > 
> > Looking at the dmesg, am I right that the piixide in compatibility mode is
> > thus resulting in this error since the hvm wd0 uses LBA48 addressing.
> Yes, it looks like the IDE emulation in qemu is not working as it should
> with LBA48

wd0 reports it supports LBA48 still but i don't see a line claiming its using.
It only reports PIO mode 4, DMA mode 2.

> > As a side notice, the network in hvm is VERY slow most likely due to the
> > number of watchdog timeouts i get from re0. Dumping got into the 4kb/sec ;)
> > 
> > I used
> >   vif = [ 'mac=90:e6:ba:6c:6f:d2,bridge=bridge0' ]
> You could try to add 'type=ioemu, model=e1000' to the entry above.
> I found that the e1000 emulation (wm(4) under NetBSD) gives much better
> performances.

Quite so! The network speed is now upto par again! thanks for the tip.

As per suggestion on chat, i changed back to xentools41 and had to revert back
to xenkernel41 too. It feels more responsive but it still has the same mapping
issue, so far no luck. What strikes me is that it is near bit 28, a kind of
odd number unless the top 4 bits mean something else to code somewhere in the
whole chain.

Any idea on how to persue this further? Any fixes?

With regards,

Attachment: pgpONIijhj8on.pgp
Description: PGP signature

Home | Main Index | Thread Index | Old Index