• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Qemu - socket closed unexpectedly when trying to create VM

Red Squirrel

[H]F Junkie
Joined
Nov 29, 2009
Messages
9,217
Been testing KVM/Qemu (I always get confused, not really sure what to call it) as a possible solution to replace Virtualbox as I want something that is easier to manage and is more "server friendly" such as having the VMs run in background and still being able to get the console with the GUI app etc...

Been having trouble getting a remote virt-manager to connect to the server as it always errors out so what I've been doing is just using SSH and use X forwarding to run it locally, works fine that way.

I created one test VM, worked fine, but I can't create any more VMs now, I get to the end of the wizard then get this error after it's done creating the disk:

Unable to complete install '<class 'libvirt.libvirtError'> socket closed unexpectedly
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/create.py", line 723, in do_install
dom = guest.start_install(False, meter = meter)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 732, in start_install
return self._do_install(consolecb, meter, removeOld, wait)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 767, in _do_install
self.domain = self.conn.createLinux(install_xml, 0)
File "/usr/lib64/python2.5/site-packages/libvirt.py", line 915, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: socket closed unexpectedly
'


This is the log file for the VM:

Code:
[root@borg windows2008]# cat /var/log/libvirt/qemu/test-win2008.log
LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/bin/qemu-system-x86_64 -S -M pc -no-kqemu -m 2048 -smp 1 -name test-win2008 -monitor pty -localtime -no-reboot -boot d -drive file=/data/vms/dev/qemu-test/windows2008/win2008,if=ide,index=0 -drive file=/data/public/iso/Windows Server 2008 & R2 Collections/en_windows_server_2008_r2_standard_enterprise_datacenter_web_vl_build_x64_dvd_x15-59754.iso,if=ide,media=cdrom,index=2 -net nic,macaddr=54:52:00:43:51:e9,vlan=0 -net tap,fd=19,script=,vlan=0,ifname=vnet1 -serial pty -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:2 -k en-us -soundhw es1370
QEMU PC emulator version 0.9.1, Copyright (c) 2003-2008 Fabrice Bellard
usage: qemu [options] [disk_image]

'disk_image' is a raw hard image image for IDE hard disk 0

Standard options:
-M machine      select emulated machine (-M ? for list)
-cpu cpu        select CPU (-cpu ? for list)
-fda/-fdb file  use 'file' as floppy disk 0/1 image
-hda/-hdb file  use 'file' as IDE hard disk 0/1 image
-hdc/-hdd file  use 'file' as IDE hard disk 2/3 image
-cdrom file     use 'file' as IDE cdrom image (cdrom is ide1 master)
-drive [file=file][,if=type][,bus=n][,unit=m][,media=d][index=i]
       [,cyls=c,heads=h,secs=s[,trans=t]][snapshot=on|off]       [,cache=on|off]
                use 'file' as a drive image
-mtdblock file  use 'file' as on-board Flash memory image
-sd file        use 'file' as SecureDigital card image
-pflash file    use 'file' as a parallel flash image
-boot [a|c|d|n] boot on floppy (a), hard disk (c), CD-ROM (d), or network (n)
-snapshot       write to temporary files instead of disk image files
-no-frame       open SDL window without a frame and window decorations
-alt-grab       use Ctrl-Alt-Shift to grab mouse (instead of Ctrl-Alt)
-no-quit        disable SDL window close capability
-no-fd-bootchk  disable boot signature checking for floppy disks
-m megs         set virtual RAM size to megs MB [default=128]
-smp n          set the number of CPUs to 'n' [default=1]
-nographic      disable graphical output and redirect serial I/Os to console
-portrait       rotate graphical output 90 deg left (only PXA LCD)
-k language     use keyboard layout (for example "fr" for French)
-audio-help     print list of audio drivers and their options
-soundhw c1,... enable audio support
                and only specified sound cards (comma separated list)
                use -soundhw ? to get the list of supported cards
                use -soundhw all to enable all of them
-localtime      set the real time clock to local time [default=utc]
-full-screen    start in full screen
-win2k-hack     use it when installing Windows 2000 to avoid a disk full bug
-usb            enable the USB driver (will be the default soon)
-usbdevice name add the host or guest USB device 'name'
-name string    set the name of the guest

Network options:
-net nic[,vlan=n][,macaddr=addr][,model=type]
                create a new Network Interface Card and connect it to VLAN 'n'
-net user[,vlan=n][,hostname=host]
                connect the user mode network stack to VLAN 'n' and send
                hostname 'host' to DHCP clients
-net tap[,vlan=n][,fd=h][,ifname=name][,script=file][,downscript=dfile]
                connect the host TAP network interface to VLAN 'n' and use the
                network scripts 'file' (default=/etc/qemu-ifup)
                and 'dfile' (default=/etc/qemu-ifdown);
                use '[down]script=no' to disable script execution;
                use 'fd=h' to connect to an already opened TAP interface
-net socket[,vlan=n][,fd=h][,listen=[host]:port][,connect=host:port]
                connect the vlan 'n' to another VLAN using a socket connection
-net socket[,vlan=n][,fd=h][,mcast=maddr:port]
                connect the vlan 'n' to multicast maddr and port
