** Changed in: qemu (Ubuntu)
Status: Incomplete = Won't Fix
** Changed in: qemu (Ubuntu Hardy)
Status: Incomplete = Won't Fix
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You received this bug notification because you are a member of Ubuntu
As the last year and a half has clearly demonstrated, I don't have time
to work on this bug.
If anyone has the time to find the appropriate fix and drive the SRU
process for it, I'd be happy to do the sponsoring. Feel free to e-mail
me or ping me on IRC if you're up for it!
** Changed in: qemu
but still a bug?
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Yes, the bug still exists. The image created by version 0.8 of qemu
can't be used with version 0.9.
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The software I needed in Windows NT now runs nicely with Wine. Also
making a fresh WinNT install in the lates QEmu works fine. In other
words, this bug is no longer important for me.
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You received this bug
I tested the image in Ubuntu 8.04 snapshot with QEmu version
0.9.0+20070816-1ubuntu3 and bochsbios-qemu version 2.3.5-1ubuntu1. QEmu
displays the same error message as cited in beginning of this bug
report. The image works fine with Ubuntu 7.04 version of qemu.
--
qemu fails to boot a disk image
My problem (zenwalk 5.0 would boot with kvm but not qemu) was fixed by
installing bochsbios-qemu 2.3.5-1ubuntu1 as referenced at Bug #123185
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You received this bug notification because you are a member of Ubuntu
This bug was nominated for Gutsy but does currently not qualify for a
7.10 stable release update (SRU) and the nomination is therefore
declined. According the the SRU policy, the fix should already be
deployed and tested in the current development version before an update
to the stable releases
*** This bug is a duplicate of bug 123185 ***
https://bugs.launchpad.net/bugs/123185
Installing bochsbios_2.3+20070705-2ubuntu1_all.deb didn't solve my
problem described in the beginning of this page.
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You
Darn. I removed the duplicate status.
** This bug is no longer a duplicate of bug 123185
qemu completely broken with current version of bochbios
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 123185 ***
https://bugs.launchpad.net/bugs/123185
Great! Given this, I've now tagged this bug as a duplicate.
** This bug has been marked a duplicate of bug 123185
qemu completely broken with current version of bochbios
--
qemu fails to boot a disk
Indeed switching to hardy bochsbios fixed the problem for me. I'm now using
gutsy qemu and hardy bochsbios. I installed bochsbios using:
sudo wget
http://archive.ubuntu.com/ubuntu/pool/universe/b/bochs/bochsbios_2.3+20070705-2ubuntu1_all.deb
sudo dpkg -i bochsbios_2.3+20070705-2ubuntu1_all.deb
This might be a duplicate of bug #123185. Try if the hardy packages of
qemu and bochsbios-qemu work.
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Rui, does your network work on gutsy with feisty qemu packages? When I
tried it did not work. What is the command line you are using to run it
please.
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You received this bug notification because you are a member
TAP networking is working for me using the feisty packages on gutsy.
qemu -hda /media/qemu/WindowsMC/WindowsMC.qcow -boot c -net nic -net
tap,ifname=tap1 -m 256 -localtime
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You received this bug notification
Same as Tim here.
One of the VM I created in Feisty, a gutsy install, stopped booting
while finding the network interface when I booted after I upgraded the
host to Gutsy. I've tried the recovery mode on the guest, but it stopped
on the same place (while finding network interface). Then I trashed
a guy from #qemu on irc.freenode says that it's a bug from libata that
is fixed in earlier cvs.
I am starting to question the efficiency of Ubuntu releases.
This mean the maintainer of the package didn't even ran Qemu at all, because
nothing works if uses ide, so well nothing at all in fact ...
Same here, I'm getting the same problem - it drops to an initramfs
prompt when booting a 7.10 Desktop image.
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
I tried downgrading to feisty's qemu-0.8.2. It will boot and load
[k,x]ubuntu, but for some reason my network does not work. It used to
work under feisty. So, I tried qemu 0.9.0+20070816 from
packages.debian.org, but it will drops to the initramfs prompt also,
just like gutsy's qemu.
Now I
I have the same problem with qemu on gutsy. It drops to an initramfs
prompt when I try to boot any *buntu 7.10 image.
Anyone know a work around?
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You received this bug notification because you are a member of
Same problem here. I have a WinXP installation in QEMU that ran
perfectly under feisty. After upgrading to Gutsy, it hangs during boot.
I inserted the WinXP install CD and booted from it. It starts loading
installation files off the CD and then BSOD (page fault).
I reverted QEMU back to 0.8, but
Forgot to add: I'm running QEMU 0.9 + kernel 2.6.22 on my other PC
(which is Gentoo) and it has no problem with running the WinXP QEMU
session. So it seems it is something with Gutsy itself, not kernel or
QEMU 0.9 related.
--
qemu fails to boot a disk image in gutsy
There is another bug (also not yet resolved) which might be related:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/154960
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I just want to add that I've got the exact same problem as Alan Pope.
Under Feisty qemu worked fine but under gutsy I get dropped to an
initramfs prompt (the image is Ubuntu 7.04 server). It's as if qemu
can't see the filesystem in the image.
Here's a simple version of the command that I use to
On Tue, Oct 16, 2007 at 10:34:01AM -, Alan Pope wrote:
This also happens when booting linux images under qemu 0.9.0 under
gutsy. They drop to an initramfs prompt after failing to find the root
fs. The same image works if you manually install qemu 0.8.2 from feisty
What type and size of
$ qemu-img info qemu-winnt.img
image: qemu-winnt.img
file format: raw
virtual size: 1.0G (1073741824 bytes)
disk size: 1.0G
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
This also happens when booting linux images under qemu 0.9.0 under
gutsy. They drop to an initramfs prompt after failing to find the root
fs. The same image works if you manually install qemu 0.8.2 from feisty
** Changed in: qemu (Ubuntu)
Status: New = Confirmed
--
qemu fails to boot a
After copying the image to a feisty installation and running it in qemu
it seems to run very well. In other words this excludes the possibility
of a corrupted image.
--
qemu fails to boot a disk image in gutsy
https://bugs.launchpad.net/bugs/144368
You received this bug notification because you
28 matches
Mail list logo
