Control: severity -1 normal
Forgot to mention, this issue isn't that important anymore apparently,
lovering severity to normal... :)
(And removing "Bulk" from the subject, too ;)
Thanks,
/mjt
Hello.
I'm rehashing older bugreports now, and this one is from 2012.
Do you still have problems described in there?
I still don't have any AMD system around, but reportedly
qemu/kvm works on these just fine nowadays (and worked
before bulldozer too).
Thanks,
/mjt
On 06/07/12 04:49 AM, Michael Tokarev wrote:
On 06.07.2012 01:46, Gary Dale wrote:
That's got some things working. The virtual machine I had previously started
installing XP64 on has completed the install (after picking up where it
previously hung) and is now installing SP2.
However, another n
On 06.07.2012 01:46, Gary Dale wrote:
> That's got some things working. The virtual machine I had previously started
> installing XP64 on has completed the install (after picking up where it
> previously hung) and is now installing SP2.
> However, another new VM I tried creating (with XP64) usin
On 05/07/12 03:07 PM, Michael Tokarev wrote:
On 05.07.2012 21:36, Gary Dale wrote:
I'm getting an error when I try to create a new virtual machine using the
command string you suggested earlier (
kvm -cdrom WindowsXPPro64.iso -drive file=ghostwheel.img,cache=unsafe -m 1G
-cpu qemu64).
kvm
On 05.07.2012 21:36, Gary Dale wrote:
> I'm getting an error when I try to create a new virtual machine using the
> command string you suggested earlier (
>
> kvm -cdrom WindowsXPPro64.iso -drive file=ghostwheel.img,cache=unsafe -m 1G
> -cpu qemu64).
>
>
> kvm: symbol lookup error: kvm: undef
On 03/07/12 10:36 AM, Michael Tokarev wrote:
15.06.2012 18:58, Gary Dale wrote:
[]
OK, so the Windows install is still hanging. This time it stopped when looking
for devices. That's a little further than it got when I used virt-manager to
install over the existing image.
Since this is a brand
15.06.2012 18:58, Gary Dale wrote:
[]
> OK, so the Windows install is still hanging. This time it stopped when
> looking for devices. That's a little further than it got when I used
> virt-manager to install over the existing image.
>
> Since this is a brand new image file, it suggests that ther
After further experimenting, I note that kvm run from the command line
allows for -cpu phenom, while virt-manager doesn't.
Nonetheless, I'm getting the Windows XP install hanging very early in
the process, just after copying the files and rebooting into a graphical
environment. It does this mo
On 15/06/12 01:41 AM, Michael Tokarev wrote:
On 15.06.2012 02:11, Gary Dale wrote:
[]
It doesn't open an X window. It complains about:
No protocol specified
Could not initialize SDL(No available video device) - exiting
Now I seem to have SDL installed. However, searching through the kvm
docum
On 15/06/12 01:41 AM, Michael Tokarev wrote:
On 15.06.2012 02:11, Gary Dale wrote:
[]
It doesn't open an X window. It complains about:
No protocol specified
Could not initialize SDL(No available video device) - exiting
Now I seem to have SDL installed. However, searching through the kvm
docum
On 15.06.2012 02:11, Gary Dale wrote:
[]
> It doesn't open an X window. It complains about:
>
> No protocol specified
> Could not initialize SDL(No available video device) - exiting
>
> Now I seem to have SDL installed. However, searching through the kvm
> documentation to find information about
On 14/06/12 06:00 PM, Michael Tokarev wrote:
On 15.06.2012 01:46, Gary Dale wrote:
On 14/06/12 04:26 PM, Michael Tokarev wrote:
kvm -cdrom WindowsXPPro64.iso -drive file=ghostwheel.img,cache=unsafe -m 1G
-cpu qemu64
I get an error about SDL:
I told you it will open an X window. Give it a $D
On 14/06/12 06:00 PM, Michael Tokarev wrote:
On 15.06.2012 01:46, Gary Dale wrote:
On 14/06/12 04:26 PM, Michael Tokarev wrote:
kvm -cdrom WindowsXPPro64.iso -drive file=ghostwheel.img,cache=unsafe -m 1G
-cpu qemu64
I get an error about SDL:
I told you it will open an X window. Give it a $D
On 15.06.2012 01:46, Gary Dale wrote:
> On 14/06/12 04:26 PM, Michael Tokarev wrote:
>> kvm -cdrom WindowsXPPro64.iso -drive file=ghostwheel.img,cache=unsafe -m 1G
>> -cpu qemu64
> I get an error about SDL:
I told you it will open an X window. Give it a $DISPLAY.
/mjt
--
To UNSUBSCRIBE, ema
On 14/06/12 04:26 PM, Michael Tokarev wrote:
kvm -cdrom WindowsXPPro64.iso -drive file=ghostwheel.img,cache=unsafe -m 1G
-cpu qemu64
I get an error about SDL:
No protocol specified
Could not initialize SDL(No available video device) - exiting
Changing the display to vnc:5900 leaves me wonderi
On 14/06/12 04:26 PM, Michael Tokarev wrote:
On 15.06.2012 00:10, Gary Dale wrote:
I finally bit the bullet to try a fresh install from the command line. After
much gnashing of teeth, the command line I came up with is:
virt-install -n ghostwheel --cpu kvm64 -c
"/home/garydale/Downloads/Windo
On 15.06.2012 00:10, Gary Dale wrote:
> I finally bit the bullet to try a fresh install from the command line. After
> much gnashing of teeth, the command line I came up with is:
>
> virt-install -n ghostwheel --cpu kvm64 -c
> "/home/garydale/Downloads/WindowsXPPro64.iso" --os-variant=winxp64 --
I finally bit the bullet to try a fresh install from the command line.
After much gnashing of teeth, the command line I came up with is:
virt-install -n ghostwheel --cpu kvm64 -c
"/home/garydale/Downloads/WindowsXPPro64.iso" --os-variant=winxp64
--disk path=/var/lib/libvirt/images/ghostwheel.i
I just tried repairing the install, which didn't work. Neither did
overwriting the install with a fresh one. Is there something in the img
file that remembers what it was created on? Otherwise I'm at a loss to
explain why I can't get Windows XP to run.
BTW: I also tried to create a fresh virtu
OK, the img that worked on my Phenom II system using qemu64 as the CPU
doesn't work on my Bulldozer system using the same CPU setting. That
would suggest that qemu64 doesn't do a complete emulation. I'm getting
something carried over from the host CPU.
-
I've tried running it
I've tried running it with various cpu models. Using virt-manager, I get
the option to "Copy host CPU configuration", which worked about as well
as kvm64, Opteron_G4 and qemu64 (i.e. didn't work - still hangs or blue
screens). Choosing Phenom gives me a start-up message that guest CPU is
not co
On 11.06.2012 03:44, Gary Dale wrote:
[]
> Here's the qemu/ghoswheel64.log entries for the startup of the local copy:
>
> 2012-06-10 23:38:23.205+: starting up
> LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
> HOME=/ QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-1.0 -
On 10/06/12 06:28 PM, Michael Tokarev wrote:
On 11.06.2012 00:15, Gary Dale wrote:
How do I get a command line from virt-mgr?
It should be available in the log, and shown by ps.
Secondly, whether or not I can create a new virtual machine is a different
issue. I shouldn't have to create new v
On 11.06.2012 00:15, Gary Dale wrote:
> How do I get a command line from virt-mgr?
It should be available in the log, and shown by ps.
> Secondly, whether or not I can create a new virtual machine is a different
> issue. I shouldn't have to create new virtual machines every time I upgrade
> my
On 10/06/12 03:43 PM, Michael Tokarev wrote:
On 10.06.2012 23:12, Gary Dale wrote:
On 10/06/12 02:31 PM, Michael Tokarev wrote:
[]
So I need a way to reproduce this issue somehow. At least, full command line
you use to start it.
They're started with virt-mgr (see attached xml files).
Please
On 10.06.2012 23:12, Gary Dale wrote:
> On 10/06/12 02:31 PM, Michael Tokarev wrote:
[]
>> So I need a way to reproduce this issue somehow. At least, full command line
>> you use to start it.
> They're started with virt-mgr (see attached xml files).
Please read again what I asked for. Qemu-kvm
On 10/06/12 02:31 PM, Michael Tokarev wrote:
tags 676950 + unreproducible moreinfo
thanks
On 10.06.2012 22:01, Gary Dale wrote:
Package: qemu-kvm
Version: 1.0+dfsg-11
Severity: important
Dear Maintainer,
* What led up to the situation?
I have two working Windows XP/Pro VMs, one 32bit and o
tags 676950 + unreproducible moreinfo
thanks
On 10.06.2012 22:01, Gary Dale wrote:
> Package: qemu-kvm
> Version: 1.0+dfsg-11
> Severity: important
>
> Dear Maintainer,
>* What led up to the situation?
> I have two working Windows XP/Pro VMs, one 32bit and one 64bit, that run fine
> on my ol
Package: qemu-kvm
Version: 1.0+dfsg-11
Severity: important
Dear Maintainer,
* What led up to the situation?
I have two working Windows XP/Pro VMs, one 32bit and one 64bit, that run
fine on my older
Phenom II based machine. However, they run into all kinds of errors when
I copy the img files
30 matches
Mail list logo