-net none       use it alone to have zero network devices; if no -net option
                is provided, the default is '-net nic -net user'

-tftp dir       allow tftp access to files in dir [-net user]
-bootp file     advertise file in BOOTP replies
-smb dir        allow SMB access to files in 'dir' [-net user]
-redir [tcp|udp]:host-port:[guest-host]:guest-port
                redirect TCP or UDP connections from host to guest [-net user]

Linux boot specific:
-kernel bzImage use 'bzImage' as kernel image
-append cmdline use 'cmdline' as kernel command line
-initrd file    use 'file' as initial ram disk

Debug/Expert options:
-monitor dev    redirect the monitor to char device 'dev'
-serial dev     redirect the serial port to char device 'dev'
-parallel dev   redirect the parallel port to char device 'dev'
-pidfile file   Write PID to 'file'
-S              freeze CPU at startup (use 'c' to start execution)
-s              wait gdb connection to port
-p port         set gdb connection port [default=1234]
-d item1,...    output log to /tmp/qemu.log (use -d ? for a list of log items)
-hdachs c,h,s[,t]  force hard disk 0 physical geometry and the optional BIOS
                translation (t=none or lba) (usually qemu can guess them)
-L path         set the directory for the BIOS, VGA BIOS and keymaps
-kernel-kqemu   enable KQEMU full virtualization (default is user mode only)
-no-kqemu       disable KQEMU kernel module usage
-std-vga        simulate a standard VGA card with VESA Bochs Extensions
                (default is CL-GD5446 PCI VGA)
-no-acpi        disable ACPI
-no-reboot      exit instead of rebooting
-loadvm file    start right away with a saved state (loadvm in monitor)
-vnc display    start a VNC server on display
-daemonize      daemonize QEMU after initializing
-option-rom rom load a file, rom, into the option ROM space
-clock          force the use of the given methods for timer alarm.
                To see what timers are available use -clock help

During emulation, the following keys are useful:
ctrl-alt-f      toggle full screen
ctrl-alt-n      switch to virtual console 'n'
ctrl-alt        toggle mouse and keyboard grab

When using -nographic, press 'ctrl-a h' to get some help.
[root@borg windows2008]#

Seems like an odd log file, looks more like a --help file for a command. Almost seems like virt-manager is not generating the proper command or something.


On a side note, anyone know of a good tutorial on networking for this solution? I want to do virtual networks, vlans and stuff.
 
Odd, after several tries (starting wizard from scratch) it decided to work. So far I'm not really impressed though. win2k8 just blue screens right away at the boot disc. Win98 does not even do anything, just black screen.... so far only Linux installs seem to work. I'm working over a slow VPN link though, so I will have to retry once I'm home. Maybe it's a latency problem with X.
 
Odd, after several tries (starting wizard from scratch) it decided to work. So far I'm not really impressed though. win2k8 just blue screens right away at the boot disc. Win98 does not even do anything, just black screen.... so far only Linux installs seem to work. I'm working over a slow VPN link though, so I will have to retry once I'm home. Maybe it's a latency problem with X.

well, I previously had XP and possibly 7 (I forget) running under KVM on my linux box fine but the main problem is that it was a royal pain to deal with given starting it up involved a ssh shell to the box given I couldn't find any decent web UIs.
 
Got win98 setup to boot, was just a latency issue I guess, was not displaying fast enough so by the time I saw the screen it had already booted off the empty hard disk. Was just a test anyway, might install it for shits and giggles though but if it does not work it wont be end of the world.

The Win2k8 VM just randomly crapped out though, wont even boot at all now, I just get this error:

Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 532, in run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 380, in startup
self.vm.create()
File "/usr/lib64/python2.5/site-packages/libvirt.py", line 285, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error QEMU quit during console startup

Definitely a bad start, I also don't like the fact that I have to run the management software as root.

Once I have enough money to build myself a new server think I will look into a hypervisor solution like Proxmox instead and once I have that going then I can migrate stuff over. Worse case I might go VMware, but I hate how they keep changing their product line all the time, and I just don't want to depend on the free version always being available. It also has no Linux management utility so I'd need to use a Windows VM just to manage VMs. Rather stick with open source.
 
Once I have enough money to build myself a new server think I will look into a hypervisor solution like Proxmox instead and once I have that going then I can migrate stuff over. Worse case I might go VMware, but I hate how they keep changing their product line all the time, and I just don't want to depend on the free version always being available. It also has no Linux management utility so I'd need to use a Windows VM just to manage VMs. Rather stick with open source.

Keep in mind that Proxmox is just a nice web ui wrapper around KVM so if it doesn't work now with KVM it's not likely to work with Proxmox.

still odd that server 2k8 won't run given that the the compatibility list says it should.
 
I wonder if it may have to do with the fact I have Virtualbox on the same machine (some production vms on there so I can turn it down). Could it be? I've been toying with the idea of instead of buying a new server I'll just upgrade the OS/environment on this one, but it's kind of nerve wracking to do it that way, so may have to just stick to my original plan and just keep saving up. Hopefully a clean install of Proxmox on newer hardware will work better.

Windows 98 also blue screened upon the first boot.
 
Back
Top