On Thu, Jul 19, 2018 at 10:58:08AM -0400, Thor Lancelot Simon wrote:
> It *may* also avoid a bluescreen at boot due to incompatibility of the
> drivers for the previous platform's emulated hardware with the Xen
> platform's emulated hardware. It's worth a shot.
Thanks. Also saw an article with
On Thu, Jul 19, 2018 at 04:43:17PM +0200, Manuel Bouyer wrote:
> On Thu, Jul 19, 2018 at 07:50:06PM +0530, Mayuresh wrote:
> > On Thu, Jul 19, 2018 at 10:20:00AM +0300, pierre-philipp braun wrote:
> > > 2. try to install the GPLPV drivers before the conversion --
> > >
On Thu, Jul 19, 2018 at 07:50:06PM +0530, Mayuresh wrote:
> On Thu, Jul 19, 2018 at 10:20:00AM +0300, pierre-philipp braun wrote:
> > 2. try to install the GPLPV drivers before the conversion --
> > https://wiki.xen.org/wiki/Xen_Windows_GplPv
>
> A tiny doubt: Does winxp run paravritualized? I
On Thu, Jul 19, 2018 at 12:03:29PM +0200, Frank Wille wrote:
> ...and two 550 GB SAS RAID-1 disks, configured via the BIOS and appearing
> as a single SCSI disk:
> ciss0 at pci7 dev 0 function 0: HP Smart Array 3
> ciss0: interrupting at ioapic0 pin 16
> ciss0: 1 LD, HW rev 3, FW 5.20/5.20, 64bit
On Thu, Jul 19, 2018 at 10:20:00AM +0300, pierre-philipp braun wrote:
> 2. try to install the GPLPV drivers before the conversion --
> https://wiki.xen.org/wiki/Xen_Windows_GplPv
A tiny doubt: Does winxp run paravritualized? I thought it's hvm so PV
drivers shouldn't be needed. No?
Mayuresh
On Thu, Jul 19, 2018 at 10:20:00AM +0300, pierre-philipp braun wrote:
> If it is really a virtual disk conversion problem, Mayuresh, I would try
> to convert it with VBoxManage instead of qemu-img, or the other way
> around. Both support RAW, QCOW2 and VDI. Depending on the conversions,
> the
Hi,
I'm currently setting up a HP ProLiant DL360 G5 with NetBSD/amd64 8.0RC2.
It has 16GB RAM...
NetBSD 8.0_RC2 (GENERIC) #0: Tue Jul 3 07:13:41 UTC 2018
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
total memory = 16381 MB
avail memory = 15883 MB
...Xeon 5160 3GHz
>> Cons 2: Converting the VirtualBox vdi disk to "raw" and using it as DomU
>> disk hasn't worked. It just leads to "blue screen of death". (A fresh
>> installation of WinXP works, but my constraint is to carry the node locked
>> software as explained above.)
>>
>
> This *may* be just a simple
