search for: cpu64

...dev=hostnet0,id=net0,mac=52:54:00:77:a5:a6,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -usb -vnc 127.0.0.1:2,password -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 char device redirected to /dev/pts/6 Using CPU model "cpu64-rhel6" block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argument (22) block I/O error in device 'drive-ide0-0-0': Invalid argu...

...hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='custom' match='exact'> <model fallback='allow'>cpu64-rhel6</model> <topology sockets='2' cores='2' threads='2'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <t...

Hi,all i get a problem as below when i create a vm: virsh create deployment.0 error: Failed to create domain from deployment.0 error: monitor socket did not show up.: No such file or directory but the situation is very few. So,can some tell me about this? I just want to know why has this kind of situation. Thanks. Best Regards! ??? tel: 13718913184 mail: zhanggp at neusoft.com ????????

...alAppliance_v6.1.qcow2: 100% [=============================================================================================================================================================]D 0h00m32s > find: failed to restore initial working directory: Permission denied > Using CPU model "cpu64-rhel6" > unknown filesystem label SWAP-sda5 > Error running rpm -qa: command_lines: command_lines: rpm: No such file or directory at /usr/share/perl5/vendor_perl/Sys/VirtV2V/GuestfsHandle.pm line 188. > at /usr/lib64/perl5/vendor_perl/Sys/Guestfs/Lib.pm line 1022 > virt-v2v: Unable...

> -------- Original message -------- > Subject: Re: [libvirt-users] Can I configure cores instead of CPU's > From: Todd And Margo Chester <toddandmargo at gmail.com> > To: "libvirt-users at redhat.com" <libvirt-users at redhat.com> > CC: > > > Hi All, > > Scientific Linux 6.1 x64 > qemu-kvm-0.12.1.2-2.160.el6_1.2.x86_64 > > My XP-Pro

...CentOS 6.0/64bit onto an Intel server to virtualize our Linux fileserver and four WinXP boxes with rdp each. Since recent times I didn't do any upgrades of the server's OS. Now I have CentOS 6.2. After an upgrade I noticed that all virtual cpu name changed to QEMU Virtual CPU version (cpu64-rhel6) The new features were 1) The ability to specify cpu type and even exact capabilities 2) The ability to set the topology. It's good because before this ability appears WinXP guests won't use more than two cores. I got problem with both of these features. First, I can't manual...

...i get a problem as below when i create a vm: > virsh create deployment.0 > error: Failed to create domain from deployment.0 > error: monitor socket did not show up.: No such file or directory > > ok,here is my /var/log/libvirt/qemu/guest.log error: > > Using CPU model "cpu64-rhel6" > kvm: -device lsi,id=scsi0,bus=pci.0,addr=0x4: Parameter 'driver' expects a > driver name > Try with argument '?' for a list. > I had to admit that my template is error ,this is my error part: > <disk type='file' device='disk' > >...

...s 6.0 x86_64 time set with ntpd Intel(R) Xeon(R) CPU X5650 /proc/cpuinfo shows the "constant_tsc" bit. ~ guest OS ~ Centos 6.0 x86_64 /proc/cpuinfo : processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : QEMU Virtual CPU version (cpu64-rhel6) stepping : 3 cpu MHz : 2666.998 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 4 wp : yes flags : fpu de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 syscall nx lm up rep_good unf...

Hi, I?m using libvirt version 0.9.12 under Debian Squeeze with and AMD Opteron 4280. Executing the virsh capabilities command only show me the following flags: <cpu> <arch>x86_64</arch> <model>Opteron_G4</model> <vendor>AMD</vendor> <topology sockets='1' cores='8' threads='2'/> <feature name='nodeid_msr'/>

...libguestfs: trace: add_drive_opts = 0 libguestfs: trace: add_drive_ro_with_if "/var/lib/virt-v2v/transfer.iso" "ide" libguestfs: trace: add_drive_ro_with_if = 0 libguestfs: trace: set_network true libguestfs: trace: set_network = 0 libguestfs: trace: launch Using CPU model "cpu64-rhel6" libguestfs: trace: launch = 0 libguestfs: trace: set_autosync true libguestfs: trace: set_autosync = 0 libguestfs: trace: list_devices libguestfs: trace: list_devices = ["/dev/sda", "/dev/sdb"] libguestfs: trace: mount_ro "/dev/sda" "/" libguestfs...

...ed. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.1-STABLE #0 r248465: Mon Mar 18 11:19:23 EDT 2013 pmather at freebsd9.virtual.lib.vt.edu:/usr/obj/usr/src/sys/KVMTEST amd64 FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221 CPU: QEMU Virtual CPU version (cpu64-rhel6) (2100.15-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x6d3 Family = 0x6 Model = 0xd Stepping = 3 Features=0x783f3ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2> Features2=0x80002001<SSE3,CX16,HV> AMD Features=0x22...

...35k freed [ 0.029555] ftrace: converting mcount calls to 0f 1f 44 00 00 [ 0.030003] ftrace: allocating 21432 entries in 85 pages [ 0.031043] Setting APIC routing to flat [ 0.034365] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 0.034959] CPU0: Intel QEMU Virtual CPU version (cpu64-rhel6) stepping 03 [ 0.137032] Performance Events: Broken PMU hardware detected, using software events only. [ 0.137917] NMI watchdog disabled (cpu0): hardware events not enabled [ 0.138005] Brought up 1 CPUs [ 0.138301] Total of 1 processors activated (4800.16 BogoMIPS). [ 0.139419]...

Unfortunately, placing the link into the /boot does not work. libguestfs-test-tool failes with the same message: ************************************************************ * IMPORTANT NOTICE * * When reporting bugs, include the COMPLETE, UNEDITED * output below in your bug report. *