From: John Arbuckle <programmingkidx@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1737194] Re: Windows NT 4.0 fails to boot from qcow2 installation
Date: Thu, 25 Jan 2018 16:43:41 -0000 [thread overview]
Message-ID: <5FD1490A-41F7-4200-AB5C-3802358E1362@gmail.com> (raw)
In-Reply-To: CAFEAcA9vJ7A+J2OSPNsfyT575p+heE5o_++T-Jtp6S3dyG3NTQ@mail.gmail.com
> On Jan 25, 2018, at 11:16 AM, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On 25 January 2018 at 15:58, John Arbuckle <programmingkidx@gmail.com> 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 qemu-io
>> Undefined symbols for architecture x86_64:
>> "_use_rt_clock", referenced from:
>> _bdrv_acct_start in block.o
>> _bdrv_acct_done in block.o
>> Undefined symbols for architecture x86_64:
>> _qemu_clock_get_ns in qemu-timer.o
>> "_use_rt_clock", referenced from:
>> _bdrv_acct_start in block.o
>> _bdrv_acct_done in block.o
>> _qemu_clock_get_ns in qemu-timer.o
>
> 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 same error? (We've had some issues in the past I think
> where configure put libraries on the main binary link line but
> not on the tools link lines, so maybe worth a try...)
>
> thanks
> -- PMM
>
It still fails to build:
Build commands: ./configure --disable-tools --target-list=i386-softmmu
&& make -j 4
QEMU at commit: 306ec6c3cece7004429c79c1ac93d49919f1f1cc
LINK i386-softmmu/qemu-system-i386
Undefined symbols for architecture x86_64:
"_use_rt_clock", referenced from:
_bdrv_acct_start in block.o
_bdrv_acct_done in block.o
_qemu_clock_get_ns in qemu-timer.o
_cpu_get_clock in cpus.o
_cpu_enable_ticks in cpus.o
_cpu_disable_ticks in cpus.o
_icount_warp_rt in cpus.o
...
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [qemu-system-i386] Error 1
make: *** [subdir-i386-softmmu] Error 2
--
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 4.0 fails to boot from qcow2 installation
Status in QEMU:
New
Bug description:
Windows NT 4.0 will not boot from an installation more than once if
installed in a qcow2 image file. A quick fix to this problem is to use
the qcow format instead.
Steps to reproduce this issue:
Create the image file:
qemu-img create -f qcow2 winnt4.qcow2 1G
Boot from a Windows NT 4.0 Workstation CD:
qemu-system-i386 -hda winnt4.qcow2 -cdrom /dev/cdrom -boot d -m 128 -cpu pentium -vga cirrus
During the installation process you have the choise between FAT and
NTFS. You can pick anyone.
After finishing the installation the guest will reboot to install
additional items. Once this is done the guest will be bootable. Eject
any CD media from QEMU and reboot. You will then see Windows NT 4.0
booting up to the desktop. Go to "Start->Shut down" to shut down. Then
when Windows is ready quit QEMU.
Now try to boot using this command:
qemu-system-i386 -hda winnt4.qcow2 -boot c -m 128 -cpu pentium -vga cirrus
The BIOS screen will display an error message:
For NTFS:
Booting from Hard Disk...
A disk read error occurred.
Insert a system diskette and restart
the system.
For FAT:
No bootable device.
Additional information:
qemu-system-i386 version: 2.10.1
qemu-img version: 2.10.92 (v2.11.0-rc4-dirty)
If you don't have a Windows NT 4.0 Workstation installation CD, you may download one from here:
https://winworldpc.com/product/windows-nt-40/40
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1737194/+subscriptions
next prev parent reply other threads:[~2018-01-25 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 15:35 [Qemu-devel] [Bug 1737194] [NEW] Windows NT 4.0 fails to boot from qcow2 installation John Arbuckle
2017-12-08 18:41 ` [Qemu-devel] [Bug 1737194] " John Snow
2017-12-08 20:21 ` John Arbuckle
2018-01-25 7:53 ` i336_
2018-01-25 15:58 ` John Arbuckle
2018-01-25 16:16 ` Peter Maydell
2018-01-25 16:43 ` John Arbuckle [this message]
2018-01-25 17:07 ` Peter Maydell
2018-01-25 16:37 ` John Arbuckle
2018-01-26 14:51 ` David Lindsay
2018-01-26 17:03 ` John Arbuckle
2018-01-27 0:39 ` [Qemu-devel] [Bug 1737194] " John Arbuckle
2020-11-16 18:13 ` [Bug 1737194] " Thomas Huth
2021-01-16 4:17 ` Launchpad Bug Tracker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5FD1490A-41F7-4200-AB5C-3802358E1362@gmail.com \
--to=programmingkidx@gmail.com \
--cc=1737194@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).