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

[Zhangzijian]

> -----Original Message-----
> From: Donald R Laster Jr [mailto:address@hidden
> Sent: Thursday, May 11, 2017 10:11 PM
> To: zhangzijian 10356 (Cloud); address@hidden
> Subject: Re: [Qemu-discuss] windows guest became unactivated when qemu
> upgrade
> 
> 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.

I modified the 'builtin_x86_defs' to keep the same with qemu-1.5. But it still 
need to register again.
Is there any other difference to CPU 'qemu64' between qemu-1.5.0 and qemu-2.1.2?

diff --git a/target-i386/cpu.c b/target-i386/cpu.c
index f9fcbca..8f77e19 100644
--- a/target-i386/cpu.c
+++ b/target-i386/cpu.c
@@ -656,7 +656,7 @@ static X86CPUDefinition builtin_x86_defs[] = {
         .level = 4,
         .vendor = CPUID_VENDOR_AMD,
         .family = 6,
-        .model = 6,
+        .model = 2,
         .stepping = 3,
         .features[FEAT_1_EDX] =
             PPRO_FEATURES |
@@ -2151,7 +2151,7 @@ void x86_cpudef_setup(void)
                 pstrcpy(def->model_id, sizeof(def->model_id),
                         "QEMU Virtual CPU version ");
                 pstrcat(def->model_id, sizeof(def->model_id),
-                        qemu_get_version());
+                        "1.5.0");
                 break;
             }
         }

> 
>    But I suspect to accomplish what you want you will have to re-register
> again.
> 
>     Don
> 
> 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
> file=/vms/images/windows2008-ent-4c-top,if=none,id=drive-virtio-disk0,format
> =qcow2,cache=directsync -device
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0
> ,bootindex=1 -netdev tap,id=hostnet0 -device
> rtl8139,netdev=hostnet0,id=net0,mac=0c:da:41:1d:eb:2d,bus=pci.0,addr=0x3
> -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
> virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,na
> me=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0 -vnc
> 0.0.0.0:15 -device VGA,id=video0,bus=pci.0,addr=0x2 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6
> >
> > 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!
> >