** Changed in: fedora
Status: Unknown => Won't Fix
** Changed in: fedora
Importance: Unknown => High
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/586175
Title:
Windows XP/2003 doesn't
** Changed in: qemu
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/586175
Title:
Windows XP/2003 doesn't boot
Status in QEMU:
Fix Released
Status in
virtio disk is entrely different story, unrelated to this issue.
** Changed in: qemu
Status: Incomplete = Fix Committed
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of qemu-
devel-ml, which is
In qemu-kvm-0.12.5-r1 Windows XP/2003 is booting fine on IDE, but it
hangs directly after the first reboot of the Windows setup if you try to
install it on a viostor drive. Windows Vista and higher never had any
problems in any version of qemu-kvm with any drive (IDE and viostor)...
I'm using the
This bug was fixed in the package qemu-kvm - 0.12.5+noroms-0ubuntu6
---
qemu-kvm (0.12.5+noroms-0ubuntu6) maverick; urgency=low
* debian/fix-CMOS-info-for-drives-defined-with--device.patch: make sure
the CMOS knows about the correct geometry so Windows XP installs
properly.
** Branch linked: lp:ubuntu/qemu-kvm
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Incomplete
Status in “qemu-kvm” package in Ubuntu: Fix Released
This bug is annoying. I don't know who patched what but:
1. I finally was able (with version 0.12.5) to set up a WinXP
installation which is able to boot on its own.
2. But this works only with IDE, if I try to use VirtIO I still can't
boot the installation.
3. I just updated from 0.12.5 to
P.S.: I just read the link posted by Michael.
I have also to mention that this boot problem not only appears by using
the -drive parameter, even the good old -hda got this bug.
I've also tried to correct some funny offsets in the NTFS header, but
all offsets were already set to the right values.
Does anyone else has similar problem? With 0.12.4 I were able to repeat
it. With 0.12.5 all winxp and win2003 installations, existing and new,
just work with either -drive or -hda or with virtio...
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug
This is fixed by a backport of the mentioned patchset to stable-0.12
branch, in qemu git tree, see
http://git.savannah.gnu.org/gitweb/?p=qemu.git;a=commit;h=6394bd0e05441c363ebb73597c74c951378810e6
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug
This appears to be fixed in 0.13-tobe by this patch:
http://lists.gnu.org/archive/html/qemu-devel/2010-07/msg00152.html
(hence it's fix released in debian which now has 0.13 in experimental).
** Bug watch added: Debian Bug tracker #588739
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588739
(and it is also filed agains debian qemu-kvm package, not just qemu --
http://bugs.debian.org/588739 )
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in
** Changed in: debian
Status: New = Fix Released
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Incomplete
Status in “qemu-kvm” package in
Great solution Andreas, it worked for a Win2k image which I could only
boot previously using an iso from http://www.resoo.org/docs/ntldr/files/
However, I have a w7 image that I have never managed to boot, apart from
its installation cd image using virt-install
20Gb w7 image:
# losetup
Hi Andy
When i look at your w7 partition table output, then there seems to be a
problem with start/end cylinders.
Your first partitions last cylinder is 13, but also the start cylinder
of your second partition is 13. two partitions should not share the same
cylinder/sector! Something seems to be
I had the same problem.
I.ve tried with VirtualBox and KVM: Win Xp SP3 hang on the same point (mup.sys
when safe mode)...
Both has the same problem I believe the libvirt maybe the cause.
So I use Raw Access with VirtualBox that solved my problem
00:00:01.385
Andreas,
The program that created the disk image seems confused, but it worked for
creating a VM for FC11.
Windows install seems to run fine, until wanting to boot from the drive it
created.
I don't know what creates the drive image and geometry, but it is broken.
I think this is what I used
I run into the same problem, but the workaround regarding editing the
number of heads in the ntfs partition boot sector did it for me. Little
Howto:
Asume: A raw complete harddisc image within a bootable NTFS partition
with XP or 2k3 on it
Incident: when using these image with kvm based qemu,
On Sun, Jul 25, 2010 at 08:15:24PM -, CurtisNelson wrote:
My next step at this point was to install hexedit and compare the two
resulting images. Specifically, the mbr at the beginning of the disk
and the ntfs partition starting at sector 63. On the net there is some
talk about changing
I'm getting the same error with restoring an Acronis based image to KVM
on Scientific Linux 5.4. The image is known good, and I just tested to
physical hardware and it boots fine. I hope this can be fixed...
How are people hex editing the disk?
--
Windows XP/2003 doesn't boot
I am struggling with the same problem with a WIndows 2003 install under
virt-manager/virsh The byte at 7e1c was already set to 3F. hexediting
the byte at offset 7e1a to FF allowed the system to boot OK.
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided = Medium
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Incomplete
Status in “qemu-kvm”
I have this problem as well. I'm installing using a slightly different
situation -- I'm restoring a WinXP/Win2k3 backup that was made with
fsarchiver -- but essentially I run across the same issue namely that
boot fails when mbr tries to boot the first partition. In my case I use
install-mbr
** Also affects: ubuntu
Importance: Undecided
Status: New
** Package changed: ubuntu = qemu-kvm (Ubuntu)
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
I'm not sure all experience the same as me, but it may be worth having a
look at the workaround I found, described here : http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=579166#17
Hth.
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification
I have to correct myself.
Booting from Windows XP/2003 after the first reboot of the Windows setup
is still impossible (without booting from the install CD at first).
I tried both the command line used by libvirt and the following one:
qemu-kvm -hda thisfile -cdrom thatfile -boot c
Also, I
I agree to #10. Today I installed qemu-kvm-0.12.4-r3 and I still can't
boot Windows XP/2003 without booting the install cd at first.
But now: After I tried to boot the Windows installation I get the same
odd char in the screen as described by #10. Plus, I can install Windows
without problems, but
P.S.: Of course I can't boot Windows XP/2003 from a VirtIO drive at all,
because the install cd only checks the IDE bus for an existing Windows
installation...
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of
Ran into this problem today with fresh Windows 2003 R2 install on a IDE
boot drive. Because the CD-ROM boot bypasses this problem the install
completes just fine, until I tell it to boot from the hard disk (via
libvirt).
Latest available packages from Debian testing;
qemu 0.12.4+dfsg-3
qemu-kvm
Long time no post, i tried to install Win2k3 through RIS/PXE this time.
I still get the same error at boot time: A disk read error occurred.
Press Ctrl + Alt + Del to restart.
Neither the Win2k3 install source nor the VirtIO drivers are defective.
Something's just wrong with QEMU.
Currently
I can reproduce with qemu-kvm 0.12.4 like the original reporter. I
cannot reproduce with qemu-kvm upstream, qemu stable, or qemu upstream.
So boot=on could be the culprit. Libvirt generated command line:
LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/bin
/qemu-system-x86_64
Cole Robinson crobi...@redhat.com writes:
I can reproduce with qemu-kvm 0.12.4 like the original reporter. I
cannot reproduce with qemu-kvm upstream, qemu stable, or qemu upstream.
So boot=on could be the culprit. Libvirt generated command line:
LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin
** Bug watch added: Debian Bug tracker #579166
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579166
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579166
Importance: Unknown
Status: Unknown
--
Windows XP/2003 doesn't boot
** Changed in: debian
Status: Unknown = New
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Incomplete
Status in Debian GNU/Linux: New
Status
On Sun, Jun 20, 2010 at 01:16:11PM -, Bug Watch Updater wrote:
** Changed in: debian
Status: Unknown = New
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed
Do you mean, I should try to install and boot Win2k3 without libvirt?
If I install Windows through libvirt and boot it with a simple command line like
qemu-kvm -hda /someimage.img -enable-kvm
it doesn't boot.
It's in fact this bug, just like Cole meant:
It sounds like this is an existing image that you can't boot from. I
can create a new 2k3 VM with upstream qemu and boot it again after
install with no issues. So I'm wondering if you can also do this. If
so, then something happened to your existing image (maybe some sort of
corruption of the
** Tags added: windows
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: New
Status in Fedora: Unknown
Bug description:
Hello everyone,
my qemu
Can someone post the exact qemu command line that gets generated so we
can test without libvirt?
** Changed in: qemu
Status: New = Incomplete
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of qemu-
There's a fedora rawhide bug about this as well:
https://bugzilla.redhat.com/show_bug.cgi?id=579348
Which points to a qemu-devel posting talking about disk geometry
confusion:
http://article.gmane.org/gmane.comp.emulators.qemu/66135
** Bug watch added: Red Hat Bugzilla #579348
Can someone try to reproduce this without ,boot=on?
It's possible that extboot is screwing up the disk geometry.
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=579348
Importance: Unknown
Status: Unknown
--
Windows XP/2003 doesn't boot
I don't have any problem using TCG.
Tested with Windows XP Home Update in 0.12.4 and Windows 2003 Enterprise
Server in 0.12.3.
--
Windows XP/2003 doesn't boot
https://bugs.launchpad.net/bugs/586175
You received this bug notification because you are a member of qemu-
devel-ml, which is
It's a very strange bug.
Starting qemu without boot=on results in the same dilemma.
But: I've used a .vdi image (because qcow2 is terribly slow).
Just now I tried a raw image. Now I can boot neither directly from the image
nor with the install cd. Both ways boot finally NTLDR, but now the
43 matches
Mail list logo
