qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: yhlu <yinghailu@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] win64
Date: Thu, 6 Jul 2006 08:50:46 -0700	[thread overview]
Message-ID: <2ea3fae10607060850n710b24c2y472e09ec01c1c8cd@mail.gmail.com> (raw)
In-Reply-To: <2ea3fae10606302115k2cd1ac0w6d9ef21a93e707a7@mail.gmail.com>

it works well with "-smp 1", but the "-smp 2" will have blue screen
when it try to get into gui installation window.

Also for 32 bit win, even "-smp 2", there will be only one cpu show up
on the guest win...

YH

On 6/30/06, yhlu <yinghailu@gmail.com> wrote:
> win64 as guest?
>
> YH
>
> On 6/26/06, ZIGLIO, Frediano, VF-IT <Frediano.Ziglio@vodafone.com> wrote:
> > I got windows xp 64 working using current CVS.
> > I still have problems with network, I had to use this patch
> >
> > Index: hw/rtl8139.c
> > ===================================================================
> > RCS file: /sources/qemu/qemu/hw/rtl8139.c,v
> > retrieving revision 1.1
> > diff -u -1 -0 -r1.1 rtl8139.c
> > --- hw/rtl8139.c        5 Feb 2006 04:14:41 -0000       1.1
> > +++ hw/rtl8139.c        26 Jun 2006 08:44:49 -0000
> > @@ -2826,21 +2826,21 @@
> >      d = (PCIRTL8139State *)pci_register_device(bus,
> >                                                "RTL8139",
> > sizeof(PCIRTL8139State),
> >                                                -1,
> >                                                NULL, NULL);
> >      pci_conf = d->dev.config;
> >      pci_conf[0x00] = 0xec; /* Realtek 8139 */
> >      pci_conf[0x01] = 0x10;
> >      pci_conf[0x02] = 0x39;
> >      pci_conf[0x03] = 0x81;
> >      pci_conf[0x04] = 0x05; /* command = I/O space, Bus Master */
> > -    pci_conf[0x08] = 0x20; /* 0x10 */ /* PCI revision ID; >=0x20 is for
> > 8139C+ */
> > +    pci_conf[0x08] = 0x10; /* 0x10 */ /* PCI revision ID; >=0x20 is for
> > 8139C+ */
> >      pci_conf[0x0a] = 0x00; /* ethernet network controller */
> >      pci_conf[0x0b] = 0x02;
> >      pci_conf[0x0e] = 0x00; /* header_type */
> >      pci_conf[0x3d] = 1;    /* interrupt pin 0 */
> >      pci_conf[0x34] = 0xdc;
> >
> >      s = &d->rtl8139;
> >
> >      /* I/O handler for memory-mapped I/O */
> >      s->rtl8139_mmio_io_addr =
> >
> > without it using rtl3139 card windows hangs (it don't have driver for
> > ne2000). Perhaps it would be helpful to add a rtl8139old card.
> > With patch all is working however saving state and restoring (after
> > quitting qemu) cause machine to hangs (mouse do not move, cursors do not
> > blink, remote desktop give timeout but I can see cpu activity with info
> > registers).
> >
> > bye
> >   Frediano Ziglio
> >
> >
> >
> > _______________________________________________
> > Qemu-devel mailing list
> > Qemu-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/qemu-devel
> >
>

  parent reply	other threads:[~2006-07-06 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AcaZADxJ2Tq4/qsJSOW00d5JjNi8kg==>
2006-06-26  9:09 ` [Qemu-devel] win64 ZIGLIO, Frediano, VF-IT
2006-06-26 19:57   ` Fabrice Bellard
2006-07-01  4:15   ` yhlu
2006-07-01 17:30     ` [Qemu-devel] Simulated devices of Qemu? Tieu Ma Dau
2006-07-06 15:50     ` yhlu [this message]
2006-06-27  8:21 [Qemu-devel] win64 ZIGLIO, Frediano, VF-IT

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=2ea3fae10607060850n710b24c2y472e09ec01c1c8cd@mail.gmail.com \
    --to=yinghailu@gmail.com \
    --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).