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

[Reinoud Zandijk <reinoud%NetBSD.org@localhost>]

Hi Manuel,

On Tue, May 26, 2015 at 11:43:00PM +0200, Manuel Bouyer wrote:
> > > Yes, probably. try using /dev/rwd1d instead of /dev/wd1d maybe ?
> > 
> > Xen seems to only want to use block devices.
> > 
> > I think i've found the issue though! Xentools42 is creating qemu-system-i386
> > on this amd64 system. Could that result in the crippled harddisc access?
> 
> No, I think qemu-system-i386 is the right name.
> Do you have errors in logs when trying the raw device ?

It just won't start! I get:

# xl create netbsd-hvm 
Parsing config from netbsd-hvm
libxl: error: libxl_device.c:266:libxl__device_disk_set_backend: Disk vdev=hda
phys path is not a block dev or file: /dev/rwd1d
libxl: error: libxl_dm.c:1269:libxl__destroy_device_model: could not find
device-model's pid for dom 1
libxl: error: libxl.c:1419:libxl__destroy_domid: libxl__destroy_device_model
failed for 1
# 

this is with:
disk = [ 'phy:/dev/rwd1d,ioemu:hda,rw' ]

Has there been updates in the Xen support? Should i update my Xen + dom0
kernel? They are both from 20150305, NetBSD 7.99.5.I run a freshly compiled
xentools42-4.2.5nb4.

(XEN) Xen version 4.2.5 (reinoud@) (gcc (nb2 20150115) 4.8.4) Fri Mar 27
10:57:24 CET 2015

I do get :

(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000e4c00 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bf780000 (usable)
(XEN)  00000000bf780000 - 00000000bf798000 (ACPI data)
(XEN)  00000000bf798000 - 00000000bf7dc000 (ACPI NVS)
(XEN)  00000000bf7dc000 - 00000000c0000000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ffe00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000340000000 (usable)
...
(XEN) [VT-D]dmar.c:562:   RMRR address range not in reserved memory base =
bf7dc000 end = bf7dbfff; iommu_inclusive_mapping=1 parameter may be needed.
(XEN) [VT-D]dmar.c:625:   The RMRR (bf7dc000, bf7dbfff) is incorrect!
(XEN) Failed to parse ACPI DMAR.  Disabling VT-d.
...
(XEN) Freed 252kB init memory.
(XEN) ioapic_guest_write: apic=0, pin=0, irq=0
(XEN) ioapic_guest_write: new_entry=000109f0
(XEN) ioapic_guest_write: old_entry=00010000 pirq=0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=2, irq=0
(XEN) ioapic_guest_write: new_entry=000109f0
(XEN) ioapic_guest_write: old_entry=000009f0 pirq=0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) irq.c:1879: dom0: pirq 0 or irq 3 already mapped
(XEN) irq.c:1879: dom0: pirq 0 or irq 4 already mapped
(XEN) irq.c:1879: dom0: pirq 0 or irq 5 already mapped
(XEN) irq.c:1879: dom0: pirq 0 or irq 6 already mapped
(XEN) irq.c:1879: dom0: pirq 0 or irq 7 already mapped
(XEN) irq.c:1879: dom0: pirq 0 or irq 8 already mapped
(XEN) irq.c:1879: dom0: pirq 0 or irq 9 already mapped
(XEN) irq.c:1879: dom0: pirq 0 or irq 10 already mapped
(XEN) irq.c:1879: dom0: pirq 0 or irq 11 already mapped
(XEN) irq.c:1879: dom0: pirq 0 or irq 12 already mapped


Can these hurt / explain?

Thanks in advance,
Reinoud