I revoke my previous comments. Meanwhile it turned out that the server I
was testing with had HW problems (namely it couldn't handle 6x2GB RAM
despite of the motherboard docs claiming it would). So my error reports
are unreliable ... they might have been caused by HW issues.
--
Cannot start exist
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
I can confirm the bug for 9.10. I'm using kvm/libvirt and a flat image.
Windows XP SP2 initially works, however after applying all
updates/patches i sometimes get "STOP: c221 unknown Hard error
\SystemRoot\System32\ntdll.dll" when booting. After doing a chkdsk /p in
the recorvery console (which
Unfortunately my qcow2 corruptions were not related to VM crashes. :-(
I've now experienced them without having the any of the VMs crashed, ie.
during normal use. Bug#404394 seems to be related to this so I'll take
the problem there.
--
Cannot start existing VM after upgrade to 9.10 beta
https://
I can confirm that my images (both in RAW format and the ones stored in
LVM volumes) stopped working with the KVM in Ubuntu 9.10 (Karmic).
Converting to qcow2 format allowed me to boot and use these images.
However recently I've experienced filesystem corruption in some of the
qcow2 images. :-o I'
Thanks Hedgehog_57!
I can confirm that after the conversions my images also start working
again.
--
Cannot start existing VM after upgrade to 9.10 beta
https://bugs.launchpad.net/bugs/448694
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Some news.
I have WinXP wich can't boot even in safe mode. Disks was in RAW format.
I've converted then in qcow2 format. I'm lucky! WinXP boot now without
problems. All content is intact. Nothing is lost.
Command:
kvm-img convert -O qcow2 /opt/vmf/winxp.img /opt/vmf/winxp.qcow2
--
Cannot star
I have now installed ubuntu-virt-mgmt and ubuntu-virt-server on amd64
Karmic USB-Stick, and successfully installed Karmic inside a new vm. So
the issue seems to be specific to my setup.
I'll now try to find a spare USB-Disk and
- install a Jaunty,
- update all packages,
- install Jaunty into a
On the initial reboot of a Jaunty installation I get:
run-init: /sbin/init: Exec format error
[ 11.564899] Kernel panic - not syncing: Attempted to kill init!
It seems my installation if KVM/virt-manager seems to be unusable...
Let me know if there is any configurations I should check that ma
I have just tried installing Karmic within a vm again:
Installation passed without errors.
After reboot update manager proposed many updates which a accepted.
Installing the updates iget the following error message:
E: /var/cache/apt/archives/libpython2.6_2.6.4-0ubuntu2_i386.deb: Unterprozess
dp
I have also upgraded from 9.04 to 9.10. Some of my images were created
on 8.04 and upgraded to 9.04 previously. Some are raw disk images
obtained by dd from real disks... yet all seem to have issues.
I currently cannot run any image reliably. (Hang on boot of Jaunty,
segfault on login in etch, c
Based on the traceback from virt-manager, it seems you are trying to
restore from a saved state file.
Is that accurate?
--
Cannot start existing VM after upgrade to 9.10 beta
https://bugs.launchpad.net/bugs/448694
You received this bug notification because you are a member of Ubuntu
Bugs, which
I've the same problem. I've reinstalled Windows XP in Ubuntu 9.10 kvm
using a raw disk image and gets corrupted quickly and Windows doesn't
boot after three or four reboots (installing windows updates).
Now I have installed Windows XP using a qcow2 disk image and it's
working properly. So it's see
I can confirm the initial problem reported in this bug:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/manager.py", line 426, in
restore_saved_callback
self.current_connection().restore(file_to_load)
File "/usr/share/virt-manager/virtManager/connection.py", li
Thierry,
My VM disk with WinXP is still here. I can try to provide You with
information You need to fix this issue. I really need to get this VM
working without reinstalling it.
For now i cannot boot tis VM even in Safe mode without network.
You are not really right about license situation. If Y
Thierry,
I agree that from my initial submission it is a bit confusing. When I
upgraded to 9.04 I switched from calling KVM from terminal to the
virtual manager. The error after upgrading to 9.10 was what appeared in
virtual manager. In trying to get the VM working, I reverted back to
starting it
You submitted multiple different issues, which makes this bug a little
confusing.
The heart of it seems to be:
- You had a Windows XP VM working alright under KVM/libvirt/virt-manager in 9.04
- You upgrade to 9.10
- Trying to run this image under KVM 9.10 gives you a BSOD with STOP: c221
unkn
Good bye KVM (unistalled) and Hello VirtualBox.
--
Cannot start existing VM after upgrade to 9.10 beta
https://bugs.launchpad.net/bugs/448694
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.
I'm now using virtualbox for virtualisation, which works (after
disabling the kvm_intel module). And virtualbox uses another disk image
format, indeed.
--
Cannot start existing VM after upgrade to 9.10 beta
https://bugs.launchpad.net/bugs/448694
You received this bug notification because you are
The disk image gets corrupted. Using qcow2 format, the corruption
doesn't happen (or is less frequent).
Best regards.
On Tue, Nov 10, 2009 at 12:34 PM, Johan Vervloet
wrote:
> "Safe mode" works, "Safe mode with networking" doesn't.
>
> The problem does not occur for unpatched Win XP SP 2 or unpat
"Safe mode" works, "Safe mode with networking" doesn't.
The problem does not occur for unpatched Win XP SP 2 or unpatched Win
2000. It only appears after updating the system.
--
Cannot start existing VM after upgrade to 9.10 beta
https://bugs.launchpad.net/bugs/448694
You received this bug noti
Does anybody have a solution?
--
Cannot start existing VM after upgrade to 9.10 beta
https://bugs.launchpad.net/bugs/448694
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
https:/
Yes, mine will start in "safe mode" also.
--
Cannot start existing VM after upgrade to 9.10 beta
https://bugs.launchpad.net/bugs/448694
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
Same problem in the release of 9.10.
Have upgraded from 9.04 to 9.10. Now my VM with winxp stop with BSOD
like
STOP: c221 unknown Hard error
\SystemRoot\System32\ntdll.dll
Can start it in "safe mode". Last run under 9.04 was correct.
--
Cannot start existing VM after upgrade to 9.10 beta
h
Looks like VM image became corrupted during upgrade. Windows error when
running VM from terminal:
kvm vm8.img
STOP: c221 unknown Hard error
\SystemRoot\System32\ntdll.dll
--
Cannot start existing VM after upgrade to 9.10 beta
https://bugs.launchpad.net/bugs/448694
You received this bug noti
Also found KVM un-installed after upgrade. Installed and tried to run
existing image from terminal and it started to boot XP, but died with
blue screen of death.
--
Cannot start existing VM after upgrade to 9.10 beta
https://bugs.launchpad.net/bugs/448694
You received this bug notification becaus
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33446551/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/33446552/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/33446553/ProcStatus.txt
** Attachm
27 matches
Mail list logo