similar to: managedsave/start fails because of Q35 UHCI Host Controller

Hi, I'm facing a strange behaviour of windows 2008 guests. After a virsh managedsave and start, the windows guest open a "unexpected shutdown" window. The window looks like this one (randomly taken from the web): http://toastytech.com/guis/srv2k3login2.jpg This happens in all virtualized windows in a hypervisor. Has anyone else experienced such issue? Thanks, -- Nicolas

If I manually delete the Q35 USB Controllers, I can use managedsave/start, but I start getting tty errors that don't happen before the managedsave/start. Using libvirt 1.2.18 (-1 Arch) and QEMU git-master (2.4.0.r40384.2d69736). Installed using Q35 chipset. I'm running QEMU git, which allows SCSI controller migration, so I can attempt doing this. I started my guest, and waited for 15

Hi All, We are trying to do "virsh managedsave" on a VM but it is failing with the following error. libvirtError: operation failed: domain save job: unexpectedly failed^M libvirt and qemu versions are as follows: libvirt-1.1.1-29.el7.x86_64 qemu-kvm-1.5.3-60.el7_0.11.x86_64 VM is provided with a small pxe image such that it pxe boots from a remote server. VM doesn't have any

On 05.02.2015 01:54, Paul Apostolescu wrote: > Hello, > > I am running into issues restoring VMs during reboot for some of my XP > VMs - the environment is QEMU 2.2.0, libvirt 1.2.12 on CentOS 6.5 with > KVM and libvirt-guests is set to suspend at shutdown. The weird part is > Windows 7 is restored properly from the managedsave however XP does not, > doing a start from virsh

Hello, I am running into issues restoring VMs during reboot for some of my XP VMs - the environment is QEMU 2.2.0, libvirt 1.2.12 on CentOS 6.5 with KVM and libvirt-guests is set to suspend at shutdown. The weird part is Windows 7 is restored properly from the managedsave however XP does not, doing a start from virsh shows this: virsh # start xp-check error: Failed to start domain xp-check

I have CentOS 5 installed on a Compaq Evo. I don't know the exact Evo model. When I first installed it, booted up fine. Now, when it boots, it freezes when it loads the UHCI kernel module. Here's what I see: input: AT Translated set 2 keyboard as /class/input/input0 Creating block device nodes. Loading uhci-hcd.ko module. USB Universal Host Controller Interface driver 3.0 And that's

I observed that following could cause machine lockup since at least 8-CURRENT. Now I'm on 9-STABLE No usb in kernel, attached mouse pointer. # kldload usb ums ehci # kldload uhci or # kldload uhci usb ums ehci uhci is required for working mouse. Can anyone confirm? Please test few different iterations, as it's probably not easily reproducible. Most times nothing happens, if

Hello, all Is there anyone interested in the performance of USB under QEMU? I found that when use OHCI to replace UHCI in qemu, it will improve the performance of USB storage device. I have tested it, the performance is almost equal of a real usb device. The way to do this is making little change in the file xen-3.1.0-src/tools/ioemu/hw/pc.c . --- pc.c.original 2007-08-14

I ran in to an almost impossible ability to run MeetMe on our poweredge. Our PE is a 4 proc with OHCI and we had no need to buy any PCI cards other than for running MeetMe. If you know how to recompile your kernel, recompile it and make RTC a module (its compiled in by default). Then you can use zaprtc as your timing source. Be sure to `rmmod rtc` before you `insmod zaprtc` because zaprtc is a

Hello, For a while I have been running NUT 2.0.0 just fine with my APC Back-UPS RS 800 using the usbhid interface. I decided to upgrade to 2.0.2, and all went well (upsc and upsd/upsmon seem happy to talk to the UPS), but I am getting a ton of these messages in my syslog: Jul 6 17:12:45 yggdrasil kernel: usb-uhci.c: interrupt, status 3, frame# 780 Jul 6 17:12:50 yggdrasil kernel:

Purchased DQ35JO on Vt-d/PCI passthrough wiki''s recommendations. Built latest xen-unstable and am getting the following via ''xm dmesg'': (XEN) [VT-D]dmar.c:374: RMRR error: base_addr d0000000 end_address cfffffff (XEN) Failed to parse ACPI DMAR. Disabling VT-d. My grub.conf looks like this: kernel /xen.gz vga=mode-0x0317 vtd=1 iommu=1

On 03/11/2015 08:20 PM, Nerijus Baliunas wrote: > Laine Stump <laine@...> writes: > >> And it is also true that any machine with a SATA controller can't be >> migrated because of problems with the driver. I just talked to the >> person responsible for fixing these bugs in qemu, and he said that the >> patches will go upstream "soon", and that he

On 03/22/2015 08:23 PM, Nerijus Baliunas wrote: > On Thu, 12 Mar 2015 14:56:08 -0400 Laine Stump <laine@laine.org> wrote: > >> Here is the info straight from the author (I've also Cc'ed him to this >> mail): >> >> =============== >> The AHCI migration series is here: >> >>

On 03/23/2015 08:05 PM, Nerijus Baliunas wrote: > On Mon, 23 Mar 2015 10:36:33 -0400 John Snow <jsnow@redhat.com> wrote: > >>> Are the needed patches in 2.3.0-rc0? >>> Is it possible to backport AHCI migration to RHEL 7.1 qemu or will it be too much work? >> >> The patches that improve the stability of AHCI migration are in 2.3-rc0. >> We still have

On 08/10/2015 12:41 AM, Michael Darling wrote: > What's the status of the SATA controller migration bug? Are the patches for it expected to be in 2.4? > Looks like they didn't make it into 2.3. That's a question better suited for the qemu developers than us. I'm Cc'ing John Snow, who authored the qemu patches. John? > Since you last wrote, if the SATA controller

Hi all, What are the differences between pc and q35?? By default, virt-manager+libvirt setups kvm guest machine as a pc-i440fx-rhel7.1.0. [hicheck at ckvm015 ~]$ /usr/libexec/qemu-kvm -machine ? Supported machines are: pc RHEL 7.1.0 PC (i440FX + PIIX, 1996) (alias of pc-i440fx-rhel7.1.0) pc-i440fx-rhel7.1.0 RHEL 7.1.0 PC (i440FX + PIIX, 1996) (default) pc-i440fx-rhel7.0.0

On 02/23/2015 02:26 PM, Thomas Stein wrote: > Hello. > > I'm not able to disable the sata controller on a machine='pc-q35-2.1' type VM. > Whenever i delete: > > <controller type='sata' index='0'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' > function='0x2'/> >

Laine Stump <laine@...> writes: > And it is also true that any machine with a SATA controller can't be > migrated because of problems with the driver. I just talked to the > person responsible for fixing these bugs in qemu, and he said that the > patches will go upstream "soon", and that he hopes they will be in qemu > 2.3. Are these patches available yet?

Hi, i was trying to install CentOS 5.1 on new machine based on Intel Q35 desktop board, witch 2 SATA disks (configured as RAID 1) , 8GB RAM and Intel Core2 QUADCORE. The first problem was with install - it hangs before installer startup at ACPI messages. So i installed it with ACPI=off switch. The first problem is : Dec 7 09:54:01 vmhost1 kernel: BIOS bug, no explicit IRQ entries, using default

On Mon, 23 Mar 2015 10:36:33 -0400 John Snow <jsnow@redhat.com> wrote: > > Are the needed patches in 2.3.0-rc0? > > Is it possible to backport AHCI migration to RHEL 7.1 qemu or will it be too much work? > > The patches that improve the stability of AHCI migration are in 2.3-rc0. > We still have not /enabled/ migration upstream, but editing to code to > allow it