[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Problem running fully virtualized NetBSD under the new XenServer 6.2
Citrix released XenServer 6.2 (now completely free & open source - see
XenServer.org). I was unable to start any of my NetBSD guests running
fully virtualized (the PV hosts continue to run fine as before). The
problem is that the kernel somehow finds one (or in some instances,
two) non-existent disks:
wdc1 at isa0 port 0x170-0x177 ir1 6 drq 2
atabus1 at wdc1 channel 0
wd1 at atabus1 drive 0
wd1: 69632 KB, 1024 cyl, 8 head, 17 sec, 512 bytes/sec x 139264 sectors
wdc1: device timeout reading fsbn 0 (wd1 bn 0; cn 0 tn 0 sn 0), retrying
wdc1:0:0: lost interrupt
type ata tc_bcount: 512 tc_skip: 0
Last three lines repeat ad inf., kernel does not complete
initialization. Needless to say, there is no ST506 disk attached to
the VM at all.
This happens with all systems I tried (amd64 6.0, 6.1 and -current as
of a few days ago), even booting from an .iso file with no disk
attached (in this case it finds two of these).
As a data point, FreeBSD 8.2 fully virtualized continue to work as
before; OpenBSD 5.2 likewise (but the networking does not work as
always in this case), FreeBSD 9 also stopped working with endless
messages every 60 seconds as in:
run_interrupt_driven_hooks: still waiting after [n*60] seconds for
I guess I'll cross-post the same on the forums at xenserver.org.
I occasionally run fully virtualized NetBSD for installation testing;
the everyday VMs under XenServer are PV. The .xva file for 6.1 seems
to work just fine.
Main Index |
Thread Index |