[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 Wed, May 27, 2015 at 12:14:41PM +0200, Reinoud Zandijk wrote:
> 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
No, I think nobody tried to use a HVM guest with a physical block device
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
Main Index |
Thread Index |