| Summary: | Windows 10 guest cannot wake up from S3 using rtc wake | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | iaopenbug |
| Component: | qemu | Assignee: | Fedora Virtualization Maintainers <virt-maint> |
| Status: | CLOSED DEFERRED | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | amit.shah, berrange, cfergeau, crobinso, dwmw2, iaopenbug, itamar, pbonzini, rjones, virt-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-15 20:20:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
iaopenbug
2016-03-15 06:30:07 UTC
Are you using fedora? I don't see any indication you are... Did this work in previous qemu versions? (In reply to Cole Robinson from comment #1) > Are you using fedora? I don't see any indication you are... > > Did this work in previous qemu versions? # lsb_release -a LSB Version: :core-4.1-amd64:core-4.1-noarch Distributor ID: Fedora Description: Fedora release 23 (Twenty Three) Release: 23 Codename: TwentyThree Did not test with previous QEMU versions. (In reply to iaopenbug from comment #2) > (In reply to Cole Robinson from comment #1) > > Are you using fedora? I don't see any indication you are... > > > > Did this work in previous qemu versions? > # lsb_release -a > LSB Version: :core-4.1-amd64:core-4.1-noarch > Distributor ID: Fedora > Description: Fedora release 23 (Twenty Three) > Release: 23 > Codename: TwentyThree > > Did not test with previous QEMU versions. What QEMU package are you using? >What QEMU package are you using?
tested with qemu 2.5 and almost latest qemu( commit a648c137383d84bc4f95696e5293978d9541a26e) + latest seabios( dce99e01b6bfc51175bdf32612fd4f2738e5c3c8)
Since you are using upstream qemu I think it's just better to stick with the upstream launchpad bug you filed, and ping on the mailing list after a while if you don't get a response |