I found a solution to my problem.
The culprit was my overclock. I don't know why I didn't reset my BIOS
settings in start of troubleshooting, but today I reset it and everything
works...
Interesting note though, naturally I tried to pinpoint what part of
overclock is messing up the start of
!!!
I have some, hopefully, great news.
I was messing around searching some help online and I got an idea to try
installing Win7 StandaloneVM following the
https://www.qubes-os.org/doc/windows-tools/ guide.
I kid you not, it worked on first try! HVM mode, even got the Windows Tools
working.
When I compared your logs to what I have, it came to my mind that some
years ago I had similar problems - because of processor microcode which was
too old. I had to update that to get hvms working.
I couldn't find which microcode version you have, it is somehow not shown
in the cpu log you
The log file you provided as xl_log.txt is actually the Xen hypervisor log.
Yes, there are some warnings - which show that there are some bugs in the
BIOS, but overall, the virtualization and all the required features needed
for IOMMU are there and enabled. So this is strange.
Maybe - and I
Hi.
I tried everything you said (in both sys-usb and sys-net). I even tried to
not assign any pass through devices and I still get the same output in
/var/log/xen/console/guest-sys-net.log.
But not assigning any device, or giving all devices strictreset as you
mention gives me this output in
The libxl-driver.log shows symptoms, when indeed the USB device cannot be
reseted (FLR functionality missing).
As I wrote, you can disable strictreset for HVM passed through devices:
- go for the "Qube Settings" of one of the HVMs (sys-usb), where the USB
devices (PCI: 00:10.0, 00:10.1, 00:12.0,
Dana utorak, 3. prosinca 2019. u 18:15:02 UTC, korisnik qubes123 napisao je:
>
> Maybe if you post the content of /var/log/libvirt/libxl/libxl-driver.log file
> also, we can see what the problem is. Otherwise the logs seem OK for me.
> If you installed a std R4.0.1 and let the setup configure the
Hi.
I sure can! I uploaded the libxl-driver.log as well.
As of your second part of the message, I didn't mention that after doing
all the steps suggested in linked "Bug in libxenlight" topic I encountered
that all assigned HVMs (bullet 8) wouldn't load (such as sys-usb and
sys-net) and dom0
...correction: R4.0.1 is not old (this is the current released version),
but the iso build is from January...
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Maybe if you post the content of /var/log/libvirt/libxl/libxl-driver.log file
also, we can see what the problem is. Otherwise the logs seem OK for me.
If you installed a std R4.0.1 and let the setup configure the base qubes,
then sys-net should already be a HVM with all your Net cards passed
10 matches
Mail list logo
