Re: [qubes-users] win7 HVM will not start with RAM > 3GB with "Failed to load VM config"

Mailing Lists qubes-users
1

You can obtain xen messages with 'xl dmesg'.

2

My logfiles also appear to not be touched (after a few failed launches of
my win7 HVM). I see the same behaviour as Abel - enabled trace debug
output, restarted service, still no dice. Further, output of xl dmesg is
identical before and after a failed or successful launch of my win7 HVM.
Not a single new message there...

To verify I've enabled the right type of trace/log, here's what xl dmesg
tells me:
(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)

Is this right?

Alex

3

I've forgot about this... I've enabled some more verbose loglevels: add to the
xen command line (line with "module xen.gz" in grub): loglvl=all guest_loglvl=all

4

Thanks - editing the line to

multiboot /xen.gz placeholder console=none loglvl=all guest_loglvl=all

gives me the following in xl dmesg:

(XEN) Xen trace buffers: disabled
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All

So now I'm sitting back and waiting for the bug to appear :slight_smile:

Btw, how can I make the loglvl=all parameters stick across reboots? A bit
lost with grub/grub2 files under /boot. Might be a sensible default for the
next Qubes release?

Alex