[Bug 1737194] Re: Windows NT 4.0 fails to boot from qcow2 installation

[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1737194 Title: Windows NT

[Bug 1737194] Re: Windows NT 4.0 fails to boot from qcow2 installation

The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now. If you still think this bug report here is valid, then please switch

Re: [Qemu-devel] [Bug 1737194] Re: Windows NT 4.0 fails to boot from qcow2 installation

> On Jan 26, 2018, at 9:51 AM, David Lindsay wrote: > > Hi John & others: > > (3 separate things.) > > 1: Image formats > > Regarding qcow, unfortunately there is no change if I use this format. > > - Windows 3.1 initially hung at "Starting MS-DOS..."; upon restart it >

[Qemu-devel] [Bug 1737194] Re: Windows NT 4.0 fails to boot from qcow2 installation

Hi John & others: (3 separate things.) 1: Image formats Regarding qcow, unfortunately there is no change if I use this format. - Windows 3.1 initially hung at "Starting MS-DOS..."; upon restart it crashed when it decided it couldn't find COMMAND.COM (a frequent failure mode I forgot to

Re: [Qemu-devel] [Bug 1737194] Re: Windows NT 4.0 fails to boot from qcow2 installation

On 25 January 2018 at 16:43, John Arbuckle wrote: >> On Jan 25, 2018, at 11:16 AM, Peter Maydell wrote: >> If you configure with --disable-tools does it manage to build, >> or does it just go on to fail to link the main QEMU binary >> with the

Re: [Qemu-devel] [Bug 1737194] Re: Windows NT 4.0 fails to boot from qcow2 installation

> On Jan 25, 2018, at 11:16 AM, Peter Maydell wrote: > > On 25 January 2018 at 15:58, John Arbuckle wrote: >> I did try to build at commits 306ec6c3cece7004429c79c1ac93d49919f1f1cc >> and e689f7c668cbd9d08f330e17c3dd3a059c9553d3. Both failed

Re: [Qemu-devel] [Bug 1737194] Re: Windows NT 4.0 fails to boot from qcow2 installation

> # WinNT 4 Terminal Server > > Most of the time, NTLDR will fire up normally. But every so often... > > SeaBIOS (version > rel-1.7.3-117-g31b8b4e-20131206_080705-nilsson.home.kraxel.org) > > Booting from Hard Disk... > A disk read error occurred. > Insert a system diskette and restart

Re: [Qemu-devel] [Bug 1737194] Re: Windows NT 4.0 fails to boot from qcow2 installation

On 25 January 2018 at 15:58, John Arbuckle wrote: > I did try to build at commits 306ec6c3cece7004429c79c1ac93d49919f1f1cc > and e689f7c668cbd9d08f330e17c3dd3a059c9553d3. Both failed to build on my > Mac OS X system. Here is the error message I usually saw: > > LINK

Re: [Qemu-devel] [Bug 1737194] Re: Windows NT 4.0 fails to boot from qcow2 installation

> On Jan 25, 2018, at 2:53 AM, i336_ wrote: > > Hi, > > I've been experiencing various disk I/O issues with Windows NT too, as > well as with Windows 3.1. I think `-M isapc` may be to blame somehow. > > I've documented my experiences over at >

[Qemu-devel] [Bug 1737194] Re: Windows NT 4.0 fails to boot from qcow2 installation

Hi, I've been experiencing various disk I/O issues with Windows NT too, as well as with Windows 3.1. I think `-M isapc` may be to blame somehow. I've documented my experiences over at https://bugs.launchpad.net/qemu/+bug/1745312. That report contains information on how to lift out and build the

Re: [Qemu-devel] [Bug 1737194] Re: Windows NT 4.0 fails to boot from qcow2 installation

> On Dec 8, 2017, at 1:41 PM, John Snow <1737...@bugs.launchpad.net> wrote: > > If you do two identical installs with qcow2 and raw, do you see any > differences with qemu-img compare afterwards that might indicate what > could possibly have gone wrong? I think what you want is for me to compare

[Qemu-devel] [Bug 1737194] Re: Windows NT 4.0 fails to boot from qcow2 installation

If you do two identical installs with qcow2 and raw, do you see any differences with qemu-img compare afterwards that might indicate what could possibly have gone wrong? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.