[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] windows guest became unactivated when qemu upgrade

From: Donald R Laster Jr
Subject: Re: [Qemu-discuss] windows guest became unactivated when qemu upgrade
Date: Thu, 11 May 2017 10:11:06 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40

Richard Zhang,

  win2k8 might have detected that the "hardware" environment it is running 
under has changed.  When Microsoft Windows products execute the registration process they 
apparently lock themselves down to the hardware they are being executed upon.  So if the 
CPU information changed that would probably cause win2k8 to decided it is not registered 
for this system - or in this case this virtual machine environment.

  You could try to execute it under the 1.5.0 version of qemu and see if the 
win2k8 decides it is still registered.  But I suspect you would have to 
register it again.  If you have a full image backup you could try running it 
under the older QEMU, or the one with the modified 'builtin_x86_defs' that 
mirrors 1.5.0, and see if thinks it is or is not registered.

  But I suspect to accomplish what you want you will have to re-register again.


Zhangzijian wrote on 05/11/2017 05:00 AM:
Hi all
There is an issue about device difference between qemu versions.

A win2k8 guest running under qemu-1.5.0. After I upgraded qemu to qemu-2.1.2. 
The guest became unactivated. The guest is started with the same command line.
I noticed that CPU information defined in ‘builtin_x86_defs’ changed, so I 
modify source-code(qemu-2.1.2) and recompiled it. But I got the same result.

I just run guest with different qemu-system-x86_64, so the BIOS 
file(/usr/share/qemu/bios.bin) is the same.
So, is there any difference between qemu-1.5.0 and qemu-2.1.2, which would 
cause win2k8 became unactivated?

The guest command line:
qemu-2.1.2 -name windows2008-ent-4c -S -machine 
pc-i440fx-1.5,accel=kvm,usb=off,system=windows -cpu 
qemu64,hv_relaxed,hv_spinlocks=0x2000 -m 8192 -smp 
4,maxcpus=160,sockets=40,cores=4,threads=1 -uuid 
56c9ecc2-4c1d-4200-a02d-3217fb669492 -no-user-config -nodefaults -chardev 
stdio,id=charmonitor -mon chardev=charmonitor,id=monitor -rtc 
base=localtime,clock=vm,driftfix=slew -no-hpet -no-shutdown -device 
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device 
usb-ehci,id=ehci,bus=pci.0,addr=0x4 -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive 
 -netdev tap,id=hostnet0 -device 
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-chardev socket,id=charchannel0,path=/var/lib/l
ibvirt/qemu/windows2008-ent-4c.agent,server,nowait -device 
 -device usb-tablet,id=input0,bus=usb.0 -vnc -device 
VGA,id=video0,bus=pci.0,addr=0x2 -device 

Sincerely, Richard Zhang
This e-mail and its attachments contain confidential information from H3C, 
which is
intended only for the person or entity whose address is listed above. Any use 
of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender
by phone or email immediately and delete it!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]