thr3ads.net - libvirt users - [libvirt-users] virt-p2v - Windows 10 guest hangs at boot after successful P2V [Jan 2017]

If this information is useful, please help other people find it:
Share via:

JT Edwards

2017-Jan-09 15:17 UTC

[libvirt-users] virt-p2v - Windows 10 guest hangs at boot after successful P2V

Hi all,

I successfully virt-p2v'ed a Windows 10 laptop to my Centos 7.3 instance
running KVM. However, on boot, the guest hangs. Is there a registry fix
that is needed after the P2V is done? Here is what is in the guest's
logfile:
017-01-08 03:20:37.508+0000: starting up libvirt version: 2.0.0, package:
10.el7_3.2 (CentOS BuildSystem <http://bugs.centos.org>,
2016-12-06-19:53:38, c1bm.rdu2.centos.org), qemu version: 1.5.3
(qemu-kvm-1.5.3-126.el7), hostname: torden40.me.org
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name win10 -S -machine
pc-i440fx-rhel7.0.0,accel=kvm,usb=off -cpu
Conroe,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 4096 -realtime
mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid
f72e7ad5-98d4-44ab-aa85-347fe232b4e5 -no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-9-win10/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc
base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard
-no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global
PIIX4_PM.disable_s4=1 -boot strict=on -device
ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device
ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive
file=/home/tstrike39/Virtuals/tordenmobile.img,format=qcow2,if=none,id=drive-ide0-0-0
-device
ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1
-netdev tap,fd=26,id=hostnet0 -device
rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:d6:c8:67,bus=pci.0,addr=0x3
-chardev pty,id=charserial0 -device
isa-serial,chardev=charserial0,id=serial0 -chardev
spicevmc,id=charchannel0,name=vdagent -device
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0
-device usb-tablet,id=input0,bus=usb.0,port=1 -spice
port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on
-vga qxl -global qxl-vga.ram_size=67108864 -global
qxl-vga.vram_size=67108864 -global qxl-vga.vgamem_mb=16 -device
intel-hda,id=sound0,bus=pci.0,addr=0x4 -device
hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev
spicevmc,id=charredir0,name=usbredir -device
usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev
spicevmc,id=charredir1,name=usbredir -device
usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on
char device redirected to /dev/pts/2 (label charserial0)
main_channel_link: add main channel client
main_channel_handle_parsed: net test: latency 0.140000 ms, bitrate
14222222222 bps (13563.368055 Mbps)
((null):19947): Spice-Warning **:
red_channel.c:542:red_channel_client_send_ping: getsockopt failed,
Operation not supported
red_dispatcher_set_cursor_peer:
inputs_connect: inputs channel client create
((null):19947): Spice-Warning **:
red_channel.c:542:red_channel_client_send_ping: getsockopt failed,
Operation not supported
((null):19947): Spice-Warning **:
red_channel.c:542:red_channel_client_send_ping: getsockopt failed,
Operation not supported



Below is the XML of my migrated instance:

<?xml version='1.0' encoding='utf-8'?>
<domain type='kvm'>
  <!-- generated by virt-v2v 1.32.7rhel=7,release=3.el7.centos,libvirt -->
  <name>localhost</name>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <vcpu>2</vcpu>
  <os>
    <type arch='x86_64'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'
cache='none'/>
      <source file='/home/tstrike39/Virtuals/localhost-sda'/>
      <target dev='vda' bus='virtio'/>
    </disk>
    <interface type='network'>
      <source network='default'/>
      <model type='virtio'/>
      <mac address='f0:de:f1:08:9c:c4'/>
    </interface>
    <video>
      <model type='cirrus' vram='9216' heads='1'/>
    </video>
    <graphics type='vnc' autoport='yes'
port='-1'/>
    <input type='tablet' bus='usb'/>
    <input type='mouse' bus='ps2'/>
    <console type='pty'/>
  </devices>
</domain>


Any help would be appreciated!

Richard W.M. Jones

2017-Feb-01 15:32 UTC

head link

Re: [libvirt-users] virt-p2v - Windows 10 guest hangs at boot after successful P2V

On Mon, Jan 09, 2017 at 09:17:47AM -0600, JT Edwards
wrote:> Hi all,
> 
> I successfully virt-p2v'ed a Windows 10 laptop to my Centos 7.3
instance
> running KVM. However, on boot, the guest hangs. Is there a registry fix
> that is needed after the P2V is done? Here is what is in the guest's
> logfile:
We don't normally check this mailing list for virt-p2v problems which
is why I didn't see this message before.

If you are still having issues, then you'll need to find the full
debug logs, post them on a web server somewhere else, and send a
message pointing to them to libguestfs@redhat.com.  (See also
http://libguestfs.org/virt-p2v.1.html#how-virt-p2v-works )

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html

JT Edwards

2017-Feb-01 15:34 UTC

head link

Re: [libvirt-users] virt-p2v - Windows 10 guest hangs at boot after successful P2V

Rich,

I got this resolved by making sure that the P2V Windows 10 image's CPU
signature matches that as the host system.

Thank you in advance,
JT



On Wed, Feb 1, 2017 at 9:32 AM, Richard W.M. Jones <rjones@redhat.com>
wrote:
> On Mon, Jan 09, 2017 at 09:17:47AM -0600, JT Edwards wrote:
> > Hi all,
> >
> > I successfully virt-p2v'ed a Windows 10 laptop to my Centos 7.3
instance
> > running KVM. However, on boot, the guest hangs. Is there a registry
fix
> > that is needed after the P2V is done? Here is what is in the
guest's
> > logfile:
>
> We don't normally check this mailing list for virt-p2v problems which
> is why I didn't see this message before.
>
> If you are still having issues, then you'll need to find the full
> debug logs, post them on a web server somewhere else, and send a
> message pointing to them to libguestfs@redhat.com.  (See also
> http://libguestfs.org/virt-p2v.1.html#how-virt-p2v-works )
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~
> rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-builder quickly builds VMs from scratch
> http://libguestfs.org/virt-builder.1.html
>

Possibly Parallel Threads

Search for more maybe matching threads

libvirt users - Jan 2017 - virt-p2v - Windows 10 guest hangs at boot after successful P2V

[libvirt-users] virt-p2v - Windows 10 guest hangs at boot after successful P2V

Re: [libvirt-users] virt-p2v - Windows 10 guest hangs at boot after successful P2V

Re: [libvirt-users] virt-p2v - Windows 10 guest hangs at boot after successful P2V

Possibly Parallel Threads